devflow-kit 3.13.0 → 3.14.0

package/CHANGELOG.md

@@ -5,6 +5,14 @@ All notable changes to Devflow will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [3.14.0] - 2026-11-04
+
+### Changed
+
+- **`/implement` gives each Code phase or subtask and the Harden self-review the plan's acceptance criteria and known limits** ([#756](https://github.com/dean0x/devflow/issues/756)). With a sequential or parallel strategy, each phase or subtask plan adds the plan's Acceptance Criteria and Known limits, and its own steps still set its scope; a single Code agent already takes the full plan. The Harden spawn passes the same criteria as Evaluate and Test, and the plan's known limits (else `(none)`). Code builds only to the criteria and not past a stated limit. Harden tests to the criteria, every pillar still applies, and a stated limit is not a finding. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test. `/dynamic-build`, `/resolve` and a spawn by hand pass no new input and work as before.
+
+---
+
 ## [3.13.0] - 2026-11-04
 
 ### Added
@@ -2454,6 +2462,7 @@ devflow init
 ---
 
 [Unreleased]: https://github.com/dean0x/devflow/compare/v3.8.0...HEAD
+[3.14.0]: https://github.com/dean0x/devflow/compare/v3.13.0...v3.14.0
 [3.13.0]: https://github.com/dean0x/devflow/compare/v3.12.1...v3.13.0
 [3.12.1]: https://github.com/dean0x/devflow/compare/v3.12.0...v3.12.1
 [3.12.0]: https://github.com/dean0x/devflow/compare/v3.11.0...v3.12.0

package/dist/agents/code.md

@@ -44,22 +44,22 @@ You receive from orchestrator:
 - **BASE_BRANCH**: Branch this feature branch was created from
 - **EXECUTION_PLAN**: Plan with steps, files, tests
 - **PATTERNS**: Codebase patterns to follow
-- **OPERATION** (optional): `implement` (default when absent) | `issue-fix` — selects operating mode; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
-- **ISSUES** (when OPERATION: issue-fix): FIX_NOW issues from the Triage agent
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Build only to the criteria and not past a stated limit. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
+- **OPERATION** (optional): `implement` (default when absent) | `issue-fix`; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
 - **SCOPE** (when OPERATION: issue-fix): Blast-radius scope hint (Standard | Careful | `Standard, prose only`) per issue
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets most relevant to the task (anti-patterns, gotchas, invariants), the KB path and a heading index; sections are read on demand
 
 **Worktree Support**: With `WORKTREE_PATH`, resolve paths by the `devflow:worktree-support` skill; without it, use cwd.
 
-**Sequential execution context** (when chaining multiple Code agents):
+**Sequential execution context**:
 - **PRIOR_PHASE_SUMMARY**: Summary from the previous Code agent (format in Handoff)
 - **FILES_FROM_PRIOR_PHASE**: Files created that must be read and understood
 - **HANDOFF_REQUIRED**: true if another Code agent follows this one
-- **HANDOFF_FILE** (optional): Path to the branch-scoped handoff file (steps 1 and 6 below)
+- **HANDOFF_FILE** (optional): Path to the handoff file (steps 1 and 6 below)
 
 ## Responsibilities
 
-1. **Orient on branch state** (always, before any implementation): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
+1. **Orient on branch state** (always, first): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
    - In one Bash call, run `git status`, `git diff --stat`, `git diff --cached --stat` and `git log --oneline --stat -n 10`
    - Match the changed files against EXECUTION_PLAN, then Read the relevant ones together, by Read once: the interfaces, types, conventions, error handling and test patterns of prior work
    - If PRIOR_PHASE_SUMMARY is provided, check your understanding against it; the code wins over the summary
@@ -82,7 +82,7 @@ You receive from orchestrator:
 
 You fix the issues the Triage agent marked FIX_NOW. Do not re-litigate dispositions.
 
-**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix; the orchestrator pushes after its final validation gate)
+**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix)
 
 **Protocol:**
 1. Same-file issues → one commit (never two Code agents editing the same file concurrently)

package/dist/agents/harden.md

@@ -40,6 +40,7 @@ You evaluate the implementation against the 9 quality pillars and fix the issues
 You receive from orchestrator:
 - **TASK_DESCRIPTION**: What was implemented
 - **FILES_CHANGED** (optional): The branch diff's file list, with no deleted file or old rename path
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Test to the criteria; every pillar still applies. A stated limit is not a finding. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
 - **DECISIONS_CONTEXT** (optional): Compact index of active ADR/PF entries for this repository (pre-rendered to `.devflow/curation/index.md` in its main worktree). `(none)` when absent. Use `devflow:apply-decisions` to Read full bodies on demand.
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets and the KB path, with no heading index. Check the implementation against each bullet's anti-pattern, gotcha or invariant. Follow `devflow:apply-feature-knowledge`.
 
@@ -55,13 +56,13 @@ Follow the `devflow:apply-decisions` skill: check that the implementation is con
 
 1. **Gather changes**: Read all files in FILES_CHANGED.
 
-2. **Evaluate P0 pillars** (Design, Functionality, Security) and fix every issue.
+2. **Evaluate P0 pillars** and fix every issue.
 
 3. **Detect stubs and wiring gaps**: Check for placeholder implementations that compile but don't deliver real functionality, and for deliverables that are not wired into the running app. See `references/stub-detection.md` for patterns. Flag as P0-Functionality issues.
 
-4. **Evaluate P1 pillars** (Complexity, Error Handling, Tests) and fix every issue.
+4. **Evaluate P1 pillars** and fix every issue.
 
