chief-clancy 0.1.7 → 0.2.0-beta.2

package/src/workflows/settings.md

@@ -46,10 +46,14 @@ Jira
 [4] Queue status      {CLANCY_JQL_STATUS:-To Do}
 [5] Sprint filter     {on if CLANCY_JQL_SPRINT set, else off}
 [6] Label filter      {CLANCY_LABEL if set, else off — only pick up tickets with this label}
+[7] Pickup status     {CLANCY_STATUS_IN_PROGRESS if set, else off — move ticket on pickup}
+[8] Done status       {CLANCY_STATUS_DONE if set, else off — move ticket on completion}
 
 {If Linear:}
 Linear
 [4] Label filter      {CLANCY_LABEL if set, else off — only pick up issues with this label}
+[5] Pickup status     {CLANCY_STATUS_IN_PROGRESS if set, else off — move issue on pickup}
+[6] Done status       {CLANCY_STATUS_DONE if set, else off — move issue on completion}
 
 Optional enhancements
 [{N}] Figma MCP       {enabled if FIGMA_API_KEY set, else not set}
@@ -62,7 +66,7 @@ Optional enhancements
 Which setting would you like to change?
 ```
 
-Number each option sequentially. Show only the board-specific section that matches the configured board. If Jira: show [4] queue status, [5] sprint, [6] label. If Linear: show [4] label. If GitHub: no board-specific options.
+Number each option sequentially. Show only the board-specific section that matches the configured board. If Jira: show [4] queue status, [5] sprint, [6] label, [7] pickup status, [8] done status. If Linear: show [4] label, [5] pickup status, [6] done status. If GitHub: no board-specific options.
 
 ---
 
@@ -164,6 +168,40 @@ If [2]: remove `CLANCY_LABEL` from `.clancy/.env`.
 
 ---
 
+### [7] Jira In Progress status (Jira only)
+
+```
+Jira In Progress status — current: {value or "off"}
+When set, Clancy moves a ticket to this status when it starts working on it.
+Must match the exact column name shown in your Jira board.
+
+[1] Set status name
+[2] Off (do not transition on pickup)
+[3] Cancel
+```
+
+If [1]: prompt `What status name should Clancy use for In Progress? (e.g. In Progress, In Dev, Doing)` then write `CLANCY_STATUS_IN_PROGRESS=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_IN_PROGRESS` from `.clancy/.env`.
+
+---
+
+### [8] Jira Done status (Jira only)
+
+```
+Jira Done status — current: {value or "off"}
+When set, Clancy moves a ticket to this status after completing it.
+Must match the exact column name shown in your Jira board.
+
+[1] Set status name
+[2] Off (do not transition on completion)
+[3] Cancel
+```
+
+If [1]: prompt `What status name should Clancy use for Done? (e.g. Done, Complete, Closed)` then write `CLANCY_STATUS_DONE=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_DONE` from `.clancy/.env`.
+
+---
+
 ### [4] Linear label filter (Linear only)
 
 ```
@@ -181,6 +219,40 @@ If [2]: remove `CLANCY_LABEL` from `.clancy/.env`.
 
 ---
 
+### [5] Linear In Progress status (Linear only)
+
+```
+Linear In Progress status — current: {value or "off"}
+When set, Clancy moves an issue to this workflow state when it starts working on it.
+Must match the exact state name shown in your Linear board column header.
+
+[1] Set state name
+[2] Off (do not transition on pickup)
+[3] Cancel
+```
+
+If [1]: prompt `What workflow state name should Clancy use for In Progress? (e.g. In Progress, In Dev, Doing)` then write `CLANCY_STATUS_IN_PROGRESS=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_IN_PROGRESS` from `.clancy/.env`.
+
+---
+
+### [6] Linear Done status (Linear only)
+
+```
+Linear Done status — current: {value or "off"}
+When set, Clancy moves an issue to this workflow state after completing it.
+Must match the exact state name shown in your Linear board column header.
+
+[1] Set state name
+[2] Off (do not transition on completion)
+[3] Cancel
+```
+
+If [1]: prompt `What workflow state name should Clancy use for Done? (e.g. Done, Complete, Closed)` then write `CLANCY_STATUS_DONE=<value>` to `.clancy/.env`.
+If [2]: remove `CLANCY_STATUS_DONE` from `.clancy/.env`.
+
+---
+
 ### Figma MCP
 
 ```
@@ -336,50 +408,9 @@ When updating a value:
 
 ---
 
-### Save as global defaults
-
-At the bottom of the settings menu (before Exit), show:
-
-```
-[{N}] Save as defaults   save current settings for all future projects
-```
-
-When selected:
-
-1. Read the current `.clancy/.env` and extract only the non-credential, non-board-specific settings:
-   - `MAX_ITERATIONS`
-   - `CLANCY_MODEL`
-   - `CLANCY_BASE_BRANCH`
-   - `PLAYWRIGHT_ENABLED`
-   - `PLAYWRIGHT_STARTUP_WAIT`
-
-2. Write these to `~/.clancy/defaults.json`:
-   ```json
-   {
-     "MAX_ITERATIONS": "5",
-     "CLANCY_MODEL": "claude-sonnet-4-6",
-     "CLANCY_BASE_BRANCH": "main"
-   }
-   ```
-
-3. Print: `✓ Defaults saved to ~/.clancy/defaults.json — new projects will inherit these settings.`
-
-4. Loop back to the settings menu.
-
-**Never save credentials, board-specific settings (status filter, sprint, label), or webhook URLs to global defaults.**
-
----
-
-## Step 6 — Load global defaults during init
-
-When `/clancy:init` creates `.clancy/.env`, check if `~/.clancy/defaults.json` exists. If so, pre-populate the `.env` with those values instead of the built-in defaults. The user's answers during init still take priority — defaults are only used for settings that init doesn't ask about (max iterations, model, etc.).
-
----
-
 ## Notes
 
 - All changes are written to `.clancy/.env` immediately after confirmation
 - Switching boards verifies credentials before making any changes — nothing is written if verification fails
 - `/clancy:init` remains available for a full re-setup (re-scaffolds scripts and docs)
 - This command never restarts any servers or triggers any ticket processing
-- Global defaults (`~/.clancy/defaults.json`) are optional — if the file doesn't exist, built-in defaults are used

package/src/workflows/uninstall.md

@@ -35,9 +35,33 @@ Continue? (yes / no)
 ```
 
 - `no` → print "Nothing removed." and stop
