coding-agent-harness 1.0.1 → 1.0.2

package/templates/development/cross-repo-debugging.md

@@ -0,0 +1,18 @@
+# Cross-Repo Debugging
+
+Context Doc Type: cross-repo-debugging
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Debug Flow
+
+1. Identify the failing interface or flow.
+2. Read `docs/03-ARCHITECTURE/service-catalog.md` for ownership and upstream/downstream services.
+3. Read the matching `docs/06-INTEGRATIONS/` contract.
+4. Use the matching `docs/04-DEVELOPMENT/external-context/<service-key>.md` notes for mocks and local debugging.
+
+## Known Failure Modes
+
+| Symptom | Likely Service | First Check | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- |

package/templates/development/external-context/service-template.md

@@ -0,0 +1,33 @@
+# External Development Context: <service-key>
+
+Context Doc Type: external-development-context
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Index Links
+
+| Service Profile | Source Pack | Integration Contracts | Last Verified | Confidence |
+| --- | --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-source-packs/<source-key>/README.md` or N/A | `docs/06-INTEGRATIONS/<contract>.md` | unknown | low |
+
+## Development Use
+
+[What an agent needs to know about this external service while changing this repository.]
+
+## Do Not Assume
+
+- [Assumption that is unsafe without checking the external repo or owner.]
+
+## Mocks / Stubs
+
+| Scenario | Stub / Mock | Command or Path | Source Evidence |
+| --- | --- | --- | --- |
+
+## Cross-Repo Debug Notes
+
+[How to debug when this service is involved.]
+
+## Placement Rule
+
+This file only covers local development, testing, and debugging context for this external service. Put service responsibility in `03-ARCHITECTURE`; put interface fields and schemas in `06-INTEGRATIONS`.

package/templates/development/external-source-packs/README.md

@@ -0,0 +1,24 @@
+# External Source Packs
+
+Context Doc Type: external-source-pack-registry
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Purpose
+
+This directory is only for external source intake, indexing, and digests. Stable facts become Harness execution context only after they are projected into `03-ARCHITECTURE`, `04-DEVELOPMENT/external-context`, or `06-INTEGRATIONS`.
+
+Read `docs/11-REFERENCE/external-source-intake-standard.md` before adding a source pack.
+
+## Source Packs
+
+| Source Key | External Project / Service | Raw Storage Mode | Source Count | Digest Status | Projected To 03/04/06 | Owner | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+
+## Placement Rule
+
+- If there are fewer than 5 source documents, prefer linking them from `Source Evidence` in `03/04/06`; a source pack may be unnecessary.
+- If the material is large, multi-topic, or expected to grow, create `<source-key>/README.md` and `digests/`.
+- `raw/` may contain only commit-safe material with no secrets, personal data, or customer data.
+- Non-committable material should be represented by external path, owner, access condition, and digest only.

package/templates/development/external-source-packs/digest-template.md

@@ -0,0 +1,28 @@
+# External Source Digest: <source-id>
+
+Context Doc Type: external-source-digest
+Source Pack: <source-key>
+Original Location: <path-or-url-or-owner>
+Digest Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Source Summary
+
+[Summarize what this source is, what it covers, how trustworthy it is, and when it was last updated in 5-10 lines.]
+
+## Extracted Facts
+
+| Fact ID | Fact | Category | Project To | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- | --- |
+| F-001 | [verifiable fact] | architecture / development / integration / security / operations / product / unknown | `docs/...` or hold | <source-id> | unknown | low |
+
+## Questions / Unsafe Assumptions
+
+| ID | Question Or Assumption | Why It Matters | Owner | Status |
+| --- | --- | --- | --- | --- |
+
+## Projection Status
+
+| Target Doc | Action | Status | Evidence |
+| --- | --- | --- | --- |

package/templates/development/local-setup.md

@@ -0,0 +1,16 @@
+# Local Setup
+
+Context Doc Type: local-setup
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Commands
+
+| Task | Command | Expected Result | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- |
+
+## Environment
+
+| Variable | Required | Purpose | Source Evidence |
+| --- | --- | --- | --- |

package/templates/development/stubs-and-mocks.md

@@ -0,0 +1,11 @@
+# Stubs and Mocks
+
+Context Doc Type: stubs-and-mocks
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Available Stubs
+
+| External Service | Scenario | Stub Path | How To Run | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- | --- |

package/templates/integrations/README.md

@@ -0,0 +1,40 @@
+# Integrations
+
+Context Doc Type: integration-index
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Purpose
+
+This folder owns concrete interface contracts: APIs, events, webhooks, SDK usage, third-party integrations, auth, payloads, errors, and contract tests.
+
+## Boundary
+
+- Put service topology and ownership in `docs/03-ARCHITECTURE/`.
+- Put development mocks and debugging notes in `docs/04-DEVELOPMENT/`.
+- Put endpoint, payload, error, auth, event, webhook, and SDK contracts here.
+
+## Structure Contract
+
+| File / Path | Facts to maintain | Write rule |
+| --- | --- | --- |
+| `<service-key>-api.md` | API endpoints, auth, payloads, errors, contract tests | Create from `api-contract.md` |
+| `<event-name>-event.md` | Event producer/consumer, schema, delivery, retry | Create from `event-contract.md` |
+| `<webhook-name>-webhook.md` | Webhook source, target, signature, payload, retry | Create from `webhook-contract.md` |
+| `third-party/<vendor-key>.md` | Third-party platform, account/permission boundaries, SDK usage, limits | Create from `third-party/vendor-template.md` |
+
+## Contract Rule
+
+Every interface contract must be its own file and link back to the related service:
+
+- Service ownership and topology: `docs/03-ARCHITECTURE/service-catalog.md` or `services/<service-key>.md`
+- Local mocks, stubs, and debugging: `docs/04-DEVELOPMENT/external-context/<service-key>.md`
+- Concrete payloads, auth, errors, and contract tests: this folder
+
+Do not mix multiple services into one large "integration notes" document. Multi-service systems should have multiple contract files; the Contract Index below is the navigation layer for humans and agents.
+
+## Contract Index
+
+| Contract | Type | Producer | Consumer | Service Profile | Development Context | Contract Tests | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |

package/templates/integrations/api-contract.md

@@ -0,0 +1,42 @@
+# API Contract: <service-or-api>
+
+Context Doc Type: api-contract
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Contract Type
+
+API
+
+## Index Links
+
+| Service Profile | Development Context | Contract Index | Last Verified | Confidence |
+| --- | --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+
+## Auth
+
+[Authentication and authorization requirements.]
+
+## Endpoints
+
+| Method | Path | Purpose | Request Payload | Response Payload | Errors | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+
+## Payload
+
+[Schema or link to schema.]
+
+## Errors
+
+[Error codes, retry rules, and user-visible behavior.]
+
+## Contract Tests
+
+| Test | Command / Path | Expected Result |
+| --- | --- | --- |
+
+## Placement Rule
+
+This file describes one API contract only. Put service responsibility in `03-ARCHITECTURE`; put local mock/stub/debug details in `04-DEVELOPMENT`.

package/templates/integrations/event-contract.md

@@ -0,0 +1,46 @@
+# Event Contract: <event-name>
+
+Context Doc Type: event-contract
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Contract Type
+
+Event
+
+## Index Links
+
+| Service Profile | Development Context | Contract Index | Last Verified | Confidence |
+| --- | --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+
+## Topic / Channel
+
+[Queue, topic, stream, or bus.]
+
+## Auth
+
+[Producer/consumer permission, signature, or access control. Use N/A with evidence when no auth exists.]
+
+## Payload
+
+[Event schema or link.]
+
+## Producers and Consumers
+
+| Role | Service | Responsibility | Source Evidence |
+| --- | --- | --- | --- |
+
+## Errors
+
+[Dead-letter, retry, and compatibility behavior.]
+
+## Contract Tests
+
+| Test | Command / Path | Expected Result |
+| --- | --- | --- |
+
+## Placement Rule
+
+This file describes one event contract only. Put service responsibility in `03-ARCHITECTURE`; put local mock/stub/debug details in `04-DEVELOPMENT`.

package/templates/integrations/third-party/vendor-template.md

@@ -0,0 +1,42 @@
+# Third-Party Integration: <vendor>
+
+Context Doc Type: third-party-integration
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Contract Type
+
+Third-party service
+
+## Index Links
+
+| Service Profile | Development Context | Contract Index | Last Verified | Confidence |
+| --- | --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/services/<vendor-key>.md` | `docs/04-DEVELOPMENT/external-context/<vendor-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+
+## Auth
+
+[Credential and permission model. Do not include secrets.]
+
+## API / SDK Surface
+
+| Surface | Purpose | Contract Link | Source Evidence | Last Verified | Confidence |
+| --- | --- | --- | --- | --- | --- |
+
+## Payload
+
+[Important request/response bodies or links.]
+
+## Errors
+
+[Vendor error, quota, retry, and fallback behavior.]
+
+## Contract Tests
+
+| Test | Command / Path | Expected Result |
+| --- | --- | --- |
+
+## Placement Rule
+
+This file describes one third-party integration only. Put account/permission/SDK/limit facts here; put business responsibility and system topology in `03-ARCHITECTURE`.

package/templates/integrations/webhook-contract.md

@@ -0,0 +1,41 @@
+# Webhook Contract: <webhook-name>
+
+Context Doc Type: webhook-contract
+Owner: project coordinator
+Last Verified: unknown
+Confidence: low
+
+## Contract Type
+
+Webhook
+
+## Index Links
+
+| Service Profile | Development Context | Contract Index | Last Verified | Confidence |
+| --- | --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/services/<service-key>.md` | `docs/04-DEVELOPMENT/external-context/<service-key>.md` | `docs/06-INTEGRATIONS/README.md` | unknown | low |
+
+## Auth
+
+[Signature, token, or IP allowlist.]
+
+## Payload
+
+[Webhook body schema or link.]
+
+## Source Evidence
+
+[Code, vendor docs, owner note, or discovery command.]
+
+## Errors
+
+[Retry, timeout, and idempotency behavior.]
+
+## Contract Tests
+
+| Test | Command / Path | Expected Result |
+| --- | --- | --- |
+
+## Placement Rule
+
+This file describes one webhook contract only. Put service responsibility in `03-ARCHITECTURE`; put local mock/stub/debug details in `04-DEVELOPMENT`.

