Why: include the current parent initiative baseline before verification.
Evidence: resolved feature/norm-remediation=c6fe5adba34d7266e7bcfbb9a2c64a0ae61e9b8e.
Impact: integrate parent initiative changes without rewriting task history.
Refs: task-sync
Why: Preserve credential-boundary and truthful-fact verification before delivery.
Evidence: Eight offline tests and 503 governance tests passed (18 skipped); independent fresh PI review has no blocker.
Impact: Task record only; implementation remains at reviewed candidate 39834ead.
Refs: U4 remediation plan
Why: Save offline verification before the final credential-boundary repair.
Evidence: Six offline fact verification tests and syntax/diff checks passed on 7e0b0e4.
Impact: SELF task record only.
Refs: U4 remediation plan
Why: Bind the worker to approved U4 paths and offline regression scenarios.
Evidence: U4 plan and strict READY receipt; parent head 6cee4c5.
Impact: Task metadata only.
Refs: PR #616
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-norm-remediation-u4.md; R0=eef7e5e778cabcb6216f74b74213a3d7511f383b.
Impact: task metadata only; the feature workspace starts at 6cee4c5728.
Refs: .task/feature-norm-remediation-u4.md
Why: Record the final pre-merge sync against the current initiative head.\nEvidence: make task-sync exited 0 with changed=0 at target fe0f1cd.\nImpact: Keep exact-target evidence with the archived task card.\nRefs: PR #620
Why: The child card must distinguish root main from its immediate initiative target.\nEvidence: Initiative PR #616 is open with base main; task-pr-check rejected the incorrect root_target.\nImpact: Restore correct target provenance without changing policy or gates.\nRefs: PR #620, PR #616
Why: Retain the SELF receipt for task-card closure in the archived U3 record.\nEvidence: task-close SELF=1 exited successfully for PR #620.\nImpact: Keep the pre-merge closeout reproducible without changing policy code.\nRefs: PR #620
Why: close the task card inside its own PR so landing it needs no post-merge backfill or separate close PR.
Evidence: .task/feature-norm-remediation-u3.md -> .task/archive/feature-norm-remediation-u3.md; status 已完成(合入前闭合); PR #620https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/620.
Impact: task metadata only; the card is archived within PR #620 and lands with its merge commit.
Refs: task.sh close --self
Why: Preserve the independent review receipt and latest initiative sync before task closure.\nEvidence: Fresh PI review found no blocking issue; task-sync reported changed=0 at the initiative target.\nImpact: Keep the L2-to-L1 handoff traceable.\nRefs: U3 remediation plan
Why: Record the approved U3 scope, worker transport, review, and affected checks.\nEvidence: make test-affected passed test-worktree and test-governance (495 passed, 18 skipped).\nImpact: Keep the child task auditable before L2-to-L1 delivery.\nRefs: U3 remediation plan
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-norm-remediation-u3.md; R0=fe0f1cd4649f11b0d855ec39b882b8ca37fffb6b.
Impact: task metadata only; the feature workspace starts at fe0f1cd464.
Refs: .task/feature-norm-remediation-u3.md
Why: Record the cached-target outage fix, host review, and final local verification for U2.\nEvidence: SELF receipts cover 84 focused tests and 495 governance tests; 18 checks skipped.\nImpact: Preserve exact-head delivery traceability without changing implementation.\nRefs: PR #618
Why: Preserve the final network-error classification, child-parent identity gate, and full governance test result.
Evidence: 83 focused tests and all 494 governance tests passed (18 skips) on the code candidate; child outage/missing-parent contrast tests passed.
Impact: New task and formal delivery gates remain strict; current PR head CI and final review are still required.
Refs: U2 / PR #618
Why: Preserve final root/child offline resume behavior and its reachable-parent-missing guard.
Evidence: 80 evidence/recovery tests and all 491 governance tests pass (18 expected skips) on the code candidate.
Impact: Local resume remains bounded; known missing remote parent refuses, network outage may use the registered local parent. Final-head CI remains required.
Refs: U2 / PR #618
Why: Preserve host verification and worker transport records for offline root and child task resume.
Evidence: 79 evidence/recovery tests passed; governance validation is being rerun on the final implementation candidate.
Impact: LOCAL_READY remains local-only; exact-head CI and final independent review remain required.
Refs: U2 / PR #618
Why: Preserve the final guard for a reachable advertised target whose commit object cannot be compared locally.
Evidence: The regression test, 74 focused evidence/recovery tests, and all 485 governance tests pass.
Impact: Network outages retain LOCAL_READY; known but unverified target history returns REMOTE_UNVERIFIED. Exact-head CI remains pending.
Refs: U2 / PR #618
Why: Preserve the final test matrix and review corrections for the U2 candidate.
Evidence: All 484 governance tests pass (18 skipped); the targeted evidence and recovery cases pass on the same implementation.
Impact: SELF evidence only; final-head CI and independent review remain required.
Refs: U2 / PR #618
Why: Preserve the closed-task and remote-target rewind corrections with their regression and governance test evidence.
Evidence: 71 focused tests and all 482 governance tests passed; the previous exact-head CI failed in an unrelated backend runtime test and requires a fresh run.
Impact: Review findings are fixed in scope; independent final review and current-head CI remain required.
Refs: U2 / PR #618
Why: Capture the final offline recovery cases and host verification on the PR candidate.
Evidence: 68 focused evidence and task-recovery tests pass; two broader task-start failures reproduce on the parent baseline.
Impact: Local evidence remains SELF; exact-head CI and independent review are still required.
Refs: U2 / PR #618