@chief-clancy/plan 0.3.0 → 0.4.1

package/README.md

@@ -80,7 +80,43 @@ The `--from` flag lets you go from idea to implementation plan without ever touc
 
 Plans are tracked in the brief file itself via a `<!-- planned:1,2,3 -->` marker, so re-running advances to the next unplanned row automatically.
 
-To approve and implement plans you'll need the full pipeline (`npx chief-clancy`).
+## Approving plans
+
+The plan package ships `/clancy:approve-plan` so the approval gate works without the full pipeline. The behaviour depends on the install mode.
+
+### Standalone (no board)
+
+```bash
+# Approve a specific local plan
+/clancy:approve-plan add-dark-mode-2
+
+# Or auto-select the oldest unapproved local plan
+/clancy:approve-plan
+```
+
+The command writes a `.clancy/plans/{stem}.approved` marker file containing the full lowercase hex SHA-256 of the plan file and an ISO 8601 UTC approval timestamp:
+
+```
+sha256=d2c9f3a1b4e6c8f09123456789abcdef0123456789abcdef0123456789abcd
+approved_at=2026-04-08T22:30:00Z
+```
+
+The full 64-character hex hash is what `.approved` actually stores — `/clancy:implement-from` (PR 8) reads the marker, hashes the current plan file the same way, and blocks implementation on any mismatch.
+
+The marker is the gate `/clancy:implement-from` (shipping in the next PR) checks before applying changes — if the plan file is edited after approval, the SHA mismatch blocks implementation until you re-approve. Clancy also tries to update the brief file's `<!-- planned:1,2 -->` marker to `<!-- approved:1 planned:1,2 -->` so `/clancy:plan --list` knows which rows are approved, but that brief-marker update is best-effort and may warn-and-skip if the expected brief metadata or matching marker is missing.
+
+### Standalone+board (board credentials but no full pipeline)
+
+The argument decides which path runs:
+
+- **Plan-file stem** (e.g. `add-dark-mode-2`): writes the local marker. The board push offer for local plan stems lands in a future PR
+- **Board ticket key** (e.g. `PROJ-123`): runs the full board comment-to-description transport flow — fetches the plan comment, appends it to the ticket description, edits the plan comment with an approval note, swaps the ticket labels (`CLANCY_LABEL_PLAN` → `CLANCY_LABEL_BUILD`, both with sensible defaults), and — only if `CLANCY_STATUS_PLANNED` is configured — transitions the ticket status. Label swaps are mandatory; status transitions are opt-in via the `CLANCY_STATUS_PLANNED` env var
+
+The plan-file lookup runs first, so plan stems win on collision (`PROJ-123.md` exists locally AND `PROJ-123` is a valid ticket key → the local plan wins).
+
+### Terminal mode (full pipeline)
+
+Existing behaviour, unchanged. Board ticket transport, queue transitions, and the implementation handoff all work as they did before.
 
 ## Board ticket mode
 

package/bin/plan.js

@@ -83,12 +83,8 @@ const ask = (label) => new Promise((resolve) => rl.question(label, resolve));
 // File lists (keep in sync with install.ts)
 // ---------------------------------------------------------------------------
 
-// Note: `approve-plan.md` lives in `packages/plan/src/{commands,workflows}/`
-// after PR 7a but is NOT shipped by the standalone installer yet — the
-// workflow content is currently board-only (byte-identical to terminal's
-// previous version). PR 7b makes it standalone-safe and adds it here.
-const COMMAND_FILES = ['board-setup.md', 'plan.md'];
-const WORKFLOW_FILES = ['board-setup.md', 'plan.md'];
+const COMMAND_FILES = ['approve-plan.md', 'board-setup.md', 'plan.md'];
+const WORKFLOW_FILES = ['approve-plan.md', 'board-setup.md', 'plan.md'];
 
 // ---------------------------------------------------------------------------
 // Installer
@@ -214,6 +210,9 @@ async function main() {
   console.log(
     `      ${cyan('/clancy:plan')}           ${dim('Generate an implementation plan')}`,
   );
+  console.log(
+    `      ${cyan('/clancy:approve-plan')}   ${dim('Approve a plan (run /clancy:plan first)')}`,
+  );
   console.log(
     `      ${cyan('/clancy:board-setup')}    ${dim('Configure board credentials (optional)')}`,
   );

package/dist/installer/install.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"install.d.ts","sourceRoot":"","sources":["../../src/installer/install.ts"],"names":[],"mappings":"AAaA,wEAAwE;AACxE,MAAM,MAAM,eAAe,GAAG,QAAQ,GAAG,OAAO,CAAC;AAEjD,8DAA8D;AAC9D,MAAM,MAAM,gBAAgB,GAAG;IAC7B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;CAChC,CAAC;AAEF,iDAAiD;AACjD,KAAK,kBAAkB,GAAG;IACxB,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;CAC/B,CAAC;AAEF;;;;GAIG;AACH,KAAK,eAAe,GAAG;IACrB,QAAQ,CAAC,MAAM,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;IAC3C,QAAQ,CAAC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC;IAC5C,QAAQ,CAAC,SAAS,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,KAAK,IAAI,CAAC;IAC5D,QAAQ,CAAC,KAAK,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACvC,QAAQ,CAAC,QAAQ,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACvD,oEAAoE;IACpE,QAAQ,CAAC,SAAS,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;CAC/C,CAAC;AAEF,0CAA0C;AAC1C,MAAM,MAAM,qBAAqB,GAAG;IAClC,QAAQ,CAAC,IAAI,EAAE,eAAe,CAAC;IAC/B,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;IACjC,QAAQ,CAAC,OAAO,EAAE,kBAAkB,CAAC;IACrC,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,EAAE,EAAE,eAAe,CAAC;CAC9B,CAAC;AA2BF;;;;;GAKG;AACH,eAAO,MAAM,oBAAoB,GAC/B,MAAM,SAAS,MAAM,EAAE,KACtB,eAAe,GAAG,IAKpB,CAAC;AAEF;;;;;;;GAOG;AACH,eAAO,MAAM,uBAAuB,GAClC,MAAM,eAAe,EACrB,SAAS,MAAM,EACf,KAAK,MAAM,KACV,gBAQF,CAAC;AA4EF;;;;;;;;GAQG;AACH,eAAO,MAAM,cAAc,GAAI,SAAS,qBAAqB,KAAG,IAuB/D,CAAC"}
+{"version":3,"file":"install.d.ts","sourceRoot":"","sources":["../../src/installer/install.ts"],"names":[],"mappings":"AAaA,wEAAwE;AACxE,MAAM,MAAM,eAAe,GAAG,QAAQ,GAAG,OAAO,CAAC;AAEjD,8DAA8D;AAC9D,MAAM,MAAM,gBAAgB,GAAG;IAC7B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,QAAQ,CAAC,aAAa,EAAE,MAAM,CAAC;CAChC,CAAC;AAEF,iDAAiD;AACjD,KAAK,kBAAkB,GAAG;IACxB,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;CAC/B,CAAC;AAEF;;;;GAIG;AACH,KAAK,eAAe,GAAG;IACrB,QAAQ,CAAC,MAAM,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;IAC3C,QAAQ,CAAC,QAAQ,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,MAAM,CAAC;IAC5C,QAAQ,CAAC,SAAS,EAAE,CAAC,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,KAAK,IAAI,CAAC;IAC5D,QAAQ,CAAC,KAAK,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACvC,QAAQ,CAAC,QAAQ,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,KAAK,IAAI,CAAC;IACvD,oEAAoE;IACpE,QAAQ,CAAC,SAAS,EAAE,CAAC,IAAI,EAAE,MAAM,KAAK,OAAO,CAAC;CAC/C,CAAC;AAEF,0CAA0C;AAC1C,MAAM,MAAM,qBAAqB,GAAG;IAClC,QAAQ,CAAC,IAAI,EAAE,eAAe,CAAC;IAC/B,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;IACjC,QAAQ,CAAC,OAAO,EAAE,kBAAkB,CAAC;IACrC,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,QAAQ,CAAC,EAAE,EAAE,eAAe,CAAC;CAC9B,CAAC;AAuBF;;;;;GAKG;AACH,eAAO,MAAM,oBAAoB,GAC/B,MAAM,SAAS,MAAM,EAAE,KACtB,eAAe,GAAG,IAKpB,CAAC;AAEF;;;;;;;GAOG;AACH,eAAO,MAAM,uBAAuB,GAClC,MAAM,eAAe,EACrB,SAAS,MAAM,EACf,KAAK,MAAM,KACV,gBAQF,CAAC;AA4EF;;;;;;;;GAQG;AACH,eAAO,MAAM,cAAc,GAAI,SAAS,qBAAqB,KAAG,IAuB/D,CAAC"}

