@polymorphism-tech/morph-spec 4.7.2 → 4.8.4

package/.morph/plans/eager-watching-bunny.md

@@ -1,105 +0,0 @@
-# Plan: Fix Statusline Not Being Installed
-
-## Context
-
-`morph-spec init` is supposed to install the global statusline to `~/.claude/` so
-it appears in every Claude Code session. Two bugs exist:
-
-1. **`update.js` never calls `installGlobalStatusline`** — running `morph-spec update`
-   leaves the statusline missing or stale, and there is no path for existing users to
-   get it without running `init` from scratch.
-2. **No success confirmation in `init.js` output** — after a successful installation the
-   "Files installed:" list never mentions `~/.claude/statusline.sh`, so users assume
-   it was skipped (especially since failures are silently swallowed by a bare `catch {}`).
-
-Root cause confirmed by: reading `update.js` (no `installGlobalStatusline` import or call)
-and `init.js` lines 462–505 (success block omits statusline entry). Tests for
-`installGlobalStatusline` in isolation pass; there is no integration test covering the
-init/update flow.
-
----
-
-## Critical Files
-
-| File | Change |
-|------|--------|
-| `src/commands/project/update.js` | Add `installGlobalStatusline` import + call |
-| `src/commands/project/init.js` | Add `✓ ~/.claude/statusline.sh` to success output |
-| `test/hooks/hooks-installer.test.js` | Already has good coverage — no change needed |
-| `test/commands/init.test.js` | Add `statusline-installation` describe suite |
-
----
-
-## Implementation Steps
-
-### 1. `update.js` — Add statusline installation
-
-**File:** `src/commands/project/update.js`
-
-**Import change** (line 27 — extend existing destructure):
-```js
-import { installClaudeHooks, installGlobalStatusline } from '../../utils/claude-settings-manager.js';
-```
-
-**Call** — insert after the CLAUDE.md sync block (after line 280, before "Update Claude
-Code hooks" at line 282):
-```js
-// Sync statusline globally to ~/.claude/
-updateSpinner.text = 'Syncing statusline to ~/.claude/...';
-const HOOKS_SRC = join(__dirname, '..', '..', '..', 'framework', 'hooks', 'claude-code');
-try {
-  await installGlobalStatusline(HOOKS_SRC);
-} catch {
-  // Non-critical: global dir may not be writable in all environments
-  logger.dim('  ⚠ Could not install statusline globally (non-critical)');
-}
-```
-
-**Success output** — add line after `.claude/CLAUDE.md` entry (around line 324):
-```js
-logger.dim('  ✓ ~/.claude/statusline.sh (global statusline synced)');
-```
-
-Note: `update.js` already uses `__dirname` (defined at line 6 via `fileURLToPath`),
-so use `__dirname` instead of `import.meta.dirname` to stay consistent with the file.
-
----
-
-### 2. `init.js` — Add statusline to success output
-
-**File:** `src/commands/project/init.js`
-
-After line 505 (`logger.dim('  ✓ .claude/agents/...')`), add:
-```js
-logger.dim('  ✓ ~/.claude/statusline.sh (global statusline installed)');
-```
-
-This line is unconditional — the installation is always attempted and the message
-reflects the intent (mirrors how skills/agents are always listed even without a flag).
-
----
-
-### 3. `test/commands/init.test.js` — Add statusline integration test suite
-
-Add a new `describe('statusline-installation')` block that:
-- Calls `installGlobalStatusline` directly with a `globalClaudeDirOverride` temp dir
-  and the real `framework/hooks/claude-code` source path
-- Asserts `statusline.sh` and `statusline.py` were copied
-- Asserts `settings.json` has a `statusLine` key pointing to `statusline.sh`
-
-This mirrors the pattern used by the `rules-installation` suite.
-
----
-
-## Verification
-
-```bash
-# Run full test suite — must stay green (678+ pass, 0 fail)
-node --test --test-concurrency=1
-
-# Smoke test update path
-node bin/morph-spec.js update --skip-detection --skip-mcp 2>&1 | grep -i statusline
-
-# Manually verify ~/.claude/statusline.sh exists and settings.json has statusLine key
-node -e "const s = require('fs').readFileSync(require('os').homedir()+'/.claude/settings.json','utf8'); console.log(JSON.parse(s).statusLine)"
-```

package/.morph/plans/temporal-seeking-nebula.md

@@ -1,45 +0,0 @@
-# Plan: Remove `detect` command and fix `init` for PowerShell execution
-
-## Context
-
-`morph-spec init` is run from PowerShell (not inside Claude Code), so `detectClaudeCode()` always returns false, making step 13 a dead code branch that shows a confusing warning. `morph-spec detect` is registered but provides no additional value beyond what `init` already does with `detectProject()`. `--wizard` is referenced in messages but was never registered as a CLI option. This plan removes the dead code and makes `init` self-sufficient.
-
-## What changes
-
-### 1. Delete `src/commands/project/detect.js`
-The command is obsolete — its functionality (stack/arch detection + saving to `.morph/project/context/`) is superseded by the `detectProject()` call already inside `init` at step 11c.
-
-### 2. `bin/morph-spec.js`
-- Remove `import { detectCommand }` (line 14)
-- Remove the `.command('detect')` block (lines 131–136)
-
-### 3. `src/commands/project/init.js`
-- Remove imports: `AutoContextOrchestrator` (line 21), `detectClaudeCode` (line 22)
-- **Remove step 13 entirely** (lines 509–540) — the entire `if (!options.skipDetection && detectClaudeCode())` / `else if` / `else` block
-- Fix context README.md template (line 110): remove `Run \`morph-spec detect\`` sentence, replace with `Edit this file to describe your project context.`
-- Fix Next Steps (line 470): remove `logger.step(1, 'Run detection: morph-spec detect')`, renumber remaining steps (step 1 → "Review .morph/config/config.json", step 2 → "Open project in VS Code with Claude Code", step 3 → "Start your first feature:")
-
-### 4. `src/commands/project/update.js`
-- Remove imports: `AutoContextOrchestrator`, `detectClaudeCode` (lines ~3–4 in that file)
-- Remove the `if (!options.skipDetection && detectClaudeCode())` / `else if` / `else` block (lines 331–363)
-
-## Files to modify
-- `bin/morph-spec.js`
-- `src/commands/project/init.js`
-- `src/commands/project/update.js`
-
-## Files to delete
-- `src/commands/project/detect.js`
-
-## Files NOT changed
-- `test/integration/wizard-fallback.test.js` — tests `mapAnswersToConfig()` from `wizard-questions.js`, unrelated to detect command; still passes
-- `test/commands/init.test.js` — no references to detect/wizard/detectClaudeCode; unaffected
-- `src/core/orchestrator.js`, `src/ui/wizard-questions.js`, `src/llm/environment-detector.js` — left in place (may be used elsewhere); just remove imports/usage from init+update
-- `src/lib/detectors/index.js` + `detectProject()` — **kept** in init (step 11c); this is the static file-based stack detection that works without Claude Code
-
-## Verification
-1. `node bin/morph-spec.js --help` — `detect` command should no longer appear
-2. `node bin/morph-spec.js init --help` — no `--skip-detection` or `--wizard` references
-3. `node bin/morph-spec.js update --help` — same
-4. Run test suite: `npm test` — should still pass 678 tests (no tests reference detect/wizard in init.test.js)
-5. Manual: run `morph-spec init` from PowerShell in a test project — should complete without the "Claude Code not detected" warning

package/.morph/state.json

@@ -1,48 +0,0 @@
-{
-  "version": "4.0.0",
-  "features": {
-    "override-feature": {
-      "status": "in_progress",
-      "phase": "implement",
-      "tasks": {
-        "total": 20,
-        "completed": 30
-      },
-      "checkpoints": [
-        {
-          "passed": true
-        },
-        {
-          "passed": true
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        },
-        {
-          "passed": false
-        }
-      ],
-      "trustConfig": {}
-    }
-  },
-  "threads": {},
-  "metadata": {}
-}

package/CLAUDE.md

@@ -1,77 +0,0 @@
-# MORPH-SPEC Runtime Instructions
-
-> by Polymorphism Tech — Spec-driven development for .NET/Blazor/Next.js/Azure
-
----
-
-## Project Context
-
-@.morph/context/README.md
-
----
-
-## Critical Rules
-
-**NEVER:**
-- Skip to code without a specification
-- Implement without design approval
-- Ignore standards in `.morph/framework/standards/`
-- Create infrastructure manually
-- Generate code without defined contracts
-
-**ALWAYS:**
-- Follow the mandatory phases
-- Generate outputs in `.morph/features/{feature}/`
-- Document decisions in `decisions.md`
-- Checkpoint every 3 implemented tasks
-- Use Infrastructure as Code
-
----
-
-## Quick Reference
-
-| Command | Purpose |
-|---------|---------|
-| `/morph-proposal {feature}` | Full spec pipeline (phases 1–4, pauses for approval) |
-| `/morph-apply {feature}` | Implement feature (phase 5) |
-| `/morph-status` | Feature status dashboard |
-| `/morph-preflight` | Pre-implementation validation |
-
----
-
-## State & Outputs
-
-| Path | Notes |
-|------|-------|
-| `.morph/state.json` | **READ-ONLY** — use `morph-spec` CLI to update |
-| `.morph/features/{feature}/{phase}/` | Feature outputs organized by phase |
-| `.morph/framework/` | **READ-ONLY** — framework files managed by morph-spec |
-| `.morph/config/config.json` | Project configuration (editable) |
-
----
-
-## Phase Sequence
-
-```
-proposal → setup → [uiux] → design → clarify → tasks → implement → [sync]
-```
-
-Use `morph-spec status {feature}` to see current phase and pending approval gates.
-
----
-
-## Agents
-
-Tier-1 and tier-2 MORPH agents are available as native subagents in `.claude/agents/`.
-They can be invoked directly by Claude Code during multi-agent workflows.
-
----
-
-## Context Window Tip
-
-When using 3+ MCPs, add `"experimental": { "mcpCliMode": true }` to `.claude/settings.json`.
-MCP tools load on-demand instead of all at startup — keeps context clean for actual work.
-
----
-
-*MORPH-SPEC v4.5.0 by Polymorphism Tech*

package/docs/ARCHITECTURE.md

@@ -1,331 +0,0 @@
-# morph-spec Architecture
-
-> System design reference for morph-spec v4.6.0
-
----
-
-## Overview
-
-morph-spec is a CLI tool that scaffolds a spec-driven development workflow on top of Claude Code. It installs a structured set of files into `.morph/` and `.claude/`, then lets the AI orchestrate feature development through well-defined phases with approval gates.
-
-The framework has three main concerns:
-
-1. **State** — tracking features, phases, and outputs in `.morph/state.json`
-2. **Agents** — 37 specialized agents organized in 4 tiers, installed as native Claude Code subagents
-3. **Workflow** — 8 phases from proposal through implementation, enforced via hooks and guards
-
----
-
-## Agent hierarchy
-
-```
-Tier 1 — Orchestrators (3)
-  standards-architect   always active — Chief Architect, enforces standards
-  ai-system-architect   on-demand — multi-agent / AI system design
-  po-pm-advisor         on-demand — requirements, business value
-
-Tier 2 — Domain Leaders (3)
-  dotnet-senior         always active — Backend Squad lead
-  infra-architect       always active — Infrastructure Squad Leader (cloud-agnostic)
-  ui-designer           on-demand — UI/UX Squad lead
-
-Tier 3 — Specialists (27)
-  Backend (10)          ef-modeler, event-architect, api-designer, nosql-cache-expert,
-                        ddd-expert, hangfire-orchestrator, ms-agent-expert,
-                        asaas-financial, clerk-auth, resend-email
-  Frontend (3)          blazor-builder, nextjs-expert, css-specialist
-  Infrastructure (6)    azure-architect, bicep-architect, devops-engineer,
-                        container-specialist, observability-expert, azure-identity
-  Quality/Cross (8)     testing-specialist, code-analyzer, troubleshooting-expert,
-                        load-testing-expert, documentation-specialist,
-                        migration-specialist, integration-specialist, data-modeler
-
-Tier 4 — Validators (5)
-  security-expert       SQL injection, XSS, hardcoded secrets
-  architecture-expert   DbContext, async/await, DI order
-  packages-validator    NuGet conflicts, .NET 10 compatibility
-  design-system-validator CSS palette, spacing, typography
-  blazor-concurrency-validator DbContext lifecycle, async void, JSInterop
-```
-
-### Agent installation
-
-Tier 1–2 agents are installed to `.claude/agents/morph-{id}.md` with YAML frontmatter:
-
-```yaml
----
-name: morph-standards-architect
-description: Chief Architect...
-model: sonnet
----
-```
-
-Tier 3 domain agents are installed to `.claude/agents/morph-domain-{name}.md` with:
-
-```yaml
----
-model: sonnet
-memory: project
-maxTurns: 20
----
-```
-
-Both sets are updated by `morph-spec update` and `morph-spec update-agents`.
-
-### Agent detection
-
-When a feature is created, `detect-agents` matches keywords in the feature description against `agents.json` keyword lists. Matched agents are stored in `state.json` under the feature's `activeAgents` array. The active agent set determines which standards are loaded and which validators run.
-
----
-
-## Phase pipeline
-
-```
-0-proposal → 1-setup → [1.5-uiux] → 2-design → 3-clarify → 4-tasks → 5-implement → [6-sync]
-```
-
-| Phase | ID | Optional | Approval gate | Output directory |
-|-------|-----|----------|--------------|-----------------|
-| Proposal | `proposal` | No | Yes | `0-proposal/` |
-| Setup | `setup` | No | No | — |
-| UI/UX | `uiux` | Yes | Yes | `2-ui/` |
-| Design | `design` | No | Yes | `1-design/` |
-| Clarify | `clarify` | No | No | `1-design/` (updates) |
-| Tasks | `tasks` | No | Yes | `3-tasks/` |
-| Implement | `implement` | No | No | `4-implement/` |
-| Sync | `sync` | Yes | No | `.morph/context/` |
-
-Phase transitions are controlled by the state machine in `src/lib/state/`. Advancing to a phase with an approval gate is blocked until the gate is explicitly passed. `protect-spec-files.js` (hook) guards spec/contracts from edits after the design gate is passed.
-
-Canonical phase definitions live in `framework/phases.json`.
-
----
-
-## File structure
-
-### Framework source (this repo)
-
-```
-framework/
-├── agents.json              # 37 agents definition (v3.1.0)
-├── phases.json              # 8 phase definitions
-├── CLAUDE_runtime.md        # copied to .claude/CLAUDE.md on init
-├── agents/                  # tier 1-2 agent markdown files
-├── hooks/
-│   ├── claude-code/         # 11 Claude Code hook scripts
-│   │   └── shared/          # state-reader, phase-utils, hook-response, stdin-reader
-│   └── git/                 # pre-commit, commit-msg, pre-push
-├── rules/                   # 5 rule files (copied to .claude/rules/)
-├── skills/
-│   ├── README.md
-│   ├── level-0-meta/        # 7 meta skills (brainstorming, code-review, etc.)
-│   │   └── {skill}/
-│   │       ├── SKILL.md     # skill content
-│   │       ├── scripts/     # optional helper scripts
-│   │       └── references/  # optional reference materials
-│   └── level-1-workflows/   # 8 workflow skills (phase-proposal, phase-design, etc.)
-│       └── {skill}/
-│           └── SKILL.md
-├── standards/               # 74 standards, 11 categories
-│   ├── STANDARDS.json       # registry (regenerate: node scripts/generate-standards-registry.js)
-│   ├── core/
-│   ├── backend/
-│   ├── frontend/
-│   ├── infrastructure/
-│   └── integration/
-├── templates/               # Handlebars v2.0 code and IaC templates
-│   ├── infrastructure/      # Bicep, Docker, GitHub Actions
-│   └── ...
-└── workflows/
-    └── configs/             # 10 workflow configs (express, spec-only, zero-touch, fusion, ...)
-```
-
-### Installed into a project (after init)
-
-```
-.morph/
-├── config/config.json       # editable project config
-├── framework/               # READ-ONLY copy from package
-│   ├── agents.json
-│   ├── standards/
-│   └── templates/
-├── context/                 # editable project context
-│   ├── README.md            # loaded at every SessionStart
-│   └── standards.md
-├── features/{feature}/      # feature outputs
-│   ├── 0-proposal/
-│   ├── 1-design/
-│   ├── 2-ui/
-│   ├── 3-tasks/
-│   └── 4-implement/
-├── checkpoints/
-├── logs/tool-failures.log
-└── state.json               # READ-ONLY
-
-.claude/
-├── CLAUDE.md                # runtime instructions
-├── commands/                # slash command .md files
-├── skills/                  # flat install of framework/skills/
-│   └── {skill-name}/
-│       └── SKILL.md
-├── agents/                  # native subagents
-│   ├── morph-{id}.md        # tier 1-2 (from framework/agents/)
-│   └── morph-domain-{name}.md # tier 3 (from framework/skills/level-2-domains/)
-├── rules/                   # path-scoped rules (from framework/rules/)
-│   ├── morph-workflow.md    # always active
-│   ├── csharp-standards.md
-│   ├── frontend-standards.md
-│   ├── testing-standards.md
-│   └── infrastructure-standards.md
-└── settings.local.json      # hooks, permissions.deny, env vars
-```
-
----
-
-## Skills system
-
-Skills are Markdown files that provide Claude Code with domain knowledge and procedures. They are invoked via the `Skill` tool inside Claude Code.
-
-### Directory structure
-
-Each skill lives in its own directory under `framework/skills/{level}/{skill-name}/`:
-
-```
-{skill-name}/
-├── SKILL.md           # required — main content
-├── scripts/           # optional — helper scripts (.mjs)
-└── references/        # optional — reference documents
-```
-
-### Levels
-
-| Level | Directory | Count | Purpose |
-|-------|-----------|-------|---------|
-| 0 | `level-0-meta/` | 7 | Cross-cutting: brainstorming, code review, verification, tool usage |
-| 1 | `level-1-workflows/` | 8 | Phase workflows: phase-proposal, phase-setup, phase-uiux, phase-design, phase-clarify, phase-tasks, phase-implement, phase-sync |
-
-### Installation
-
-`installSkills()` in `src/utils/skills-installer.js` flattens all skills to `.claude/skills/{name}/SKILL.md`. Skills become available as `/{name}` slash commands in Claude Code.
-
----
-
-## Hooks system
-
-11 Claude Code hooks are configured in `.claude/settings.local.json`. All hooks fail-open (catch + exit 0) to prevent blocking Claude Code on errors.
-
-| Event | Hook | Function |
-|-------|------|----------|
-| `SessionStart` | `inject-morph-context.js` | Injects active feature `1-design/spec.md` (3000 char max) into context |
-| `UserPromptSubmit` | `protect-spec-files.js` | Guards spec files after design gate approval |
-| `PreToolUse` (Bash) | Prompt-type inline guard | Detects destructive shell patterns in Claude's reasoning |
-| `PreToolUse` (Write/Edit) | `validate-feature-phase.js` | Validates write targets against current phase |
-| `PostToolUse` (Write) | `track-output-creation.js` | Detects when feature output files are created; updates state directly via JSON I/O (no subprocess) |
-| `PostToolUse` (any) | `checkpoint-trigger.js` | Triggers auto-checkpoint every 3 completed tasks |
-| `PostToolUseFailure` | `handle-tool-failure.js` | Appends failure details to `.morph/logs/tool-failures.log` |
-| `Stop` | `session-summary.js` | Writes session summary |
-| `PreCompact` | `compact-context.js` | Preserves critical state before context compaction |
-| `Notification` | `morph-notify.js` | Routes approval gate notifications |
-
-Shared utilities live in `framework/hooks/claude-code/shared/`:
-- `state-reader.js` — reads `.morph/state.json` without subprocess
-- `phase-utils.js` — phase validation helpers
-- `hook-response.js` — standardized hook response formatting
-- `stdin-reader.js` — reads hook event data from stdin
-
-Git hooks (`framework/hooks/git/`): `pre-commit`, `commit-msg` (Conventional Commits), `pre-push` (runs tests).
-
-### Protected files
-
-`permissions.deny` in `settings.local.json` blocks direct edits:
-
-```json
-"permissions": {
-  "deny": [
-    "Write(.morph/state.json)",
-    "Edit(.morph/state.json)",
-    "Write(.morph/framework/**)",
-    "Edit(.morph/framework/**)"
-  ]
-}
-```
-
----
-
-## State machine
-
-`.morph/state.json` tracks the state of all features. It is managed exclusively by the CLI — never edited directly.
-
-```json
-{
-  "version": "4.0.0",
-  "features": {
-    "my-feature": {
-      "phase": "design",
-      "status": "in_progress",
-      "activeAgents": ["dotnet-senior", "ef-modeler", "testing-specialist"],
-      "approvals": {
-        "proposal": true,
-        "design": false,
-        "tasks": false
-      }
-    }
-  }
-}
-```
-
-State auto-migrates from v3.0.0 to v4.0.0 on first CLI access.
-
-Feature outputs (spec.md, contracts.cs, tasks.md, etc.) are tracked by scanning the filesystem at runtime — not stored in state. This keeps state lean and avoids the circular tracking bug of earlier versions.
-
----
-
-## Standards registry
-
-74 standards across 11 categories are registered in `framework/standards/STANDARDS.json`. Each entry has an `id`, `name`, `path`, `scope`, `layer`, and `keywords`.
-
-Regenerate the registry after adding standards:
-
-```bash
-node scripts/generate-standards-registry.js
-```
-
-Browse via CLI:
-
-```bash
-morph-spec standards --list
-morph-spec standards --list --category backend
-morph-spec standards --search "async"
-morph-spec standards --show csharp-naming
-```
-
----
-
-## Workflow configs
-
-`framework/workflows/configs/` contains 10 workflow configurations that customize how the phase pipeline runs:
-
-| Config | Description |
-|--------|-------------|
-| `default` | Full pipeline with all phases |
-| `express` | Condensed pipeline for small features |
-| `spec-only` | Proposal through tasks, no implementation |
-| `zero-touch` | Fully automated (maximum trust level) |
-| `fusion` | Combines setup + design into single phase |
-| ... | + 5 more |
-
-Trust levels (`low`, `medium`, `high`, `maximum`) control how many approval gates are enforced automatically vs manually.
-
----
-
-## CLI internals
-
-- **Entry point:** `bin/morph-spec.js` — Commander.js, 110+ commands
-- **Commands:** `src/commands/` — organized into subdirectories by domain
-- **Libraries:** `src/lib/` — state, validators, templates, agents, detection
-- **Templates engine:** Handlebars v2.0 with helpers (pascalCase, camelCase, snakeCase, pluralize)
-- **Test suite:** `test/` — Node.js built-in test runner, 625+ tests
-
----
-
-*morph-spec v4.6.0 by Polymorphism Tech*