chief-clancy 0.2.0 → 0.3.1

package/dist/utils/ansi/ansi.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ansi.d.ts","sourceRoot":"","sources":["../../../src/utils/ansi/ansi.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,GAAG,GAAI,GAAG,MAAM,KAAG,MAA8B,CAAC;AAE/D;;;;;GAKG;AACH,eAAO,MAAM,IAAI,GAAI,GAAG,MAAM,KAAG,MAA8B,CAAC;AAEhE;;;;;GAKG;AACH,eAAO,MAAM,IAAI,GAAI,GAAG,MAAM,KAAG,MAAiC,CAAC;AAEnE;;;;;GAKG;AACH,eAAO,MAAM,IAAI,GAAI,GAAG,MAAM,KAAG,MAA+B,CAAC;AAEjE;;;;;GAKG;AACH,eAAO,MAAM,KAAK,GAAI,GAAG,MAAM,KAAG,MAA+B,CAAC;AAElE;;;;;GAKG;AACH,eAAO,MAAM,GAAG,GAAI,GAAG,MAAM,KAAG,MAA+B,CAAC;AAEhE;;;;;GAKG;AACH,eAAO,MAAM,MAAM,GAAI,GAAG,MAAM,KAAG,MAA+B,CAAC"}

package/dist/utils/ansi/ansi.js

@@ -0,0 +1,55 @@
+/**
+ * ANSI escape code helpers for terminal output.
+ *
+ * Wraps strings in ANSI sequences for styling in CLI environments.
+ */
+/**
+ * Dim the given string (reduced intensity).
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI dim codes.
+ */
+export const dim = (s) => `\x1b[2m${s}\x1b[0m`;
+/**
+ * Bold the given string.
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI bold codes.
+ */
+export const bold = (s) => `\x1b[1m${s}\x1b[0m`;
+/**
+ * Colour the given string blue (bold).
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI blue codes.
+ */
+export const blue = (s) => `\x1b[1;34m${s}\x1b[0m`;
+/**
+ * Colour the given string cyan.
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI cyan codes.
+ */
+export const cyan = (s) => `\x1b[36m${s}\x1b[0m`;
+/**
+ * Colour the given string green.
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI green codes.
+ */
+export const green = (s) => `\x1b[32m${s}\x1b[0m`;
+/**
+ * Colour the given string red.
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI red codes.
+ */
+export const red = (s) => `\x1b[31m${s}\x1b[0m`;
+/**
+ * Colour the given string yellow.
+ *
+ * @param s - The string to style.
+ * @returns The string wrapped in ANSI yellow codes.
+ */
+export const yellow = (s) => `\x1b[33m${s}\x1b[0m`;
+//# sourceMappingURL=ansi.js.map

package/dist/utils/ansi/ansi.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ansi.js","sourceRoot":"","sources":["../../../src/utils/ansi/ansi.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,GAAG,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC;AAE/D;;;;;GAKG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,UAAU,CAAC,SAAS,CAAC;AAEhE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,aAAa,CAAC,SAAS,CAAC;AAEnE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,WAAW,CAAC,SAAS,CAAC;AAEjE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,WAAW,CAAC,SAAS,CAAC;AAElE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,GAAG,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,WAAW,CAAC,SAAS,CAAC;AAEhE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG,CAAC,CAAS,EAAU,EAAE,CAAC,WAAW,CAAC,SAAS,CAAC"}

package/dist/utils/parse-json/parse-json.d.ts

@@ -0,0 +1,20 @@
+/**
+ * Safely parse a JSON string, returning `undefined` on failure.
+ *
+ * Hooks and scripts receive JSON from external sources — this helper
+ * avoids try/catch boilerplate and never throws.
+ *
+ * @param raw - The JSON string to parse.
+ * @returns The parsed value cast to `T`, or `undefined` if parsing fails.
+ *
+ * @example
+ * ```ts
+ * const data = parseJson<{ name: string }>('{"name":"clancy"}');
+ * // data?.name === 'clancy'
+ *
+ * const bad = parseJson('not json');
+ * // bad === undefined
+ * ```
+ */
+export declare function parseJson<T = unknown>(raw: string): T | undefined;
+//# sourceMappingURL=parse-json.d.ts.map