package/dist/installer/install.js

@@ -9,18 +9,14 @@ import { join } from 'node:path';
 // ---------------------------------------------------------------------------
 // Constants
 // ---------------------------------------------------------------------------
-/**
- * Command files shipped with the plan package.
- *
- * Note: `approve-plan.md` exists in `src/commands/` after PR 7a but is NOT
- * shipped by the standalone installer yet — the workflow content is currently
- * board-only (byte-identical to terminal's previous version). PR 7b makes it
- * standalone-safe and adds it here. Terminal already ships approve-plan via
- * `plan-content.ts`, so the file is reachable from `npx chief-clancy`.
- */
-const COMMAND_FILES = ['board-setup.md', 'plan.md'];
-/** Workflow files shipped with the plan package. See COMMAND_FILES. */
-const WORKFLOW_FILES = ['board-setup.md', 'plan.md'];
+/** Command files shipped with the plan package. */
+const COMMAND_FILES = ['approve-plan.md', 'board-setup.md', 'plan.md'];
+/** Workflow files shipped with the plan package. */
+const WORKFLOW_FILES = [
+    'approve-plan.md',
+    'board-setup.md',
+    'plan.md',
+];
 /** Matches `@.claude/clancy/workflows/<filename>.md` on its own line. */
 const WORKFLOW_REF = /^@\.claude\/clancy\/workflows\/([^/\\]+\.md)\r?$/gm;
 // ---------------------------------------------------------------------------

package/dist/installer/install.js.map

