chief-clancy 0.1.4 → 0.1.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chief-clancy",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Autonomous, board-driven development for Claude Code — scaffolds docs, integrates Kanban boards, runs tickets in a loop.",
   "keywords": [
     "claude",

package/src/workflows/uninstall.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-Remove Clancy's slash commands from the local project, globally, or both. Optionally remove the `.clancy/` project folder (which includes `.clancy/.env`). Never touch `CLAUDE.md` under any circumstances.
+Remove Clancy's slash commands from the local project, globally, or both. Optionally remove the `.clancy/` project folder (which includes `.clancy/.env`). Clean up CLAUDE.md and .gitignore changes made during init.
 
 ---
 
@@ -41,7 +41,46 @@ If "Both" was chosen in Step 1: confirm once for both, remove all four directori
 
 ---
 
-## Step 3 — Offer to remove .clancy/ (if present)
+## Step 3 — Clean up CLAUDE.md
+
+Check whether `CLAUDE.md` exists in the current project directory.
+
+If it does, check for Clancy markers (`<!-- clancy:start -->` and `<!-- clancy:end -->`):
+
+**If markers found:**
+
+Read the full file content. Determine whether Clancy created the file or appended to an existing one:
+
+- **Clancy created it** (the file contains only whitespace outside the markers — no meaningful content before `<!-- clancy:start -->` or after `<!-- clancy:end -->`): delete the entire file.
+- **Clancy appended to an existing file** (there is meaningful content outside the markers): remove everything from `<!-- clancy:start -->` through `<!-- clancy:end -->` (inclusive), plus any blank lines immediately before the start marker that were added as spacing. Write the cleaned file back.
+
+Print `✓ CLAUDE.md cleaned up.` (or `✓ CLAUDE.md removed.` if deleted).
+
+**If no markers found:** skip — Clancy didn't modify this file.
+
+**If CLAUDE.md does not exist:** skip.
+
+---
+
+## Step 4 — Clean up .gitignore
+
+Check whether `.gitignore` exists in the current project directory.
+
+If it does, check whether it contains the Clancy entries (`# Clancy credentials` and/or `.clancy/.env`):
+
+**If found:** remove the `# Clancy credentials` comment line and the `.clancy/.env` line. Also remove any blank line immediately before or after the removed block to avoid leaving double blank lines. Write the cleaned file back.
+
+If the file is now empty (or contains only whitespace) after removal, delete it entirely — Clancy created it during init.
+
+Print `✓ .gitignore cleaned up.` (or `✓ .gitignore removed.` if deleted).
+
+**If not found:** skip — Clancy didn't modify this file.
+
+**If .gitignore does not exist:** skip.
+
+---
+
+## Step 5 — Offer to remove .clancy/ (if present)
 
 Check whether `.clancy/` exists in the current project directory.
 
@@ -59,7 +98,7 @@ If `.clancy/` does not exist, skip this step entirely.
 
 ---
 
-## Step 4 — Final message
+## Step 6 — Final message
 
 ```
 Clancy uninstalled. To reinstall: npx chief-clancy
@@ -69,7 +108,6 @@ Clancy uninstalled. To reinstall: npx chief-clancy
 
 ## Hard constraints
 
-- **Never touch any `.env` at the project root** — Clancy's credentials live in `.clancy/.env` and are only removed as part of `.clancy/` in Step 3
-- **Never touch `CLAUDE.md`** — under any circumstances, in any scenario
-- Steps 1–2 (commands removal) and Step 3 (`.clancy/` removal) are always asked separately — never bundle them into one confirmation
-- If the user says no to commands removal in Step 2, skip Step 3 entirely and stop
+- **Never touch any `.env` at the project root** — Clancy's credentials live in `.clancy/.env` and are only removed as part of `.clancy/` in Step 5
+- Steps 1–2 (commands removal), Steps 3–4 (CLAUDE.md and .gitignore cleanup), and Step 5 (`.clancy/` removal) are always asked separately — never bundle them into one confirmation
+- If the user says no to commands removal in Step 2, skip all remaining steps and stop

package/src/workflows/update.md

@@ -2,60 +2,167 @@
 
 ## Overview
 
-Update Clancy itself to the latest version via npx.
+Check for Clancy updates via npm, display changelog for versions between installed and latest, obtain user confirmation, and execute clean installation.
 
 ---
 
-## Step 1 — Check current version
+## Step 1 — Detect installed version
 
-Read current version from the installed package (check `~/.claude/commands/clancy/` or `./.claude/commands/clancy/` for a `VERSION` file, or from npm).
+Determine whether Clancy is installed locally or globally by checking both locations:
 
 ```bash
-npm view chief-clancy version 2>/dev/null || echo "unknown"
+LOCAL_VERSION_FILE="./.claude/commands/clancy/VERSION"
+GLOBAL_VERSION_FILE="$HOME/.claude/commands/clancy/VERSION"
+
+if [ -f "$LOCAL_VERSION_FILE" ] && grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+' "$LOCAL_VERSION_FILE"; then
+  INSTALLED=$(cat "$LOCAL_VERSION_FILE")
+  INSTALL_TYPE="LOCAL"
+elif [ -f "$GLOBAL_VERSION_FILE" ] && grep -Eq '^[0-9]+\.[0-9]+\.[0-9]+' "$GLOBAL_VERSION_FILE"; then
+  INSTALLED=$(cat "$GLOBAL_VERSION_FILE")
+  INSTALL_TYPE="GLOBAL"
+else
+  INSTALLED="unknown"
+  INSTALL_TYPE="UNKNOWN"
+fi
+
+echo "$INSTALLED"
+echo "$INSTALL_TYPE"
 ```
 
+Parse output:
+- First line = installed version (or "unknown")
+- Second line = install type (LOCAL, GLOBAL, or UNKNOWN)
+
+**If version is unknown:**
+```
+## Clancy Update
+
+**Installed version:** Unknown
+
+Your installation doesn't include version tracking.
+
+Running fresh install...
+```
+
+Proceed to Step 4 (treat as version 0.0.0 for comparison).
+
 ---
 
-## Step 2 — Run the updater
+## Step 2 — Check latest version
+
+Check npm for the latest published version:
+
+```bash
+npm view chief-clancy version 2>/dev/null
+```
 
+**If npm check fails:**
 ```
-Updating Clancy...
+Couldn't check for updates (offline or npm unavailable).
+
+To update manually: `npx chief-clancy@latest`
 ```
 
-Run:
+Exit.
+
+---
+
+## Step 3 — Compare versions and confirm
+
+Compare installed vs latest:
+
+**If installed == latest:**
+```
+## Clancy Update
+
+**Installed:** X.Y.Z
+**Latest:** X.Y.Z
+
+You're already on the latest version.
+```
+
+Exit.
+
+**If update available**, fetch the changelog from GitHub and show what's new BEFORE updating:
+
 ```bash
-npx chief-clancy@latest
+curl -s https://raw.githubusercontent.com/Pushedskydiver/clancy/main/CHANGELOG.md
 ```
 
-This re-runs the installer, which copies the latest command files into the correct `.claude/commands/clancy/` directory (global or local, matching the existing install location).
+Extract only the entries between the installed version and the latest version. Display:
 
-The update only touches `.claude/commands/clancy/` (slash commands and workflows). It never modifies:
-- `.clancy/clancy-once.sh` or `.clancy/clancy-afk.sh` — shell scripts are not updated
-- `.clancy/docs/` codebase documentation
-- `.clancy/progress.txt` progress log
-- `.clancy/.env` credentials
-- `CLAUDE.md`
+```
+## Clancy Update Available
+
+**Installed:** {installed}
+**Latest:** {latest}
+
+### What's New
+────────────────────────────────────────────────────────────
+
+{relevant CHANGELOG entries between installed and latest}
+
+────────────────────────────────────────────────────────────
 
-**To update the shell scripts** (`.clancy/clancy-once.sh`, `.clancy/clancy-afk.sh`), re-run `/clancy:init` — it will detect the existing setup and re-scaffold the scripts without asking for credentials again.
+⚠️  **Note:** The update performs a clean install of Clancy command folders:
+- `.claude/commands/clancy/` will be replaced
+- `.claude/clancy/workflows/` will be replaced
+
+Your project files are preserved:
+- `.clancy/` project folder (scripts, docs, .env, progress log) ✓
+- `CLAUDE.md` ✓
+- Custom commands not in `commands/clancy/` ✓
+- Custom hooks ✓
+```
+
+Ask the user: **"Proceed with update?"** with options:
+- "Yes, update now"
+- "No, cancel"
+
+**If user cancels:** Exit.
 
 ---
 
-## Step 3 — Show changelog diff
+## Step 4 — Run the update
 
-After update, fetch and display the CHANGELOG section for any versions between old and new:
+Run the installer using the detected install type:
 
+```bash
+npx -y chief-clancy@latest
 ```
-Updated Clancy from v{old} to v{new}.
 
-What's new:
-{relevant CHANGELOG entries}
+The installer auto-detects whether to install globally or locally based on the existing install.
 
-View full changelog: github.com/Pushedskydiver/clancy/blob/main/CHANGELOG.md
+This only touches `.claude/commands/clancy/` and `.claude/clancy/workflows/`. It never modifies:
+- `.clancy/clancy-once.sh` or `.clancy/clancy-afk.sh` — shell scripts
+- `.clancy/docs/` — codebase documentation
+- `.clancy/progress.txt` — progress log
+- `.clancy/.env` — credentials
+- `CLAUDE.md`
+
+**To update the shell scripts**, re-run `/clancy:init` — it will detect the existing setup and re-scaffold the scripts without asking for credentials again.
+
+---
+
+## Step 5 — Clear update cache and confirm
+
+Clear the update check cache so the statusline indicator disappears:
+
+```bash
+rm -f "$HOME/.claude/cache/clancy-update-check.json"
+rm -f "./.claude/cache/clancy-update-check.json"
 ```
 
-If version is already latest:
+Display completion message:
+
 ```
-Clancy is already up to date (v{version}).
+╔═══════════════════════════════════════════════════════════╗
+║  Clancy Updated: v{old} → v{new}                        ║
+╚═══════════════════════════════════════════════════════════╝
+
+⚠️  Restart Claude Code to pick up the new commands.
+
+View full changelog: github.com/Pushedskydiver/clancy/blob/main/CHANGELOG.md
 ```
 
 ---
@@ -64,4 +171,4 @@ Clancy is already up to date (v{version}).
 
 - If the user installed globally, the update applies globally
 - If the user installed locally, the update applies locally
-- After updating, the new commands take effect immediately in Claude Code
+- After updating, restart Claude Code for new commands to take effect