package/dist/utils/parse-json/parse-json.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"parse-json.d.ts","sourceRoot":"","sources":["../../../src/utils/parse-json/parse-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,SAAS,CAAC,CAAC,GAAG,OAAO,EAAE,GAAG,EAAE,MAAM,GAAG,CAAC,GAAG,SAAS,CAMjE"}

package/dist/utils/parse-json/parse-json.js

@@ -0,0 +1,27 @@
+/**
+ * Safely parse a JSON string, returning `undefined` on failure.
+ *
+ * Hooks and scripts receive JSON from external sources — this helper
+ * avoids try/catch boilerplate and never throws.
+ *
+ * @param raw - The JSON string to parse.
+ * @returns The parsed value cast to `T`, or `undefined` if parsing fails.
+ *
+ * @example
+ * ```ts
+ * const data = parseJson<{ name: string }>('{"name":"clancy"}');
+ * // data?.name === 'clancy'
+ *
+ * const bad = parseJson('not json');
+ * // bad === undefined
+ * ```
+ */
+export function parseJson(raw) {
+    try {
+        return JSON.parse(raw);
+    }
+    catch {
+        return undefined;
+    }
+}
+//# sourceMappingURL=parse-json.js.map

package/dist/utils/parse-json/parse-json.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"parse-json.js","sourceRoot":"","sources":["../../../src/utils/parse-json/parse-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,UAAU,SAAS,CAAc,GAAW;IAChD,IAAI,CAAC;QACH,OAAO,IAAI,CAAC,KAAK,CAAC,GAAG,CAAM,CAAC;IAC9B,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,SAAS,CAAC;IACnB,CAAC;AACH,CAAC"}

package/hooks/clancy-check-update.js