package/templates/planning/brief.md

@@ -0,0 +1,32 @@
+# {{TASK_TITLE}}
+
+## Brief
+
+## Task ID
+
+`{{TASK_ID}}`
+
+## Created
+
+{{DATE}}
+
+## Outcome
+
+State the user-visible or project-visible result this task must deliver.
+
+## Boundaries
+
+- In scope: files, behavior, documentation, or verification this task may change.
+- Out of scope: work that must not be folded into this task.
+- Stop conditions: uncertainty, risk, or missing access that requires coordinator or user review.
+
+## Execution Contract
+
+- Owner: coordinator
+- Lifecycle state: not_started
+- Required files: `task_plan.md`, `execution_strategy.md`, `visual_map.md`, `progress.md`, `findings.md`, `review.md`
+- Required closeout: verification evidence recorded in `progress.md`
+
+## First Next Step
+
+Replace this line with the first concrete action before implementation starts.

package/templates/planning/lesson_candidates.md

@@ -0,0 +1,58 @@
+# {{TASK_TITLE}} - Lesson Candidates
+
+This file is the task-local lesson candidate queue. It is not the Lessons SSoT. Human review decides whether any candidate should move into governance promotion.
+
+## Candidate Status
+
+| Field | Value |
+| --- | --- |
+| Schema version | lesson-candidate-v1 |
+| Task-level status | pending-review |
+| Review gate | candidate-file-present |
+| Review decision | pending-human-review |
+| Promotion state | not-promoted |
+| Closeout token | pending |
+| Source task | {{TASK_ID}} |
+| Owner | coordinator |
+| Last updated | {{DATE}} |
+
+## Schema
+
+Allowed task-level status:
+
+- `missing`: candidate file is absent.
+- `pending-review`: candidate file exists, but human decision is not complete.
+- `no-candidate-accepted`: human accepted the agent's no-candidate reason.
+- `needs-promotion`: at least one candidate is queued for governance promotion.
+- `promoted`: all accepted candidates were promoted to Lessons SSoT.
+- `rejected`: all candidates were rejected or archived with reasons.
+
+Allowed row status:
+
+- `ready-for-review`: agent believes this candidate may matter.
+- `needs-promotion`: human marked the candidate worth preserving.
+- `promoted`: maintenance CLI promoted the candidate to Lessons SSoT.
+- `rejected`: human rejected the candidate with a reason.
+
+Aggregation rule:
+
+- Any `ready-for-review` row keeps task-level status `pending-review`.
+- Any `needs-promotion` row sets task-level status `needs-promotion` unless another row is still `ready-for-review`.
+- All rows `promoted` sets task-level status `promoted`.
+- All rows `rejected` sets task-level status `rejected`.
+- A no-candidate task must use task-level status `no-candidate-accepted` and fill `No-Candidate Reason`.
+
+## Candidates
+
+| ID | Row Status | Title | Why It Might Matter | Review Decision | Promotion Target |
+| --- | --- | --- | --- | --- | --- |
+
+## No-Candidate Reason
+
+Not decided yet. Fill this only when review accepts that the task produced no reusable lesson candidate.
+
+## Promotion Notes
+
+- If human review decides a candidate is worth preserving, mark the row `needs-promotion` and record the target governance location.
+- If human review rejects a candidate, mark the row `rejected` and keep the reason in the review decision.
+- `needs-promotion` does not block task closeout, but it must remain visible in the maintenance queue and closeout record.