-5. **Evaluate P2** (Documentation): Fix if straightforward.
+5. **Evaluate P2**: Fix if straightforward.
 
 6. **Commit fixes**: If any changes were made, create a commit with message "fix: address self-review issues".
 
@@ -74,8 +75,7 @@ Code-scanning runs in the Code agent; do not scan here.
 ## Principles
 
 1. **Minimal changes** - Fix the issue, don't refactor surrounding code
-2. **Honest assessment** - If a P0 issue is unfixable, report BLOCKED immediately
-3. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
+2. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
 
 ## Output
 
@@ -103,12 +103,12 @@ Code-scanning runs in the Code agent; do not scan here.
 - {file} ({change description})
 
 ### Commits Created
-- {sha} fix: address self-review issues
+- {sha} {message}
 ```
 
 A workflow spawn pins the return: `{"status": "PASS" | "FIXED" | "BLOCKED"}`.
 
-Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them). `### Files Modified` and `### Commits Created` are narrative and capped.
+Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them).
 
 ## Boundaries
 

package/dist/commands/implement.md

@@ -3,15 +3,13 @@ description: Execute a single task through implementation, quality gates, and PR
 ---
 # Implement Command
 
-Orchestrate a single task by spawning agents.
-
 ## Input
 
 <command-input>
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty (use the conversation).
+`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty.
 
 **Issue-reference grammar.** Scan `COMMAND_INPUT` for candidate issue references: a `#`-prefixed token or a bare digit run. Collect them in source order as `ISSUE_REFS`, and forward the list to the Git agent verbatim. Do not render, normalise, pad, strip or drop a token. Under `github`, a token that matches `^#?[1-9][0-9]{0,8}$` is a reference, and the Git agent renders it as `#{n}`.
 
@@ -220,6 +218,8 @@ Setup context is the plan document, issue body or conversation.
 | **SEQUENTIAL_CODE_AGENTS** | The plan writes >= 10 files or has >= 7 steps |
 | **PARALLEL_CODE_AGENTS** | True artifact independence (rare) |
 
+Each phase or subtask `EXECUTION_PLAN` adds the plan's Acceptance Criteria and Known limits; its own steps still set its scope.
+
 ---
 
 **SINGLE_CODE_AGENT**:
@@ -336,9 +336,11 @@ After Phase 3, spawn Harden agent:
 Agent(subagent_type="Harden"):
 "TASK_DESCRIPTION: {task description}
 FILES_CHANGED: {branch_diff}