@@ -37,7 +37,7 @@ if (!fs.existsSync(cacheDir)) {
 // This script returns immediately so it never delays session start.
 const child = spawn(process.execPath, ['-e', `
   const fs = require('fs');
-  const { execSync } = require('child_process');
+  const { execFileSync } = require('child_process');
 
   const cacheFile = ${JSON.stringify(cacheFile)};
   const versionFile = ${JSON.stringify(versionFile)};
@@ -47,7 +47,7 @@ const child = spawn(process.execPath, ['-e', `
 
   let latest = null;
   try {
-    latest = execSync('npm view chief-clancy version', {
+    latest = execFileSync('npm', ['view', 'chief-clancy', 'version'], {
       encoding: 'utf8',
       timeout: 10000,
       windowsHide: true,

package/hooks/clancy-credential-guard.js

@@ -66,8 +66,15 @@ function scanForCredentials(content) {
   return matches;
 }
 
+// Read hook input — Claude Code passes PreToolUse data as a JSON argument.
+// Fall back to stdin for forward compatibility with potential API changes.
+function readInput() {
+  if (process.argv[2]) return process.argv[2];
+  try { return require('fs').readFileSync('/dev/stdin', 'utf8'); } catch { return '{}'; }
+}
+
 try {
-  const input = JSON.parse(process.argv[2] || '{}');
+  const input = JSON.parse(readInput());
   const toolName = input.tool_name || '';
   const toolInput = input.tool_input || {};
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chief-clancy",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "description": "Autonomous, board-driven development for Claude Code — scaffolds docs, integrates Kanban boards, runs tickets in a loop.",
   "keywords": [
     "claude",
@@ -23,21 +23,61 @@
   },
   "license": "MIT",
   "author": "Alex Clapperton",
+  "type": "module",
   "bin": {
-    "clancy": "bin/install.js"
+    "clancy": "dist/installer/install.js"
   },
-  "main": "bin/install.js",
+  "main": "dist/installer/install.js",
   "files": [
-    "bin/",
+    "dist/",
     "hooks/",
-    "src/",
+    "src/commands/",
+    "src/workflows/",
+    "src/agents/",
+    "src/templates/",
     "registry/"
   ],
   "scripts": {
-    "test": "bash test/unit/jira.test.sh && bash test/unit/github.test.sh && bash test/unit/linear.test.sh && bash test/unit/scaffold.test.sh && bash test/unit/credential-guard.test.sh",
-    "smoke": "bash test/smoke/smoke.sh"
+    "clean": "rm -rf dist",
+    "build": "npm run clean && tsc && tsc-alias && npm run bundle",
+    "bundle": "mkdir -p dist/bundle && esbuild dist/scripts/once/once.js --bundle --platform=node --format=esm --target=node22 --outfile=dist/bundle/clancy-once.js && esbuild dist/scripts/afk/afk.js --bundle --platform=node --format=esm --target=node22 --outfile=dist/bundle/clancy-afk.js",
+    "dev": "vitest",
+    "test": "vitest run",
+    "test:coverage": "vitest run --coverage",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "format": "prettier --write .",
+    "format:check": "prettier --check .",
+    "typecheck": "tsc --noEmit",
+    "prepublishOnly": "npm run build",
+    "prepare": "husky"
+  },
+  "lint-staged": {
+    "*.ts": [
+      "eslint --fix",
+      "prettier --write"
+    ]
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=22.0.0"
+  },
+  "devDependencies": {
+    "@eslint/js": "^10.0.1",
+    "@trivago/prettier-plugin-sort-imports": "^6.0.2",
+    "@types/node": "^25.4.0",
+    "@vitest/coverage-v8": "^4.0.18",
+    "esbuild": "^0.27.3",
+    "eslint": "^10.0.3",
+    "eslint-config-prettier": "^10.1.8",
+    "eslint-plugin-prettier": "^5.5.5",
+    "husky": "^9.1.7",
+    "jiti": "^2.6.1",
+    "lint-staged": "^16.3.3",
+    "prettier": "^3.8.1",
+    "tsc-alias": "^1.8.16",
+    "typescript": "^5.9.3",
+    "typescript-eslint": "^8.57.0",
+    "vitest": "^4.0.18",
+    "zod": "^4.3.6"
   }
 }

package/registry/boards.json

@@ -14,8 +14,7 @@
         "CLANCY_JQL_SPRINT",
         "CLANCY_LABEL",
         "CLANCY_BASE_BRANCH"
-      ],
-      "script": "clancy-once.sh"
+      ]
     },
     {
       "id": "github",
@@ -27,8 +26,7 @@
         "GITHUB_REPO",
         "CLANCY_LABEL",
         "CLANCY_BASE_BRANCH"
-      ],
-      "script": "clancy-once-github.sh"
+      ]
     },
     {
       "id": "linear",
@@ -40,8 +38,7 @@
         "LINEAR_TEAM_ID",
         "CLANCY_LABEL",
         "CLANCY_BASE_BRANCH"
-      ],
-      "script": "clancy-once-linear.sh"
+      ]
     }
   ]
 }

package/src/templates/CLAUDE.md

@@ -4,7 +4,7 @@
 This project uses Clancy for autonomous ticket-driven development.
 
 ### Version check
-At the start of each session, read `~/.claude/cache/clancy-update-check.json` (use the Bash tool). If it exists and `update_available` is true, display exactly:
+At the start of each session, read `~/.claude/cache/clancy-update-check.json` (use the Read tool). If it exists and `update_available` is true, display exactly:
 `⚠ Clancy update available: v{installed} → v{latest}. Run /clancy:update to upgrade.`
 Then continue normally. If the file is missing or unreadable, continue silently.
 

package/src/workflows/doctor.md

@@ -4,7 +4,7 @@ Before doing anything else, check for updates:
 
 1. Run: `npm show chief-clancy version`
 2. Read the installed version from the Clancy `package.json`
