Why: include the current integration baseline before verification.
Evidence: fetched origin/main=11aa76a3bc1c5047791f9a2de154e451634b6567.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: card_merge only recognized "Merge ... from <branch> into main"
merge commits, so a PR landed as a squash (real case: #457) left its
task card in .task/ forever; task-close reported nothing to close and
precheck showed no debt. Closing required a manual backfill (PR #541).
Evidence: card_merge now returns sha|subject|pr and falls back to a
Gitea API lookup by head ref or label (deleted branches keep the
original name only in label), gated by merge_commit_sha ancestry in
origin/main; precheck [cards] reuses card_merge so both surfaces agree.
Live probe against production Gitea returns 226a4af15791|Reset
per-service runtime state in svc.sh env_config|457 for
feature/svc-pidcheck-leak; stub-server tests cover squash landing,
decoy skip and the not-on-main refusal; full governance suite follows
in-card evidence.
Impact: scripts/task.sh close and precheck detect squash-merged cards
when GITEA_TOKEN is set (merge-commit path unchanged without token);
tests/test_task.py adds two regressions; no protocol change for
existing merge-commit closures beyond the appended pr field.
Refs: card-merge-misses-squash-merges (memory); PR #541 manual closure.
Why: The Documents pin and authoritative base changed after the prior Stage 7 GATE.
Evidence: make evidence captured sync, make test, and make build on the new component combination; the initial uncommitted-pin failure remains recorded.
Impact: Dev task card identifies the tested Documents SHA and awaits current-head CI and review.
Refs: Dev PR #540; Documents PR #102; DHF U1 Stage 8 review
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-card-merge-squash-detect.md; R0=d23fb4363dcc0a206e71e47f9cd23a644c7e1c70.
Impact: task metadata only; the feature workspace starts at d23fb4363d.
Refs: .task/feature-card-merge-squash-detect.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d23fb4363dcc0a206e71e47f9cd23a644c7e1c70.
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: PR #457 landed as a squash so main has no "from
feature/svc-pidcheck-leak into main" merge commit and task-close's
card_merge did not pick the card up; user authorized wrap-up on
2026-10-14. R2 (service restoration, rdmcand independent data) was
verified live today before closure.
Evidence: merge 226a4af157 verified as
origin/main ancestor; SELF receipts /tmp/svc-list-verify-20261014T072236.json
and /tmp/svc-info-rdmcand-verify-20261014T072259.json record the live
svc-list and svc-info checks; in-card test-governance receipts back R1.
Impact: backfills status, results, merge and cleanup records on the
card and moves it to .task/archive/; no code changes.
Why: Dev main advanced before the WIP PR, so the fixed Documents pin needed fresh combination evidence on the new base.
Evidence: make task-sync incorporated d40579e; make test and make build exited 0 at 5f88fd6 with SELF receipts.
Impact: Task evidence only; CI/GATE and final merge window remain pending.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d40579ed7fe3bbca68d3c6fcd1bce6707688d59e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The updated Documents pin needed fresh combined tests before its PR candidate could be fixed.
Evidence: make task-sync changed=0; make test and make build exited 0 at f628e6b with SELF receipts.
Impact: Task evidence only; publication and deployment remain untouched.
Refs: .task/feature-dhf-template-pipeline-plan.md
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: The synchronized Dev combination has a new exact test/build receipt for the current DHF increment.
Evidence: make task-sync, make test and make build at 6b5cc2de58 exited 0; source is SELF in the task card.
Impact: Task record only; PR HEAD CI, owner acceptance and deployment remain pending.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=427e9faf47641a427c5f2173244f65b8867c4500.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: The Dev task card must preserve the manual stage boundary before formal verification begins.
Evidence: Owner confirmed the fixed U1 review object with 14 DOC fidelity and 40 assets still open.
Impact: Stage state only; no component, publication or deployment change.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: Dev main and component pins advanced before the U1 increment review, so the new combination needed its own test and build evidence.
Evidence: make task-sync, make test, and make build exited 0 with SELF receipts at the synchronized Dev checkpoint 71fabf3120.
Impact: Task evidence only; no component or plan-body changes beyond the synchronized main composition.
Refs: .task/feature-dhf-template-pipeline-plan.md
Why: F2 token extraction predates the two-section (HOME/IMC) layout of
~/.secrets/gitea so it concatenated both tokens and always failed; F6
registered a grep BRE alternation that facts-verify unescapes into a
literal pipe, failing re-verification and misaligning precheck's naive
pipe split into a spurious F6 date-format expiry warning, while both
underlying facts still hold.
Evidence: make facts-verify now 6/6 PASS with last_verified refreshed
to 2026-10-14; new regression test for escaped pipes in facts rows;
full governance suite 342 tests OK (18 skipped); precheck [facts] line
reports all facts fresh on the fixed parser.
Impact: policy/facts.md F2 (HOME-section awk extraction) and F6
(negated pipe-free grep); scripts/task.sh precheck neutralizes escaped
pipes the same way facts-verify does; tests/test_task.py covers it.
Refs: precheck WARN 过期事实 F6(日期格式); AGENTS.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: 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
weichen