+ACCEPTANCE_CRITERIA: {extracted criteria if available}
+KNOWN_LIMITS: {plan's Known limits, else (none)}
 DECISIONS_CONTEXT: {decisions_context}
 FEATURE_KNOWLEDGE: {feature_knowledge_rules}
-Evaluate 9 pillars, fix P0/P1 issues, report status"
+Evaluate 9 pillars"
 ```
 
 Harden agent reports `### Status: PASS | FIXED | BLOCKED`. **If BLOCKED:** report to user and halt. **If PASS or FIXED:** continue to Phase 5. A FIXED status commits fixes and starts no Validate of its own: the Phase 6 run covers them.
@@ -429,7 +431,7 @@ Run build, typecheck, lint, test. Report pass/fail with failure details."
 
 Any other or missing Status: report and halt; never PASS.
 
-**Evidence claims** come from the evidence script, which owns the claim lines and the `## Claims` section. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
+**Evidence claims** come from the evidence script. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" claim --evidence ".devflow/docs/evidence-{branch_slug}.md" --head <head> gate|TP-<n>=<PASS|FAIL|SKIP>[:<exit>] ...
@@ -482,13 +484,13 @@ After every Test agent run — whatever its Status, first run or retry — appen
 **Produces:** REVALIDATION_RESULT
 **Requires:** QA_RESULT, VALIDATED_HEAD, BASE_REF, GATE_LEVEL
 
-Run this phase only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
+Run only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
 
 ```
 Agent(subagent_type="Validate"):
 "FILES_CHANGED: {output of `git diff --name-only --diff-filter=d VALIDATED_HEAD..HEAD`}
 VALIDATION_SCOPE: changed-only
-Verify the qa-fix commits did not break anything."
+Verify the qa-fix commits."
 ```
 
 At `lean`, open the prompt with Phase 6's `GATE_LEVEL` and `BASE_SHA` lines; its `Lint pack:` line, or `Lint pack: UNVERIFIED` if it prints none, replaces Phase 6's in VALIDATION_RESULT.
@@ -564,7 +566,7 @@ git push origin HEAD; echo "exit=$?"
 
 `exit=0` continues to the script. Any other result, a rejected non-fast-forward push included, does not block: record `TRACEABILITY: DEGRADED (evidence push failed)` for the Phase 12 report and run the script anyway.
 
-**Then refresh, inline.** The refresh is plumbing, so no Git agent runs it: `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
+**Then refresh, inline.** `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" publish --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --publication {REVIEW_PUBLICATION resolved in Phase 1, or auto}; echo "exit=$?"

package/dist/compliance-off/commands/implement.md

@@ -3,15 +3,13 @@ description: Execute a single task through implementation, quality gates, and PR
 ---
 # Implement Command
 
-Orchestrate a single task by spawning agents.
-
 ## Input
 
 <command-input>
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty (use the conversation).
+`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty.
 
 **Issue-reference grammar.** Scan `COMMAND_INPUT` for candidate issue references: a `#`-prefixed token or a bare digit run. Collect them in source order as `ISSUE_REFS`, and forward the list to the Git agent verbatim. Do not render, normalise, pad, strip or drop a token. Under `github`, a token that matches `^#?[1-9][0-9]{0,8}$` is a reference, and the Git agent renders it as `#{n}`.
 
@@ -232,6 +230,8 @@ Setup context is the plan document, issue body or conversation.
 | **SEQUENTIAL_CODE_AGENTS** | The plan writes >= 10 files or has >= 7 steps |
 | **PARALLEL_CODE_AGENTS** | True artifact independence (rare) |
 
+Each phase or subtask `EXECUTION_PLAN` adds the plan's Acceptance Criteria and Known limits; its own steps still set its scope.
+
 ---
 
 **SINGLE_CODE_AGENT**:
@@ -348,9 +348,11 @@ After Phase 3, spawn Harden agent:
 Agent(subagent_type="Harden"):
 "TASK_DESCRIPTION: {task description}
 FILES_CHANGED: {branch_diff}
+ACCEPTANCE_CRITERIA: {extracted criteria if available}
+KNOWN_LIMITS: {plan's Known limits, else (none)}
 DECISIONS_CONTEXT: {decisions_context}
 FEATURE_KNOWLEDGE: {feature_knowledge_rules}
-Evaluate 9 pillars, fix P0/P1 issues, report status"
+Evaluate 9 pillars"
 ```
 
 Harden agent reports `### Status: PASS | FIXED | BLOCKED`. **If BLOCKED:** report to user and halt. **If PASS or FIXED:** continue to Phase 5. A FIXED status commits fixes and starts no Validate of its own: the Phase 6 run covers them.
@@ -441,7 +443,7 @@ Run build, typecheck, lint, test. Report pass/fail with failure details."
 
 Any other or missing Status: report and halt; never PASS.
 
-**Evidence claims** come from the evidence script, which owns the claim lines and the `## Claims` section. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
+**Evidence claims** come from the evidence script. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" claim --evidence ".devflow/docs/evidence-{branch_slug}.md" --head <head> gate|TP-<n>=<PASS|FAIL|SKIP>[:<exit>] ...
@@ -494,13 +496,13 @@ After every Test agent run — whatever its Status, first run or retry — appen
 **Produces:** REVALIDATION_RESULT
 **Requires:** QA_RESULT, VALIDATED_HEAD, BASE_REF, GATE_LEVEL
 
-Run this phase only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
+Run only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
 
 ```
 Agent(subagent_type="Validate"):
 "FILES_CHANGED: {output of `git diff --name-only --diff-filter=d VALIDATED_HEAD..HEAD`}
 VALIDATION_SCOPE: changed-only
-Verify the qa-fix commits did not break anything."
+Verify the qa-fix commits."
 ```
 
 At `lean`, open the prompt with Phase 6's `GATE_LEVEL` and `BASE_SHA` lines; its `Lint pack:` line, or `Lint pack: UNVERIFIED` if it prints none, replaces Phase 6's in VALIDATION_RESULT.
@@ -574,7 +576,7 @@ git push origin HEAD; echo "exit=$?"
 
 `exit=0` continues to the script. Any other result, a rejected non-fast-forward push included, does not block: record `TRACEABILITY: DEGRADED (evidence push failed)` for the Phase 12 report and run the script anyway.
 
-**Then verify, inline.** The verify is plumbing, so no Git agent runs it: `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
+**Then verify, inline.** `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" verify --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --comment-out ".devflow/docs/evidence-result-{branch_slug}.md"; echo "exit=$?"

package/dist/curation-compliance-off/commands/implement.md

@@ -3,15 +3,13 @@ description: Execute a single task through implementation, quality gates, and PR
 ---
 # Implement Command
 
-Orchestrate a single task by spawning agents.
-
 ## Input
 
 <command-input>
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty (use the conversation).
+`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty.
 
 **Issue-reference grammar.** Scan `COMMAND_INPUT` for candidate issue references: a `#`-prefixed token or a bare digit run. Collect them in source order as `ISSUE_REFS`, and forward the list to the Git agent verbatim. Do not render, normalise, pad, strip or drop a token. Under `github`, a token that matches `^#?[1-9][0-9]{0,8}$` is a reference, and the Git agent renders it as `#{n}`.
 
@@ -206,6 +204,8 @@ Setup context is the plan document, issue body or conversation.
 | **SEQUENTIAL_CODE_AGENTS** | The plan writes >= 10 files or has >= 7 steps |
 | **PARALLEL_CODE_AGENTS** | True artifact independence (rare) |
 
+Each phase or subtask `EXECUTION_PLAN` adds the plan's Acceptance Criteria and Known limits; its own steps still set its scope.
+
 ---
 
 **SINGLE_CODE_AGENT**:
@@ -317,8 +317,10 @@ After Phase 3, spawn Harden agent:
 Agent(subagent_type="Harden"):
 "TASK_DESCRIPTION: {task description}
 FILES_CHANGED: {branch_diff}
+ACCEPTANCE_CRITERIA: {extracted criteria if available}
+KNOWN_LIMITS: {plan's Known limits, else (none)}
 FEATURE_KNOWLEDGE: {feature_knowledge_rules}
-Evaluate 9 pillars, fix P0/P1 issues, report status"
+Evaluate 9 pillars"
 ```
 
 Harden agent reports `### Status: PASS | FIXED | BLOCKED`. **If BLOCKED:** report to user and halt. **If PASS or FIXED:** continue to Phase 5. A FIXED status commits fixes and starts no Validate of its own: the Phase 6 run covers them.
@@ -407,7 +409,7 @@ Run build, typecheck, lint, test. Report pass/fail with failure details."
 
 Any other or missing Status: report and halt; never PASS.
 
-**Evidence claims** come from the evidence script, which owns the claim lines and the `## Claims` section. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
+**Evidence claims** come from the evidence script. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" claim --evidence ".devflow/docs/evidence-{branch_slug}.md" --head <head> gate|TP-<n>=<PASS|FAIL|SKIP>[:<exit>] ...
@@ -459,13 +461,13 @@ After every Test agent run — whatever its Status, first run or retry — appen
 **Produces:** REVALIDATION_RESULT
 **Requires:** QA_RESULT, VALIDATED_HEAD, BASE_REF, GATE_LEVEL
 
-Run this phase only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
+Run only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
 
 ```
 Agent(subagent_type="Validate"):
 "FILES_CHANGED: {output of `git diff --name-only --diff-filter=d VALIDATED_HEAD..HEAD`}
 VALIDATION_SCOPE: changed-only
-Verify the qa-fix commits did not break anything."
+Verify the qa-fix commits."
 ```
 
 At `lean`, open the prompt with Phase 6's `GATE_LEVEL` and `BASE_SHA` lines; its `Lint pack:` line, or `Lint pack: UNVERIFIED` if it prints none, replaces Phase 6's in VALIDATION_RESULT.
@@ -539,7 +541,7 @@ git push origin HEAD; echo "exit=$?"
 
 `exit=0` continues to the script. Any other result, a rejected non-fast-forward push included, does not block: record `TRACEABILITY: DEGRADED (evidence push failed)` for the Phase 12 report and run the script anyway.
 
-**Then verify, inline.** The verify is plumbing, so no Git agent runs it: `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
+**Then verify, inline.** `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" verify --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --comment-out ".devflow/docs/evidence-result-{branch_slug}.md"; echo "exit=$?"

package/dist/curation-off/agents/code.md

@@ -42,22 +42,22 @@ You receive from orchestrator:
 - **BASE_BRANCH**: Branch this feature branch was created from
 - **EXECUTION_PLAN**: Plan with steps, files, tests
 - **PATTERNS**: Codebase patterns to follow
-- **OPERATION** (optional): `implement` (default when absent) | `issue-fix` — selects operating mode; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
-- **ISSUES** (when OPERATION: issue-fix): FIX_NOW issues from the Triage agent
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Build only to the criteria and not past a stated limit. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
+- **OPERATION** (optional): `implement` (default when absent) | `issue-fix`; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
 - **SCOPE** (when OPERATION: issue-fix): Blast-radius scope hint (Standard | Careful | `Standard, prose only`) per issue
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets most relevant to the task (anti-patterns, gotchas, invariants), the KB path and a heading index; sections are read on demand
 
 **Worktree Support**: With `WORKTREE_PATH`, resolve paths by the `devflow:worktree-support` skill; without it, use cwd.
 
-**Sequential execution context** (when chaining multiple Code agents):
+**Sequential execution context**:
 - **PRIOR_PHASE_SUMMARY**: Summary from the previous Code agent (format in Handoff)
 - **FILES_FROM_PRIOR_PHASE**: Files created that must be read and understood
 - **HANDOFF_REQUIRED**: true if another Code agent follows this one
-- **HANDOFF_FILE** (optional): Path to the branch-scoped handoff file (steps 1 and 6 below)
+- **HANDOFF_FILE** (optional): Path to the handoff file (steps 1 and 6 below)
 
 ## Responsibilities
 
-1. **Orient on branch state** (always, before any implementation): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
+1. **Orient on branch state** (always, first): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
    - In one Bash call, run `git status`, `git diff --stat`, `git diff --cached --stat` and `git log --oneline --stat -n 10`
    - Match the changed files against EXECUTION_PLAN, then Read the relevant ones together, by Read once: the interfaces, types, conventions, error handling and test patterns of prior work
    - If PRIOR_PHASE_SUMMARY is provided, check your understanding against it; the code wins over the summary
@@ -79,7 +79,7 @@ You receive from orchestrator:
 
 You fix the issues the Triage agent marked FIX_NOW. Do not re-litigate dispositions.
 
-**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix; the orchestrator pushes after its final validation gate)
+**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix)
 
 **Protocol:**
 1. Same-file issues → one commit (never two Code agents editing the same file concurrently)

package/dist/curation-off/agents/harden.md

@@ -39,6 +39,7 @@ You evaluate the implementation against the 9 quality pillars and fix the issues
 You receive from orchestrator:
 - **TASK_DESCRIPTION**: What was implemented
 - **FILES_CHANGED** (optional): The branch diff's file list, with no deleted file or old rename path
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Test to the criteria; every pillar still applies. A stated limit is not a finding. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets and the KB path, with no heading index. Check the implementation against each bullet's anti-pattern, gotcha or invariant. Follow `devflow:apply-feature-knowledge`.
 
 **Empty FILES_CHANGED**: If the prompt has a `FILES_CHANGED` line that lists no file, report `### Status: PASS` with the line `no files reviewed`, and review nothing; with no `FILES_CHANGED` line, find the branch changes and review them.
@@ -49,13 +50,13 @@ You receive from orchestrator:
 
 1. **Gather changes**: Read all files in FILES_CHANGED.
 
-2. **Evaluate P0 pillars** (Design, Functionality, Security) and fix every issue.
+2. **Evaluate P0 pillars** and fix every issue.
 
 3. **Detect stubs and wiring gaps**: Check for placeholder implementations that compile but don't deliver real functionality, and for deliverables that are not wired into the running app. See `references/stub-detection.md` for patterns. Flag as P0-Functionality issues.
 
-4. **Evaluate P1 pillars** (Complexity, Error Handling, Tests) and fix every issue.
+4. **Evaluate P1 pillars** and fix every issue.
 
-5. **Evaluate P2** (Documentation): Fix if straightforward.
+5. **Evaluate P2**: Fix if straightforward.
 
 6. **Commit fixes**: If any changes were made, create a commit with message "fix: address self-review issues".
 
@@ -68,8 +69,7 @@ Code-scanning runs in the Code agent; do not scan here.
 ## Principles
 
 1. **Minimal changes** - Fix the issue, don't refactor surrounding code
-2. **Honest assessment** - If a P0 issue is unfixable, report BLOCKED immediately
-3. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
+2. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
 
 ## Output
 
@@ -97,12 +97,12 @@ Code-scanning runs in the Code agent; do not scan here.
 - {file} ({change description})
 
 ### Commits Created
-- {sha} fix: address self-review issues
+- {sha} {message}
 ```
 
 A workflow spawn pins the return: `{"status": "PASS" | "FIXED" | "BLOCKED"}`.
 
-Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them). `### Files Modified` and `### Commits Created` are narrative and capped.
+Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them).
 
 ## Boundaries
 