-3. If a newer version exists, print: `ℹ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
+3. If a newer version exists, print: `ℹ️ Clancy v{current} → v{latest} available. Run /clancy:update to upgrade.` then continue normally.
 4. If already on latest, continue silently.
 5. If the npm check fails for any reason (offline, network error), continue silently. Never block on this.
 
@@ -22,7 +22,7 @@ Diagnose your Clancy setup — test every configured integration and report what
 
 - Verify Clancy commands are installed (`.claude/commands/clancy/` or `~/.claude/commands/clancy/`)
 - Read installed version from `package.json` in the commands directory
-- Print: `✓ Clancy v{version} installed ({location})`
+- Print: `✅ Clancy v{version} installed ({location})`
 
 ---
 
@@ -32,24 +32,23 @@ Test each required binary:
 
 | Binary | Check | Fix hint |
 |---|---|---|
-| `jq` | `command -v jq` | `brew install jq` / `apt install jq` |
-| `curl` | `command -v curl` | Install curl for your OS |
+| `node` | `command -v node` | Install Node.js 22+ |
 | `git` | `command -v git` | Install git for your OS |
 
-Print `✓` or `✗` for each.
+Print `✅` or `❌` for each.
 
 ---
 
 ## Step 3 — Check project setup
 
-- `.clancy/` exists → `✓ .clancy/ found`
-- `.clancy/clancy-once.sh` exists and is executable → `✓ clancy-once.sh`
-- `.clancy/clancy-afk.sh` exists and is executable → `✓ clancy-afk.sh`
-- `.clancy/.env` exists → `✓ .clancy/.env found`
-- `.clancy/docs/` has non-empty files → `✓ codebase docs present ({N} files)`
+- `.clancy/` exists → `✅ .clancy/ found`
+- `.clancy/clancy-once.js` exists → `✅ clancy-once.js`
+- `.clancy/clancy-afk.js` exists → `✅ clancy-afk.js`
+- `.clancy/.env` exists → `✅ .clancy/.env found`
+- `.clancy/docs/` has non-empty files → `✅ codebase docs present ({N} files)`
 
-If `.clancy/` is missing: `✗ .clancy/ not found — run /clancy:init`
-If `.clancy/.env` is missing: `✗ .clancy/.env not found — run /clancy:init`
+If `.clancy/` is missing: `❌ .clancy/ not found — run /clancy:init`
+If `.clancy/.env` is missing: `❌ .clancy/.env not found — run /clancy:init`
 
 ---
 
@@ -78,8 +77,8 @@ Source `.clancy/.env` and detect which board is configured:
 
 **Figma** — if `FIGMA_API_KEY` is set:
 - Call `GET https://api.figma.com/v1/me` with `X-Figma-Token: $FIGMA_API_KEY`
-- On success: print `✓ Figma connected — {email}`
-- On 403: print `✗ Figma authentication failed. Check FIGMA_API_KEY in .clancy/.env.`
+- On success: print `✅ Figma connected — {email}`
+- On 403: print `❌ Figma authentication failed. Check FIGMA_API_KEY in .clancy/.env.`
 - Note: Figma's API does not expose plan information — check your plan at figma.com/settings
 
 **Playwright** — if `PLAYWRIGHT_ENABLED=true`:
@@ -97,19 +96,29 @@ Source `.clancy/.env` and detect which board is configured:
 ## Step 6 — Summary
 
 ```
-Clancy doctor — {N} checks passed, {N} warnings, {N} failures
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-✓ Clancy v0.1.0 installed (global)
-✓ jq, curl, git — all present
-✓ .clancy/ set up — 10 docs present
-✓ Jira connected — PROJ reachable
-✓ Figma connected — alex@example.com (check plan at figma.com/settings)
-✗ PLAYWRIGHT_STORYBOOK_PORT — not set in .clancy/.env
+{N} checks passed, {N} warnings, {N} failures
 
-Fix the ✗ items, then run /clancy:once to verify end-to-end.
+✅ Clancy v0.1.0 installed (global)
+✅ node, git — all present
+✅ .clancy/ set up — 10 docs present
+✅ Jira connected — PROJ reachable
+✅ Figma connected — alex@example.com (check plan at figma.com/settings)
+❌ PLAYWRIGHT_STORYBOOK_PORT — not set in .clancy/.env
+
+Fix the ❌ items, then run /clancy:once to verify end-to-end.
+
+"We've got a 415 in progress — a config disturbance."
 ```
 
 If all checks pass:
 ```
-All good. Run /clancy:once to pick up your first ticket.
+🚨 Clancy — Doctor
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+All {N} checks passed.
+
+"Nothing to see here, folks. Move along." — Run /clancy:once to pick up your first ticket.
 ```

