coding-agent-harness 1.0.2 → 1.0.4

package/templates/dashboard/assets/i18n.js

@@ -4,7 +4,7 @@ window.HarnessI18n = {
     "projectCockpit": "Console",
     "overview": "Overview",
     "taskIndex": "Task Index",
-    "reviewQueue": "Review Queue",
+    "reviewQueue": "Lifecycle Queue Workbench",
     "moduleView": "Modules",
     "readiness": "Readiness",
     "tasks": "Tasks",
@@ -77,12 +77,6 @@ window.HarnessI18n = {
     "moduleTasks": "Module Tasks",
     "noModuleTasks": "No module tasks.",
     "migration": "Migration",
-    "migrationSnapshot": "Migration Snapshot",
-    "taskPreset": "Task preset",
-    "targetLevel": "Target level",
-    "achievedLevel": "Achieved level",
-    "strictDeferred": "Strict deferred",
-    "evidenceBundle": "Evidence bundle",
     "migrationSummary": "Migration Attention",
     "migrationWorkbench": "Migration Workbench",
     "aggregateMigrationView": "aggregate migration view",
@@ -174,20 +168,39 @@ window.HarnessI18n = {
     "layout": "View Layout",
     "layoutList": "List View",
     "layoutGrid": "Grid View",
+    "sortByTime": "Time order",
+    "sortNewest": "Newest first",
+    "sortOldest": "Oldest first",
+    "activeBriefCount": "{count} briefs · {order}",
+    "copyTaskName": "Copy task folder name",
+    "copyTaskNameShort": "Copy",
+    "copyTaskNameSuccess": "Copied",
+    "copyTaskNameFailed": "Failed",
     "legacyState": "Task state",
     "lifecycleState": "Lifecycle",
     "reviewStatus": "Review",
-    "closeoutStatus": "Closeout",
+    "sedimentationStatus": "Sedimentation",
+    "closeoutStatus": "Finalization",
+    "lifecycleQueues": "Lifecycle queues",
+    "queueReasons": "Queue reasons",
     "state_closing": "closing",
     "state_closed": "closed",
     "state_ready": "ready",
     "state_in_review": "in review",
     "state_review-blocked": "review blocked",
+    "state_closed-review-pending": "closed, review pending",
     "state_missing": "missing",
     "state_required": "required",
-    "state_reviewed-unconfirmed": "reviewed",
+    "state_agent-reviewed": "agent reviewed",
     "state_confirmed": "confirmed",
     "state_blocked-open-findings": "blocked findings",
+    "state_not-in-queue": "not in queue",
+    "state_needs-material": "needs material",
+    "state_ready-to-confirm": "ready to confirm",
+    "state_closed-debt": "closed debt",
+    "state_missing-materials": "missing materials",
+    "state_soft-deleted-superseded": "soft-deleted / superseded",
+    "state_finalized": "finalized",
     "reviewActions": "Review Actions",
     "reviewWorkspace": "Review Workspace",
     "openReviewWorkspace": "Open Review Workspace",
@@ -197,14 +210,52 @@ window.HarnessI18n = {
     "documentMissing": "Document missing from this snapshot.",
     "staticReadOnly": "Static snapshot is read-only",
     "staticReadOnlyDetail": "Use the dynamic workbench to submit review or governance actions.",
-    "reviewQueueSubtitle": "Only tasks currently in the execution Review stage appear here. Closeout is tracked separately.",
+    "reviewQueueSubtitle": "Routes tasks by lifecycle queue so review work, repairs, blockers, lessons, finalized records, and superseded history stay separate.",
+    "reviewQueueTabs": "Lifecycle queues",
+    "queueReview": "Review",
+    "queueReviewDesc": "Only tasks whose taskQueues include review. These are ready for human review confirmation.",
+    "queueMissingMaterials": "Missing Materials",
+    "queueMissingMaterialsDesc": "Tasks missing review submissions, walkthroughs, lesson decisions, or other required materials.",
+    "queueBlocked": "Blocked",
+    "queueBlockedDesc": "Tasks with open blocking findings or state conflicts that prevent confirmation.",
+    "queueLessons": "Lessons",
+    "queueLessonsDesc": "Tasks with lesson candidates or promotion work that still needs governance routing.",
+    "queueConfirmedFinalized": "Confirmed / Finalized",
+    "queueConfirmedFinalizedDesc": "Human-confirmed tasks and finalized records kept for audit and closeout follow-through.",
+    "queueSoftDeletedSuperseded": "Soft-deleted / Superseded",
+    "queueSoftDeletedSupersededDesc": "Historical tasks with tombstones, replacements, merges, archives, or abandoned state.",
+    "reasonFilter": "Reason filter",
+    "allReasons": "All reasons",
+    "reason": "Reason",
+    "sortBy": "Sort by",
+    "sortQueuePriority": "Queue priority",
+    "sortTaskId": "Task ID",
+    "reviewSubmitted": "Review submitted",
+    "materialsReady": "Materials ready",
+    "yes": "Yes",
+    "no": "No",
+    "copyRepairPrompt": "Copy repair prompt",
+    "copyRepairPromptSuccess": "Prompt copied",
+    "copyLessonPrompt": "Copy lesson prompt",
+    "createLessonTask": "Create sedimentation task",
+    "openFollowUpTask": "Open follow-up task",
+    "lessonSedimentationActions": "Sedimentation actions",
+    "lessonWorkbenchRequired": "Creation is available in the dynamic workbench. The prompt can still be copied from this snapshot.",
+    "moreLessonCandidates": "+{count} more candidates in full workspace",
+    "lessonTaskCreating": "Creating task...",
+    "lessonTaskCreated": "Task created",
+    "lessonTaskCreateFailed": "Lesson task creation failed",
+    "noQueueTasks": "No tasks in this lifecycle queue.",
     "reviewReady": "Ready",
+    "reviewNeedsMaterial": "Needs material",
+    "reviewClosedDebt": "Closed debt",
     "reviewBlockedQueue": "Blocked",
     "reviewConfirmedQueue": "Confirmed",
     "noReviewTasks": "No tasks are currently in review.",
     "reviewAlreadyConfirmed": "Human review is already confirmed.",
     "reviewBlocked": "Close P0-P2 open or release-blocking findings before confirming.",
     "reviewWalkthroughRequired": "Add and link a walkthrough in Closeout SSoT before confirming human review.",
+    "reviewQueueRequired": "This task is not in the canonical Review queue.",
     "reviewWorkbenchReady": "Confirm the human review when the evidence and findings are checked.",
     "reviewConfirmChecklist": "I checked the walkthrough, task review evidence, and open findings.",
     "confirmReviewComplete": "Confirm Human Review",
@@ -219,7 +270,7 @@ window.HarnessI18n = {
     "projectCockpit": "控制台",
     "overview": "总览",
     "taskIndex": "任务索引",
-    "reviewQueue": "审查队列",
+    "reviewQueue": "生命周期队列工作台",
     "moduleView": "模块",
     "readiness": "发布状态",
     "tasks": "任务",
@@ -292,12 +343,6 @@ window.HarnessI18n = {
     "moduleTasks": "模块任务",
     "noModuleTasks": "没有模块任务。",
     "migration": "迁移",
-    "migrationSnapshot": "迁移快照",
-    "taskPreset": "任务 preset",
-    "targetLevel": "目标等级",
-    "achievedLevel": "实际完成等级",
-    "strictDeferred": "Strict deferred",
-    "evidenceBundle": "证据包",
     "migrationSummary": "迁移关注项",
     "migrationWorkbench": "迁移工作台",
     "aggregateMigrationView": "聚合迁移视图",
@@ -389,20 +434,39 @@ window.HarnessI18n = {
     "layout": "展示布局",
     "layoutList": "列表布局",
     "layoutGrid": "网格布局",
+    "sortByTime": "时间排序",
+    "sortNewest": "最新优先",
+    "sortOldest": "最早优先",
+    "activeBriefCount": "{count} 个 Brief · {order}",
+    "copyTaskName": "复制任务文件夹名",
+    "copyTaskNameShort": "复制",
+    "copyTaskNameSuccess": "已复制",
+    "copyTaskNameFailed": "失败",
     "legacyState": "任务状态",
     "lifecycleState": "生命周期",
     "reviewStatus": "审查状态",
-    "closeoutStatus": "收口状态",
-    "state_closing": "收口中",
+    "sedimentationStatus": "沉淀状态",
+    "closeoutStatus": "结项状态",
+    "lifecycleQueues": "生命周期队列",
+    "queueReasons": "队列原因",
+    "state_closing": "结项中",
     "state_closed": "已关闭",
     "state_ready": "就绪",
     "state_in_review": "审查中",
     "state_review-blocked": "审查阻塞",
+    "state_closed-review-pending": "已结项待人审",
     "state_missing": "缺失",
     "state_required": "待审查",
-    "state_reviewed-unconfirmed": "已审未确认",
+    "state_agent-reviewed": "Agent 自查",
     "state_confirmed": "已确认",
     "state_blocked-open-findings": "发现阻塞",
+    "state_not-in-queue": "不在队列",
+    "state_needs-material": "材料不齐",
+    "state_ready-to-confirm": "可确认",
+    "state_closed-debt": "结项待确认",
+    "state_missing-materials": "材料不齐",
+    "state_soft-deleted-superseded": "软删除 / 已替代",
+    "state_finalized": "已最终结项",
     "reviewActions": "审查操作",
     "reviewWorkspace": "审查工作台",
     "openReviewWorkspace": "打开审查工作台",
@@ -412,14 +476,52 @@ window.HarnessI18n = {
     "documentMissing": "当前快照中没有这个文档。",
     "staticReadOnly": "静态快照只读",
     "staticReadOnlyDetail": "需要提交审查或治理动作时，请使用动态 workbench。",
-    "reviewQueueSubtitle": "这里只显示当前处在执行审查阶段的任务；收口状态单独跟踪。",
+    "reviewQueueSubtitle": "按生命周期队列拆分审查、材料修复、阻塞、教训沉淀、已确认结项和已替代历史任务。",
+    "reviewQueueTabs": "生命周期队列",
+    "queueReview": "Review",
+    "queueReviewDesc": "只显示 taskQueues 包含 review 的任务，这些任务等待人工审查确认。",
+    "queueMissingMaterials": "Missing Materials",
+    "queueMissingMaterialsDesc": "缺少审查提交、Walkthrough、lesson 判定或其他必需材料的任务。",
+    "queueBlocked": "Blocked",
+    "queueBlockedDesc": "存在开放阻塞发现或状态冲突，当前不能确认审查的任务。",
+    "queueLessons": "Lessons",
+    "queueLessonsDesc": "还有 lesson candidate 或 promotion 治理动作需要处理的任务。",
+    "queueConfirmedFinalized": "Confirmed / Finalized",
+    "queueConfirmedFinalizedDesc": "已经人工确认或最终结项的任务，用于审计和结项追踪。",
+    "queueSoftDeletedSuperseded": "Soft-deleted / Superseded",
+    "queueSoftDeletedSupersededDesc": "带 tombstone、替代、合并、归档或废弃状态的历史任务。",
+    "reasonFilter": "原因筛选",
+    "allReasons": "全部原因",
+    "reason": "原因",
+    "sortBy": "排序",
+    "sortQueuePriority": "队列优先级",
+    "sortTaskId": "任务 ID",
+    "reviewSubmitted": "已提交审查",
+    "materialsReady": "材料就绪",
+    "yes": "是",
+    "no": "否",
+    "copyRepairPrompt": "复制修复提示",
+    "copyRepairPromptSuccess": "已复制提示",
+    "copyLessonPrompt": "复制沉淀提示",
+    "createLessonTask": "创建沉淀任务",
+    "openFollowUpTask": "打开后续任务",
+    "lessonSedimentationActions": "沉淀操作",
+    "lessonWorkbenchRequired": "创建任务需要使用动态 workbench；当前快照仍可复制沉淀提示。",
+    "moreLessonCandidates": "还有 {count} 个候选，请进详情查看",
+    "lessonTaskCreating": "正在创建任务...",
+    "lessonTaskCreated": "任务已创建",
+    "lessonTaskCreateFailed": "沉淀任务创建失败",
+    "noQueueTasks": "这个生命周期队列暂无任务。",
     "reviewReady": "待确认",
+    "reviewNeedsMaterial": "材料不齐",
+    "reviewClosedDebt": "收口待确认",
     "reviewBlockedQueue": "阻塞",
     "reviewConfirmedQueue": "已确认",
     "noReviewTasks": "当前没有处在审查阶段的任务。",
     "reviewAlreadyConfirmed": "人工审查已经确认。",
     "reviewBlocked": "先关闭 P0-P2 开放项或阻塞发布的发现，再确认审查。",
     "reviewWalkthroughRequired": "先在 Closeout SSoT 中补充并链接 Walkthrough，再确认人工审查。",
+    "reviewQueueRequired": "这个任务不在 canonical Review 队列中。",
     "reviewWorkbenchReady": "确认前请核对审查证据与开放发现。",
     "reviewConfirmChecklist": "我已核对 Walkthrough、任务审查证据和开放发现。",
     "confirmReviewComplete": "确认人工审查",

package/templates/ledger/Harness-Ledger.md

@@ -2,38 +2,26 @@
 
 ## Purpose
 
-Track whether each meaningful task kept the harness contract intact: planning, scope control, SSoT updates, regression evidence, review, walkthrough, lessons, and reference routing.
+Generated canonical task lifecycle index. Humans should use the Dashboard for current status; agents should use `task-list`, `task-index`, or this generated ledger for low-cost lookup.
 
-## Status Legend
+This file is not a hand-written work log. Do not edit lifecycle rows manually. Update task-local facts (`task_plan.md`, `progress.md`, `review.md`, `lesson_candidates.md`, closeout / walkthrough evidence), then run `harness governance rebuild --archive --apply`.
 
-| Status | Meaning | Required Next Step |
-| --- | --- | --- |
-| proposed | Work is identified but not accepted into active execution. | Assign an owner or reject with a reason. |
-| planned | Scope, owner, and expected evidence are known. | Start execution or update schedule. |
-| active | Work is in progress. | Keep task plan and evidence current. |
-| review | Implementation is complete and waiting for review or verification. | Complete review and regression gates. |
-| blocked | Work cannot proceed without a decision or dependency. | Record blocker owner and unblock condition. |
-| closed | Work is complete and closeout evidence exists. | Archive only when no longer operationally useful. |
-| archived | Entry is historical and no longer part of active coordination. | Keep a pointer to the archive location. |
+Repo Governance / CI-CD changes remain routed through their reference standards and task evidence. Regression gates, delivery sequencing, cadence rules, closeout contracts, and module ownership remain in their dedicated governance files until explicitly replaced by equivalent scanner-supported facts.
 
 ## Active Ledger
 
-| ID | Task or Change | Owner | Status | Plan | Feature or Delivery SSoT | Regression Evidence | Review Evidence | Walkthrough | Lessons Check | Residual | Updated |
+| ID | Scope | Module | Task | State | Queues | Plan | Review | Lessons Check | Closeout | Residual | Updated |
 | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| HL-YYYY-MM-DD-001 | Short operational title | owner | planned | docs/09-PLANNING/TASKS/.../task_plan.md | F-000 or D-000 | RG-000 or n/a | review.md or n/a | pending | pending | none | YYYY-MM-DD |
+| HL-YYYY-MM-DD-001 | task | none | Short operational title | planned | none | docs/09-PLANNING/TASKS/.../task_plan.md | pending | pending | pending | none | YYYY-MM-DD |
 
-## Routing Rules
+## Field Rules
 
-1. Create or update one ledger row for every non-trivial feature, refactor, release, harness update, or multi-agent handoff.
-2. Link to durable files and commands. Do not rely on chat history as evidence.
-3. If a task changes product behavior, route it through Feature SSoT or Delivery SSoT.
-4. If a task changes regression expectations, route it through Regression SSoT and Cadence Ledger.
-5. If a task changes agent process, documentation standards, or repeatable checks, route it through Lessons SSoT.
-6. A row can move to `closed` only when the walkthrough, regression evidence, review disposition, and lessons check are recorded.
+- `Scope`: `task` for root planning tasks, `module` for module-local tasks.
+- `Module`: module key, or `none`.
+- `Queues`: scanner-derived lifecycle queues; query with `harness task-list --queue`.
+- `Review`, `Lessons Check`, `Closeout`, and `Residual`: scanner-derived summaries and routes. Detailed evidence stays in task-local files.
+- `Updated`: generation date, not a manual edit timestamp.
 
-## Archive Rules
+## Legacy Tables
 
-- Keep active, blocked, review, and recently closed rows in this file.
-- Move old closed rows to `docs/01-GOVERNANCE/archive/` or the project archive path when they no longer affect current coordination.
-- Preserve the ledger ID, final status, closeout link, and archive date in any archive entry.
-- Never delete a row to hide skipped verification, `accepted-risk`, or unresolved review feedback.
+`Feature-SSoT.md` and `Private-Feature-SSoT.md` are legacy task lifecycle projections. Current Harness versions archive them during `harness governance rebuild --archive --apply` and do not regenerate them.

package/templates/lessons/lesson-arch-process-change.md

@@ -39,7 +39,7 @@ Describe the recurring architecture, ownership, phase-gate, or operating-process
 ## Acceptance Criteria
 
 - The new rule has a durable home in a reference, template, checker, or project operating model.
-- The Lessons SSoT row links this detail doc and the applied change.
+- This promoted lesson detail doc links the applied change and the closeout record.
 - Existing active tasks know whether the new rule applies immediately or only to future work.
 
 ## Disposition

package/templates/lessons/lesson-new-doc.md

@@ -43,7 +43,7 @@ Describe the missing reference document, template, checklist, or operating guide
 
 - The new document exists at the target path and is linked from the relevant index or entrypoint.
 - The document contains operational rules, not background essay content.
-- The Lessons SSoT row links this detail doc and the new document.
+- This promoted lesson detail doc links the new document and the closeout record.
 
 ## Disposition
 

package/templates/lessons/lesson-ref-change.md

@@ -37,7 +37,7 @@ ref-change
 ## Acceptance Criteria
 
 - The target reference, template, or checker is updated.
-- The update is linked from Lessons SSoT.
+- The update is linked from this promoted lesson detail doc and the closeout record.
 - Any active task affected by the rule has a migration or no-impact note.
 
 ## Disposition

package/templates/planning/execution_strategy.md

@@ -4,6 +4,37 @@
 
 [Describe the execution approach, including why this operating model fits the risk and scope.]
 
+## Subagent Authorization
+
+Read this section at the start of the task and report the current authorization state before delegating.
+This is an audit record, not an execution sandbox.
+
+| Role | Status | Permission | Authorized By | Authorized At | Scope | Worktree / Branch | Reuse |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| reviewer subagent | allowed by default | read-only | harness task policy | task creation | current task review | n/a | allowed within this task |
+| worker subagent | not authorized | write only after user approval | pending | pending | pending | pending | allowed only within approved task/scope |
+
+## Subagent Delegation Decision
+
+At task start, the coordinator must make this decision from the user's goal, even if the user never mentions subagents.
+Do not expect the user to know what a subagent or worker is. If delegation would help, explain the benefit in plain language and ask for permission once.
+It is fine to say "subagent" or "worker" to the user; the important rule is that the agent must not wait for the user to ask for them.
+If the task is clearly split into independent slices, decide `ask-user` before implementation. If exact file paths are still unknown, first identify the paths, then immediately ask for the independent execution helper authorization.
+
+| Question | Decision | Reason | Next Action |
+| --- | --- | --- | --- |
+| Should a reviewer subagent be used? | yes / no | [why reviewer review helps or is unnecessary] | If yes, call a read-only reviewer without asking for extra permission. |
+| Would a worker subagent materially help? | no / ask-user / already-authorized | [parallel slice, independent implementation, focused investigation, or not useful] | If ask-user, ask directly: "This task is suitable for a worker subagent. Do you authorize me to assign one worker subagent to modify only [scope] in [worktree/branch] while I coordinate and review the result?" |
+
+## User Authorization Decision
+
+If the worker decision above is `ask-user`, implementation is blocked until this table records the user's answer.
+Allowed resolved states are `authorized`, `denied`, or `not-needed`. Do not leave this as `pending` after choosing `ask-user`.
+
+| Gate | State | Decided By | Decided At | Scope | Worktree / Branch | Notes |
+| --- | --- | --- | --- | --- | --- | --- |
+| worker subagent | pending | pending | pending | pending | pending | Fill only after directly asking the user. |
+
 ## Operating Model
 
 - Model: solo / team / split-repo / program / waterfall / kanban / module-parallel

package/templates/planning/lesson_candidates.md

@@ -1,6 +1,6 @@
 # {{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.
+This file is the task-local lesson candidate queue. Human review decides whether any candidate should stay task-local, be rejected, enter dry-run promotion, become a promoted lesson detail doc, or become a separate sedimentation task.
 
 ## Candidate Status
 
@@ -24,14 +24,14 @@ Allowed task-level status:
 - `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.
+- `promoted`: all accepted candidates were promoted to the agreed governance target.
 - `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.
+- `needs-promotion`: human marked the candidate worth preserving through dry-run promotion or a follow-up sedimentation task.
+- `promoted`: maintenance CLI or an approved follow-up task promoted the candidate to the agreed governance target.
 - `rejected`: human rejected the candidate with a reason.
 
 Aggregation rule:
@@ -44,8 +44,8 @@ Aggregation rule:
 
 ## Candidates
 
-| ID | Row Status | Title | Why It Might Matter | Review Decision | Promotion Target |
-| --- | --- | --- | --- | --- | --- |
+| ID | Row Status | Title | Scope | Module Key | Detail Artifact | Boundary Reason | Why It Might Matter | Review Decision | Promotion Target | Conflict Check | Required Standard Update | Follow-up Task |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
 
 ## No-Candidate Reason
 
@@ -54,5 +54,17 @@ Not decided yet. Fill this only when review accepts that the task produced no re
 ## Promotion Notes
 
 - If human review decides a candidate is worth preserving, mark the row `needs-promotion` and record the target governance location.
+- If a candidate is marked `needs-promotion`, write the full task-local detail artifact while the source task context is fresh, then link it in `Detail Artifact`.
+- Use `Scope` values `task`, `module`, or `global`; module-scoped candidates must fill `Module Key`.
 - 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.
+- Default promotion behavior is dry-run or follow-up-task first. Do not write a shared Lessons table; accepted candidates become promoted lesson detail docs.
+- A sedimentation task must classify scope, check conflicts against existing lessons and standards, propose the target change, and report verification before applying.
+
+## Queue Routing
+
+| Queue | When this task enters it | Exit condition |
+| --- | --- | --- |
+| Lessons | Any candidate is `ready-for-review` or `needs-promotion`. | Human rejects it, keeps it task-local, creates a sedimentation task, or approves promotion. |
+| Missing Materials | The file is absent, has invalid status, or lacks a required no-candidate reason. | Agent repairs the candidate file. |
+| Confirmed / Finalized | Human review is confirmed but a candidate still has deferred governance work. | Follow-up task or dry-run decision is recorded. |

package/templates/planning/optional/artifacts/INDEX.md

@@ -2,9 +2,9 @@
 
 Use this index for generated outputs that support the task but are not the source of truth.
 
-| Artifact | Purpose | Generated By | Keep? |
-| --- | --- | --- | --- |
-| [file] | [why it exists] | [command, tool, or agent] | yes / no |
+| ID | Type | Path | Summary | Produced By |
+| --- | --- | --- | --- | --- |
+| [artifact-id] | command / diff / fixture / screenshot / review / report | TARGET:path or URL:https://example.com | [why it exists] | coordinator |
 
 ## Retention Notes
 

package/templates/planning/optional/references/INDEX.md

@@ -2,9 +2,9 @@
 
 Use this index for sources the task depends on but does not own.
 
-| Reference | Type | Why It Matters | Source |
-| --- | --- | --- | --- |
-| [name] | doc / link / transcript / code | [why this source is relevant] | [path or URL] |
+| ID | Type | Path | Summary | Used By |
+| --- | --- | --- | --- | --- |
+| [reference-id] | doc / link / transcript / code | TARGET:path or URL:https://example.com | [why this source is relevant] | coordinator |
 
 ## Source Rules
 

package/templates/planning/review.md

@@ -13,6 +13,36 @@
 - Out of scope: [explicit exclusions]
 - Source materials: [task plan, diff, test output, runtime evidence]
 
+## Agent Review Submission
+
+This section is written by the agent or coordinator when the review packet is ready.
+It is not human approval.
+
+| Field | Value |
+| --- | --- |
+| Submission ID | [generated by task-review] |
+| Submitted At | [timestamp] |
+| Submitted By | [agent or coordinator identity] |
+| Task Key | {{TASK_ID}} |
+| Materials Checklist Hash | [generated by task-review; informational, not a manual gate] |
+| Evidence Summary | [tests, diff, runtime, and review packet evidence] |
+| Open Findings Count | [number] |
+| Scanner Version | [generated scanner version] |
+
+### Material Checklist
+
+| Material | Required? | Status | Evidence |
+| --- | --- | --- | --- |
+| Brief | yes / no | present / missing / incomplete | [path or reason] |
+| Task plan | yes / no | present / missing / incomplete | [path or reason] |
+| Progress and evidence | yes / no | present / missing / incomplete | [path or reason] |
+| Visual map | yes / no | present / missing / incomplete | [path or reason] |
+| Lesson candidate decision | yes / no | present / missing / incomplete | [path or reason] |
+| Walkthrough or closeout link | yes / no | present / missing / incomplete | [path or reason] |
+
+The scanner derives `materialsReady` from required files, sections, evidence, and this strict submission block. If materials are not ready, route the task to Missing Materials instead of Human Review Confirmation.
+If there are open P0/P1/P2 blocking findings, route the task to Blocked instead of Human Review Confirmation.
+
 ## Confidence Challenge
 
 Answer directly: do you have 100% confidence in the plan, implementation, and strategy?
@@ -31,6 +61,24 @@ Do not keep sample findings. If there are no material findings, leave only the h
 
 [If no material findings remain, state what evidence was checked and why no material finding remains.]
 
+## Human Review Confirmation
+
+This section must only be completed by a human reviewer or by a command/workbench action acting on explicit human confirmation. Agent review submission, self-review, and subagent review do not satisfy this gate.
+
+| Field | Value |
+| --- | --- |
+| Confirmation ID | [generated by review-confirm] |
+| Confirmed At | [timestamp] |
+| Reviewer | [human name] |
+| Reviewer Email | [email, if available] |
+| Task Key | {{TASK_ID}} |
+| Confirm Text | [must match the task id or confirmation phrase required by the command] |
+| Evidence Checked | [review packet / tests / diff summary] |
+| Commit SHA | [confirmation commit SHA generated by review-confirm] |
+| Audit Status | committed / blocked |
+
+Do not fill this section when the task still belongs in Missing Materials, Blocked, or Lessons routing. `review-confirm` and the Dashboard Workbench must reject dirty Git state, missing commit identity, hook failures, or writes outside the current task `review.md` / `progress.md` allowlist.
+
 ## Evidence Checked
 
 | Evidence ID | Type | Path | Summary |
@@ -43,6 +91,17 @@ Do not keep sample findings. If there are no material findings, leave only the h
 | --- | --- | --- | --- |
 | [risk] | [owner] | yes / no | [path or next action] |
 
+## Lifecycle Queue Routing
+
+| Queue | Applies? | Reason | Exit condition |
+| --- | --- | --- | --- |
+| Review | yes / no | Submitted review packet is ready for human confirmation. | Human confirms or returns it. |
+| Missing Materials | yes / no | Required file, section, evidence, or review submission is absent/incomplete. | Agent repairs materials and resubmits review. |
+| Blocked | yes / no | Open blocking finding, invalid state transition, failed audit, or human waiver needed. | Blocker is fixed, closed, or explicitly waived. |
+| Lessons | yes / no | Lesson candidate needs rejection, task-local retention, dry-run promotion, or a sedimentation task. | Human decides candidate routing; promotion remains a separate maintenance task unless explicitly approved. |
+| Confirmed / Finalized | yes / no | Human confirmation exists; closeout or governance work may still be pending. | Closeout, ledger, and lesson routing are complete. |
+| Soft-deleted / Superseded | yes / no | Task has tombstone, superseded-by, archive, duplicate, or abandoned status. | Reopen or keep as read-only audit history. |
+
 ## Final Confidence Basis
 
 [Explain the final confidence basis after fixes and verification. If confidence is limited, name the remaining limits and who owns them.]

package/templates/planning/task_plan.md

@@ -16,8 +16,8 @@ Task Contract: harness-task/v1
 | Budget | Use When | Required Structure |
 | --- | --- | --- |
 | 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 |
-| complex | Multi-hour work, L2/L3 evidence, subagent/reviewer, or optional artifact/reference indexes | Standard files plus optional structures as needed |
+| standard | Normal feature, fix, or documentation change | `brief.md`, `task_plan.md`, `execution_strategy.md`, `visual_map.md`, `findings.md`, `lesson_candidates.md`, `progress.md`, `review.md` |
+| complex | Multi-hour work, L2/L3 evidence, subagent/reviewer, or optional artifact/reference indexes | Standard files plus `references/INDEX.md` and `artifacts/INDEX.md` |
 
 Selected budget: {{TASK_BUDGET}}
 
@@ -29,15 +29,39 @@ Selected budget: {{TASK_BUDGET}}
 
 ## Required Files
 
-| Contract File | Required | Purpose |
-| --- | --- | --- |
-| `execution_strategy.md` | yes | Operating model, allocation, conflict control, and evidence strategy |
-| `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 |
+Do not hand-copy this template to create task directories. Use `harness new-task`
+so the selected budget creates the correct file set and `harness check` can
+enforce it.
+
+| Budget | Required Files |
+| --- | --- |
+| simple | `brief.md`, `task_plan.md`, `visual_map.md`, `progress.md` |
+| standard | simple files plus `execution_strategy.md`, `findings.md`, `lesson_candidates.md`, `review.md` |
+| complex | standard files plus `references/INDEX.md`, `artifacts/INDEX.md` |
+| long-running add-on | `long-running-task-contract.md` when `--long-running` is selected |
+
+Optional subdirectories are created only when triggered:
+
+- `lessons/LC-*.md`: task-local detail artifacts for lesson candidates marked `needs-promotion`.
+- `references/INDEX.md`: complex-task source package and reference index.
+- `artifacts/INDEX.md`: complex-task generated evidence and artifact index.
+
+File purposes:
+
+| Contract File | Purpose |
+| --- | --- |
+| `brief.md` | Human-readable task summary and current context packet |
+| `task_plan.md` | Goal, scope, budget, acceptance, and operating decisions |
+| `execution_strategy.md` | Operating model, allocation, conflict control, and evidence strategy |
+| `visual_map.md` | Diagram collection: phase map, optional architecture/sequence/data-flow/state diagrams, completion state, evidence state, and blocking risk |
+| `progress.md` | Execution log, decisions, and handoff |
+| `findings.md` | Findings, research notes, and unresolved risks |
+| `lesson_candidates.md` | Task-local lesson candidate queue. Human review must accept no-candidate, reject candidates, or queue promotion before review confirmation |
+| `lessons/LC-*.md` | Optional task-local lesson detail artifacts written while source context is fresh and linked from `Detail Artifact` |
+| `review.md` | Agent review submission, adversarial review, or specialist review report |
+| `references/INDEX.md` | Complex-task source package and reference index |
+| `artifacts/INDEX.md` | Complex-task generated evidence and artifact index |
+| `long-running-task-contract.md` | Continuous execution permission, loop rules, and stop conditions |
 
 ## Steps
 
@@ -75,10 +99,9 @@ Selected budget: {{TASK_BUDGET}}
 
 ## Links
 
-- Feature SSoT entry: [reference]
 - Related Regression Gate: [reference]
 - Review Report: [path / n/a]
-- Harness Ledger entry: [complete at closeout]
+- Generated Ledger: rebuilt by lifecycle CLI / `harness governance rebuild`
 - Prerequisite tasks: [reference or none]
 
 ## Coordinator Handoff

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

@@ -12,8 +12,9 @@ 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. 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.
+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, checks failed, dirty ownership is unclear, or a documented blocker prevents a clean commit. Deferred commits require a no-commit reason, owner, and next step.
+8. Use CLI lifecycle commands for mechanical Harness writes whenever available. CLI-owned writes use locked, allowlisted auto-commit and refuse dirty Git state; agent-owned manual edits still need an explicit task commit or deferred-commit rationale.
+9. 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
 
@@ -21,7 +22,7 @@ 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.
+- Verified slices have commit SHAs, or the no-commit reason, owner, and next step are written down.
 - Review status and material findings are recorded.
 - Residuals are explicit and assigned.
 - Closeout artifacts are updated when required.