package/templates/planning/long-running-task-contract.md

@@ -18,6 +18,12 @@
 
 - [Shared files that may conflict with other work, or none]
 
+## Primary Caller / Entry
+
+- Primary caller: [CLI / local agent / UI / API / automation / integration / other]
+- Entries this task must support: [list]
+- Entries explicitly not required: [list]
+
 ## Permission Boundaries
 
 - Continuous execution allowed: yes / no
@@ -50,6 +56,7 @@
 - [ ] Runtime verification: [URL / command / log]
 - [ ] Review report: `review.md` / n/a
 - [ ] Residual risks recorded: yes / no
+- [ ] Lesson candidate review recorded: `lesson_candidates.md` uses `no-candidate-accepted`, `needs-promotion`, `promoted`, or `rejected`
 
 ## Stop Conditions
 

package/templates/planning/module_brief.md

@@ -0,0 +1,25 @@
+# {{TASK_TITLE}} Module
+
+## Brief
+
+## Module Key
+
+`{{TASK_ID}}`
+
+## Created
+
+{{DATE}}
+
+## Role
+
+State what this module owns and why it exists.
+
+## Boundaries
+
+- Owns: directories, services, or document areas under this module.
+- Shared surfaces: files that require coordinator sync.
+- Does not own: adjacent modules or global files outside the declared scope.
+
+## Current Work
+
+List the active module tasks or point to `module_plan.md`.

