Pin corrected checkpoint evaluation settings
Why: The browser mechanism exposed an ineffective integer output cap in the isolated evaluation server. Evidence: Backend live-tag numeric regression RED then GREEN; full Backend Go suite passed at 627b6e4. Impact: The task records the failed first browser run and pins the fixed Backend fixture for a fresh isolated replay. Refs: U3 quality revision r0.2
This commit is contained in:
+1
-1
Submodule modules/backend updated: d480030de7...627b6e4f31
Reference in New Issue
Block a user