create-claude-workspace 1.1.87 → 1.1.89

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ladislav Brodecký
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/template/.claude/agents/orchestrator.md

@@ -150,71 +150,19 @@ git pull --rebase origin HEAD
 ```
 If no remote, skip this step.
 
-### 8. Check git log and structure
-- `git log --oneline -10`
-- Scan current file structure
-
-### 9. Detect PLAN.md changes
-If `PLAN.md` exists in the project root, check whether it changed since the last session. This runs AFTER git sync (step 6) to avoid commit conflicts with remote changes.
-
-1. Read PLAN.md content
-2. Read MEMORY.md `PLAN_MD_Hash` value (if present)
-3. Compute a hash of PLAN.md content: take first 8 chars of hex SHA-256 (`node -e "const c=require('crypto');process.stdout.write(c.createHash('sha256').update(require('fs').readFileSync('PLAN.md','utf-8')).digest('hex').slice(0,8))"`)
-4. If hash matches → skip (no changes). If `PLAN_MD_Hash` is absent (first run) → treat as "changed" to seed the state.
-5. If changed — read PLAN.md and diff against current project state. Delegate updates based on WHICH sections changed:
-
-| Changed section | Action |
-|---|---|
-| **Product Vision** (Target users, Core problem, MVP features, Non-goals) | Delegate to `product-owner`: "PLAN.md Product Vision was updated. Read the new PLAN.md and current PRODUCT.md. Update PRODUCT.md to reflect the new vision. Output what changed." |
-| **Technical Decisions** (Framework, Backend, Database, Deployment, CI/CD, Testing) | Delegate to `technical-planner`: "PLAN.md Technical Decisions were updated. Read new PLAN.md, current CLAUDE.md, and TODO.md. Update TODO.md tasks if the tech stack changed (e.g., framework switch may invalidate existing tasks). Update CLAUDE.md Tech Stack section to match." If only Deployment/CI/CD changed, also delegate to `deployment-engineer`: "PLAN.md deployment config changed. Update CI/CD pipeline config to match new settings." |
-| **Workflow** (Mode, Branch strategy, Auto-push, Auto-merge, Review required) | Update CLAUDE.md `Workflow:` field directly. If mode changed from solo→team or team→solo, log in MEMORY.md Notes. |
-| **Constraints** (Max lines per file, Coverage threshold, Forbidden patterns) | Update CLAUDE.md constraints section directly (Code Quality & Linting, coverage thresholds). |
-| **Project Info** (Name, Description, Framework, Package manager, Monorepo) | Delegate to `technical-planner`: "PLAN.md Project Info changed. Update CLAUDE.md header and Tech Stack to match." |
-| **Access & Credentials** | Validate new credentials (run auth checks). Log status in MEMORY.md Session Config. Do NOT store credential values. |
-| **Initial State / Runtime** | Read values but do NOT delegate — these are consumed by `autonomous.mjs`, not agents. |
-
-6. After all delegations complete, update MEMORY.md: set `PLAN_MD_Hash: [new-hash]`
-7. If any files were modified (CLAUDE.md, PRODUCT.md, TODO.md), commit: `git add CLAUDE.md PRODUCT.md TODO.md MEMORY.md && git commit -m "chore: propagate PLAN.md changes to project files"`
-8. Push if remote exists: `git push origin HEAD`
-9. Skip this entire step if PLAN.md does not exist.
-
-**How to detect which sections changed** (without storing the old file):
-- Compare PLAN.md values against current project files:
-  - `Product Vision` → compare MVP features list against PRODUCT.md features
-  - `Technical Decisions` → compare framework/backend/database against CLAUDE.md Tech Stack
-  - `Workflow` → compare mode against CLAUDE.md `Workflow:` field
-  - `Constraints` → compare coverage threshold against CLAUDE.md code quality section
-- If a PLAN.md value differs from the corresponding project file value, that section "changed"
-
-### 10. Retroactive git integration sync
-- **Trigger condition**: remote exists (`git remote -v | grep origin`) AND TODO.md exists with tasks BUT no `<!-- #N -->` markers found in TODO.md AND CLI is available (`gh --version` or `glab --version`) AND auth is valid (`gh auth status` or `glab auth status`)
-- This means work was done locally without git integration (token was missing or platform wasn't set up), and now it's available
-- Delegate to `devops-integrator` agent:
-  "Run retroactive sync (Operation 9). TODO.md has tasks completed locally without git integration.
-  Create milestones for all phases, create issues for all tasks, and sync their status:
-  - `[x]` tasks → create issue with `status::done` label (already completed locally)
-  - `[~]` tasks → create issue with `status::skipped` label
-  - `[ ]` tasks → create issue with `status::todo` label
-  Add `<!-- #N -->` markers to TODO.md for all created issues.
-  This is a one-time sync — subsequent iterations will use normal git integration."
-- After sync, commit the updated TODO.md: `git add TODO.md && git commit -m "chore: sync TODO.md with git platform issues"`
-- Push if remote exists: `git push origin HEAD`
-- Log in MEMORY.md Notes: "Retroactive git sync completed — [N] issues created, [M] marked as done"
-- Skip if any trigger condition is not met (no remote, no TODO.md, markers already present, CLI missing, auth invalid)
-
-### 11. Kit auto-upgrade (check npm + migrate project)
-Automatically check for newer `create-claude-workspace` versions, update kit files, analyze changes, and create migration tasks for the target project.
+### 8. Kit auto-upgrade (check npm + migrate project)
+Automatically check for newer `create-claude-workspace` versions, update kit files, analyze changes, and create migration tasks for the target project. Runs early (before PLAN.md detection and other checks) so that agents, profiles, and templates are up-to-date before any delegation.
 
-#### 11a. Check npm registry for latest version
+#### 8a. Check npm registry for latest version
 ```bash
 CURRENT=$(cat .claude/.kit-version 2>/dev/null || echo "0.0.0")
 LATEST=$(npm view create-claude-workspace version 2>/dev/null || echo "")
 ```
-- If `LATEST` is empty (network failure, npm unavailable) → skip entire step 11
-- If `LATEST` equals `CURRENT` → skip (already up to date)
-- If `LATEST` is newer than `CURRENT` → proceed to 11b
+- If `LATEST` is empty (network failure, npm unavailable) → skip npm upgrade, but still proceed to 8c (local diff check)
+- If `LATEST` is newer than `CURRENT` → proceed to 8b (npm upgrade)
+- If `LATEST` equals `CURRENT` → skip 8b, proceed to 8c (local diff check — files may have been updated manually via `--update` or edited by hand)
 
-#### 11b. Update kit files
+#### 8b. Update kit files (only if newer version on npm)
 ```bash
 # Run update using the project's package runner
 {PKG_RUNNER} create-claude-workspace@latest --update
@@ -222,12 +170,13 @@ LATEST=$(npm view create-claude-workspace version 2>/dev/null || echo "")
 - This overwrites `.claude/` files (agents, profiles, templates, docker, router, .kit-version) with the latest version
 - Project-specific files (CLAUDE.md, PRODUCT.md, TODO.md, MEMORY.md) are NOT touched by the update command
 
-#### 11c. Capture and analyze diff
+#### 8c. Capture and analyze diff (ALWAYS runs)
+Check for uncommitted changes in `.claude/` — these may come from 8b (npm upgrade) OR from manual `--update` / hand edits between sessions:
 ```bash
 # Capture what changed in .claude/
 git diff .claude/
 ```
-- If diff is empty (update ran but nothing changed) → skip to 11e
+- If diff is empty (no changes in .claude/) → skip to 8e
 - Categorize changes:
   - **Template changes** (`.claude/templates/claude-md.md`) → new conventions, patterns, rules for project CLAUDE.md
   - **Profile changes** (`.claude/profiles/*.md`) → new frontend patterns, review checklists
@@ -235,10 +184,10 @@ git diff .claude/
   - **Docker changes** (`.claude/docker/*`) → updated container config
   - **Router changes** (`.claude/CLAUDE.md`) → updated routing instructions
 
-#### 11d. Create migration tasks (if project changes needed)
+#### 8d. Create migration tasks (if project changes needed)
 Only if template or profile changes affect the target project — delegate to `technical-planner`:
 
-"The `create-claude-workspace` kit was upgraded from v{CURRENT} to v{LATEST}. Below is the diff of changed files. Analyze what changed and determine if the TARGET PROJECT needs migration or refactoring tasks.
+"The `create-claude-workspace` kit files were updated (v{CURRENT} → v{LATEST}, or manual update). Below is the diff of changed files. Analyze what changed and determine if the TARGET PROJECT needs migration or refactoring tasks.
 
 **The diff:**
 ```
@@ -263,11 +212,11 @@ Only if template or profile changes affect the target project — delegate to `t
 
 Read the current TODO.md and MEMORY.md for context on the project's current phase and tech stack."
 
-- If planner returns `MIGRATION: NONE` → no tasks created, proceed to 11e
+- If planner returns `MIGRATION: NONE` → no tasks created, proceed to 8e
 - If planner creates tasks → if git integration active, delegate to `devops-integrator` to create issues for the new migration tasks
 - Log in MEMORY.md Notes: "Kit upgraded v{CURRENT} → v{LATEST}: [N migration tasks created / no project migration needed]"
 
-#### 11e. Commit update + refresh CLAUDE.md
+#### 8e. Commit update + refresh CLAUDE.md
 1. Run `/revise-claude-md` to reconcile the project's CLAUDE.md with new conventions from the updated template (`.claude/templates/claude-md.md`). If `/revise-claude-md` is unavailable, manually compare CLAUDE.md against the template and update sections with new content. Do NOT overwrite project-specific content (project name, tech stack choices, deployment config).
 2. Update MEMORY.md: set `Kit_Version: [value from .claude/.kit-version]`
 3. Commit all changes:
@@ -277,15 +226,67 @@ Read the current TODO.md and MEMORY.md for context on the project's current phas
    ```
 4. Push if remote exists: `git push origin HEAD`
 
-#### 11f. Migration task priority
-- After step 11 completes, if migration tasks were created in TODO.md, they become the **next tasks to pick** in STEP 1 (before any regular development tasks in the current phase)
+#### 8f. Migration task priority
+- After step 8 completes, if migration tasks were created in TODO.md, they become the **next tasks to pick** in STEP 1 (before any regular development tasks in the current phase), subject to the crash-recovery exception in STEP 1 (if `Current Worktree` is set, the in-progress task is finished first)
 - This ensures the project stays aligned with kit conventions before new features are built on outdated patterns
 - Migration tasks follow the normal development cycle (STEP 1-12) — they get architect plans, tests, review, just like any other task
 
 #### Skip conditions
-- `.claude/.kit-version` does not exist → skip entire step 11
-- `npm view` fails (network, npm not installed) → skip, log in MEMORY.md Notes: "Kit version check skipped — npm registry unreachable"
-- Current version equals latest → skip (up to date)
+- `.claude/.kit-version` does not exist → skip entire step 8
+- `npm view` fails (network, npm not installed) → skip npm upgrade (8b), but still check local diff (8c)
+- No uncommitted changes in `.claude/` AND version is current → skip (nothing to do)
+
+### 9. Check git log and structure
+- `git log --oneline -10`
+- Scan current file structure
+
+### 10. Detect PLAN.md changes
+If `PLAN.md` exists in the project root, check whether it changed since the last session. This runs AFTER git sync (step 7) to avoid commit conflicts with remote changes.
+
+1. Read PLAN.md content
+2. Read MEMORY.md `PLAN_MD_Hash` value (if present)
+3. Compute a hash of PLAN.md content: take first 8 chars of hex SHA-256 (`node -e "const c=require('crypto');process.stdout.write(c.createHash('sha256').update(require('fs').readFileSync('PLAN.md','utf-8')).digest('hex').slice(0,8))"`)
+4. If hash matches → skip (no changes). If `PLAN_MD_Hash` is absent (first run) → treat as "changed" to seed the state.
+5. If changed — read PLAN.md and diff against current project state. Delegate updates based on WHICH sections changed:
+
+| Changed section | Action |
+|---|---|
+| **Product Vision** (Target users, Core problem, MVP features, Non-goals) | Delegate to `product-owner`: "PLAN.md Product Vision was updated. Read the new PLAN.md and current PRODUCT.md. Update PRODUCT.md to reflect the new vision. Output what changed." |
+| **Technical Decisions** (Framework, Backend, Database, Deployment, CI/CD, Testing) | Delegate to `technical-planner`: "PLAN.md Technical Decisions were updated. Read new PLAN.md, current CLAUDE.md, and TODO.md. Update TODO.md tasks if the tech stack changed (e.g., framework switch may invalidate existing tasks). Update CLAUDE.md Tech Stack section to match." If only Deployment/CI/CD changed, also delegate to `deployment-engineer`: "PLAN.md deployment config changed. Update CI/CD pipeline config to match new settings." |
+| **Workflow** (Mode, Branch strategy, Auto-push, Auto-merge, Review required) | Update CLAUDE.md `Workflow:` field directly. If mode changed from solo→team or team→solo, log in MEMORY.md Notes. |
+| **Constraints** (Max lines per file, Coverage threshold, Forbidden patterns) | Update CLAUDE.md constraints section directly (Code Quality & Linting, coverage thresholds). |
+| **Project Info** (Name, Description, Framework, Package manager, Monorepo) | Delegate to `technical-planner`: "PLAN.md Project Info changed. Update CLAUDE.md header and Tech Stack to match." |
+| **Access & Credentials** | Validate new credentials (run auth checks). Log status in MEMORY.md Session Config. Do NOT store credential values. |
+| **Initial State / Runtime** | Read values but do NOT delegate — these are consumed by `autonomous.mjs`, not agents. |
+
+6. After all delegations complete, update MEMORY.md: set `PLAN_MD_Hash: [new-hash]`
+7. If any files were modified (CLAUDE.md, PRODUCT.md, TODO.md), commit: `git add CLAUDE.md PRODUCT.md TODO.md MEMORY.md && git commit -m "chore: propagate PLAN.md changes to project files"`
+8. Push if remote exists: `git push origin HEAD`
+9. Skip this entire step if PLAN.md does not exist.
+
+**How to detect which sections changed** (without storing the old file):
+- Compare PLAN.md values against current project files:
+  - `Product Vision` → compare MVP features list against PRODUCT.md features
+  - `Technical Decisions` → compare framework/backend/database against CLAUDE.md Tech Stack
+  - `Workflow` → compare mode against CLAUDE.md `Workflow:` field
+  - `Constraints` → compare coverage threshold against CLAUDE.md code quality section
+- If a PLAN.md value differs from the corresponding project file value, that section "changed"
+
+### 11. Retroactive git integration sync
+- **Trigger condition**: remote exists (`git remote -v | grep origin`) AND TODO.md exists with tasks BUT no `<!-- #N -->` markers found in TODO.md AND CLI is available (`gh --version` or `glab --version`) AND auth is valid (`gh auth status` or `glab auth status`)
+- This means work was done locally without git integration (token was missing or platform wasn't set up), and now it's available
+- Delegate to `devops-integrator` agent:
+  "Run retroactive sync (Operation 9). TODO.md has tasks completed locally without git integration.
+  Create milestones for all phases, create issues for all tasks, and sync their status:
+  - `[x]` tasks → create issue with `status::done` label (already completed locally)
+  - `[~]` tasks → create issue with `status::skipped` label
+  - `[ ]` tasks → create issue with `status::todo` label
+  Add `<!-- #N -->` markers to TODO.md for all created issues.
+  This is a one-time sync — subsequent iterations will use normal git integration."
+- After sync, commit the updated TODO.md: `git add TODO.md && git commit -m "chore: sync TODO.md with git platform issues"`
+- Push if remote exists: `git push origin HEAD`
+- Log in MEMORY.md Notes: "Retroactive git sync completed — [N] issues created, [M] marked as done"
+- Skip if any trigger condition is not met (no remote, no TODO.md, markers already present, CLI missing, auth invalid)
 
 ### 12. Ingest external issues (if git integration active)
 - **Only run at phase transitions** — not every invocation
@@ -321,7 +322,7 @@ To determine if a task is frontend, backend, or fullstack, use this heuristic:
 - Read MEMORY.md, find next incomplete item and current phase
 - Update MEMORY.md: set `Current Step: 1 — PICK`
 - Cross-reference with TODO.md — find the first unchecked `- [ ]` task in the current phase
-  - **Kit-upgrade tasks first**: if any `- [ ]` tasks in the current phase have `Kit-Upgrade:` tag, pick those before any regular tasks (regardless of position in the phase)
+  - **Kit-upgrade tasks first**: if any `- [ ]` tasks in the current phase have `Kit-Upgrade:` tag, pick those before any regular tasks (regardless of position in the phase). **Exception**: if `Current Worktree` is set in MEMORY.md (in-progress task from a previous session), finish that task first — kit-upgrade will be picked in the next clean invocation. Never remove an in-progress worktree to make room for a kit-upgrade task.
   - Skip tasks marked as `- [~]` (skipped/blocked)
 - **If no `[ ]` tasks remain in the current phase**: advance to the next phase. Update MEMORY.md `Current Phase` to the next phase heading from TODO.md. Then look for the first `- [ ]` task in that new phase. This IS a phase transition — the phase transition check below will trigger for the first task. If no `[ ]` tasks remain in ANY phase, go to the final completion sequence in STEP 12.
 - **Dependency check**: verify ALL tasks listed in "Depends on" are checked `[x]` in TODO.md. If any dependency is incomplete, skip this task and pick the next one without unmet dependencies.

package/dist/template/.claude/docker/Dockerfile

@@ -29,8 +29,8 @@ RUN GLAB_VER=$(curl -fsSL "https://gitlab.com/api/v4/projects/34675721/releases/
       -o /tmp/glab.deb && \
     dpkg -i /tmp/glab.deb && rm /tmp/glab.deb
 
-# Install bun (system-wide so non-root claude user can access it)
-RUN BUN_INSTALL=/usr/local curl -fsSL https://bun.sh/install | bash
+# Install bun (system-wide via npm — reliable PATH, works for non-root claude user)
+RUN npm install -g bun
 
 # Install Claude Code natively as the claude user
 RUN gosu claude bash -c 'curl -fsSL https://claude.ai/install.sh | bash'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.87",
+  "version": "1.1.89",
   "description": "Scaffold a project with Claude Code agents for autonomous AI-driven development",
   "type": "module",
   "bin": {