package/dist/curation-off/commands/implement.md

@@ -3,15 +3,13 @@ description: Execute a single task through implementation, quality gates, and PR
 ---
 # Implement Command
 
-Orchestrate a single task by spawning agents.
-
 ## Input
 
 <command-input>
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty (use the conversation).
+`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty.
 
 **Issue-reference grammar.** Scan `COMMAND_INPUT` for candidate issue references: a `#`-prefixed token or a bare digit run. Collect them in source order as `ISSUE_REFS`, and forward the list to the Git agent verbatim. Do not render, normalise, pad, strip or drop a token. Under `github`, a token that matches `^#?[1-9][0-9]{0,8}$` is a reference, and the Git agent renders it as `#{n}`.
 
@@ -194,6 +192,8 @@ Setup context is the plan document, issue body or conversation.
 | **SEQUENTIAL_CODE_AGENTS** | The plan writes >= 10 files or has >= 7 steps |
 | **PARALLEL_CODE_AGENTS** | True artifact independence (rare) |
 
+Each phase or subtask `EXECUTION_PLAN` adds the plan's Acceptance Criteria and Known limits; its own steps still set its scope.
+
 ---
 
 **SINGLE_CODE_AGENT**:
@@ -305,8 +305,10 @@ After Phase 3, spawn Harden agent:
 Agent(subagent_type="Harden"):
 "TASK_DESCRIPTION: {task description}
 FILES_CHANGED: {branch_diff}