package/src/workflows/init.md

@@ -30,20 +30,20 @@ Before proceeding, silently run `command -v` for each required binary:
 
 | Binary | Install hint |
 |---|---|
-| `jq` | `brew install jq` / `apt install jq` |
-| `curl` | pre-installed on macOS and most Linux |
+| `node` | Install Node.js 22+ (nodejs.org) |
 | `git` | `brew install git` / `apt install git` |
+| `claude` | `npm install -g @anthropic-ai/claude-code` |
 
 If all are present: continue silently.
 
 If any are missing, output:
 
 ```
-⚠ Missing prerequisites:
+⚠️ Missing prerequisites:
 
-  ✗ jq — brew install jq  (or apt install jq on Linux)
+  ❌ node — Install Node.js 22+ (nodejs.org)
 
-Clancy's shell scripts require these binaries to run. Install them, then re-run /clancy:init.
+Clancy requires these binaries to run. Install them, then re-run /clancy:init.
 ```
 
 List only the missing ones. Then stop — do not proceed with setup until prerequisites are satisfied.
@@ -54,9 +54,16 @@ List only the missing ones. Then stop — do not proceed with setup until prereq
 
 Output:
 
+```
+🚨 Clancy — Init
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+"Chief Wiggum reporting for duty."
+
 Clancy pulls tickets from your Kanban board, implements them, commits, and squash-merges — one ticket per run, fresh context every time.
 
 Let's get you set up.
+```
 
 ---
 
@@ -79,13 +86,12 @@ Clancy currently supports Jira, GitHub Issues, and Linear out of the box.
 
 Your board isn't supported yet — but you can add it:
   · Open an issue:   github.com/Pushedskydiver/clancy/issues
-  · Contribute one:  see CONTRIBUTING.md — adding a board is just a script template + a boards.json entry
+  · Contribute one:  see CONTRIBUTING.md — adding a board is a TypeScript module + a boards.json entry
 
 In the meantime, you can still use Clancy manually:
   · Run /clancy:map-codebase to scan and document your codebase
-  · Use the clancy-once.sh template from the GitHub repo as a starting point
-  · Implement your board's API fetch, store credentials in .clancy/.env
-  · Point clancy-afk.sh at your custom script via CLANCY_ONCE_SCRIPT in .clancy/.env
+  · Run `npx -y chief-clancy@latest` and implement your board's API module
+  · Store credentials in .clancy/.env
 
 Do not scaffold anything after this message. Stop completely.
 
