Why: Chat, lightweight, fallback and vision settings need a seed path, and the backend now sends current-turn images only to models declared capable of seeing them.
Evidence: The backend change is cfde38d. The seed test covers fallback and vision settings. A local image conversation on each builtin profile returned the pictured content from the expected model, and removing the chat model from the capable list switched that turn to the vision model.
Impact: New runs can use the four builtin profiles and image input. Secrets stay in the ignored env file. The live 8788 process is unchanged.
Refs: .task/feature-four-model-vision.md
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev main advanced with a vendor skills task while this UI combination was being verified.
Evidence: Backend main ead5ade contains both Backend #199 and #200; the component merge affects recipes, not run-history handlers.
Impact: Preserve the new main task card and pin the Backend merge containing both changes; combination checks follow on this head.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: The fast and slow channel UI duplicated work cards and hid intermediate output after the final reply.
Evidence: SELF isolated-network make test and make build; 15 browser scenarios; independent component review; component PRs #55, #199, #85.
Impact: Pin merged Backend, Frontend and UI revisions and update DESIGN.md for one detail location and durable folded history.
Refs: .task/feature-work-companion-visibility.md; Agent-System-UI #55; Agent-System-Backend #199; Agent-System-Frontend #85
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=3538d40f45ad5a7c779426eb3322f79751db380c.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Documents PR (feature/dhf-plan-progress-note) corrects the stale
WIP/stage-8 wording in the DHF plan progress note; the Dev combo must
pin the updated Documents commit so combined verification covers it.
Evidence: task card records make test exit 2 (transient lock-probe flake
in test_recover_skips_when_lock_held, single rerun OK) then exit 0 on
rerun; make build and task-sync receipts follow in later commits.
Impact: gitlink moves 6619835 -> 46506ae (Documents PR head); note-only
doc change, no code paths affected.
Refs: Documents PR feature/dhf-plan-progress-note; Dev task card
feature-dhf-plan-progress-note
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=7e9ebdea5055a63c713ccc0fb1f938ffe35a6b9d.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Stage 8 review found that the main plan still described the approved increment as a draft.
Evidence: Documents commit 6619835 adds a dated status note without changing the approved plan body; the first pre-commit combination check correctly rejected the uncommitted pin drift.
Impact: Dev now records the exact Documents component SHA for renewed combination validation.
Refs: Documents PR #102; Dev PR #540; DHF U1 Stage 8 review
Why: The Documents main gained an unrelated merge-queue report before PR submission, so the feature branch must include the current authoritative base.
Evidence: Comparing c256558 and fdca353 shows only the merge-queue report changed; the DHF plan, index and asset inventory retain their bytes. Dev combination tests follow on this exact pin.
Impact: Update the Documents gitlink and stage-seven trace; no DHF package, publication or runtime data change.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=4f84c2e1630cd0311643529fae1c3a99f1dd5d64.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d852c159b6b3387a2f418a42ab6d3696ac873d01.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The Dev U7 task must consume the actual reviewed Backend merge and record the current agent-only delivery authorization.
Evidence: Backend #185 merged as 8e80e261 after independent REPLAY and exact-head GATE run 3062; task card preserves the original SELF resume receipt.
Impact: Advance the Backend gitlink to the merged component; parent combination and CI remain pending final synchronization.
Refs: Dev #486; Backend #185; Dev queue #518
Why: Keep the Dev project entry and task record aligned with the approved DHF implementation and saved U1 evidence.
Evidence: SELF make test passed on the Dev combination with Documents c256558; the complete output is in the task card.
Impact: Advances only the Documents pin and progress metadata; no template publication, migration, or deployment.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=f00165e8d71e4dc8ba0ceb7dc50c1a8a3deb6d60.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Prepare genuine Dev #488 for its final window using actually merged component versions and the authorized agent merge scope.
Evidence: Frontend PR 73 tree-identical merge and independent review; RDM PR 301 GATE3044, independent replay, Root merge ef510. Full Dev combination and exact-head CI remain pending.
Impact: Advances the frontend pin and task record only; current target main sync follows in the scheduled final window.
Refs: Dev PR #488; Frontend PR #73; RDM PR #301; Issue #518
Why: Resume the approved DHF work from saved planning artifacts and a clean task tree.
Evidence: Startup failure and combination-check receipts are retained in the task card.
Impact: Planning entry, task authorization and Documents composition only.
Refs: feature/dhf-template-pipeline-plan; DHF plan r0.1
Why: restore the assigned task against the current target while retaining its original baseline and all newer component capabilities.
Evidence: startup precheck and real parent/component sync receipts capture the original conflict; Documents PR89 was independently reviewed, merged by the agent, and its tree verified.
Impact: include origin/main and the delivered documentation merge 7bd4e17827d4c7c88647bf3c9199c495b60cb107 without rewriting task history or pushing waiting branches.
Refs: Dev PR #489; Documents PR #89; merge queue Issue #518; user takeover authorization on 2026-10-14
Why: Carry the actual merged contract and approved permission implementation boundary into the integration composition.
Evidence: Documents PR 99 merged as a7ff466d9ae91fc67a53d2bf4991f47fc63a2a4c after independent review and verified source digest; RDM PR 360 preserves actual-actor projection semantics.
Impact: Update documentation pin, navigation and delivery records only; new composition tests and final-head CI remain required.
Refs: IAM I1 permission contract section 8; Documents PRs 98 and 99; RDM PR 360.
Why: Record user acceptance and use the actual merged permission contract in the integration composition.
Evidence: Documents PR 98 merged as 3cf263962bd106529ee0531c8415cb16eecedfe3; independent document review and full SELF receipts retained in the task record.
Impact: Advance only Documents and delivery evidence; full IAM later increments and deployment remain outside scope.
Refs: Documents PR 98; IAM I1 U1-U2; policy/delivery.md stages 8-9.
Why: Keep the user-approved implementation and pending acceptance separate in the fixed integration records.
Evidence: Current Dev make test passed at10789653 and RDM combined checks passed at70e27b08; final text-only combination is verified next.
Impact: Documents and card records only; no permission source, pins in RDM, existing services or production data changes.
Refs: I1 stage 7 acceptance candidate
Why: Preserve the human stage 6 approval separately from the synchronized formal test candidate.
Evidence: Original reviewed objects and the user approval are recorded; startup recovery and synchronization outputs are captured as complete SELF receipts.
Impact: Advance approval records only, retain all upstream membership records and enter planned I1 API/command verification. No production operations or later increments started.
Refs: User approval; policy/delivery.md stage 6 to 7
Why: The resumed task requires a fresh baseline before recording the approved implementation and formal checks.
Evidence: Startup identified SYNC_REQUIRED; Documents pointer conflict was resolved by merging the referenced upstream commit while preserving all three approved I1 documents byte-for-byte.
Impact: Workspace recovery only; retain incoming project-membership records and the fixed I1 approval objects. Formal checks remain pending.
Refs: User approval of I1 implementation; policy/governance.md startup and recovery
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: Keep the reviewable contract and observed verification together in the fixed parent composition.
Evidence: Dev make test passed on 0ab70b0c and RDM make test passed on ef075bd1, recorded as complete SELF receipts. Final parent pin verification follows this metadata checkpoint.
Impact: Advance the text-only review record and save evidence; no implementation components changed.
Refs: IAM I1 U1-U2 local review
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=143e6367367760deceac91ac3de5ccb3ed6adebc.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Keep the accepted IAM direction and I1 review entry visible from the authoritative integration checkout.
Evidence: Full SELF document consistency receipts are recorded in the I1 task card. Final synchronized parent combination verification follows this checkpoint.
Impact: Advance Documents only and record I1 local authorization; backend, frontend and UI behavior pins remain unchanged.
Refs: Approved IAM plan r1; I1 U1-U2
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: 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 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: 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: 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: 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
weichenandCursor