Why: The Frontend Stage 7 review packet needs an exact Dev synchronization receipt after main advanced.
Evidence: Tool-written make task-sync receipt records sync_base and tested_head; current Frontend PR GATE and independent replay remain tied to their own fixed SHAs.
Impact: Task card preserves the current review boundary without promoting older Dev combination receipts.
Refs: IAM U3; Frontend PR #86
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=99119a733830bc120cd6747b8b61736ea6da6078.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The task record must distinguish the owner-published Backend tag, RDM pin, and Frontend Stage 7 candidate from earlier implementation snapshots.
Evidence: Tool-written SELF receipts preserve isolated browser red/green runs, independent REPLAY log import, and current Frontend GATE query for PR #86.
Impact: Reviewers can assess exact component versions and outstanding manual gates without treating historical NOT_RUN states as current.
Refs: IAM U3; Frontend PR #86; RDM PR #380
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=bc76b68cd075379122430acb24fa080b0a38ff5e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: RDM can formally consume the merged Backend public contract only after a trusted release tag, and release publication is an owner-only dual-key operation.
Evidence: The task card records absent proposed v0.5.0 refs, the verified merge commit, current RDM pin and exact readback/creation commands.
Impact: No tag was created or pushed; downstream formal pin and combined acceptance remain pending owner action.
Refs: IAM U3; Backend PR #198; AGENTS.md high-consequence release boundary
Why: Backend PR #198 has merged, but U3 depends on a user-published trusted Backend tag before RDM can adopt the public contract.
Evidence: Tool-written postmerge receipt verifies PR merged=true, merge 2716b9e with expected base/head parents, current main and Gitea run 3190 at the tested head.
Impact: Backend component is merged; RDM pins, combined acceptance, production work and cleanup remain open.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 9
Why: Backend PR #198 has the required affected Stage 7 approval and needs a final current-target check before merge.
Evidence: Tool-written make task-sync receipt records Dev base a9fa63f, tested_head 4faaeed and changed=0; Backend branch is 0 behind its origin/main.
Impact: Only task-card evidence changed; no Backend source or validated PR head changed.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 9
Why: The user accepted the new fixed Backend candidate after main introduced and U3 fenced the process-event read path.
Evidence: Stage 7 record binds approval to Backend 6dadde4, independent two-Store PostgreSQL replay, impact review and Gitea run 3190.
Impact: Backend PR #198 may enter final merge verification; trusted tag and downstream formal combination remain separate.
Refs: IAM U3; policy/delivery.md Stage 7; Backend PR #198
Why: The human review packet must include the latest authoritative Dev base after the vendor-skills main advance.
Evidence: Tool-written make task-sync receipt records new sync_base a9fa63f, tested_head 08a7073, and the changed component/document metadata.
Impact: Dev task branch is current; the Backend U3 PR head and its independent tests remain separate fixed objects.
Refs: IAM U3; policy/delivery.md Stage 7
Why: Main advanced during UI delivery and task metadata must identify the new combined candidate.
Evidence: task-sync source-out receipt 6122ca6; Backend ead5ade includes both reviewed run history and concurrent vendor skills.
Impact: Fill the task PR link and mark the new Backend combination and final checks pending.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=a9fa63f657e0dad1033576fd6783f63ccfabcc4e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Backend main advanced through new process-event and skills PRs after the original component approval, so the changed candidate needs impact-bound retesting and human review.
Evidence: Tool-written receipts cover red/green auth-off replay, exact-head SQLite and PG suites, independent two-Store PG replay, delta review and Gitea run 3190.
Impact: Backend PR #198 remains draft; affected Stage 7 approval, merge, trusted tag and RDM formal pin remain pending.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 7
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: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-vendor-popular-skills.md(PR#549) — merges verified via git log --merges plus Gitea API squash lookup against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
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: The user explicitly accepted the fixed Backend component test candidate while cross-repository U3 acceptance remains separate.
Evidence: Stage 7 record binds approval to Backend PR #198 head 121b4d6, local SELF, independent replay and Gitea run 3174.
Impact: Backend code review may proceed; trusted tag, RDM pin, Dev combined acceptance and production operations remain pending.
Refs: IAM U3; policy/delivery.md Stage 7
Why: Stage 7 review requires a current-base sync after the final Backend evidence was recorded.
Evidence: Tool-written make task-sync receipt reports Dev sync_base e1bc260, tested_head a33cbe0, and changed=0; Backend remains 0 commits behind origin/main.
Impact: This commit adds only task-card evidence; the tested Backend, Frontend, and UI objects are unchanged.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The Backend draft PR moved to a new HEAD after CI exposed a time-sensitive SSE test and the corrected candidate now has verified GATE and independent replay.
Evidence: Tool-written receipts include final SQLite and isolated PostgreSQL suites, original reviewer replay, and a Gitea run/job identity check for PR #198 at 121b4d6.
Impact: Human Stage 7 review can use fixed Backend evidence; RDM trusted pin and Dev combined acceptance remain open.
Refs: IAM U3; Backend PR #198; policy/delivery.md Stage 7
Why: The final review packet must show a clean current-base sync after the planning-status correction.
Evidence: make task-sync recorded sync_base e1bc260, tested_head b14c431, and changed=0; full output is tool-written in the task card.
Impact: Only task-card evidence changed; Backend candidate and component test objects remain fixed.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The planning line lagged the final Backend SHA and completed independent replay.
Evidence: The task card now points to the fixed component and preserves the failed dirty-tree sync receipt.
Impact: Stage 7 remains pending human review; no application code or component pin changed.
Refs: IAM U3; policy/delivery.md Stage 7
Why: The Stage 7 component review needs a fresh check against the authoritative Dev target without changing the candidate.
Evidence: Tool-written make task-sync receipt records sync_base e1bc260 and changed=0; Backend branch independently contains origin/main.
Impact: Review packet reflects the latest observed base while formal RDM pins and combined CI remain pending.
Refs: IAM U3; policy/delivery.md Stage 7; policy/merge-queue.md
Why: Stage 6 approval advanced U3 to formal testing and isolated PostgreSQL exposed a migration guard regression.
Evidence: The task card contains tool-written SELF receipts for the failing and corrected Backend candidate, current SQLite and PG suites, Frontend/UI, browser, Dev governance, and an imported independent reviewer log.
Impact: Backend Stage 7 is reviewable on fixed SHA 26305ca; trusted RDM pin, combined CI, and human acceptance remain open.
Refs: IAM U3; docs/proposals/2026-10-14-iam-u3-account-contract-and-plan.md §10
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-vendor-popular-skills.md; R0=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: task metadata only; the feature workspace starts at e1bc2602e1.
Refs: .task/feature-vendor-popular-skills.md
Why: Stage-seven recovery initially found a stale branch; after synchronization its own evidence receipt left the task card as the sole dirty path.
Evidence: Tool-written receipts preserve the SYNC_REQUIRED and SHARED_WORKSPACE_BUSY precheck results and the successful make task-sync output at the new Dev head.
Impact: Saves only this task card and restores a clean worktree for strict resume; no formal U3 acceptance or component pin change is claimed.
Refs: U3 task card and policy/governance.md startup and recovery gate.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-work-companion-visibility.md; R0=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: task metadata only; the feature workspace starts at e1bc2602e1.
Refs: .task/feature-work-companion-visibility.md
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-dhf-plan-progress-note.md(PR#547) — merges verified via git log --merges plus Gitea API squash lookup against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
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: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-pptx-register-structural-gate.md(PR#543) — merges verified via git log --merges plus Gitea API squash lookup against origin/main.
Impact: .task/*.md moved to .task/archive/ with status backfilled; no code or submodule change.
Refs: task.sh close (card-autoclose-r1)
weichen