+ACCEPTANCE_CRITERIA: {extracted criteria if available}
+KNOWN_LIMITS: {plan's Known limits, else (none)}
 FEATURE_KNOWLEDGE: {feature_knowledge_rules}
-Evaluate 9 pillars, fix P0/P1 issues, report status"
+Evaluate 9 pillars"
 ```
 
 Harden agent reports `### Status: PASS | FIXED | BLOCKED`. **If BLOCKED:** report to user and halt. **If PASS or FIXED:** continue to Phase 5. A FIXED status commits fixes and starts no Validate of its own: the Phase 6 run covers them.
@@ -395,7 +397,7 @@ Run build, typecheck, lint, test. Report pass/fail with failure details."
 
 Any other or missing Status: report and halt; never PASS.
 
-**Evidence claims** come from the evidence script, which owns the claim lines and the `## Claims` section. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
+**Evidence claims** come from the evidence script. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" claim --evidence ".devflow/docs/evidence-{branch_slug}.md" --head <head> gate|TP-<n>=<PASS|FAIL|SKIP>[:<exit>] ...
@@ -447,13 +449,13 @@ After every Test agent run — whatever its Status, first run or retry — appen
 **Produces:** REVALIDATION_RESULT
 **Requires:** QA_RESULT, VALIDATED_HEAD, BASE_REF, GATE_LEVEL
 
-Run this phase only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
+Run only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
 
 ```
 Agent(subagent_type="Validate"):
 "FILES_CHANGED: {output of `git diff --name-only --diff-filter=d VALIDATED_HEAD..HEAD`}
 VALIDATION_SCOPE: changed-only
-Verify the qa-fix commits did not break anything."
+Verify the qa-fix commits."
 ```
 
 At `lean`, open the prompt with Phase 6's `GATE_LEVEL` and `BASE_SHA` lines; its `Lint pack:` line, or `Lint pack: UNVERIFIED` if it prints none, replaces Phase 6's in VALIDATION_RESULT.
@@ -529,7 +531,7 @@ git push origin HEAD; echo "exit=$?"
 
 `exit=0` continues to the script. Any other result, a rejected non-fast-forward push included, does not block: record `TRACEABILITY: DEGRADED (evidence push failed)` for the Phase 12 report and run the script anyway.
 
-**Then refresh, inline.** The refresh is plumbing, so no Git agent runs it: `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
+**Then refresh, inline.** `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" publish --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --publication {REVIEW_PUBLICATION resolved in Phase 1, or auto}; echo "exit=$?"

package/dist/curation-tdd-off/agents/code.md

@@ -41,22 +41,22 @@ You receive from orchestrator:
 - **BASE_BRANCH**: Branch this feature branch was created from
 - **EXECUTION_PLAN**: Plan with steps, files, tests
 - **PATTERNS**: Codebase patterns to follow
-- **OPERATION** (optional): `implement` (default when absent) | `issue-fix` — selects operating mode; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
-- **ISSUES** (when OPERATION: issue-fix): FIX_NOW issues from the Triage agent
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Build only to the criteria and not past a stated limit. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
+- **OPERATION** (optional): `implement` (default when absent) | `issue-fix`; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
 - **SCOPE** (when OPERATION: issue-fix): Blast-radius scope hint (Standard | Careful | `Standard, prose only`) per issue
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets most relevant to the task (anti-patterns, gotchas, invariants), the KB path and a heading index; sections are read on demand
 
 **Worktree Support**: With `WORKTREE_PATH`, resolve paths by the `devflow:worktree-support` skill; without it, use cwd.
 
-**Sequential execution context** (when chaining multiple Code agents):
+**Sequential execution context**:
 - **PRIOR_PHASE_SUMMARY**: Summary from the previous Code agent (format in Handoff)
 - **FILES_FROM_PRIOR_PHASE**: Files created that must be read and understood
 - **HANDOFF_REQUIRED**: true if another Code agent follows this one
-- **HANDOFF_FILE** (optional): Path to the branch-scoped handoff file (steps 1 and 6 below)
+- **HANDOFF_FILE** (optional): Path to the handoff file (steps 1 and 6 below)
 
 ## Responsibilities
 
-1. **Orient on branch state** (always, before any implementation): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
+1. **Orient on branch state** (always, first): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
    - In one Bash call, run `git status`, `git diff --stat`, `git diff --cached --stat` and `git log --oneline --stat -n 10`
    - Match the changed files against EXECUTION_PLAN, then Read the relevant ones together, by Read once: the interfaces, types, conventions, error handling and test patterns of prior work
    - If PRIOR_PHASE_SUMMARY is provided, check your understanding against it; the code wins over the summary
@@ -78,7 +78,7 @@ You receive from orchestrator:
 
 You fix the issues the Triage agent marked FIX_NOW. Do not re-litigate dispositions.
 
-**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix; the orchestrator pushes after its final validation gate)
+**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix)
 
 **Protocol:**
 1. Same-file issues → one commit (never two Code agents editing the same file concurrently)