-- `yes` → delete both the commands directory and the workflows directory for the chosen location(s), print "✓ Clancy removed from [location]."
+- `yes` → proceed to remove commands, workflows, hooks, and settings entries (Steps 2a–2c)
 
-If "Both" was chosen in Step 1: confirm once for both, remove all four directories, print two confirmation lines.
+If "Both" was chosen in Step 1: confirm once for both, remove everything for both locations.
+
+### Step 2a — Remove command and workflow directories
+
+Delete both the commands directory and the workflows directory for the chosen location(s):
+- Project-local: `.claude/commands/clancy/` and `.claude/clancy/`
+- Global: `~/.claude/commands/clancy/` and `~/.claude/clancy/`
+
+Print: `✓ Clancy commands removed from [location].`
+
+### Step 2b — Remove hooks
+
+For each location being removed, delete these hook files if they exist:
+- Project-local: `.claude/hooks/clancy-check-update.js`, `.claude/hooks/clancy-statusline.js`, `.claude/hooks/clancy-context-monitor.js`
+- Global: `~/.claude/hooks/clancy-check-update.js`, `~/.claude/hooks/clancy-statusline.js`, `~/.claude/hooks/clancy-context-monitor.js`
+
+Then remove the Clancy hook registrations from the corresponding `settings.json` (`.claude/settings.json` for local, `~/.claude/settings.json` for global):
+- Remove any entry in `hooks.SessionStart` whose `command` contains `clancy-check-update`
+- Remove any entry in `hooks.PostToolUse` whose `command` contains `clancy-context-monitor`
+- Remove the `statusLine` key if its `command` value contains `clancy-statusline`
+- If removing an entry leaves a `hooks.SessionStart` or `hooks.PostToolUse` array empty, remove the key entirely
+
+Also remove the update check cache if it exists: `~/.claude/cache/clancy-update-check.json`
+
+If `settings.json` does not exist or cannot be parsed, skip silently — do not create or overwrite it.
 
 ---
 

package/src/workflows/update.md

@@ -108,9 +108,6 @@ Extract only the entries between the installed version and the latest version. D
 - `.claude/commands/clancy/` will be replaced
 - `.claude/clancy/workflows/` will be replaced
 
-If you've modified any Clancy files directly, they'll be automatically backed up
-to `.claude/clancy/local-patches/` before overwriting.
-
 Your project files are preserved:
 - `.clancy/` project folder (scripts, docs, .env, progress log) ✓
 - `CLAUDE.md` ✓
@@ -170,31 +167,6 @@ View full changelog: github.com/Pushedskydiver/clancy/blob/main/CHANGELOG.md
 
 ---
 
-## Step 6 — Check for local patches
-
-After the update completes, check if the installer backed up any locally modified files:
-
-Check for `.claude/clancy/local-patches/backup-meta.json` (local install) or `~/.claude/clancy/local-patches/backup-meta.json` (global install).
-
-**If patches were found:**
-
-```
-Local patches were backed up before the update.
-Your modified files are in .claude/clancy/local-patches/
-
-To review what changed:
-  Compare each file in local-patches/ against its counterpart in
-  .claude/commands/clancy/ or .claude/clancy/workflows/ and manually
-  reapply any customisations you want to keep.
-
-Backed up files:
-{list from backup-meta.json}
-```
-
-**If no patches:** Continue normally (no message needed).
-
----
-
 ## Notes
 
 - If the user installed globally, the update applies globally