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
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-u2.md -> .task/archive/feature-norm-remediation-u2.md; status 已完成（合入前闭合）; PR #618https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/pulls/618.
Impact: task metadata only; the card is archived within PR #618 and lands with its merge commit.
Refs: task.sh close --self
Why: Preserve the final synchronized candidate's local verification receipt before closing its task card.
Evidence: python3 -m unittest tests.test_evidence tests.test_task_recovery passed 66 tests on the synchronized candidate.
Impact: SELF evidence only; independent review and CI remain required for formal delivery.
Refs: feature/norm-remediation-u2
Why: Preserve worker transport outcomes and host verification evidence for U2.
Evidence: 66 focused evidence and task-recovery tests passed on the recorded HEAD.
Impact: Records SELF verification and the observed worker edit-serialization deviation; formal review and CI remain NOT_RUN.
Refs: feature/norm-remediation-u2
Why: Preserve the validated LOCAL_READY resume receipt before starting a worker.
Evidence: make precheck returned LOCAL_READY; make task-resume imported the receipt.
Impact: SELF-only task metadata; delivery still requires authoritative sync and checks.
Refs: feature/norm-remediation-u2
Why: include the current parent initiative baseline before verification.
Evidence: resolved feature/norm-remediation=74bd05a876136ed8506332c76d535a6eb6356433.
Impact: integrate parent initiative changes without rewriting task history.
Refs: task-sync
Why: Preserve the exact failure provenance and prepare a clean recovery record.
Evidence: The original agent-exec receipt shows overlapping edits in one Cursor session, terminal blocked, no transport, and no host fallback.
Impact: The next U2 work will use new run IDs and single-writer, short task packets.
Refs: Development Norm Remediation U2 recovery.
Why: Record the confirmed same-session overlapping edit cause and the bounded recovery sequence after the shared executor prompt fix.
Evidence: Development-Manager PR #26 merged at b178dec; the initiative still pins the prior DM revision pending the later combined adoption step.
Impact: U2 will restart from a fresh execution run using smaller serialized packets. U3-U6 remain registered but not started.
Refs: Development Norm Remediation recovery.
Why: Specify the authorized continuation boundary before implementation begins.
Evidence: Task card records U2 files, hard stops, and acceptance criteria from the approved plan.
Impact: New-task remote triage and formal delivery gates remain unchanged.
Refs: Development Norm Remediation U2.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-norm-remediation-u2.md; R0=b5e23daed2f0ea46261979de1d62e4de0cfa88f9.
Impact: task metadata only; the feature workspace starts at 01d9f50ee8.
Refs: .task/feature-norm-remediation-u2.md
Why: The cross-repository remediation needs an explicit integration contract before child implementation can start.
Evidence: The charter records approved scope, U1 merge, child-unit dependencies, and verification gates.
Impact: New requirement intake is closed; only registered U2-U6 children may join this initiative.
Refs: Development Norm Remediation plan U1-U6.
weichen
agent-exec-transport