package/dist/tdd-off/agents/code.md

@@ -43,22 +43,22 @@ You receive from orchestrator:
 - **BASE_BRANCH**: Branch this feature branch was created from
 - **EXECUTION_PLAN**: Plan with steps, files, tests
 - **PATTERNS**: Codebase patterns to follow
-- **OPERATION** (optional): `implement` (default when absent) | `issue-fix` — selects operating mode; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
-- **ISSUES** (when OPERATION: issue-fix): FIX_NOW issues from the Triage agent
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Build only to the criteria and not past a stated limit. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
+- **OPERATION** (optional): `implement` (default when absent) | `issue-fix`; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
 - **SCOPE** (when OPERATION: issue-fix): Blast-radius scope hint (Standard | Careful | `Standard, prose only`) per issue
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets most relevant to the task (anti-patterns, gotchas, invariants), the KB path and a heading index; sections are read on demand
 
 **Worktree Support**: With `WORKTREE_PATH`, resolve paths by the `devflow:worktree-support` skill; without it, use cwd.
 
-**Sequential execution context** (when chaining multiple Code agents):
+**Sequential execution context**:
 - **PRIOR_PHASE_SUMMARY**: Summary from the previous Code agent (format in Handoff)
 - **FILES_FROM_PRIOR_PHASE**: Files created that must be read and understood
 - **HANDOFF_REQUIRED**: true if another Code agent follows this one
-- **HANDOFF_FILE** (optional): Path to the branch-scoped handoff file (steps 1 and 6 below)
+- **HANDOFF_FILE** (optional): Path to the handoff file (steps 1 and 6 below)
 
 ## Responsibilities
 
-1. **Orient on branch state** (always, before any implementation): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
+1. **Orient on branch state** (always, first): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
    - In one Bash call, run `git status`, `git diff --stat`, `git diff --cached --stat` and `git log --oneline --stat -n 10`
    - Match the changed files against EXECUTION_PLAN, then Read the relevant ones together, by Read once: the interfaces, types, conventions, error handling and test patterns of prior work
    - If PRIOR_PHASE_SUMMARY is provided, check your understanding against it; the code wins over the summary
@@ -81,7 +81,7 @@ You receive from orchestrator:
 
 You fix the issues the Triage agent marked FIX_NOW. Do not re-litigate dispositions.
 
-**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix; the orchestrator pushes after its final validation gate)
+**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix)
 
 **Protocol:**
 1. Same-file issues → one commit (never two Code agents editing the same file concurrently)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "devflow-kit",
