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
Why: The target branch advanced Core, Frontend, UI and Backend pointers during the approved U3 revision.
Evidence: Core go test ./...; Backend go test ./...; UI 165 tests and typecheck; Frontend 224 tests and build passed on the resolved component trees.
Impact: Preserve both the current main settings/account/duties work and the U3 candidate at merged component SHAs.
Refs: U3 quality revision r0.2, task-sync receipt fast-slow-u2-u3-r02-sync-20261013.json
Why: The approved revision spans Backend, UI and Documents and needs one reviewable Dev composition.
Evidence: Backend go test ./...; UI 158 tests and typecheck; Frontend 84 affected tests; exact component SHAs recorded in the task card.
Impact: The task card keeps real-model QA NOT_RUN and the earlier failed sample separate from this candidate.
Refs: U3 quality revision r0.2
Why: The approved model sample violated its rejected-quote stop rule and the first guard missed JSON errors across runs.
Evidence: Original 14231-token deviation remains recorded; independent replay passed the read-only event-join guard and fail-closed cases without model calls.
Impact: Advance test-only Backend and evidence pins while keeping U3 quality and merge gates closed.
Refs: Agent-System-Dev#512; Agent-System-Backend#193; Agent-System-Documents#95
Why: The approved v7 sample had two committed checkpoints but failed semantic and final-result acceptance.
Evidence: Import the original failing SELF receipt, bind independently replayed usage/source findings, and pin the corrected read-only evaluation.
Impact: Keep model quality and merge gates closed while preserving six draft PRs for review.
Refs: Agent-System-Dev#512; Agent-System-Backend#193; Agent-System-Documents#95
Why: Bind the newly approved one-shot model evaluation to an exact reviewed candidate.
Evidence: Follow-up harness tests passed after an expected red failure; full Backend suite passed.
Impact: Record the new bounded authorization and test-only Backend revision; U3 quality remains pending.
Refs: Agent-System-Dev#512; Agent-System-Backend#193
Why: The project entry and task card must reflect current code evidence and the failed model gate.
Evidence: Native SELF receipts and independent review report cover the exact current component combination.
Impact: Save the report and status without merging or deploying the candidate.
Refs: U2/U3 plan r0.1
Why: Preserve authoritative main and both backend histories before draft review.
Evidence: Exact incoming cfb8308 merged without source conflicts; current combination and PG checks follow.
Impact: Keep session/account fixes and U2/U3 task authority in the same candidate; model gate remains failed.
Refs: Dev main aa6364f and U2/U3 task card
Why: Preserve the latest combination evidence and independent failure assessment before draft review.
Evidence: Native SELF receipts capture complete local test/build and current HTTP browser checks; model quality remains FAIL.
Impact: Pin the report and code review without merging or deploying the failed candidate.
Refs: feature-fast-slow-u2-u3-plan
Why: Preserve authoritative settings and session changes with the source-bound work candidate.
Evidence: Merged Backend, Core and live fixture guards passed local and independent checks; extra A01 remained a real FAIL.
Impact: Save a draft-reviewable composition without claiming CI, merge, deployment or model-quality approval.
Refs: U2/U3 task card and validation report
Why: The remaining open items (API-key SSE closure, cross-instance
redeem backoff, U7 atomic bootstrap/create, CLI credential delivery)
landed in Backend #192; Dev pins it and closes the contract leftovers.
Evidence: Backend #192 CI success at head bc1e0a3 (GATE); composite CI
on this PR re-runs the suite incl. test-pg (GATE).
Impact: backend pin cfb8308; contract leftover section now records all
items closed; task card H1-H6 requirement table.
Refs: Backend #192; docs/svc-deploy/2026-10-13-login-recovery-contract.md.
Why: Continue the existing delivery after explicit approval for one extra sample.
Evidence: Startup precheck READY and live output/run-limit fixture checks are recorded by evidence.
Impact: Fixed evaluation candidate, max two paid runs and no automatic retry; preserve all original failed samples.
Refs: User approval 2026-10-13
Why: check-pins failed on the follow-up CI: the newly pinned backend
(741da4a) carries deps/agent-system-core at 0f94e4b while Dev's
modules/core stayed at ba289e7 - the three-layer pin rule requires the
top-level core pin to match.
Evidence: 0f94e4b verified as an ancestor of Core origin/main; this
PR's composite CI re-runs check-pins (GATE).
Impact: modules/core gitlink to 0f94e4b; no source changes.
Refs: check-pins failure on job 4204.
Why: The follow-up CI exposed that backend #188 broke the Dev
multi-instance suite: serve --mock seeded runtime.mock at the user
scope, which system-managed settings now reject, so instances never
became healthy. Backend #190 seeds the startup flag into the system
scope; this PR repins and drops the now-invalid alice user-scope write.
Evidence: Backend #190 CI success at head 0af1ebc (GATE); this PR's
composite CI re-runs make test-multi-instance (GATE for the fix).
Impact: backend pin 741da4a; multi-instance test comments updated to
the system-managed regime.
Refs: Backend #188, #190.
Why: Preserve a clean reviewable candidate without treating code checks as a passed model gate.
Evidence: Native receipts retain final combination, PostgreSQL and actual HTTP/browser verification; independent code review is archived in Documents.
Impact: Save documentation and evidence, retain registered worktree and unmerged branches pending the requested extra test authorization.
Refs: U2/U3 plan r0.1 and validation report
Why: The completion audit flagged four gaps over the merged login
recovery implementation: real-browser acceptance, the login-key e2e
spec, SSE stream invalidation, and the Documents write-back.
Evidence: Browser acceptance receipts be7ae9a2/b3a9e691 (SELF, bound to
Dev HEAD 268ef29); Backend #189 CI success at head 8b73afe (GATE);
Documents #94 merged; this PR's composite CI is the GATE for frontend
pin 44b9646.
Impact: Pins backend=349a47d (SSE close) and frontend=44b9646 (e2e
spec); contract doc leftovers updated; task card carries the follow-up
record for closure.
Refs: docs/svc-deploy/2026-10-13-login-recovery-contract.md; Documents
proposal r3; Backend #189; Frontend #77.
Why: Keep the implementation, honest failed model evidence and approved planning progress reviewable as one candidate.
Evidence: Native SELF suite, PG and meaningful red-to-green receipts; independent reviewer reports and all original model artifacts are retained.
Impact: Pin source-record and terminal-state fixes; preserve U3 acceptance and extra-sample authorization as pending, with no deployment.
Refs: Approved U2/U3 plan and validation report
Why: Keep the accepted login recovery release and U2/U3 fixes in one current composition.
Evidence: Exact incoming Backend 467718a and Frontend 9fc7da2 were fetched and merged without source conflicts; task-sync receipts retain the gitlink conflict.
Impact: Preserve both component histories and refresh the authoritative base before final combination checks.
Refs: origin/main 268ef299; feature-fast-slow-u2-u3-plan
Why: Resolve the observed conclusion and qualification defects without rewriting failed evidence.
Evidence: Native SELF model failure and red-to-green conclusion receipts are retained in the task card.
Impact: Candidate recipe changes; an A01 rerun remains outside the original six-sample authorization.
Refs: Approved U2/U3 plan r0.1
Why: Complete the approved U2/U3 fix pass and prevent shared host fixture collisions.
Evidence: Native SELF receipts record complete Backend suite, Frontend 221 tests, meaningful startup regression failures and the bounded baseline model batch.
Impact: Pin the corrected Backend and Frontend and allocate owned recovery fixture ports; no existing service deployment.
Refs: modules/documents/docs/proposals/2026-10-13-fast-slow-u2-u3-plan.md
Why: The Dev composite must carry the exact backend (467718a) and
frontend (9fc7da2) commits implementing the login recovery contract.
Evidence: component branches pushed to their origins; make test runs in
this task worktree validate the composite (receipts in task card).
Impact: gitlink bump only; no other Dev tree changes.
Refs: docs/svc-deploy/2026-10-13-login-recovery-contract.md
Why: A fixed regression port collided with another task-owned preview and blocked full verification.
Evidence: SELF full-suite failure identified port 18795; the isolated fixture replays without stopping the unrelated process.
Impact: Changes one test fixture and records actual HTTP/browser acceptance; no service operations or production settings changed.
Refs: fast-slow-u2-u3 final verification
Why: Acceptance must cover both immediate and deferred material flows.
Evidence: SELF fixed composition and isolated PostgreSQL receipts are retained; direct browser replay follows this producer fix.
Impact: Pins the observed flow repair and controlled test suite.
Refs: fast-slow-u2-u3 Task 7
Why: Fixed composition checks must include the source preview version guard.
Evidence: SELF red-green and frontend build receipts are recorded in the task card.
Impact: Updates component pins and evidence only.
Refs: fast-slow-u2-u3 Task 7
Why: Final task verification must include the latest authoritative composition.
Evidence: Task-sync receipt records incoming main and component conflicts; each component preserves both branches.
Impact: Retains artifact typed-nil recovery, RDM role rejection state, lifecycle governance, and task checkpoint changes.
Refs: fast-slow-u2-u3 task-sync
Why: Runtime checks require fixed component inputs and task-owned process identity.
Evidence: SELF live compilation receipt in the task card; model calls have not started.
Impact: Pins the current evaluator without touching existing instances.
Refs: fast-slow-u2-u3 Task 7
Why: Fast feedback and slow-channel discoveries need a faithful progressive user interface.
Evidence: SELF startup, contract, component, atomicity, source, and recovery receipts are recorded in the task card; final composition and live acceptance are pending.
Impact: Pins the current Core, Backend, Frontend and UI implementation without deploying existing services.
Refs: Approved fast-slow-u2-u3 r0.1; feature-fast-slow-u2-u3-plan task card
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=6193db1b548b964ab3133557ddbb9d83a3643d31.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Dev has to follow the commits that landed on Backend and Documents main, which share trees with the drilled objects.
Evidence: Backend dc736e339d01 tree 498f61947564 equals 46073d30. Documents 05c13a42b14d tree equals 5335499. GATE run 2794 on 6d8b746 succeeded before this pin.
Impact: gitlinks move to the merge commits. Second-instance writes stay closed.
Refs: #186#92#497
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: the restored drill passed artifact recovery, and the handbook, checklist, and collaboration plan have to say so without opening write traffic.
Evidence: backup-20261013-013354 on Dev a83588dd and backend 46073d30; K1-K7 true, RPO 65s, RTO 3s, five artifacts matched, cross-user access 404. SELF. Documents 5335499 is PR #92.
Impact: C5 is marked SELF-pass. Second-instance writes stay closed until REPLAY or CI and a second host exist.
Refs: docs/svc.md docs/release-multi-instance.md modules/documents
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: pick up Agent-System-Frontend dcd2699 (PR #75) so the Dev combined
CI validates the RDM roles panel rejected-state fix together with the
svc.sh rdm-admin recovery tooling in this task.
Evidence: gitlink 43d1933 -> dcd2699; merge-base --is-ancestor of the
reviewed head 0159f00 into frontend main OK (SELF).
Impact: gitlink bump only; combination validated by make test in this
worktree before PR.
Refs: task card feature-rdm-admin-lockout-recovery (R3/I2)
Why: an unset object store must keep artifact bytes available to the other process, which the store-level test does not execute.
Evidence: cross_artifact_roundtrip failed with EOF on backend c6fb130 and passed on 46073d30 (SELF, isolated u7drill-k4).
Impact: Dev now builds the fixed backend. Second-instance write traffic stays closed.
Refs: modules/backend tests/integration/multi-instance/multi_instance_test.go
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: retain a coherent combination before adding the atomic projection.
Evidence: Core suite and FE UI types; material tests and startup receipts recorded as SELF.
Impact: exact component gitlinks and task record.
Refs: U2/U3 Tasks1-2
Why: preserve current-source evidence and the reviewable next increment.
Evidence: READY receipt at5212fef, exact source and open-PR audit; plan r0.1 remains pending stage5 review.
Impact: task record, proposal link and exact Documents pin; no business code or runtime changes.
Refs: fast-slow r1.1, work-companion PR493
Why: Keep exact component and verification progress recoverable before final integration gates.
Evidence: Full SELF receipts remain in the task card; independent replay and platform gates are separately identified.
Impact: Documentation and Documents version only.
Refs: feature/work-companion-ui U5
Why: Bind the final candidate to actual review fixes and stronger interface acceptance.
Evidence: Full SELF red/green receipts and original independent report identities are retained; GATE and final review remain separate.
Impact: Pin UI0da2e3a and Frontend43d1933; no Backend/Core or running service change.
Refs: UI01-UI13, ce-code-review UI and Frontend findings, work-companion-ui
Why: Keep a recoverable record of the current validated combination and honest planning status.
Evidence: Full SELF make build and isolated two-case HTTP browser receipts are retained in the task card.
Impact: Documentation and Documents pin only; no running service change.
Refs: feature/work-companion-ui, U5
weichen
