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: Approved A1-A4 fixes have a committed Backend candidate, while independent review found that delegated rename still loses the real operator at the Backend write.
Evidence: The task card contains tool-written SELF receipts for exact Backend adcd8fe SQLite full test/build, isolated PostgreSQL suites, and RDM source-overlay full test/build.
Impact: Keeps stage 6 paused and records the pending Documents 5783940 stage 4-5 contract review. No component pin, PR, merge, production migration, deployment, or real-account action.
Refs: Documents U3 r1 c236d30, approved amendment fb3a821, delegated actor proposal 5783940.
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: 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: Stage-six review needs the current Backend and RDM source identities and a clear boundary between local overlay checks and formal pin validation.
Evidence: SELF task-sync, exact-head Backend SQLite/PostgreSQL tests and build, RDM overlay checks, and Dev governance results are recorded by make evidence.
Impact: Review record only; no production migration, deployment, or formal acceptance.
Refs: IAM U3 r1; U7 PR #185
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: Stage 6 reviewers need the observed flaky-test replays and the exact order needed to move from local overlay to a fixed RDM pin.
Evidence: SELF receipts named in the task card; this commit changes only review metadata, so the prior exact-head Dev governance result remains applicable to unchanged scripts.
Impact: Keeps formal stage 7/GATE and user-executed version publication explicit; no component source or production state changes.
Refs: IAM U3 r1; policy/delivery.md stage 6
Why: The stage 6 row should point to the committed Dev candidate without leaving a pending-commit placeholder.
Evidence: SELF git diff --cached --check at the task-card follow-up commit.
Impact: Reviewers use this card HEAD for the Dev help/guard diff; component SHAs and the pin limitation remain explicit.
Refs: IAM U3 r1; feature/iam-u3-account-directory-recovery
Why: Operators need the approved no-password initialization and owner-confirmed recovery contract, and stage 6 reviewers need an exact component/evidence map.
Evidence: SELF task-card precheck and make test-governance receipts; component receipts listed in the task card with separate source identities.
Impact: svc rejects obsolete credential commands before storage binding, help points to protected delivery and recovery proposals, and the task card records stage 6 scope with formal pin/CI dependencies still pending.
Refs: IAM U3 r1 Documents c236d309; Backend 3e01614; RDM 265d33e; Frontend a961b19
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: 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: 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: bind the human review checkpoint to the authoritative baseline and fixed contract.
Evidence: SELF task-sync and document-check receipts captured by make evidence.
Impact: evidence metadata only; business tests, CI and runtime delivery remain NOT_RUN.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM U3 phase 4-5
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: preserve the authorized U3 scope and concrete contract for human phase review.
Evidence: SELF startup and document-check receipts; independent document review of fixed drafts.
Impact: task metadata only; no product code, runtime data, production operations or gitlink changes.
Refs: Documents c236d3099dd3e20f7bdd35caf162e0be9a7d52eb; IAM r1 U3
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-iam-u3-account-directory-recovery.md; R0=add097d06137c4912a4ed9279e98ca353e4e4cf1.
Impact: task metadata only; the feature workspace starts at add097d061.
Refs: .task/feature-iam-u3-account-directory-recovery.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
weichen