-  "version": "3.13.0",
+  "version": "3.14.0",
   "description": "A meta-harness for Claude Code — turns a single coding agent into an engineering team: orchestration, parallel review, persistent memory, curated decisions, and graph workflows",
   "type": "module",
   "bin": {

package/src/assets/agents/code.mds

@@ -57,22 +57,22 @@ You receive from orchestrator:
 - **BASE_BRANCH**: Branch this feature branch was created from
 - **EXECUTION_PLAN**: Plan with steps, files, tests
 - **PATTERNS**: Codebase patterns to follow
-- **OPERATION** (optional): `implement` (default when absent) | `issue-fix` — selects operating mode; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
-- **ISSUES** (when OPERATION: issue-fix): FIX_NOW issues from the Triage agent
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Build only to the criteria and not past a stated limit. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
+- **OPERATION** (optional): `implement` (default when absent) | `issue-fix`; every spawn passes it as the first prompt line. Any other value returns BLOCKED, naming it, and changes nothing.
 - **SCOPE** (when OPERATION: issue-fix): Blast-radius scope hint (Standard | Careful | `Standard, prose only`) per issue
 - **FEATURE_KNOWLEDGE** (optional): Per KB, the Rules bullets most relevant to the task (anti-patterns, gotchas, invariants), the KB path and a heading index; sections are read on demand
 
 **Worktree Support**: With `WORKTREE_PATH`, resolve paths by the `devflow:worktree-support` skill; without it, use cwd.
 
-**Sequential execution context** (when chaining multiple Code agents):
+**Sequential execution context**:
 - **PRIOR_PHASE_SUMMARY**: Summary from the previous Code agent (format in Handoff)
 - **FILES_FROM_PRIOR_PHASE**: Files created that must be read and understood
 - **HANDOFF_REQUIRED**: true if another Code agent follows this one
-- **HANDOFF_FILE** (optional): Path to the branch-scoped handoff file (steps 1 and 6 below)
+- **HANDOFF_FILE** (optional): Path to the handoff file (steps 1 and 6 below)
 
 ## Responsibilities
 
-1. **Orient on branch state** (always, before any implementation): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
+1. **Orient on branch state** (always, first): If FEATURE_KNOWLEDGE is provided, follow `devflow:apply-feature-knowledge` on it.
    - In one Bash call, run `git status`, `git diff --stat`, `git diff --cached --stat` and `git log --oneline --stat -n 10`
    - Match the changed files against EXECUTION_PLAN, then Read the relevant ones together, by Read once: the interfaces, types, conventions, error handling and test patterns of prior work
    - If PRIOR_PHASE_SUMMARY is provided, check your understanding against it; the code wins over the summary
@@ -102,7 +102,7 @@ You receive from orchestrator:
 
 You fix the issues the Triage agent marked FIX_NOW. Do not re-litigate dispositions.
 
-**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix; the orchestrator pushes after its final validation gate)
+**Inputs:** `ISSUES`, `SCOPE` (Standard | Careful | `Standard, prose only` per issue; absent means Standard), `PUSH: false` (always for issue-fix)
 
 **Protocol:**
 1. Same-file issues → one commit (never two Code agents editing the same file concurrently)

package/src/assets/agents/harden.mds

@@ -45,6 +45,7 @@ You evaluate the implementation against the 9 quality pillars and fix the issues
 You receive from orchestrator:
 - **TASK_DESCRIPTION**: What was implemented
 - **FILES_CHANGED** (optional): The branch diff's file list, with no deleted file or old rename path
+- **ACCEPTANCE_CRITERIA**, **KNOWN_LIMITS** (optional): Test to the criteria; every pillar still applies. A stated limit is not a finding. A limit or a missing criterion never drops a trust-boundary, data-loss, security or fail-closed check or its test.
 <!-- curation:on -->
 - **DECISIONS_CONTEXT** (optional): Compact index of active ADR/PF entries for this repository (pre-rendered to `.devflow/curation/index.md` in its main worktree). `(none)` when absent. Use `devflow:apply-decisions` to Read full bodies on demand.
 <!-- curation:end -->
@@ -64,13 +65,13 @@ Follow the `devflow:apply-decisions` skill: check that the implementation is con
 
 1. **Gather changes**: Read all files in FILES_CHANGED.
 
-2. **Evaluate P0 pillars** (Design, Functionality, Security) and fix every issue.
+2. **Evaluate P0 pillars** and fix every issue.
 
 3. **Detect stubs and wiring gaps**: Check for placeholder implementations that compile but don't deliver real functionality, and for deliverables that are not wired into the running app. See `references/stub-detection.md` for patterns. Flag as P0-Functionality issues.
 
-4. **Evaluate P1 pillars** (Complexity, Error Handling, Tests) and fix every issue.
+4. **Evaluate P1 pillars** and fix every issue.
 
-5. **Evaluate P2** (Documentation): Fix if straightforward.
+5. **Evaluate P2**: Fix if straightforward.
 
 6. **Commit fixes**: If any changes were made, create a commit with message "fix: address self-review issues".
 
@@ -83,8 +84,7 @@ Code-scanning runs in the Code agent; do not scan here.
 ## Principles
 
 1. **Minimal changes** - Fix the issue, don't refactor surrounding code
-2. **Honest assessment** - If a P0 issue is unfixable, report BLOCKED immediately
-3. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
+2. **Fewest turns** - Batch independent reads and lookups in one turn. No Read-back after a successful Edit or Write unless a command changed the file. No narration-only turn
 
 ## Output
 
@@ -112,12 +112,12 @@ Code-scanning runs in the Code agent; do not scan here.
 - {file} ({change description})
 
 ### Commits Created
-- {sha} fix: address self-review issues
+- {sha} {message}
 ```
 
 A workflow spawn pins the return: `{"status": "PASS" | "FIXED" | "BLOCKED"}`.
 
-Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them). `### Files Modified` and `### Commits Created` are narrative and capped.
+Report cap: final message at most about 1,500 tokens; longer material goes to a new file in a `mktemp -d` folder and the message gives its path. Exempt, inline in full: the `### Status` line and the `status` return field (commands and workflows read the status from them).
 
 ## Boundaries
 