package/templates/planning/module_session_prompt.md

@@ -30,6 +30,12 @@ Do not edit shared SSoT files, coordinator-owned integration files, or unrelated
 - Residual risks
 - Coordinator updates needed
 
+## Review And State Rule
+
+- Keep `task.state`, `lifecycleState`, `reviewStatus`, and `closeoutStatus` separate when reporting progress.
+- `done` means the implementation step finished. It is not `closed` until closeout evidence is recorded.
+- If review is required, update `review.md`. Human review completion must be confirmed through the local dashboard workbench or by the coordinator with `harness review-confirm`; do not mark it complete while open P0/P1/P2 findings remain.
+
 ## Shared Sync Rule
 
 Do not update Module Registry, Harness Ledger, Closeout SSoT, Regression SSoT, or Cadence Ledger from a worker session unless the coordinator assigned the shared lock.

package/templates/planning/task_plan.md

@@ -1,5 +1,7 @@
 # [Task Name]
 
+Task Contract: harness-task/v1
+
 ## Goal
 
 [State the outcome this task must deliver in one sentence.]
@@ -13,12 +15,11 @@
 
 | Budget | Use When | Required Structure |
 | --- | --- | --- |
-| simple | One owner, no subagent, L0/L1 evidence | Standard task files only |
+| simple | One owner, no subagent, L0/L1 evidence, no formal review gate | `brief.md`, `task_plan.md`, `visual_map.md`, `progress.md` |
 | standard | Normal feature, fix, or documentation change | Plan, strategy, roadmap, progress, findings, and review as needed |
