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: The Dev project entry and task card still described only three accepted packages after the DI owner review.
Evidence: RDM DI catalog binds four exact hashes and RDM local tests/build passed at 9997990; Dev git diff --check receipt is in this task card.
Impact: Progress record only; Documents pin, publication state, deployment and runtime data are unchanged.
Refs: PROJECT.md; .task/feature-dhf-template-pipeline-plan.md
Why: Keep the integration entry aligned with the separate project-proposal, F01 and F02 package decisions.
Evidence: SELF RDM make test passed on 87fa010; owner four-hash decisions are recorded in the RDM task card.
Impact: Progress metadata only; 44 assets remain unpublished and 14 DOC fidelity reviews remain open.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: Keep the integration task aligned with the two unpublished process-validation Word packages and their owner review boundary.
Evidence: SELF RDM make task-sync and GOWORK=off make test passed on 10933dc; receipts remain in the RDM task card.
Impact: Progress metadata only; no Documents pin, dictionary, live data, or publication change.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: The archive move staged the path changes while leaving the status and merge receipts as unstaged content; each archived card must carry its actual completed result.
Evidence: The recorded merge commits f00165e8, d852c159, and 05b997b8 are present in origin/main and match Dev PR #489/#488/#486.
Impact: Mark exactly three authorized cards complete and record their merge subjects without changing other task cards.
Refs: Dev merge queue #518; Dev #489, #488, #486
Why: pipefail treated a recent merged-card match as a failed git log after grep exited early, hiding completed cards from precheck and task-close.
Evidence: A disposable long-history regression failed before the fix and passed after it; make test-governance passed 341 cases. Git history confirms PR #489/#488/#486 merge SHAs.
Impact: Detect merged cards reliably and archive only the three authorized trial cards; four unrelated eligible cards remain untouched.
Refs: Dev merge queue #518; Dev #489, #488, #486
Why: The account task needs the actual synchronized combination and raw local checks before freezing its final Dev candidate; two spec lines overstated identity and test behavior.
Evidence: SELF make test, isolated PostgreSQL and Redis backend tests, make build, and task-sync receipts are imported; Backend #185 has independent REPLAY and exact-head GATE.
Impact: Keep current component pins, clarify read-only identity verification and test coverage, and prepare the Dev PR for final exact-head admission.
Refs: Dev #486; Backend #185; merge queue #518
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 integration project entry aligned with the owner F01/F02 purpose and stage decisions.
Evidence: SELF RDM make test passed on cdb66c5; detailed source and dictionary checks are in the RDM task card.
Impact: Progress metadata only; no dictionary registration, running data migration, or template publication.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: Keep the integration project entry aligned with the owner-approved pilot package while preserving the unpublished state.
Evidence: SELF RDM make test passed on e21a82b; owner acceptance and four artifact digests are recorded in the RDM task card.
Impact: Progress metadata only; E1, F01/F02 purpose, U1 completion and release remain open.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: Keep the Dev project entry and task record aligned with the owner semantic decision and the RDM pilot package.
Evidence: SELF RDM make task-sync and GOWORK=off make test passed on df17ed1; the exact receipts are in the RDM task card.
Impact: Progress metadata only; E1 fidelity, publication, U2-U6, and deployment remain open.
Refs: DHF r0.1 U1, feature/dhf-template-pipeline-plan
Why: Finish Dev #488 with delivered Frontend and RDM objects, explicit audit grants in private browser fixtures, and owned process cleanup.
Evidence: Tool-imported SELF precheck, final sync, make test, and real-browser runs retain failures and passes; latest isolated runtime completed seven browser cases. Final exact-head GATE and independent parent Review follow.
Impact: Preserves other main components and existing CI jobs while the one final candidate is fixed for formal checks.
Refs: Dev PR #488; Frontend PR #73; RDM PR #301; queue Issue #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: retain the approved status changes and current documentation while adopting the already approved manual delivery window after real platform validation.
Evidence: original startup, conflict resolution, combination test and writer inventory receipts are preserved in the task card; independent Doc89 and platform replay reports are referenced. Final candidate CI and review remain required.
Impact: publish the delivered Documents merge, manual trial policy and truthful capability state; keep all workflow triggers/checks and original task baseline unchanged.
Refs: Dev PR #489; Documents PR #89; Issue #518; approved merge queue implementation plan r1; user continuation authorization on 2026-10-14
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: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-dhf-template-pipeline-plan.md; R0=add097d06137c4912a4ed9279e98ca353e4e4cf1.
Impact: task metadata only; the feature workspace starts at add097d061.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=57bcb17ea212a531186b6e21617a7f3bea65a791.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: branches merged into main had left their task cards open; backfill status and archive to prevent bookkeeping debt.
Evidence: feature-merge-queue-policy-draft.md(PR#519) — merges verified via git log --merges 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 user requires all merges to follow agent-run synchronization, review, current-head CI and platform admission.
Evidence: Existing delivery stages and owner-only protection boundary reviewed; exact current Gitea Chinese labels verified from runtime resources.
Impact: Strengthen the merge executor rule only; retain human stage reviews, owner protection actions and actual CI requirements.
Refs: User instruction; merge-queue implementation plan U4/U5; Dev PR #519; Issue #518
Why: Close the delivered I1 task without modifying unrelated task records or shared workspaces.
Evidence: Dev PR 534 merged after all three exact-head CI jobs passed; RDM 360/362 and Documents 98/99 actual results and independent reviews are retained.
Impact: Archive this task card and preserve original receipts only; leave all worktrees, branches, production services and later IAM increments unchanged.
Refs: Dev PR 534; policy/delivery.md task closure authorization; IAM I1.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=e793e9804a1f5ecf49b29a40b4baac90ceb04e55.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: Preserve independent final review and current-source equivalence before platform admission.
Evidence: Final document and integration metadata review has zero findings; full composition test and source equivalence receipts are retained with precise SELF object boundaries.
Impact: Delivery evidence only; no production, provider, guideline or document changes from the reviewed candidate.
Refs: IAM I1 integration task; Documents 98/99; RDM 360/362.
Why: Preserve actual component merge results and current delivery authorization before integration CI.
Evidence: RDM PR 360 merged at exact successful CI head; new Dev make test passed and independent metadata checks preserved approved digests and pins.
Impact: Clarify historical task records and current approved repair scope; preserve documentation and delivery evidence only.
Refs: Documents PRs 98 and 99; RDM PRs 360 and 362; IAM I1 task record.
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=1e5c6b9c10ba77ed34663fd670138621a17342bd.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
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: the user confirmed acceptance in conversation on 2026-10-13; the archived
card should carry the verdict with an honest source label.
Evidence: user confirmation (conversation reply); automated ten-scenario replay
25/25 PASS rows on this card and PR #529.
Impact: archived task card note only.
Refs: task feature/rdm-increment-settings-duties (archived via #532).
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=5efbeebbdc09f8c2484613230a29c882c54652f0.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
weichen