@@ -1 +1 @@
-{"version":3,"file":"install.js","sourceRoot":"","sources":["../../src/installer/install.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AA6CjC,8EAA8E;AAC9E,YAAY;AACZ,8EAA8E;AAE9E;;;;;;;;GAQG;AACH,MAAM,aAAa,GAAG,CAAC,gBAAgB,EAAE,SAAS,CAAU,CAAC;AAE7D,uEAAuE;AACvE,MAAM,cAAc,GAAG,CAAC,gBAAgB,EAAE,SAAS,CAAU,CAAC;AAE9D,yEAAyE;AACzE,MAAM,YAAY,GAAG,oDAAoD,CAAC;AAE1E,8EAA8E;AAC9E,iBAAiB;AACjB,8EAA8E;AAE9E;;;;;GAKG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,CAClC,IAAuB,EACC,EAAE;IAC1B,IAAI,IAAI,CAAC,QAAQ,CAAC,UAAU,CAAC;QAAE,OAAO,QAAQ,CAAC;IAC/C,IAAI,IAAI,CAAC,QAAQ,CAAC,SAAS,CAAC;QAAE,OAAO,OAAO,CAAC;IAE7C,OAAO,IAAI,CAAC;AACd,CAAC,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAG,CACrC,IAAqB,EACrB,OAAe,EACf,GAAW,EACO,EAAE;IACpB,MAAM,OAAO,GACX,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,OAAO,EAAE,SAAS,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,EAAE,SAAS,CAAC,CAAC;IAEtE,OAAO;QACL,YAAY,EAAE,IAAI,CAAC,OAAO,EAAE,UAAU,EAAE,QAAQ,CAAC;QACjD,aAAa,EAAE,IAAI,CAAC,OAAO,EAAE,QAAQ,EAAE,WAAW,CAAC;KACpD,CAAC;AACJ,CAAC,CAAC;AAEF,8EAA8E;AAC9E,mBAAmB;AACnB,8EAA8E;AAE9E,kEAAkE;AAClE,MAAM,aAAa,GAAG,CACpB,IAAY,EACZ,SAAiC,EAC3B,EAAE;IACR,IAAI,SAAS,CAAC,IAAI,CAAC,EAAE,CAAC;QACpB,MAAM,IAAI,KAAK,CAAC,qBAAqB,IAAI,EAAE,CAAC,CAAC;IAC/C,CAAC;AACH,CAAC,CAAC;AASF,6EAA6E;AAC7E,MAAM,SAAS,GAAG,CAAC,OAAyB,EAAQ,EAAE;IACpD,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,EAAE,GAAG,OAAO,CAAC;IAC/C,EAAE,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IAElB,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QACrB,MAAM,GAAG,GAAG,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,CAAC;QAC/B,MAAM,IAAI,GAAG,IAAI,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC;QAEjC,IAAI,CAAC,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC;YACpB,MAAM,IAAI,KAAK,CAAC,0BAA0B,GAAG,EAAE,CAAC,CAAC;QACnD,CAAC;QAED,aAAa,CAAC,IAAI,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;QAClC,EAAE,CAAC,QAAQ,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;IACzB,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF;;;;;;GAMG;AACH,MAAM,cAAc,GAAG,CACrB,YAAoB,EACpB,aAAqB,EACrB,EAAmB,EACb,EAAE;IACR,aAAa,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QAC7B,MAAM,OAAO,GAAG,IAAI,CAAC,YAAY,EAAE,IAAI,CAAC,CAAC;QACzC,MAAM,OAAO,GAAG,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;QACrC,MAAM,QAAQ,GAAG,OAAO,CAAC,OAAO,CAC9B,YAAY,EACZ,CAAC,KAAK,EAAE,QAAgB,EAAE,EAAE;YAC1B,MAAM,MAAM,GAAG,IAAI,CAAC,aAAa,EAAE,QAAQ,CAAC,CAAC;YAE7C,OAAO,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC;QACzD,CAAC,CACF,CAAC;QAEF,IAAI,QAAQ,KAAK,OAAO,EAAE,CAAC;YACzB,aAAa,CAAC,OAAO,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;YACrC,EAAE,CAAC,SAAS,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QAClC,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF,8EAA8E;AAC9E,gBAAgB;AAChB,8EAA8E;AAE9E;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,OAA8B,EAAQ,EAAE;IACrE,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,OAAO,EAAE,OAAO,EAAE,EAAE,EAAE,GAAG,OAAO,CAAC;IAEtD,SAAS,CAAC;QACR,KAAK,EAAE,aAAa;QACpB,MAAM,EAAE,OAAO,CAAC,WAAW;QAC3B,OAAO,EAAE,KAAK,CAAC,YAAY;QAC3B,EAAE;KACH,CAAC,CAAC;IACH,SAAS,CAAC;QACR,KAAK,EAAE,cAAc;QACrB,MAAM,EAAE,OAAO,CAAC,YAAY;QAC5B,OAAO,EAAE,KAAK,CAAC,aAAa;QAC5B,EAAE;KACH,CAAC,CAAC;IAEH,IAAI,IAAI,KAAK,QAAQ,EAAE,CAAC;QACtB,cAAc,CAAC,KAAK,CAAC,YAAY,EAAE,KAAK,CAAC,aAAa,EAAE,EAAE,CAAC,CAAC;IAC9D,CAAC;IAED,MAAM,WAAW,GAAG,IAAI,CAAC,KAAK,CAAC,YAAY,EAAE,cAAc,CAAC,CAAC;IAC7D,aAAa,CAAC,WAAW,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;IACzC,EAAE,CAAC,SAAS,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;AACrC,CAAC,CAAC"}
+{"version":3,"file":"install.js","sourceRoot":"","sources":["../../src/installer/install.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AA6CjC,8EAA8E;AAC9E,YAAY;AACZ,8EAA8E;AAE9E,mDAAmD;AACnD,MAAM,aAAa,GAAG,CAAC,iBAAiB,EAAE,gBAAgB,EAAE,SAAS,CAAU,CAAC;AAEhF,oDAAoD;AACpD,MAAM,cAAc,GAAG;IACrB,iBAAiB;IACjB,gBAAgB;IAChB,SAAS;CACD,CAAC;AAEX,yEAAyE;AACzE,MAAM,YAAY,GAAG,oDAAoD,CAAC;AAE1E,8EAA8E;AAC9E,iBAAiB;AACjB,8EAA8E;AAE9E;;;;;GAKG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAAG,CAClC,IAAuB,EACC,EAAE;IAC1B,IAAI,IAAI,CAAC,QAAQ,CAAC,UAAU,CAAC;QAAE,OAAO,QAAQ,CAAC;IAC/C,IAAI,IAAI,CAAC,QAAQ,CAAC,SAAS,CAAC;QAAE,OAAO,OAAO,CAAC;IAE7C,OAAO,IAAI,CAAC;AACd,CAAC,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,uBAAuB,GAAG,CACrC,IAAqB,EACrB,OAAe,EACf,GAAW,EACO,EAAE;IACpB,MAAM,OAAO,GACX,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,OAAO,EAAE,SAAS,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,EAAE,SAAS,CAAC,CAAC;IAEtE,OAAO;QACL,YAAY,EAAE,IAAI,CAAC,OAAO,EAAE,UAAU,EAAE,QAAQ,CAAC;QACjD,aAAa,EAAE,IAAI,CAAC,OAAO,EAAE,QAAQ,EAAE,WAAW,CAAC;KACpD,CAAC;AACJ,CAAC,CAAC;AAEF,8EAA8E;AAC9E,mBAAmB;AACnB,8EAA8E;AAE9E,kEAAkE;AAClE,MAAM,aAAa,GAAG,CACpB,IAAY,EACZ,SAAiC,EAC3B,EAAE;IACR,IAAI,SAAS,CAAC,IAAI,CAAC,EAAE,CAAC;QACpB,MAAM,IAAI,KAAK,CAAC,qBAAqB,IAAI,EAAE,CAAC,CAAC;IAC/C,CAAC;AACH,CAAC,CAAC;AASF,6EAA6E;AAC7E,MAAM,SAAS,GAAG,CAAC,OAAyB,EAAQ,EAAE;IACpD,MAAM,EAAE,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,EAAE,EAAE,GAAG,OAAO,CAAC;IAC/C,EAAE,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IAElB,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QACrB,MAAM,GAAG,GAAG,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,CAAC;QAC/B,MAAM,IAAI,GAAG,IAAI,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC;QAEjC,IAAI,CAAC,EAAE,CAAC,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC;YACpB,MAAM,IAAI,KAAK,CAAC,0BAA0B,GAAG,EAAE,CAAC,CAAC;QACnD,CAAC;QAED,aAAa,CAAC,IAAI,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;QAClC,EAAE,CAAC,QAAQ,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC;IACzB,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF;;;;;;GAMG;AACH,MAAM,cAAc,GAAG,CACrB,YAAoB,EACpB,aAAqB,EACrB,EAAmB,EACb,EAAE;IACR,aAAa,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QAC7B,MAAM,OAAO,GAAG,IAAI,CAAC,YAAY,EAAE,IAAI,CAAC,CAAC;QACzC,MAAM,OAAO,GAAG,EAAE,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;QACrC,MAAM,QAAQ,GAAG,OAAO,CAAC,OAAO,CAC9B,YAAY,EACZ,CAAC,KAAK,EAAE,QAAgB,EAAE,EAAE;YAC1B,MAAM,MAAM,GAAG,IAAI,CAAC,aAAa,EAAE,QAAQ,CAAC,CAAC;YAE7C,OAAO,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,KAAK,CAAC;QACzD,CAAC,CACF,CAAC;QAEF,IAAI,QAAQ,KAAK,OAAO,EAAE,CAAC;YACzB,aAAa,CAAC,OAAO,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;YACrC,EAAE,CAAC,SAAS,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;QAClC,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC,CAAC;AAEF,8EAA8E;AAC9E,gBAAgB;AAChB,8EAA8E;AAE9E;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,OAA8B,EAAQ,EAAE;IACrE,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,OAAO,EAAE,OAAO,EAAE,EAAE,EAAE,GAAG,OAAO,CAAC;IAEtD,SAAS,CAAC;QACR,KAAK,EAAE,aAAa;QACpB,MAAM,EAAE,OAAO,CAAC,WAAW;QAC3B,OAAO,EAAE,KAAK,CAAC,YAAY;QAC3B,EAAE;KACH,CAAC,CAAC;IACH,SAAS,CAAC;QACR,KAAK,EAAE,cAAc;QACrB,MAAM,EAAE,OAAO,CAAC,YAAY;QAC5B,OAAO,EAAE,KAAK,CAAC,aAAa;QAC5B,EAAE;KACH,CAAC,CAAC;IAEH,IAAI,IAAI,KAAK,QAAQ,EAAE,CAAC;QACtB,cAAc,CAAC,KAAK,CAAC,YAAY,EAAE,KAAK,CAAC,aAAa,EAAE,EAAE,CAAC,CAAC;IAC9D,CAAC;IAED,MAAM,WAAW,GAAG,IAAI,CAAC,KAAK,CAAC,YAAY,EAAE,cAAc,CAAC,CAAC;IAC7D,aAAa,CAAC,WAAW,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC;IACzC,EAAE,CAAC,SAAS,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC;AACrC,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chief-clancy/plan",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "private": false,
   "description": "Implementation planner for Claude Code — decompose briefs into actionable plans",
   "author": "Alex Clapperton",

package/src/commands/approve-plan.md

@@ -1,6 +1,18 @@
 # /clancy:approve-plan
 
-Promote an approved Clancy plan to the ticket description. Accepts an optional ticket key argument (e.g. `/clancy:approve-plan PROJ-123`). When no key is provided, auto-selects the oldest planned-but-unapproved ticket.
+Approve a Clancy implementation plan. Behaviour depends on the install context and the argument:
+
+- **Local plan file:** `/clancy:approve-plan add-dark-mode-2` — write a `.clancy/plans/{stem}.approved` marker (with the plan's SHA-256 + approval timestamp) and update the source brief's row marker. The marker is the gate `/clancy:implement-from` checks before applying changes
+- **Board ticket:** `/clancy:approve-plan PROJ-123` — promote an approved plan from a ticket comment to the ticket description, edit the plan comment with an approval note, swap the ticket labels (`CLANCY_LABEL_PLAN` → `CLANCY_LABEL_BUILD`, both with sensible defaults), and — only if `CLANCY_STATUS_PLANNED` is configured — transition the ticket status. Requires board credentials. Runs in both standalone+board and terminal modes (the full pipeline is not required for the board transport flow itself; it is only required for downstream `/clancy:implement` to consume the result)
+- **No argument:** auto-select the oldest unapproved plan. In standalone mode this scans `.clancy/plans/`; in standalone+board / terminal mode it scans `.clancy/progress.txt` for board tickets
+
+The argument is **mode-aware**: in standalone+board / terminal modes, a plan-file lookup runs first (so `add-dark-mode-2` matches the local plan even if a board ticket happens to share the name). Plan stems win on collision.
+
+Examples:
+
+- `/clancy:approve-plan add-dark-mode-2` — approve a local plan from `/clancy:plan --from`
+- `/clancy:approve-plan PROJ-123` — promote a board plan to the ticket description
+- `/clancy:approve-plan` — auto-select the oldest pending approval
 
 Optional flags:
 
@@ -8,4 +20,4 @@ Optional flags:
 
 @.claude/clancy/workflows/approve-plan.md
 
-Follow the approve-plan workflow above. Fetch the plan comment, confirm with the user, append it to the ticket description, and transition the ticket to the implementation queue.
+Follow the approve-plan workflow above. Detect the install context, resolve the argument (plan-file stem or ticket key), and either write the local marker (Step 4a/4b) or run the existing board transport flow (Steps 5/5b/6). Do not implement anything — approval only.

package/src/workflows/approve-plan.md

@@ -2,57 +2,102 @@
 
 ## Overview
 
-Promote an approved Clancy plan from a ticket comment to the ticket description. The plan is appended below the existing description, never replacing it. After promotion, the ticket is transitioned to the implementation queue.
+Approve a Clancy implementation plan. Behaviour depends on the install context:
+
+- **Standalone mode** (no `.clancy/.env`): write a local `.clancy/plans/{stem}.approved` marker file with the plan's SHA-256 and approval timestamp. The marker is the gate `/clancy:implement-from` checks before applying changes
+- **Standalone+board mode** (`.clancy/.env` present, no full pipeline): with a board ticket key, run the existing comment-to-description transport flow; with a plan-file stem, write the local marker (board push lands in PR 9)
+- **Terminal mode** (full pipeline installed): existing behaviour — promote an approved plan from a ticket comment to the ticket description and transition the ticket to the implementation queue
 
 ---
 
 ## Step 1 — Preflight checks
 
-1. Check `.clancy/` exists and `.clancy/.env` is present. If not:
+### 1. Detect installation context
 
-   ```
-   .clancy/ not found. Run /clancy:init to set up Clancy first.
-   ```
+Check for `.clancy/.env`:
+
+- **Absent** → **standalone mode**. No board credentials. Board ticket arguments are blocked; only plan-file stems are accepted
+- **Present** → continue to `.clancy/clancy-implement.js` check below
+
+If `.clancy/.env` is present, check for `.clancy/clancy-implement.js`:
+
+- **Present** → **terminal mode**. Full Clancy pipeline installed
+- **Absent** → **standalone+board mode**. Board credentials available via `/clancy:board-setup`. Board ticket arguments work via the existing transport flow. Plan-file stems write the local marker
+
+### 2. Terminal-mode preflight (skip in standalone mode and standalone+board mode)
+
+If in **terminal mode** (`.clancy/.env` present AND `.clancy/clancy-implement.js` present):
+
+a. Source `.clancy/.env` and check board credentials are present.
+
+b. Check `CLANCY_ROLES` includes `planner` (or env var is unset, which indicates a global install where all roles are available). If `CLANCY_ROLES` is set but does not include `planner`:
+
+```
+The Planner role is not enabled. Add "planner" to CLANCY_ROLES in .clancy/.env or run /clancy:settings.
+```
+
+Stop.
+
+### 3. Standalone-mode preflight (only in standalone mode)
+
+If in **standalone mode** (no `.clancy/.env`), check that `.clancy/plans/` exists. If not:
 
-   Stop.
+```
+No local plans found. Run /clancy:plan --from .clancy/briefs/<brief>.md first.
+```
+
+Stop.
+
+### 4. Standalone+board preflight (only in standalone+board mode)
 
-2. Source `.clancy/.env` and check board credentials are present.
+If in **standalone+board mode**, source `.clancy/.env` for board credentials. Both plan-file stems and board ticket arguments are valid in this mode — Step 2 routes between them.
 
 ---
 
-## Step 2 — Parse argument / Resolve ticket
+## Step 2 — Resolve target
 
-### If no argument provided:
+The argument can be either a **plan-file stem** (e.g. `add-dark-mode-2`, matching a file at `.clancy/plans/{stem}.md`) or a **board ticket key** (e.g. `PROJ-123`, `#42`). Resolution depends on the installation mode detected in Step 1.
 
-1. Scan `.clancy/progress.txt` for entries matching `| PLAN |` or `| REVISED |` that have no subsequent `| APPROVE_PLAN |` for the same key.
-2. Sort by timestamp ascending (oldest first).
-3. If 0 found:
-   ```
-   No planned tickets awaiting approval. Run /clancy:plan first.
-   ```
-   Stop.
-4. If 1+ found, auto-select the oldest. Show:
-   ```
-   Auto-selected [{KEY}] {Title} (planned {date}). Promote this plan? [Y/n]
-   ```
-   To resolve the title, fetch the ticket from the board:
-   - **GitHub:** `GET /repos/$GITHUB_REPO/issues/$ISSUE_NUMBER` → use `.title`
-   - **Jira:** `GET $JIRA_BASE_URL/rest/api/3/issue/$KEY?fields=summary` → use `.fields.summary`
-   - **Linear:** `issues(filter: { identifier: { eq: "$KEY" } }) { nodes { title } }` → use `nodes[0].title`
-   - **Azure DevOps:** `GET https://dev.azure.com/$AZDO_ORG/$AZDO_PROJECT/_apis/wit/workitems/$ID?fields=System.Title&api-version=7.1` → use `.fields["System.Title"]`
-   - **Shortcut:** `GET https://api.app.shortcut.com/api/v3/stories/$STORY_ID` → use `.name`
-   - **Notion:** `GET https://api.notion.com/v1/pages/$PAGE_ID` → extract title from the `title` type property in `properties`
-     If fetching fails, show the key without a title: `Auto-selected [{KEY}] (planned {date}). Promote? [Y/n]`
-5. If user declines:
-   ```
-   Cancelled.
-   ```
-   Stop.
-6. Note that the user has already confirmed — set a flag to skip the Step 4 confirmation.
+### Standalone mode
+
+In standalone mode, the argument must be a plan-file stem. Board ticket keys are not valid here because there are no board credentials.
+
+**With argument:** look up `.clancy/plans/{arg}.md`. If the file does not exist:
+
+```
+Plan file not found: .clancy/plans/{arg}.md. Plan stems include the row number (e.g. `add-dark-mode-2`). Run /clancy:plan --list to see available plans.
+```
+
+Stop. Do not attempt to interpret the argument as a ticket key in standalone mode.
 
-### If argument provided:
+**No argument:** auto-select the oldest unapproved local plan.
 
-Validate the key format per board (case-insensitive):
+1. Scan `.clancy/plans/` for `.md` files
+2. **Filter to plan files only**: a file qualifies as a plan if it contains the literal heading `## Clancy Implementation Plan` (the marker written by Step 4f / 5a of `plan.md`). Files without this heading are scratch / notes / drafts and are silently skipped — they are not approvable
+3. For each remaining file, check whether a sibling `.approved` marker exists at the same path with the `.approved` suffix. The unapproved set is qualifying files with no sibling marker
+4. Sort the unapproved set by the `**Planned:**` header date (ascending). Tie-break by Plan ID (alphabetical ascending). Files with a missing or unparseable `**Planned:**` date sort **last** (after all dated plans), then by Plan ID alphabetically among themselves. Mirrors `plan.md` Step 8 inventory's deterministic ordering
+
+If the unapproved set is empty:
+
+```
+No local plans awaiting approval. Run /clancy:plan --from .clancy/briefs/<brief>.md first, or all existing plans are already approved.
+```
+
+Stop. If non-empty, auto-select the first entry. Confirm with the user (skipped in `--afk` mode):
+
+```
+Auto-selected {stem} (planned {date}). Approve this plan? [Y/n]
+```
+
+If declined: `Cancelled.` Stop.
+
+### Standalone+board and terminal modes
+
+In these modes the argument may be either a plan-file stem or a board ticket key. **Try plan-file lookup first (does `.clancy/plans/{arg}.md` exist?)**, then fall back to ticket-key validation. The plan stem wins over ticket key on collision (e.g. if `PROJ-123.md` exists in `.clancy/plans/` AND `PROJ-123` is a valid ticket key, the plan stem wins). Document the collision rule explicitly so users are not surprised.
+
+**With argument that resolves to a plan file:** continue to Step 4 (Confirm), then Step 4a (Write local marker). The board push offer for plan-file-stem mode is deferred to a future PR — for now the local marker is the only side effect.
+
+**With argument that does not resolve to a plan file:** validate as a ticket key per the board configured in `.clancy/.env` (case-insensitive):
 
 - **GitHub:** `#\d+` or bare number
 - **Jira:** `[A-Za-z][A-Za-z0-9]+-\d+` (e.g. `PROJ-123` or `proj-123`)
@@ -69,7 +114,34 @@ Invalid ticket key: {input}. Expected format: {board-specific example}.
 
 Stop.
 
-Proceed with that key.
+If valid: proceed with that key. The board transport flow runs (Steps 3-7 below) — this is the existing behaviour, unchanged from before PR 7b.
+
+**No argument:**
+
+- **Standalone+board and terminal:** scan `.clancy/progress.txt` for entries matching `| PLAN |` or `| REVISED |` that have no subsequent `| APPROVE_PLAN |` for the same key. Sort by timestamp ascending (oldest first).
+- If 0 found:
+  ```
+  No planned tickets awaiting approval. Run /clancy:plan first.
+  ```
+  Stop.
+- If 1+ found, auto-select the oldest. Show:
+  ```
+  Auto-selected [{KEY}] {Title} (planned {date}). Promote this plan? [Y/n]
+  ```
+  To resolve the title, fetch the ticket from the board:
+  - **GitHub:** `GET /repos/$GITHUB_REPO/issues/$ISSUE_NUMBER` → use `.title`
+  - **Jira:** `GET $JIRA_BASE_URL/rest/api/3/issue/$KEY?fields=summary` → use `.fields.summary`
+  - **Linear:** `issues(filter: { identifier: { eq: "$KEY" } }) { nodes { title } }` → use `nodes[0].title`
+  - **Azure DevOps:** `GET https://dev.azure.com/$AZDO_ORG/$AZDO_PROJECT/_apis/wit/workitems/$ID?fields=System.Title&api-version=7.1` → use `.fields["System.Title"]`
+  - **Shortcut:** `GET https://api.app.shortcut.com/api/v3/stories/$STORY_ID` → use `.name`
+  - **Notion:** `GET https://api.notion.com/v1/pages/$PAGE_ID` → extract title from the `title` type property in `properties`
+    If fetching fails, show the key without a title: `Auto-selected [{KEY}] (planned {date}). Promote? [Y/n]`
+- If user declines:
+  ```
+  Cancelled.
+  ```
+  Stop.
+- Note that the user has already confirmed — set a flag to skip the Step 4 confirmation.
 
 ---
 
@@ -270,6 +342,129 @@ If the user declines (interactive only), stop:
 Cancelled. No changes made.
 ```
 
+For **plan-file stem mode** (Step 2 resolved the argument to a local plan file), the summary shows the plan stem instead of `[{KEY}] {Title}`:
+
+```
+Clancy — Approve Plan (local)
+
+{stem}
+Size: {S/M/L} | {N} affected files
+Planned: {date from plan}
+
+Approve this plan? [Y/n]
+```
+
+After confirmation in plan-file stem mode, jump to Step 4a (local marker write). For board ticket key mode, continue to Step 5 below.
+
+---
+
+## Step 4a — Write local marker
+
+Run this step instead of Steps 5, 5b, 6 when the resolved argument was a plan-file stem (standalone mode, or standalone+board / terminal mode where Step 2 found a matching plan file). Write a `.clancy/plans/{stem}.approved` marker that gates `/clancy:implement-from`.
+
+### Compute the SHA-256
+
+**Order of operations** (do these in order, exactly):
+
+1. Read the plan file at `.clancy/plans/{stem}.md` from disk into memory as bytes.
+2. Compute the SHA-256 hash of those bytes — no normalisation (no line-ending fix, no trailing-whitespace strip, no BOM removal). Hex-encode lowercase.
+3. **Then** (only after the hash is computed) open the `.approved` marker for exclusive create as described below.
+
+The `.approved` file is **never** included in the hash — only `.clancy/plans/{stem}.md` is hashed, and only its on-disk byte content at the moment of step 1. PR 8's `/clancy:implement-from` re-reads the same plan file, hashes it the same way, and compares to the `sha256=` value stored in the marker. Any divergence (re-edit, line-ending change, trailing whitespace tweak) blocks implementation until re-approval.
+
+### Write the marker file with O_EXCL
+
+Open `.clancy/plans/{stem}.approved` for **exclusive create** (Node `fs.openSync(path, 'wx')`, equivalent to `open(2)` with `O_EXCL`). Write the marker body as plain text:
+
+```
+sha256={hex sha256 of the plan file at approval time}
+approved_at={ISO 8601 UTC timestamp, e.g. 2026-04-08T22:30:00Z}
+```
+
+Two `key=value` lines, each terminated with `\n`. No JSON, no extra whitespace, no comments. PR 8 parses this with a tolerant `^(sha256|approved_at)=(.+)$` regex per line.
+
+### Handle EEXIST (already-approved)
+
+If the exclusive create fails with `EEXIST`, the marker already exists — the plan was previously approved. Stop with:
+
+```
+Plan already approved: {stem}
+Marker: .clancy/plans/{stem}.approved
+
+To re-approve (e.g. after revising the plan):
+  Delete .clancy/plans/{stem}.approved manually, then re-run /clancy:approve-plan {stem}
+```
+
+A `--fresh` flag for `/clancy:approve-plan` is not implemented in this release. Manual deletion is the supported re-approval path.
+
+### Marker is the gate for /clancy:implement-from
+
+The `.approved` marker is the gate `/clancy:implement-from` checks before applying changes. PR 8 reads the marker, hashes the current plan file, and compares to the stored `sha256`. Match → proceed; mismatch → block with a "plan changed since approval" error. This is why the SHA must be computed over the plan file content (not just touched as an empty file).
+
+### After writing the marker
+
+After the marker is written successfully, update the source brief file's marker comment (Step 4b below), then jump to Step 7 (Confirm and log). Steps 5, 5b, and 6 (board transport) are skipped entirely in plan-file stem mode.
+
+---
+
+## Step 4b — Update brief marker (best-effort)
+
+After Step 4a writes the local plan marker, update the source brief file's planned-rows marker so `/clancy:plan --list` and the brief's display logic know which rows have been approved. This step is best-effort: any failure here logs a warning but does NOT roll back the `.clancy/plans/{stem}.approved` marker.
+
+### Resolve the source brief filename
+
+Read the plan file at `.clancy/plans/{stem}.md` and extract the `**Brief:**` header line (e.g. `**Brief:** 2026-04-01-add-dark-mode.md`). The value is the brief filename relative to `.clancy/briefs/`. If the line is absent or empty, warn and skip the rest of Step 4b:
+
+```
+⚠ Plan {stem} has no **Brief:** header — cannot update brief marker. Continuing without brief update.
+```
+
+### Resolve the row number
+
+Extract the row number from the plan file's `**Row:**` header line (e.g. `**Row:** #2 — Add toggle component`). The number after `#` and before the em-dash (U+2014, U+2013, or hyphen) is the row. If absent, warn and skip Step 4b.
+
+### Find and update the marker
+
+Open `.clancy/briefs/{brief-filename}` and find the marker comment matching this tolerant regex (line-anchored, allows missing-or-present `approved:` prefix, allows arbitrary whitespace):
+
+```
+^<!--\s*(?:approved:([\d,]*)\s+)?planned:([\d,]+)\s*-->\s*$
+```
+
+This matches all of:
+
+- `<!-- planned:1,2,3 -->` (no approved prefix yet — current state from PR 6b)
+- `<!-- approved:1 planned:1,2,3 -->` (PR 7b adds the approved prefix)
+- `<!-- approved: planned:1,2,3 -->` (empty approved list — should not happen but handle gracefully)
+- `<!--planned:1,2,3-->` (no surrounding spaces — hand-edited)
+
+If no marker line matches, warn and skip — do not synthesise a marker. The brief should already have one written by `/clancy:plan --from`.
+
+**Reversed-order markers** (`<!-- planned:1,2 approved:1 -->` — `planned:` first, `approved:` second) do NOT match this regex and fall through to the warn-and-skip branch. The canonical ordering is enforced on every write, so a brief that drifts into reversed order requires manual correction. If you see the warning "no marker found" but the brief clearly has a marker, check the order — `approved:` must come before `planned:`.
+
+**Code-fence false positives:** the regex is line-anchored but does NOT track fenced-code-block context. If a brief file embeds an example marker inside a triple-backtick block (e.g. documentation about how markers work), the regex may match the example. The first match wins, so authors should keep the real marker as the first marker line in the file. The `## Feedback` detector in `plan.md` Step 3a uses code-fence-aware parsing for the same reason — apply that pattern manually if a brief becomes complex enough to need it.
+
+If a marker matches, parse the existing `approved:` and `planned:` row lists. Add the current row number to the `approved:` list (deduped, sorted ascending). Reconstruct the marker with the canonical ordering: `approved:` first, `planned:` second, single space between fields and inside the comment. Example:
+
+- Before: `<!-- planned:1,2,3 -->`, current row = `2`
+- After: `<!-- approved:2 planned:1,2,3 -->`
+- Before: `<!-- approved:1 planned:1,2,3 -->`, current row = `2`
+- After: `<!-- approved:1,2 planned:1,2,3 -->`
+
+Write the updated brief file back. The read-modify-write is not concurrency-safe — running multiple `/clancy:approve-plan` commands against the same brief in parallel may produce duplicate or missing entries. Single-user local flow is assumed (mirrors the concurrency note in [`plan.md` Step 3a](./plan.md)).
+
+### Best-effort failure handling
+
+If any step in 4b fails (file not found, marker not found, write error, regex mismatch), log a warning but do NOT roll back the `.clancy/plans/{stem}.approved` marker. The local marker is the source of truth — the brief marker is metadata for display and `/clancy:plan --list`. Example warning:
+
+```
+⚠ Failed to update brief marker for {stem}: {reason}
+The plan is still approved. The .clancy/plans/{stem}.approved marker is in place.
+You can manually update .clancy/briefs/{brief}.md if needed.
+```
+
+After Step 4b completes (successfully or with a warning), jump to Step 7 (Confirm and log). Skip Steps 5, 5b, and 6 entirely.
+
 ---
 
 ## Step 5 — Update ticket description
@@ -870,7 +1065,9 @@ Could not transition ticket. Move it manually to your implementation queue.
 
 ## Step 7 — Confirm and log
 
-On success, display a board-specific message:
+**Mode gate (read first):** if Steps 4a/4b ran (the resolved argument was a plan-file stem), skip the entire "board-specific success message" and "board-mode progress.txt entry" blocks below and jump straight to the **Local mode (Step 4a / 4b path)** subsection further down. The board-success-message text only applies when Steps 5/5b/6 ran for a board ticket key. Do NOT render both — exactly one branch executes per approval.
+
+On success in **board ticket mode**, display a board-specific message:
 
 **GitHub:**
 
@@ -944,18 +1141,50 @@ Plan promoted to page content. Move the page to your implementation queue for /c
 "Book 'em, Lou." -- The ticket is ready for /clancy:implement.
 ```
 
-Append to `.clancy/progress.txt`:
+Append to `.clancy/progress.txt` for **board mode**:
 
 ```
 YYYY-MM-DD HH:MM | {KEY} | APPROVE_PLAN | —
 ```
 
-On failure:
+On board failure:
 
 ```
 Failed to update description for [{KEY}]. Check your board permissions.
 ```
 
+### Local mode (Step 4a / 4b path)
+
+For **plan-file stem mode** (Step 4a wrote a `.approved` marker), display:
+
+```
+Clancy — Approve Plan (local)
+
+✅ Approved {stem}
+   Marker: .clancy/plans/{stem}.approved
+   sha256: {first 12 hex chars}…
+
+Next: /clancy:implement-from .clancy/plans/{stem}.md
+
+"Book 'em, Lou."
+```
+
+**Conditional Brief line:** if Step 4b actually resolved AND updated the brief marker (i.e. the `**Brief:**`/`**Row:**` headers were present, the marker regex matched, and the write succeeded), insert this line between `sha256:` and the blank line above `Next:`:
+
+```
+   Brief:  .clancy/briefs/{brief}.md (row #{N} marked approved)
+```
+
+Do NOT print the Brief line when Step 4b warned and skipped (missing headers, no matching marker, or write error). In that case, also print the warning that Step 4b emitted under the success block but do not change the exit status — the plan IS approved regardless of whether the brief marker was updated.
+
+Append to `.clancy/progress.txt`:
+
+```
+YYYY-MM-DD HH:MM | {stem} | LOCAL_APPROVE_PLAN | sha256={first 12 hex}
+```
+
+The `LOCAL_APPROVE_PLAN` token mirrors the `LOCAL_PLAN` / `LOCAL_REVISED` convention used by `/clancy:plan --from` (see [`plan.md` Step 6](./plan.md)). PR 8's `/clancy:implement-from` does NOT scan progress.txt for approval state — it reads the `.clancy/plans/{stem}.approved` marker directly. The log entry is for human audit only.
+
 ---
 
 ## Notes

package/src/workflows/plan.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Fetch backlog tickets from the board, explore the codebase, and generate structured implementation plans. In board mode, plans are posted as comments on the ticket for human review. With `--from`, plans from local brief files are saved to `.clancy/plans/`, with an optional board comment when credentials are available. Does not implement anything — planning only. In **terminal mode**, use `/clancy:approve-plan` to promote plans. In **standalone mode** or **standalone+board mode**, install the full pipeline (`npx chief-clancy`) to promote plans.
+Fetch backlog tickets from the board, explore the codebase, and generate structured implementation plans. In board mode, plans are posted as comments on the ticket for human review. With `--from`, plans from local brief files are saved to `.clancy/plans/`, with an optional board comment when credentials are available. Does not implement anything — planning only. Use `/clancy:approve-plan` to approve plans in any install mode — it ships with this package, writes a local `.approved` marker for plan-file stems, and runs the board transport flow for ticket keys only when board credentials are available.
 
 ---
 
@@ -24,7 +24,7 @@ Check for `.clancy/.env`:
 If `.clancy/.env` is present, check for `.clancy/clancy-implement.js`:
 
 - **Present** → **terminal mode**. Full Clancy pipeline installed.
-- **Absent** → **standalone+board mode**. Board credentials available via `/clancy:board-setup`. Board ticket mode works. Step 5 works. But `/clancy:approve-plan` is not available (requires full pipeline).
+- **Absent** → **standalone+board mode**. Board credentials available via `/clancy:board-setup`. Board ticket mode works. Step 5 works. `/clancy:approve-plan` also works in this mode — it ships with the plan package and runs the board transport flow for ticket keys or writes a local `.approved` marker for plan-file stems.
 
 ### 2. Terminal-mode preflight (skip in standalone mode and standalone+board mode)
 
@@ -822,7 +822,7 @@ Write the plan in this exact template:
 
 ---
 
-_Generated by [Clancy](https://github.com/Pushedskydiver/chief-clancy). To request changes: comment on this ticket, then re-run `/clancy:plan` to revise. To start over: `/clancy:plan --fresh`. To approve: `/clancy:approve-plan {KEY}` (requires full pipeline — `npx chief-clancy`)._
+_Generated by [Clancy](https://github.com/Pushedskydiver/chief-clancy). To request changes: comment on this ticket, then re-run `/clancy:plan` to revise. To start over: `/clancy:plan --fresh`. To approve: `/clancy:approve-plan {KEY}`._
 ```
 
 **If re-planning with feedback**, prepend a section before Summary:
@@ -885,7 +885,7 @@ Replace the `**Ticket:** [{KEY}] {Title}` line from the board template with `**S
 **Local plan footer:** Replace the board-specific footer with:
 
 ```
-_Generated by [Clancy](https://github.com/Pushedskydiver/chief-clancy). To request changes: add a ## Feedback section to this file, then re-run `/clancy:plan --from {path}` to revise. To start over: `/clancy:plan --fresh --from {path}`. To approve: install the full pipeline — npx chief-clancy._
+_Generated by [Clancy](https://github.com/Pushedskydiver/chief-clancy). To request changes: add a ## Feedback section to this file, then re-run `/clancy:plan --from {path}` to revise. To start over: `/clancy:plan --fresh --from {path}`. To approve: `/clancy:approve-plan {plan-id}`._
 ```
 
 **Re-planning:** If `--fresh` was used, the existing plan file is overwritten (same slug + row number = same filename).
@@ -1052,8 +1052,7 @@ Planned {N} ticket(s):
   ⏭️  [{KEY4}] {Title} — not a codebase change
 
 Plans written to your board. After review:
-  Terminal mode: /clancy:approve-plan {KEY}
-  Standalone: install the full pipeline — npx chief-clancy
+  /clancy:approve-plan {KEY}
 
 "Let me dust this for prints..."
 ```
@@ -1068,7 +1067,7 @@ Single row:
 
   ✅ Saved to .clancy/plans/{slug}-{row-number}.md
 
-  To approve: install the full pipeline — npx chief-clancy
+  To approve: /clancy:approve-plan {slug}-{row-number}
 
 "Let me dust this for prints..."
 ```
@@ -1083,7 +1082,7 @@ Multi-row (`--afk`):
   ✅ Row 2: {title} — Saved to .clancy/plans/{slug}-2.md
   ⏭️  Row 3: {title} — already planned
 
-  To approve: install the full pipeline — npx chief-clancy
+  To approve: /clancy:approve-plan {slug}-{row-number} (or use /clancy:plan --list to see all plans)
 
 "Let me dust this for prints..."
 ```
@@ -1101,35 +1100,47 @@ Scan `.clancy/plans/` for all `.md` files. For each file, parse the local plan h
 - **Row** — value of the `**Row:**` line (e.g. `#2 — Add toggle component`). Display `?` if absent or empty.
 - **Source** — value of the `**Source:**` line (the brief's Source field). Display `?` if absent or empty.
 - **Planned** — value of the `**Planned:**` line (the YYYY-MM-DD planned date). Display `?` if absent or unparseable as a date.
-- **Status** — for now this is always `Planned`. Reserved for `/clancy:approve-plan` (a future PR) which will write a sibling `.approved` marker file (e.g. `.clancy/plans/add-dark-mode-2.approved`). When that marker exists for a given plan, Status becomes `Approved`. The column is included in the listing today so the format will not change when approval markers ship.
+- **Status** — derived live from the sibling `.approved` marker written by `/clancy:approve-plan` (PR 7b). The reader is filesystem-only — no `.clancy/.env` or board access required. For each plan file, follow this procedure (every numbered step either branches to a verdict or feeds the next step):
+  1. Check whether `.clancy/plans/{plan-id}.approved` exists. If marker absent → `Planned` (verdict)
+  2. Marker exists. Read and validate its `sha256=` line (the marker body is two `key=value` lines: `sha256={hex}` and `approved_at={ISO 8601}`) AND hash the current plan file's bytes the same way `/clancy:approve-plan` Step 4a does (lowercase hex SHA-256, no normalisation, no line-ending fix)
+  3. If the marker exists but is malformed, missing its `sha256=` line, has a non-hex or wrong-length `sha256` value, or otherwise cannot be parsed deterministically → `Stale (re-approve)` (verdict). Print a hint after the table: `Marker .clancy/plans/{plan-id}.approved is malformed. Delete it and re-run /clancy:approve-plan {plan-id} to recreate.` Folding this into `Stale` (rather than inventing a new state) keeps the inventory deterministic — the user's remediation is the same as for a hash drift: delete the marker and re-approve
+  4. If the marker's valid `sha256` matches the current plan file's hash → `Approved` (verdict)
+  5. If the marker exists and its valid `sha256` differs from the current hash → `Stale (re-approve)` (verdict) — the plan file was edited after approval. `/clancy:implement-from` (PR 8) will refuse to run against a stale plan until it is re-approved
+
+  A future `Implemented` state — derived from `LOCAL_IMPLEMENT` entries in `.clancy/progress.txt` — will be added by PR 8. Today the inventory shows three states (`Planned`, `Approved`, `Stale (re-approve)`), with malformed `.approved` markers folded into `Stale (re-approve)`; the table format is stable so PR 8's addition will be a one-line extension.
 
 A field is considered missing if the line is absent or its value is empty after the colon. Plans missing all expected fields are still listed (with `?` placeholders) so the user can find and clean them up.
 
 **Sort:** by `**Planned**` date, newest first. Tie-break on same date by Plan ID, alphabetical ascending. Files with a missing or unparseable date sort last (after all dated plans), and tie-break among themselves by Plan ID alphabetical ascending. The sort must be deterministic across runs.
 
-Display:
+**Summary line:** after the table, print one line in the format `{N} local plan(s). {A} approved, {S} stale, {P} planned.` where the counts match the rows above. Omit zero-count states for brevity (e.g. `3 local plan(s). 2 approved, 1 planned.` if no plans are stale). A `Stale (re-approve)` row means the plan file was edited after approval — re-running `/clancy:approve-plan {plan-id}` (after deleting the existing marker) will refresh the SHA.
+
+Display the inventory as a pipe-delimited table so each Status value is unambiguous to scan and parse:
 
 ```
 Clancy — Plans
 ================================================================
 
-  [1] add-dark-mode-2          2026-04-08  Planned  Row #2 — Add toggle component  Brief: 2026-04-01-add-dark-mode.md  Source: #50
-  [2] add-dark-mode-1          2026-04-07  Planned  Row #1 — Wire theme context    Brief: 2026-04-01-add-dark-mode.md  Source: #50
-  [3] customer-portal-3        2026-04-05  Planned  Row #3 — Billing page          Brief: 2026-03-28-customer-portal.md  Source: PROJ-200
+  | # | Plan ID            | Planned    | Status              | Row                              | Brief                              | Source    |
+  |---|--------------------|------------|---------------------|----------------------------------|------------------------------------|-----------|
+  | 1 | add-dark-mode-2    | 2026-04-08 | Approved            | #2 — Add toggle component        | 2026-04-01-add-dark-mode.md        | #50       |
+  | 2 | add-dark-mode-1    | 2026-04-07 | Stale (re-approve)  | #1 — Wire theme context          | 2026-04-01-add-dark-mode.md        | #50       |
+  | 3 | customer-portal-3  | 2026-04-05 | Planned             | #3 — Billing page                | 2026-03-28-customer-portal.md      | PROJ-200  |
 
-3 local plan(s).
+3 local plan(s). 1 approved, 1 stale, 1 planned.
 
-To revise: add a `## Feedback` section to the plan file, then re-run /clancy:plan --from <brief>.
-To start over: /clancy:plan --fresh --from <brief>.
-To approve: install the full pipeline — npx chief-clancy.
+To approve a plan:           /clancy:approve-plan {plan-id}
+To re-approve a stale plan:  delete .clancy/plans/{plan-id}.approved, then /clancy:approve-plan {plan-id}
+To revise:                   add a `## Feedback` section to the plan file, then re-run /clancy:plan --from {brief}
+To start over:               /clancy:plan --fresh --from {brief}
 ```
 
-The first column in the listing is the Plan ID (filename without `.md`), not the brief slug.
+The first column (after `#`) is the Plan ID (filename without `.md`), not the brief slug. Pipe-table format is intentional — Status values like `Stale (re-approve)` contain spaces, and a column-aligned space-delimited layout would make them ambiguous to read.
 
 If `.clancy/plans/` does not exist or contains no `.md` files:
 
 ```
-No plans found. Run /clancy:plan --from .clancy/briefs/<brief>.md to create one.
+No plans found. Run /clancy:plan --from .clancy/briefs/{brief}.md to create one.
 ```
 
 Stop after display. The `--list` step never logs to `.clancy/progress.txt` and never modifies any file — it is purely a read-only inventory view of the local plans directory.

package/src/workflows/workflows.test.ts

@@ -595,13 +595,75 @@ describe('plan inventory step', () => {
     expect(content).toContain(
       '**Plan ID** — the plan filename minus the `.md` extension',
     );
-    expect(content).toContain('first column in the listing is the Plan ID');
+    expect(content).toContain('first column (after `#`) is the Plan ID');
   });
 
-  it('reserves a Status column for the future approve-plan PR', () => {
+  it('Status column reads sibling .approved marker for live state', () => {
     expect(content).toContain('**Status**');
-    expect(content).toContain('always `Planned`');
-    expect(content).toContain('`.approved` marker');
+    expect(content).toContain('sibling `.approved` marker');
+  });
+
+  it('Status is Planned when no marker exists', () => {
+    expect(content).toContain('marker absent → `Planned`');
+  });
+
+  it('Status is Approved when marker sha256 matches the current plan file', () => {
+    expect(content).toContain('sha256` matches the current plan file');
+    expect(content).toContain('→ `Approved`');
+  });
+
+  it('Status is Stale (re-approve) when marker sha256 drifts from the plan file', () => {
+    expect(content).toContain('Stale (re-approve)');
+    expect(content).toContain('sha256` differs');
+  });
+
+  it('inventory example shows at least one Approved row', () => {
+    // Match a pipe-delimited table cell on both sides (literal `|`s with
+    // tolerant whitespace) so the test proves the example output is in the
+    // pipe-delimited table format, not just that the word `Approved` happens
+    // to appear in nearby prose.
+    expect(content).toMatch(/\|\s*Approved\s*\|/);
+  });
+
+  it('inventory example shows at least one Stale row', () => {
+    expect(content).toMatch(/\|\s*Stale \(re-approve\)\s*\|/);
+  });
+
+  it('inventory example still shows at least one Planned row', () => {
+    expect(content).toMatch(/\|\s*Planned\s*\|/);
+  });
+
+  it('inventory documents the summary line format and zero-count omission', () => {
+    expect(content).toContain('Summary line');
+    expect(content).toContain(
+      '{N} local plan(s). {A} approved, {S} stale, {P} planned.',
+    );
+    expect(content).toContain('Omit zero-count states');
+  });
+
+  it('explains that Stale means the plan was edited after approval', () => {
+    expect(content).toContain('plan file was edited after approval');
+  });
+
+  it('reserves an Implemented state for PR 8 without claiming it exists today', () => {
+    expect(content).toContain('Implemented');
+    expect(content).toContain('PR 8');
+    expect(content).toContain('shows three states');
+  });
+
+  it('folds malformed .approved markers into Stale (re-approve)', () => {
+    expect(content).toContain('marker exists but is malformed');
+    expect(content).toContain('non-hex or wrong-length');
+    expect(content).toContain('cannot be parsed deterministically');
+  });
+
+  it('uses {plan-id} placeholder consistently in the footer (no <plan-id>)', () => {
+    expect(content).not.toContain('<plan-id>');
+    expect(content).toContain('/clancy:approve-plan {plan-id}');
+  });
+
+  it('inventory footer hint points at /clancy:approve-plan', () => {
+    expect(content).toContain('/clancy:approve-plan');
   });
 
   it('sort is deterministic with explicit tie-breakers', () => {
@@ -640,3 +702,302 @@ describe('plan inventory step', () => {
     );
   });
 });
+
+// ---------------------------------------------------------------------------
+// approve-plan.md content assertions (PR 7b — standalone adaptation)
+// ---------------------------------------------------------------------------
+
+describe('approve-plan three-state preflight', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('Step 1 detects all three installation states', () => {
+    expect(content).toContain('standalone mode');
+    expect(content).toContain('standalone+board mode');
+    expect(content).toContain('terminal mode');
+  });
+
+  it('Step 1 checks .clancy/.env presence for state detection', () => {
+    expect(content).toContain('.clancy/.env');
+  });
+
+  it('Step 1 checks clancy-implement.js for terminal detection', () => {
+    expect(content).toContain('clancy-implement.js');
+  });
+
+  it('Step 1 does not hard-stop on missing .clancy/.env', () => {
+    expect(content).not.toContain(
+      '.clancy/ not found. Run /clancy:init to set up Clancy first.',
+    );
+  });
+
+  it('CLANCY_ROLES check only runs in terminal mode', () => {
+    expect(content).toContain('Terminal-mode preflight');
+    expect(content).toContain(
+      'skip in standalone mode and standalone+board mode',
+    );
+  });
+
+  it('standalone mode requires .clancy/plans/ to exist', () => {
+    expect(content).toContain('.clancy/plans/');
+  });
+});
+
+describe('approve-plan dual-mode resolver (Step 2)', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('Step 2 routes between plan-file stem and ticket key based on mode', () => {
+    expect(content).toContain('plan-file stem');
+    expect(content).toContain('ticket key');
+  });
+
+  it('standalone mode only accepts plan-file stems', () => {
+    expect(content).toContain(
+      'In standalone mode, the argument must be a plan-file stem',
+    );
+  });
+
+  it('standalone+board and terminal modes try plan-file lookup first', () => {
+    expect(content).toContain(
+      'Try plan-file lookup first (does `.clancy/plans/{arg}.md` exist?)',
+    );
+  });
+
+  it('plan stem wins over ticket key on collision', () => {
+    expect(content).toContain('plan stem wins over ticket key');
+  });
+
+  it('standalone no-arg auto-selects oldest unapproved plan', () => {
+    expect(content).toContain('auto-select the oldest unapproved local plan');
+    expect(content).toContain('no sibling marker');
+  });
+
+  it('standalone no-arg filters scan to actual plan files', () => {
+    expect(content).toContain('## Clancy Implementation Plan');
+    expect(content).toContain('Filter to plan files only');
+  });
+
+  it('standalone no-arg sorts files with missing/unparseable date last', () => {
+    expect(content).toContain('missing or unparseable `**Planned:**` date');
+    expect(content).toContain('sort **last**');
+  });
+
+  it('preserves existing terminal-mode no-arg progress.txt scan', () => {
+    expect(content).toContain('.clancy/progress.txt');
+    expect(content).toContain('| PLAN |');
+  });
+
+  it('errors clearly if standalone arg is not a plan-file stem', () => {
+    expect(content).toContain('Plan file not found:');
+  });
+
+  it('errors if standalone has no plans and no arg', () => {
+    expect(content).toContain('No local plans awaiting approval');
+  });
+});
+
+describe('approve-plan local marker (Step 4a)', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('defines Step 4a — Write local marker', () => {
+    expect(content).toContain('## Step 4a — Write local marker');
+  });
+
+  it('Step 4a runs only when the resolved arg was a plan-file stem', () => {
+    expect(content).toContain(
+      'Run this step instead of Steps 5, 5b, 6 when the resolved argument was a plan-file stem',
+    );
+  });
+
+  it('writes marker to .clancy/plans/{stem}.approved', () => {
+    expect(content).toContain('.clancy/plans/{stem}.approved');
+  });
+
+  it('uses race-safe exclusive create (O_EXCL / wx)', () => {
+    expect(content).toContain('exclusive create');
+    expect(content).toContain('O_EXCL');
+    expect(content).toContain('wx');
+  });
+
+  it('marker body contains sha256 and approved_at fields', () => {
+    expect(content).toContain('sha256=');
+    expect(content).toContain('approved_at=');
+  });
+
+  it('sha256 is computed over the plan file content at approval time', () => {
+    expect(content).toContain('SHA-256');
+    expect(content).toContain('Order of operations');
+    expect(content).toContain(
+      'Read the plan file at `.clancy/plans/{stem}.md` from disk',
+    );
+  });
+
+  it('SHA hash is never computed over the .approved marker itself', () => {
+    expect(content).toContain('`.approved` file is **never** included');
+  });
+
+  it('approved_at is ISO 8601 UTC', () => {
+    expect(content).toContain('ISO 8601');
+  });
+
+  it('handles EEXIST as already-approved', () => {
+    expect(content).toContain('EEXIST');
+    expect(content).toContain('already approved');
+  });
+
+  it('explains the marker is the gate for /clancy:implement-from', () => {
+    expect(content).toContain('/clancy:implement-from');
+    expect(content).toContain('gate');
+  });
+
+  it('after writing the marker, Step 4a jumps to Step 7 (log) and skips board flow', () => {
+    expect(content).toContain('jump to Step 7');
+  });
+});
+
+describe('approve-plan brief-marker update (Step 4b)', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('defines Step 4b — Update brief marker', () => {
+    expect(content).toContain('## Step 4b — Update brief marker');
+  });
+
+  it('resolves brief filename from the plan **Brief:** header', () => {
+    expect(content).toContain('**Brief:**');
+    expect(content).toContain('extract the `**Brief:**` header line');
+  });
+
+  it('resolves row number from the plan **Row:** header', () => {
+    expect(content).toContain('**Row:**');
+  });
+
+  it('uses a tolerant line-anchored regex with optional approved prefix', () => {
+    expect(content).toContain(
+      '^<!--\\s*(?:approved:([\\d,]*)\\s+)?planned:([\\d,]+)\\s*-->\\s*$',
+    );
+  });
+
+  it('canonical ordering puts approved before planned', () => {
+    expect(content).toContain('approved:` first, `planned:` second');
+  });
+
+  it('handles existing planned-only marker (PR 6b state)', () => {
+    expect(content).toContain('<!-- planned:1,2,3 -->');
+  });
+
+  it('handles existing approved+planned marker', () => {
+    expect(content).toContain('<!-- approved:1 planned:1,2,3 -->');
+  });
+
+  it('handles unspaced marker variant', () => {
+    expect(content).toContain('<!--planned:1,2,3-->');
+  });
+
+  it('best-effort: failure does not roll back the .approved marker', () => {
+    expect(content).toContain('does NOT roll back');
+    expect(content).toContain('local marker is the source of truth');
+  });
+
+  it('warns and skips when **Brief:** header is absent', () => {
+    expect(content).toContain('cannot update brief marker');
+  });
+
+  it('documents concurrency-not-safe nature of the read-modify-write', () => {
+    expect(content).toContain('not concurrency-safe');
+  });
+
+  it('documents reversed-order brief markers fall through to warn-and-skip', () => {
+    expect(content).toContain('Reversed-order markers');
+    expect(content).toContain('do NOT match this regex');
+  });
+
+  it('documents code-fence false-positive risk', () => {
+    expect(content).toContain('Code-fence false positives');
+    expect(content).toContain('first match wins');
+  });
+});
+
+describe('approve-plan local-mode log + summary (Step 7)', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('uses LOCAL_APPROVE_PLAN log token for plan-file stem mode', () => {
+    expect(content).toContain('LOCAL_APPROVE_PLAN');
+  });
+
+  it('local log entry includes the sha256 prefix for audit', () => {
+    expect(content).toContain('sha256={first 12 hex}');
+  });
+
+  it('local success summary points to /clancy:implement-from', () => {
+    expect(content).toContain(
+      'Next: /clancy:implement-from .clancy/plans/{stem}.md',
+    );
+  });
+
+  it('preserves board-mode APPROVE_PLAN log entry', () => {
+    expect(content).toContain('| {KEY} | APPROVE_PLAN | —');
+  });
+
+  it('Step 7 has an explicit mode gate so local and board branches do not double-render', () => {
+    expect(content).toContain('Mode gate (read first)');
+    expect(content).toContain(
+      'Do NOT render both — exactly one branch executes per approval',
+    );
+  });
+
+  it('plan-file-not-found error hints at the row-number convention', () => {
+    expect(content).toContain('Plan stems include the row number');
+    expect(content).toContain('Run /clancy:plan --list');
+  });
+
+  it('EEXIST advice points at manual deletion, not a non-existent --fresh flag', () => {
+    expect(content).toContain('Delete .clancy/plans/{stem}.approved manually');
+    expect(content).not.toContain('/clancy:approve-plan --fresh');
+  });
+});
+
+describe('approve-plan board mode preserved unchanged', () => {
+  const content = readFileSync(
+    new URL('approve-plan.md', import.meta.url),
+    'utf8',
+  );
+
+  it('keeps Jira ADF construction', () => {
+    expect(content).toContain('ADF');
+  });
+
+  it('keeps GitHub PATCH /issues for description update', () => {
+    expect(content).toContain('PATCH');
+    expect(content).toContain('/issues/');
+  });
+
+  it('keeps Linear issueUpdate mutation', () => {
+    expect(content).toContain('issueUpdate');
+  });
+
+  it('keeps Azure DevOps work item update', () => {
+    expect(content).toContain('Azure DevOps');
+  });
+
+  it('keeps Shortcut PUT /stories', () => {
+    expect(content).toContain('Shortcut');
+  });
+
+  it('keeps Notion description update', () => {
+    expect(content).toContain('Notion');
+  });
+});