Why: The first exact Dev r0.3 combination failed the Frontend unused-export ratchet despite passing runtime tests.
Evidence: The failed SELF receipt is imported into the task card; regenerated Frontend knip 51 <= 52, UI knip 61 <= 61 and component build/typechecks pass.
Impact: Pin Core, Backend, Frontend and UI corrections without changing the evidence wire shape; full Dev combination follows on this HEAD.
Refs: Dev PR #512; Core #31; Backend #193; Frontend #79; UI #51
Why: The approved r0.3 candidate now has Core evidence types, Backend normalization and matching generated frontend/UI contracts.
Evidence: Core and Backend full Go suites, selected live-tag fake-provider tests, UI 165 tests/typecheck, Frontend 265 tests/build and recursive worktree verification passed locally; final Dev combination follows on this exact commit.
Impact: Advance the five component gitlinks in the existing draft; no paid model call, merge or deployment.
Refs: Dev PR #512; Core #31; Backend #193; Frontend #79; UI #51; Documents #95
Why: The user approved zero-paid implementation after the written plan review, and the first main sync required component conflict resolution.
Evidence: Tool-imported first-sync failure and resolved-sync SELF receipts; Backend full Go and Frontend test/build results are recorded as local checks.
Impact: Pin Documents approval status and preserve the exact merge/sync trail; paid A01 remains unauthorized.
Refs: Dev PR #512; Documents PR #95
Why: The approved r0.3 plan must run against the current project member and IAM mainline.
Evidence: First task-sync conflict receipt was imported; Backend full Go tests and Frontend test/build passed after resolving component interactions; git diff --cached --check passed.
Impact: Combine current main with the existing U3 draft, preserving both planning entries and the Backend private project event proof transaction.
Refs: Dev PR #512; Backend PR #193; Frontend PR #79; Documents PR #95
Why: The r0.2 real-model sample failed semantic quality, and the user approved the r0.3 written design for detailed planning.
Evidence: Prior r0.2 A01 report and imported SELF receipts remain in the task card; plan self-review and git diff --cached --check passed.
Impact: Pin Documents f608ae5 and update planning state; implementation and paid model trials remain gated.
Refs: Documents PR #95; Dev PR #512
Why: The failed A01 needs a documented next design while the six PRs remain draft and unmerged.
Evidence: Independent semantic FAIL and the committed r0.3 spec with resolved links and explicit no-paid/no-implementation boundary.
Impact: Project entry and task card point to a pending design review; no new semantic behavior is enabled.
Refs: U3 r0.2 A01 assessment, r0.3 design
Why: An in-flight Documents edit correctly blocked build after the first post-sample test phase.
Evidence: Full exit-2 SELF receipt imported by make evidence; Documents report committed at 4971d0d with archive hashes.
Impact: The candidate now has a clean composition for a serial full rerun; model-quality FAIL is unchanged.
Refs: U3 r0.2 A01 assessment
Why: The authorized r0.2 trial had an unsupported stage inference, while replay exposed two separate diagnostic-control defects.
Evidence: Exact paid-run files and tool-imported receipts, independent REPLAY, and Backend RED-to-GREEN/full-suite checks.
Impact: U3 quality remains FAIL; the new Backend code has no paid-model acceptance and all PRs stay draft.
Refs: U3 quality implementation plan r0.2, Task 6
Why: The final base combination must reference actual reviewed main commits.
Evidence: Component PRs are merged, and each merged tree matches the independently tested candidate; whole review receipts remain unmodified.
Impact: Advance gitlinks and preserve acceptance evidence; new exact-head CI follows with no runtime changes.
Refs: Backend195 Frontend82 Documents97; feature/project-member-access
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=946cc13c9a10a2023a766b211e1148e625b62943.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Existing upload history must stay private after project adoption, and final object evidence must remain traceable.
Evidence: Original tool receipts and independent reports saved byte-for-byte; new fixed combination and CI remain pending.
Impact: Select Backend d26f3cf and proposal r1.1 with unchanged public downstream contracts; preserve workspaces and live data.
Refs: feature/project-member-access; Frontend PR82; Documents PR97
Why: A future authorized sample needs its own one-shot label rather than reusing exhausted approvals.
Evidence: Guarded label tests were RED then GREEN; full Backend Go suite passed at d89c72e.
Impact: No paid model request is triggered; the candidate SHA changes and requires fresh exact-head CI.
Refs: U3 quality implementation plan r0.2, Task 6 preparation
Why: The final zero-paid candidate needs the independent review disposition and fresh replay receipts in one composition.
Evidence: Browser receipt c4a2240e and PostgreSQL receipt 7291fe2b were imported by make evidence; Backend RED-to-GREEN fixes passed.
Impact: The task card and Documents report leave real-model validation NOT_RUN and merge gated.
Refs: U3 quality revision r0.2
Why: Review found three code-level failures in approval phrasing, checkpoint counting and evaluator identity.
Evidence: Each targeted regression was RED then GREEN; Backend full Go, race and live fixture checks passed at 9126dae.
Impact: The Dev composition now includes the corrected Backend while real-model QA remains NOT_RUN.
Refs: U3 quality revision r0.2, independent final review
Why: The reviewed candidate must carry its accurate browser, full-build and database evidence.
Evidence: make evidence imported the exact 8c1fc39 combination and isolated PostgreSQL SELF receipts.
Impact: The report remains explicit that final HEAD checks and real-model quality are pending.
Refs: U3 quality revision r0.2
Why: The task-owned HTTP/browser replay and its diagnosed first failure need to be attached to the reviewable composition.
Evidence: Browser receipt f7cbd331e82a60982716bbd79bb9d54712cac4db0395966fefe08f6f380715e7 imported by make evidence.
Impact: Documents and task card distinguish mechanism PASS from real-model NOT_RUN.
Refs: U3 quality revision r0.2
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: Final review and real composition exposed member upload rejection, private project cards and stale duty selection.
Evidence: Component correction receipts and fixed clean source SHAs; independent replays and final composition are in progress.
Impact: Select Backend d2f96e7 and Frontend 2ba275b with current UI, preserving private originals and verified project commands.
Refs: feature/project-member-access
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: include the current integration baseline before verification.
Evidence: fetched origin/main=86d975b822c2384e96edd75f9c3a2dca63593b3a.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Host-only project creation and domain membership must form one verified identity.
Evidence: Tool-imported SELF receipts and independent Backend and Frontend replay attestations; composed acceptance and final CI remain in progress.
Impact: Advance fixed component pins and record the authorized implementation and privacy boundaries without deployment or runtime changes.
Refs: .task/feature-project-member-access.md; system-project-membership proposal r1
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
weichen