package/src/assets/commands/implement.mds

@@ -13,15 +13,13 @@ output-dir: dist/commands
 @import "./_partials/_settings.mds" as settings
 # Implement Command
 
-Orchestrate a single task by spawning agents.
-
 ## Input
 
 <command-input>
 $ARGUMENTS
 </command-input>
 
-`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty (use the conversation).
+`COMMAND_INPUT` is the text above: a plan document path, an issue reference, a task description, or empty.
 
 {{issue_ref_grammar()}}
 
@@ -211,6 +209,8 @@ Setup context is the plan document, issue body or conversation.
 | **SEQUENTIAL_CODE_AGENTS** | The plan writes >= 10 files or has >= 7 steps |
 | **PARALLEL_CODE_AGENTS** | True artifact independence (rare) |
 
+Each phase or subtask `EXECUTION_PLAN` adds the plan's Acceptance Criteria and Known limits; its own steps still set its scope.
+
 ---
 
 **SINGLE_CODE_AGENT**:
@@ -337,11 +337,13 @@ After Phase 3, spawn Harden agent:
 Agent(subagent_type="Harden"):
 "TASK_DESCRIPTION: {task description}
 FILES_CHANGED: {branch_diff}
+ACCEPTANCE_CRITERIA: {extracted criteria if available}
+KNOWN_LIMITS: {plan's Known limits, else (none)}
 <!-- curation:on -->
 DECISIONS_CONTEXT: {decisions_context}
 <!-- curation:end -->
 FEATURE_KNOWLEDGE: {feature_knowledge_rules}
-Evaluate 9 pillars, fix P0/P1 issues, report status"
+Evaluate 9 pillars"
 ```
 
 Harden agent reports `### Status: PASS | FIXED | BLOCKED`. **If BLOCKED:** report to user and halt. **If PASS or FIXED:** continue to Phase 5. A FIXED status commits fixes and starts no Validate of its own: the Phase 6 run covers them.
@@ -436,7 +438,7 @@ Run build, typecheck, lint, test. Report pass/fail with failure details."
 
 Any other or missing Status: report and halt; never PASS.
 
-**Evidence claims** come from the evidence script, which owns the claim lines and the `## Claims` section. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
+**Evidence claims** come from the evidence script. `<head>` is the report's `HEAD:` value, or `none` if it holds anything but letters and digits (a before/after change too).
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" claim --evidence ".devflow/docs/evidence-{branch_slug}.md" --head <head> gate|TP-<n>=<PASS|FAIL|SKIP>[:<exit>] ...
@@ -491,13 +493,13 @@ After every Test agent run — whatever its Status, first run or retry — appen
 **Produces:** REVALIDATION_RESULT
 **Requires:** QA_RESULT, VALIDATED_HEAD, BASE_REF, GATE_LEVEL
 
-Run this phase only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
+Run only if a qa-fix committed (`git rev-parse HEAD` differs from `VALIDATED_HEAD`); else skip to Phase 9. Spawn Validate agent:
 
 ```
 Agent(subagent_type="Validate"):
 "FILES_CHANGED: {output of `git diff --name-only --diff-filter=d VALIDATED_HEAD..HEAD`}
 VALIDATION_SCOPE: changed-only
-Verify the qa-fix commits did not break anything."
+Verify the qa-fix commits."
 ```
 
 At `lean`, open the prompt with Phase 6's `GATE_LEVEL` and `BASE_SHA` lines; its `Lint pack:` line, or `Lint pack: UNVERIFIED` if it prints none, replaces Phase 6's in VALIDATION_RESULT.
@@ -594,7 +596,7 @@ git push origin HEAD; echo "exit=$?"
 `exit=0` continues to the script. Any other result, a rejected non-fast-forward push included, does not block: record `TRACEABILITY: DEGRADED (evidence push failed)` for the Phase 12 report and run the script anyway.
 
 <!-- compliance:on -->
-**Then refresh, inline.** The refresh is plumbing, so no Git agent runs it: `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
+**Then refresh, inline.** `verify-evidence.cjs publish` is the whole `update-pr-evidence` operation, scrub included, in one call. Use the Bash tool with `timeout: 180000`:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" publish --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --publication {REVIEW_PUBLICATION resolved in Phase 1, or auto}; echo "exit=$?"
@@ -602,7 +604,7 @@ cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" publish --p
 
 Drop the `--evidence` pair when that file does not exist or its path does not match `^[A-Za-z0-9._/-]{1,255}$`. `{PR_NUMBER}` is digits only, and the publication value is `auto`, `full`, `off` or `stub`. Capture its stdout as `EVIDENCE_RESULT`; empty stdout, or an exit other than 0 or 2, is `TRACEABILITY: DEGRADED (evidence unavailable)`. It never blocks: whatever it returns, continue to Phase 12.
 <!-- compliance:off -->
-**Then verify, inline.** The verify is plumbing, so no Git agent runs it: `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
+**Then verify, inline.** `verify-evidence.cjs verify` reads the PR and the local evidence file, and writes the local result file. It writes nothing to GitHub:
 
 ```bash
 cd "{worktree}" && node "$HOME/.devflow/scripts/verify-evidence.cjs" verify --pr {PR_NUMBER} --evidence ".devflow/docs/evidence-{branch_slug}.md" --comment-out ".devflow/docs/evidence-result-{branch_slug}.md"; echo "exit=$?"