@@ -124,6 +130,65 @@ If enter is pressed with no value: skip — omit the label clause entirely (Clan
 
 ---
 
+### Q2b: Board credential verification
+
+After collecting all credentials for the chosen board, verify the connection before continuing.
+
+**Jira** — call `GET {JIRA_BASE_URL}/rest/api/3/project/{JIRA_PROJECT_KEY}` with basic auth (`{JIRA_USER}:{JIRA_API_TOKEN}` base64-encoded in the `Authorization: Basic` header).
+
+On success (HTTP 200), show:
+```
+✅ Jira connected — project {JIRA_PROJECT_KEY} reachable.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to Jira (HTTP {status}).
+Check your credentials in the values you just entered.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all Jira questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+**GitHub Issues** — call `GET https://api.github.com/repos/{GITHUB_REPO}` with `Authorization: Bearer {GITHUB_TOKEN}` and `X-GitHub-Api-Version: 2022-11-28`.
+
+On success (HTTP 200), show:
+```
+✅ GitHub connected — {GITHUB_REPO} reachable.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to GitHub (HTTP {status}).
+Check your token has `repo` scope and the repo name is correct.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all GitHub questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+**Linear** — call `POST https://api.linear.app/graphql` with `Authorization: {LINEAR_API_KEY}` (no Bearer prefix) and body `{"query": "{ viewer { id name } }"}`.
+
+On success (HTTP 200 with `data.viewer`), show:
+```
+✅ Linear connected — {viewer.name}.
+```
+
+On failure, show:
+```
+❌ Couldn't connect to Linear.
+Check your API key at linear.app/settings/api.
+
+[1] Re-enter credentials
+```
+
+If [1]: go back to Q2 and re-ask all Linear questions. If the user wants to abandon setup entirely, they can Ctrl+C.
+
+Never silently continue with unverified credentials — the user must fix their credentials or exit with Ctrl+C.
+
+---
+
 ### Q3 (Jira only): Status name
 
 Output:
@@ -134,7 +199,7 @@ Common values: To Do, Selected for Development, Ready, Open
 [1] To Do (default)
 [2] Enter a different value
 
-Store as `CLANCY_JQL_STATUS` in `.clancy/.env`. Always wrap the value in double quotes — status names often contain spaces (e.g. `CLANCY_JQL_STATUS="Selected for Development"`) and unquoted values with spaces cause bash parse errors when the file is sourced.
+Store as `CLANCY_JQL_STATUS` in `.clancy/.env`. Always wrap the value in double quotes — status names often contain spaces (e.g. `CLANCY_JQL_STATUS="Selected for Development"`).
 
 ---
 
@@ -176,34 +241,40 @@ Store the detected (or confirmed) value as `CLANCY_BASE_BRANCH` in `.clancy/.env
 
 Create `.clancy/` directory and the following:
 
-1. Write the correct `clancy-once.sh` for the chosen board to `.clancy/clancy-once.sh` — use the exact script content from scaffold.md, do not generate or modify it
-2. Write `clancy-afk.sh` to `.clancy/clancy-afk.sh` — use the exact script content from scaffold.md, do not generate or modify it
-3. Make both scripts executable: `chmod +x .clancy/*.sh`
-4. Create `.clancy/docs/` with 10 empty template files (UPPERCASE.md with section headings only):
+1. Verify `.clancy/clancy-once.js` and `.clancy/clancy-afk.js` exist (copied by the installer). If missing, tell the user to run `npx -y chief-clancy@latest` and stop.
+2. Create `.clancy/docs/` with 10 empty template files (UPPERCASE.md with section headings only):
    - STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, CONVENTIONS.md, TESTING.md
    - GIT.md, DESIGN-SYSTEM.md, ACCESSIBILITY.md, DEFINITION-OF-DONE.md, CONCERNS.md
-5. Write the correct `.env.example` for the chosen board to `.clancy/.env.example` — use the exact content from scaffold.md
-6. Write collected credentials to `.clancy/.env` (if the user provided them)
-7. Handle `CLAUDE.md` — follow the merge logic in scaffold.md exactly:
+3. Write the correct `.env.example` for the chosen board to `.clancy/.env.example` — use the exact content from scaffold.md
+4. Write collected credentials to `.clancy/.env` (if the user provided them)
+5. Handle `CLAUDE.md` — follow the merge logic in scaffold.md exactly:
    - If no CLAUDE.md: write the full template as `CLAUDE.md`
    - If CLAUDE.md exists without `<!-- clancy:start -->`: append the Clancy section to the end
    - If CLAUDE.md exists with `<!-- clancy:start -->`: replace only the content between the markers
    - Never overwrite the entire file
-8. Check `.gitignore` — if `.clancy/.env` is not listed, append it
+6. Check `.gitignore` — if `.clancy/.env` is not listed, append it
 
 ---
 
 ## Step 4b — Commit scaffold
 
-After scaffolding, commit everything created (excluding `.clancy/.env` which contains credentials):
+After scaffolding, ask the user whether to commit the scaffolded files:
+
+```
+Commit the Clancy scaffold to git? (recommended) [Y/n]
+```
+
+If yes (or enter): commit everything created (excluding `.clancy/.env` which contains credentials):
 
 ```bash
-git add .clancy/clancy-once.sh .clancy/clancy-afk.sh .clancy/.env.example .clancy/docs/ CLAUDE.md .gitignore
-git commit -m "chore(clancy): initialise — scaffold scripts, docs templates, and config"
+git add .clancy/.env.example .clancy/docs/ CLAUDE.md .gitignore
+git commit -m "chore(clancy): initialise — scaffold docs templates and config"
 ```
 
 If `CLAUDE.md` was not modified (it already existed and was not changed), omit it from the `git add`. If `.gitignore` was not modified, omit it too. Only stage files that actually changed.
 
+If no: skip the commit silently. The user can commit manually later.
+
 ---
 
 ## Step 5 — Optional enhancements
@@ -240,7 +311,7 @@ If a key is entered:
 1. Verify the key by calling `GET https://api.figma.com/v1/me` with `X-Figma-Token: {key}`
 2. On success, show:
    ```
-   ✓ Figma connected: {email}
+   ✅ Figma connected: {email}
 
    Note: Figma's API does not expose plan information.
    Clancy uses 3 MCP calls per ticket (metadata, design context, screenshot).
@@ -252,7 +323,7 @@ If a key is entered:
 
 If `GET /v1/me` fails (non-200), show:
 ```
-✗ Couldn't verify Figma API key (HTTP {status}).
+❌ Couldn't verify Figma API key (HTTP {status}).
 Double-check it at figma.com/settings → Personal access tokens.
 
 [1] Try a different key
@@ -413,11 +484,15 @@ If no: output "Run /clancy:map-codebase when you're ready." then continue to fin
 
 Output:
 
-Clancy is ready.
+```
+╔═══════════════════════════════════════════════════════════╗
+║  ✅ Clancy is ready.                                     ║
+╚═══════════════════════════════════════════════════════════╝
 
-- Scripts: `.clancy/clancy-once.sh`, `.clancy/clancy-afk.sh`
+- Scripts: `.clancy/clancy-once.js`, `.clancy/clancy-afk.js`
 - Docs: `.clancy/docs/` (10 files)
 - Config: `.clancy/.env`
 - CLAUDE.md: updated
 
-Run `/clancy:dry-run` to preview the first ticket without making changes, `/clancy:once` to pick it up, or `/clancy:run` to process the full queue.
+"Clancy's on the beat." — Run /clancy:dry-run to preview, /clancy:once to pick up a ticket, or /clancy:run to process the queue.
+```

package/src/workflows/logs.md

@@ -10,7 +10,12 @@ Read `.clancy/progress.txt` and present a formatted summary.
 
 If `.clancy/progress.txt` does not exist:
 ```
-No progress logged yet. Run /clancy:once or /clancy:run to get started.
+🚨 Clancy — Logs
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+No progress logged yet.
+
+"The law is powerless to help you... but not for long." — Run /clancy:once or /clancy:run to get started.
 ```
 Stop.
 
@@ -43,15 +48,16 @@ If only 1–3 DONE entries: show a flat list, skip grouping.
 If 4+ entries, show the full grouped display:
 
 ```
-Clancy Progress Log
-───────────────────────────────────────
+🚨 Clancy — Logs
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
 Total tickets completed: {count}
 First run: {YYYY-MM-DD}
 Latest run: {YYYY-MM-DD}
 
 This week ({Mon date}–{Sun date or today}):
-  ✓ {TICKET-KEY}  {Summary}
-  ✓ {TICKET-KEY}  {Summary}
+  ✅ {TICKET-KEY}  {Summary}
+  ✅ {TICKET-KEY}  {Summary}
   ...
 
 By epic:
@@ -59,9 +65,10 @@ By epic:
   {EPIC-KEY} {Epic name or prefix}  {bar}  {count} tickets
   (other)                           {bar}  {count} tickets
 
+Reviews run: {N}
 Full log: .clancy/progress.txt
 
-Reviews run: {N}
+"The law is powerless to help you, but here's what Clancy's done."
 ```
 
 ### Display rules