-| long-running | Multi-hour autonomous loop | Add `long-running-task-contract.md` and a review loop |
-| module-parallel | Independent module slices | Add `module_plan.md`, module registry updates, and worker handoff |
+| complex | Multi-hour work, L2/L3 evidence, subagent/reviewer, or optional artifact/reference indexes | Standard files plus optional structures as needed |
 
-Selected budget: [simple / standard / long-running / module-parallel]
+Selected budget: {{TASK_BUDGET}}
 
 ## Context Packet
 
@@ -31,9 +32,10 @@ Selected budget: [simple / standard / long-running / module-parallel]
 | Contract File | Required | Purpose |
 | --- | --- | --- |
 | `execution_strategy.md` | yes | Operating model, allocation, conflict control, and evidence strategy |
-| `visual_roadmap.md` | yes | Phase graph, completion state, evidence state, and blocking risk |
+| `visual_map.md` | yes | Diagram collection: phase map, optional architecture/sequence/data-flow/state diagrams, completion state, evidence state, and blocking risk |
 | `progress.md` | yes | Execution log, decisions, and handoff |
 | `findings.md` | yes | Findings, research notes, and unresolved risks |
+| `lesson_candidates.md` | yes for standard/complex | Task-local lesson candidate queue. Human review must accept no-candidate, reject candidates, or queue promotion before review confirmation |
 | `review.md` | if needed | Adversarial or specialist review report |
 | `long-running-task-contract.md` | if needed | Continuous execution permission, loop rules, and stop conditions |
 

package/templates/planning/{visual_roadmap.md → visual_map.md}

@@ -1,4 +1,15 @@
-# [Task Name] - Visual Roadmap
+# [Task Name] - Visual Map
+
+Visual Map Contract: v1.0
+
+This file is the task's diagram collection. It is not only a phase roadmap.
+Include only diagrams that materially help a human or agent understand the task.
+
+## Map Index
+
+| ID | Type | Purpose | Required For Understanding | Source Evidence | Promotion Candidate |
+| --- | --- | --- | --- | --- | --- |
+| MAP-01 | phase | Show the execution phases and dependencies | yes | `task_plan.md` | no |
 
 ## Phase Graph
 
@@ -20,7 +31,18 @@ flowchart LR
 
 Allowed Evidence Status: missing, partial, present, waived.
 
-## Roadmap Notes
+## Supporting Maps
+
+Add optional diagrams only when useful:
+
+- architecture: module, component, or service structure.
+- sequence: frontend/backend/service/database/agent interaction.
+- data-flow: data movement and ownership.
+- state: state machine or lifecycle.
+- topology: repo, service, worker, or worktree layout.
+- decision: branch and tradeoff tree.
+
+## Map Notes
 
 - Use `missing` when no evidence has been checked.
 - Use `partial` when some evidence exists but required checks remain.

package/templates/reference/docs-library-standard.md

@@ -14,6 +14,35 @@ Define how the project documentation library is organized so agents can find cur
 6. Do not mix private runtime state, credentials, personal notes, or generated caches into the public docs library.
 7. Documentation updates that change process or behavior must be reflected in the relevant index or routing file.
 
+## Architecture / Development / Integration Routing
+
+Use these directories as a low-entropy context system:
+
+| Directory | Owns | Must Not Own | Required Schema Signals |
+| --- | --- | --- | --- |
+| `docs/03-ARCHITECTURE/` | system structure, service responsibility, ownership, service catalog, critical flows, ADRs | endpoint payloads, mock instructions, task logs | `Context Doc Type`, `Source Evidence`, `Last Verified`, `Confidence` |
+| `docs/04-DEVELOPMENT/` | local setup, codebase map, external development context, external source packs, mocks, stubs, cross-repo debugging | long-lived architecture facts, API payload contracts, undigested external document dumps | `Context Doc Type`, `Development Use`, `Do Not Assume`, `Mocks / Stubs`, `Source Evidence`, `Last Verified`, `Confidence` |
+| `docs/06-INTEGRATIONS/` | API/event/webhook/SDK/third-party contracts, auth, payloads, errors, contract tests | global topology, service ownership catalog, debugging notes | `Context Doc Type`, `Contract Type`, `Auth`, `Payload`, `Errors`, `Contract Tests`, `Source Evidence`, `Last Verified`, `Confidence` |
+
+Concrete split:
+
+- `03-ARCHITECTURE/service-catalog.md` gives only the service summary and links.
+- `06-INTEGRATIONS/<service>-api-contract.md` owns payload bodies, auth, errors, and contract tests.
+- `04-DEVELOPMENT/external-context/<service>.md` owns mocks, stubs, unsafe assumptions, and debug notes.
+- `04-DEVELOPMENT/external-source-packs/` owns external source indexes, digests, and projection status only; final facts must be written back to `03/04/06`.
+
+## External Source Intake
+
+If the target project is a microservice, multi-repo system, split frontend/backend repository, or depends on external team documents, the agent must ask the user for external source material during Diagnose / Decide. Small source sets can be linked from `Source Evidence`; large source sets must use `external-source-intake-standard.md` and a source pack.
+
+The fixed processing order is:
+
+```text
+Inventory -> Classify -> Sanitize -> Digest -> Project -> Verify -> Residual
+```
+
+Raw external material that has not been digested and projected must not become execution fact.
+
 ## Required Checklist
 
 - Entry points identify current reference standards, planning templates, SSoT files, walkthroughs, and ledgers.
@@ -22,6 +51,8 @@ Define how the project documentation library is organized so agents can find cur
 - Generated or private artifacts are excluded or explicitly separated.
 - Cross-links point to the source of truth for each subject.
 - New standards include closeout and evidence expectations.
+- `03/04/06` documents use the required schema signals and route misplaced content back to the correct directory.
+- External source packs, when present, have a registry, digests, projection targets, and residuals.
 
 ## Closeout Expectations
 

package/templates/reference/execution-workflow-standard.md

@@ -12,7 +12,8 @@ Define the standard lifecycle for non-trivial work from intake through planning,
 4. Implement in small reviewable slices and keep the plan current when scope changes.
 5. Run checks that match the risk surface before claiming completion.
 6. Route material findings through review and do not bury unresolved issues in summaries.
-7. Close the loop by updating walkthrough, SSoT, regression, ledger, or docs artifacts when the work changes durable project knowledge.
+7. Proactively commit each verified, meaningful slice. A completed slice should not remain only as unstaged or staged working-tree state unless the user explicitly asked to defer commits or a documented blocker prevents a clean commit.
+8. Close the loop by updating walkthrough, SSoT, regression, ledger, or docs artifacts when the work changes durable project knowledge. New non-simple tasks should keep `lesson_candidates.md` reviewable before human review confirmation.
 
 ## Required Checklist
 
@@ -20,10 +21,11 @@ Define the standard lifecycle for non-trivial work from intake through planning,
 - Current repo state and ownership boundaries were checked.
 - Implementation notes identify changed surfaces.
 - Required checks and evidence are captured.
+- Verified slices have commit SHAs, or the reason for deferring commit is written down.
 - Review status and material findings are recorded.
 - Residuals are explicit and assigned.
 - Closeout artifacts are updated when required.
 
 ## Closeout Expectations
 
-Closeout must provide a concise change summary, evidence checked, checks not run with reasons, review outcome, residual risk, and any durable docs or ledger updates made during the task.
+Closeout must provide a concise change summary, evidence checked, checks not run with reasons, review outcome, residual risk, relevant commit SHAs or deferred-commit rationale, and any durable docs or ledger updates made during the task.