maestro-flow 0.3.37 → 0.3.39

package/.codex/skills/manage-knowhow/SKILL.md

@@ -1,95 +1,95 @@
----
-name: manage-knowhow
-description: Manage knowhow entries across workflow and system stores (list, search, view, edit, delete, prune)
-argument-hint: "[list|search|view|edit|delete|prune] [query|id|file] [--store workflow|system|all] [--tag tag] [--type type]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Manage knowhow entries across workflow and system stores. Provides list, search, view, edit, delete, and prune operations over `.workflow/knowhow/` (workflow store) and `~/.claude/projects/{project}/memory/` (system store).
-</purpose>
-
-<context>
-$ARGUMENTS — subcommand followed by options. Defaults to `list` if no arguments.
-
-```bash
-$manage-knowhow
-$manage-knowhow "list --store workflow"
-$manage-knowhow "search authentication"
-$manage-knowhow "view KNW-20260318-001"
-$manage-knowhow "edit MEMORY.md"
-$manage-knowhow "delete TIP-20260318-001 --confirm"
-$manage-knowhow "prune --before 2026-01-01 --type tip --dry-run"
-```
-
-**Subcommands**: `list`, `search`, `view`, `edit`, `delete`, `prune`.
-
-**Flags**:
-- `--store workflow|system|all` — Target store (default: all)
-- `--tag <tag>` — Filter by tag
-- `--type <session|tip|template|recipe|reference|decision>` — Filter by knowhow type
-- `--confirm` — Skip delete confirmation prompt
-- `--before <date>` / `--after <date>` — Date filters for prune
-- `--dry-run` — Preview prune without deleting
-</context>
-
-<execution>
-
-### Step 1: Resolve Store Paths
-
-- **Workflow store**: `.workflow/knowhow/` (entries: `KNW-*.md`, `TIP-*.md`, `TPL-*.md`, `RCP-*.md`, `REF-*.md`, `DCS-*.md`, indexed in `.workflow/wiki-index.json`)
-- **System store**: `~/.claude/projects/{project}/memory/` (files: `MEMORY.md` + topic `.md` files)
-
-Derive system path from project root (replace path separators with `--`, prefix drive letter).
-
-### Step 2: Parse Subcommand
-
-Default to `list` if no arguments. Parse first token as subcommand.
-
-### Step 3: Execute Subcommand
-
-**list**: Show entries from both stores (or filtered by `--store`, `--tag`, `--type`).
-- Workflow: use `maestro wiki list --type knowhow --json` or read `.workflow/wiki-index.json`, display ID, type, category, date, tags, title
-- System: list `.md` files in system memory directory
-
-**search `<query>`**: Full-text grep across both stores. Rank by match count.
-
-**view `<id|file>`**: Auto-detect store from format (`KNW-*/TIP-*/TPL-*/RCP-*/REF-*/DCS-*` = workflow, else system). Display full content.
-
-**edit `<file>`**: Edit a system memory file. Read current content, apply changes. Warn if MEMORY.md exceeds 200 lines (W003).
-
-**delete `<id|file>`**: Require confirmation (or `--confirm` flag). MEMORY.md cannot be deleted (E004). Remove entry file (WikiIndexer auto-updates `.workflow/wiki-index.json` on next access).
-
-**prune**: Requires at least one filter (`--tag`, `--type`, `--before`, `--after`). Workflow store only. `--dry-run` previews without deleting.
-
-### Step 4: Integrity Check
-
-After write operations, verify:
-- No orphaned files without index entries (W001)
-- No dangling index references to missing files (W001)
-- System MEMORY.md references valid topic files (W002)
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | No stores found — run `Skill({ skill: "manage-knowhow-capture" })` or create MEMORY.md |
-| E002 | error | Entry ID or filename not found |
-| E003 | error | Prune requires at least one filter flag |
-| E004 | error | Cannot delete MEMORY.md — use `edit` subcommand instead |
-| W001 | warning | Index has orphaned files or dangling references |
-| W002 | warning | MEMORY.md references non-existent topic file |
-| W003 | warning | MEMORY.md exceeds 200 lines — content truncated at load |
-</error_codes>
-
-<success_criteria>
-- [ ] Store paths resolved correctly for both workflow and system stores
-- [ ] Subcommand parsed and validated (defaults to list)
-- [ ] list: displays entries from selected stores with filtering
-- [ ] search: full-text grep across stores, ranked by match count
-- [ ] view: auto-detects store, displays full content
-- [ ] edit: reads and applies changes to system memory files
-- [ ] delete: requires confirmation, prevents MEMORY.md deletion
-- [ ] prune: requires filter, supports --dry-run, workflow store only
-- [ ] Integrity check after write operations (orphans, dangling refs)
-</success_criteria>
+---
+name: manage-knowhow
+description: Manage knowhow entries (workflow and system)
+argument-hint: "[list|search|view|edit|delete|prune] [query|id|file] [--store workflow|system|all] [--tag tag] [--type type]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+<purpose>
+Manage knowhow entries across workflow and system stores. Provides list, search, view, edit, delete, and prune operations over `.workflow/knowhow/` (workflow store) and `~/.claude/projects/{project}/memory/` (system store).
+</purpose>
+
+<context>
+$ARGUMENTS — subcommand followed by options. Defaults to `list` if no arguments.
+
+```bash
+$manage-knowhow
+$manage-knowhow "list --store workflow"
+$manage-knowhow "search authentication"
+$manage-knowhow "view KNW-20260318-001"
+$manage-knowhow "edit MEMORY.md"
+$manage-knowhow "delete TIP-20260318-001 --confirm"
+$manage-knowhow "prune --before 2026-01-01 --type tip --dry-run"
+```
+
+**Subcommands**: `list`, `search`, `view`, `edit`, `delete`, `prune`.
+
+**Flags**:
+- `--store workflow|system|all` — Target store (default: all)
+- `--tag <tag>` — Filter by tag
+- `--type <session|tip|template|recipe|reference|decision>` — Filter by knowhow type
+- `--confirm` — Skip delete confirmation prompt
+- `--before <date>` / `--after <date>` — Date filters for prune
+- `--dry-run` — Preview prune without deleting
+</context>
+
+<execution>
+
+### Step 1: Resolve Store Paths
+
+- **Workflow store**: `.workflow/knowhow/` (entries: `KNW-*.md`, `TIP-*.md`, `TPL-*.md`, `RCP-*.md`, `REF-*.md`, `DCS-*.md`, indexed in `.workflow/wiki-index.json`)
+- **System store**: `~/.claude/projects/{project}/memory/` (files: `MEMORY.md` + topic `.md` files)
+
+Derive system path from project root (replace path separators with `--`, prefix drive letter).
+
+### Step 2: Parse Subcommand
+
+Default to `list` if no arguments. Parse first token as subcommand.
+
+### Step 3: Execute Subcommand
+
+**list**: Show entries from both stores (or filtered by `--store`, `--tag`, `--type`).
+- Workflow: use `maestro wiki list --type knowhow --json` or read `.workflow/wiki-index.json`, display ID, type, category, date, tags, title
+- System: list `.md` files in system memory directory
+
+**search `<query>`**: Full-text grep across both stores. Rank by match count.
+
+**view `<id|file>`**: Auto-detect store from format (`KNW-*/TIP-*/TPL-*/RCP-*/REF-*/DCS-*` = workflow, else system). Display full content.
+
+**edit `<file>`**: Edit a system memory file. Read current content, apply changes. Warn if MEMORY.md exceeds 200 lines (W003).
+
+**delete `<id|file>`**: Require confirmation (or `--confirm` flag). MEMORY.md cannot be deleted (E004). Remove entry file (WikiIndexer auto-updates `.workflow/wiki-index.json` on next access).
+
+**prune**: Requires at least one filter (`--tag`, `--type`, `--before`, `--after`). Workflow store only. `--dry-run` previews without deleting.
+
+### Step 4: Integrity Check
+
+After write operations, verify:
+- No orphaned files without index entries (W001)
+- No dangling index references to missing files (W001)
+- System MEMORY.md references valid topic files (W002)
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | error | No stores found — run `Skill({ skill: "manage-knowhow-capture" })` or create MEMORY.md |
+| E002 | error | Entry ID or filename not found |
+| E003 | error | Prune requires at least one filter flag |
+| E004 | error | Cannot delete MEMORY.md — use `edit` subcommand instead |
+| W001 | warning | Index has orphaned files or dangling references |
+| W002 | warning | MEMORY.md references non-existent topic file |
+| W003 | warning | MEMORY.md exceeds 200 lines — content truncated at load |
+</error_codes>
+
+<success_criteria>
+- [ ] Store paths resolved correctly for both workflow and system stores
+- [ ] Subcommand parsed and validated (defaults to list)
+- [ ] list: displays entries from selected stores with filtering
+- [ ] search: full-text grep across stores, ranked by match count
+- [ ] view: auto-detects store, displays full content
+- [ ] edit: reads and applies changes to system memory files
+- [ ] delete: requires confirmation, prevents MEMORY.md deletion
+- [ ] prune: requires filter, supports --dry-run, workflow store only
+- [ ] Integrity check after write operations (orphans, dangling refs)
+</success_criteria>

package/.codex/skills/manage-knowhow-capture/SKILL.md

@@ -1,110 +1,110 @@
----
-name: manage-knowhow-capture
-description: Capture reusable knowledge into .workflow/knowhow/ — session compact, template, recipe, reference, decision, or tip
-argument-hint: "[type] [description] [--lang lang] [--source url] [--tag tag1,tag2]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Capture reusable knowledge into `.workflow/knowhow/`. Six content types: `session` (full session recovery), `template` (code/config pattern), `recipe` (step-by-step guide), `reference` (external doc summary), `decision` (ADR), `tip` (quick note). Auto-detects type or asks user.
-</purpose>
-
-<context>
-$ARGUMENTS — type token followed by description and optional flags.
-
-```bash
-$manage-knowhow-capture
-$manage-knowhow-capture "compact"
-$manage-knowhow-capture "template React form pattern --lang typescript"
-$manage-knowhow-capture "tip Always check state.json before phase operations --tag workflow,state"
-$manage-knowhow-capture "recipe Deploy to production --tag deploy,ops"
-$manage-knowhow-capture "reference Stripe API --source https://docs.stripe.com/api"
-$manage-knowhow-capture "decision Use PostgreSQL over MongoDB --status accepted"
-```
-
-**Types**: `compact` | `template` | `recipe` | `reference` | `decision` | `tip`
-
-**Flags**:
-- `--lang <lang>` — Language for templates (typescript, python, bash, yaml, ...)
-- `--source <url>` — Source URL for references
-- `--tag tag1,tag2` — Categorization tags
-- `--title <title>` — Explicit title
-</context>
-
-<execution>
-
-### Step 1: Validate
-
-Verify `.workflow/` exists (E001). Create `.workflow/knowhow/` if missing.
-
-### Step 2: Detect Type
-
-Parse first token as type. If absent or ambiguous, ask user via AskUserQuestion.
-
-| Token | Type |
-|-------|------|
-| `compact`, `session`, `压缩` | session |
-| `template`, `tpl`, `模板` | template |
-| `recipe`, `rcp`, `配方`, `步骤` | recipe |
-| `reference`, `ref`, `参考` | reference |
-| `decision`, `dcs`, `决策` | decision |
-| `tip`, `note`, `记录` | tip |
-
-### Step 3: Capture Content by Type
-
-**session** (KNW-{YYYYMMDD}-{HHMM}.md):
-Extract from conversation: objective, key decisions, modified files (absolute paths), execution plan (verbatim), pending work, notes. Sections: Session ID, Project Root, Objective, Execution Plan, Working Files, Reference Files, Last Action, Decisions, Constraints, Dependencies, Changes Made, Pending, Notes.
-
-**template** (TPL-{YYYYMMDD}-{HHMM}.md):
-Prompt for or extract: language (`--lang`), usage context, code content, parameters, dependencies. Sections: Usage, Parameters, Dependencies, Code (fenced block).
-
-**recipe** (RCP-{YYYYMMDD}-{HHMM}.md):
-Prompt for or extract: goal, prerequisites, numbered steps, expected outcome, common pitfalls, related entries. Sections: Goal, Prerequisites, Steps, Expected Outcome, Common Pitfalls, Related.
-
-**reference** (REF-{YYYYMMDD}-{HHMM}.md):
-Source from `--source` flag (offer WebFetch if URL). Extract: key points, applicable scenarios, quick examples. Sections: Source, Key Points, Applicable Scenarios, Quick Examples.
-
-**decision** (DCS-{YYYYMMDD}-{HHMM}.md):
-Prompt for or extract: context, decision, alternatives (at least 2), rationale, consequences. Sections: Context, Decision, Alternatives Considered (table), Rationale, Consequences, Related.
-
-**tip** (TIP-{YYYYMMDD}-{HHMM}.md):
-Content from remaining arguments. Auto-detect context from recent conversation files. Sections: Content, Context, Tags, Timestamp.
-
-### Step 4: Write File
-
-Write to `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{HHMM}.md` with YAML frontmatter:
-
-```yaml
----
-title: {auto or --title}
-type: {type}
-category: {type}
-created: {ISO timestamp}
-tags: [{tags}]
-```
-Plus type-specific: `lang` (template), `source` (reference), `status` (decision).
-
-### Step 5: Confirm
-
-Display: type, ID, file path, and type-specific summary.
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | `.workflow/` not initialized — run `Skill({ skill: "maestro-init" })` first |
-| E002 | error | Template: no code provided after prompt |
-| E003 | error | Recipe: no steps provided after prompt |
-| W001 | warning | No active workflow session — compact captures conversation only |
-| W002 | warning | No explicit plan found — using inferred plan |
-| W003 | warning | `--source` URL could not be fetched — proceeding with manual entry |
-</error_codes>
-
-<success_criteria>
-- [ ] `.workflow/` existence validated; `.workflow/knowhow/` created if missing
-- [ ] Type detected or prompted (all 6 types)
-- [ ] Type-specific content collected (code for template, steps for recipe, etc.)
-- [ ] YAML frontmatter with type-specific fields written
-- [ ] Markdown file written with correct prefix and structured sections
-- [ ] Confirmation displayed with ID, type, category, and file path
-</success_criteria>
+---
+name: manage-knowhow-capture
+description: Capture reusable knowledge as templates, recipes, or tips
+argument-hint: "[type] [description] [--lang lang] [--source url] [--tag tag1,tag2]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+<purpose>
+Capture reusable knowledge into `.workflow/knowhow/`. Six content types: `session` (full session recovery), `template` (code/config pattern), `recipe` (step-by-step guide), `reference` (external doc summary), `decision` (ADR), `tip` (quick note). Auto-detects type or asks user.
+</purpose>
+
+<context>
+$ARGUMENTS — type token followed by description and optional flags.
+
+```bash
+$manage-knowhow-capture
+$manage-knowhow-capture "compact"
+$manage-knowhow-capture "template React form pattern --lang typescript"
+$manage-knowhow-capture "tip Always check state.json before phase operations --tag workflow,state"
+$manage-knowhow-capture "recipe Deploy to production --tag deploy,ops"
+$manage-knowhow-capture "reference Stripe API --source https://docs.stripe.com/api"
+$manage-knowhow-capture "decision Use PostgreSQL over MongoDB --status accepted"
+```
+
+**Types**: `compact` | `template` | `recipe` | `reference` | `decision` | `tip`
+
+**Flags**:
+- `--lang <lang>` — Language for templates (typescript, python, bash, yaml, ...)
+- `--source <url>` — Source URL for references
+- `--tag tag1,tag2` — Categorization tags
+- `--title <title>` — Explicit title
+</context>
+
+<execution>
+
+### Step 1: Validate
+
+Verify `.workflow/` exists (E001). Create `.workflow/knowhow/` if missing.
+
+### Step 2: Detect Type
+
+Parse first token as type. If absent or ambiguous, ask user via AskUserQuestion.
+
+| Token | Type |
+|-------|------|
+| `compact`, `session`, `压缩` | session |
+| `template`, `tpl`, `模板` | template |
+| `recipe`, `rcp`, `配方`, `步骤` | recipe |
+| `reference`, `ref`, `参考` | reference |
+| `decision`, `dcs`, `决策` | decision |
+| `tip`, `note`, `记录` | tip |
+
+### Step 3: Capture Content by Type
+
+**session** (KNW-{YYYYMMDD}-{HHMM}.md):
+Extract from conversation: objective, key decisions, modified files (absolute paths), execution plan (verbatim), pending work, notes. Sections: Session ID, Project Root, Objective, Execution Plan, Working Files, Reference Files, Last Action, Decisions, Constraints, Dependencies, Changes Made, Pending, Notes.
+
+**template** (TPL-{YYYYMMDD}-{HHMM}.md):
+Prompt for or extract: language (`--lang`), usage context, code content, parameters, dependencies. Sections: Usage, Parameters, Dependencies, Code (fenced block).
+
+**recipe** (RCP-{YYYYMMDD}-{HHMM}.md):
+Prompt for or extract: goal, prerequisites, numbered steps, expected outcome, common pitfalls, related entries. Sections: Goal, Prerequisites, Steps, Expected Outcome, Common Pitfalls, Related.
+
+**reference** (REF-{YYYYMMDD}-{HHMM}.md):
+Source from `--source` flag (offer WebFetch if URL). Extract: key points, applicable scenarios, quick examples. Sections: Source, Key Points, Applicable Scenarios, Quick Examples.
+
+**decision** (DCS-{YYYYMMDD}-{HHMM}.md):
+Prompt for or extract: context, decision, alternatives (at least 2), rationale, consequences. Sections: Context, Decision, Alternatives Considered (table), Rationale, Consequences, Related.
+
+**tip** (TIP-{YYYYMMDD}-{HHMM}.md):
+Content from remaining arguments. Auto-detect context from recent conversation files. Sections: Content, Context, Tags, Timestamp.
+
+### Step 4: Write File
+
+Write to `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{HHMM}.md` with YAML frontmatter:
+
+```yaml
+---
+title: {auto or --title}
+type: {type}
+category: {type}
+created: {ISO timestamp}
+tags: [{tags}]
+```
+Plus type-specific: `lang` (template), `source` (reference), `status` (decision).
+
+### Step 5: Confirm
+
+Display: type, ID, file path, and type-specific summary.
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | error | `.workflow/` not initialized — run `Skill({ skill: "maestro-init" })` first |
+| E002 | error | Template: no code provided after prompt |
+| E003 | error | Recipe: no steps provided after prompt |
+| W001 | warning | No active workflow session — compact captures conversation only |
+| W002 | warning | No explicit plan found — using inferred plan |
+| W003 | warning | `--source` URL could not be fetched — proceeding with manual entry |
+</error_codes>
+
+<success_criteria>
+- [ ] `.workflow/` existence validated; `.workflow/knowhow/` created if missing
+- [ ] Type detected or prompted (all 6 types)
+- [ ] Type-specific content collected (code for template, steps for recipe, etc.)
+- [ ] YAML frontmatter with type-specific fields written
+- [ ] Markdown file written with correct prefix and structured sections
+- [ ] Confirmation displayed with ID, type, category, and file path
+</success_criteria>

package/.codex/skills/manage-learn/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-learn
-description: Capture atomic learning insights into .workflow/learning/lessons.jsonl. Lightweight CRUD over the shared learning store — supports capture, list, search, and show modes. No LLM or CLI calls; all operations are pure file reads and writes.
+description: Capture and search learning insights and tips
 argument-hint: "[\"<insight text>\"|list|search <query>|show <INS-id>] [--category pattern|antipattern|decision|tool|gotcha|technique] [--tag t1,t2] [--phase N] [--confidence high|medium|low]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---

package/.codex/skills/manage-status/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: manage-status
-description: Display project dashboard with phase progress, active tasks, and next steps
+description: Show project dashboard with progress and next steps
 argument-hint: ""
 allowed-tools: Read, Bash, Glob, Grep
 ---

package/.codex/skills/manage-wiki/SKILL.md

@@ -1,55 +1,55 @@
----
-name: manage-wiki
-description: Wiki knowledge graph management — health dashboard, orphan cleanup, entry search, and graph statistics
-argument-hint: "[health|search|cleanup|stats] [options]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Unified wiki graph management. Health monitoring, interactive search, orphan cleanup, and graph statistics. Day-to-day operations to keep the knowledge graph healthy.
-
-Complements `wiki-connect` (link discovery) and `wiki-digest` (synthesis) with operational tooling.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/wiki-manage.md
-</required_reading>
-
-<context>
-$ARGUMENTS — subcommand and optional flags.
-
-**Subcommands:**
-| Subcommand | Description |
-|-----------|-------------|
-| `health` | Health dashboard — score, broken links, orphans, hubs (default) |
-| `search <query>` | Interactive BM25 search with follow-up actions |
-| `cleanup` | Find and resolve orphans, broken links, stale entries |
-| `stats` | Graph statistics — type distribution, tag frequency, growth |
-
-**Flags:**
-- `--type <type>` — Filter: spec, knowhow, note, lesson, issue
-- `--fix` — Auto-fix issues during cleanup
-- `--json` — JSON output
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/wiki-manage.md' completely.
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | fatal | `.workflow/` not initialized |
-| E002 | fatal | No wiki entries found |
-| E003 | error | Invalid subcommand |
-| W001 | warning | Health score below 50 |
-| W002 | warning | Cleanup had partial failures |
-</error_codes>
-
-<success_criteria>
-- [ ] Subcommand parsed (health/search/cleanup/stats)
-- [ ] Wiki data loaded via `maestro wiki` CLI
-- [ ] Results displayed in formatted output
-- [ ] If cleanup --fix: issues resolved and delta reported
-- [ ] Next-step suggestions provided
-</success_criteria>
+---
+name: manage-wiki
+description: Manage wiki graph -- health, cleanup, search, stats
+argument-hint: "[health|search|cleanup|stats] [options]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+<purpose>
+Unified wiki graph management. Health monitoring, interactive search, orphan cleanup, and graph statistics. Day-to-day operations to keep the knowledge graph healthy.
+
+Complements `wiki-connect` (link discovery) and `wiki-digest` (synthesis) with operational tooling.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/wiki-manage.md
+</required_reading>
+
+<context>
+$ARGUMENTS — subcommand and optional flags.
+
+**Subcommands:**
+| Subcommand | Description |
+|-----------|-------------|
+| `health` | Health dashboard — score, broken links, orphans, hubs (default) |
+| `search <query>` | Interactive BM25 search with follow-up actions |
+| `cleanup` | Find and resolve orphans, broken links, stale entries |
+| `stats` | Graph statistics — type distribution, tag frequency, growth |
+
+**Flags:**
+- `--type <type>` — Filter: spec, knowhow, note, lesson, issue
+- `--fix` — Auto-fix issues during cleanup
+- `--json` — JSON output
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/wiki-manage.md' completely.
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | fatal | `.workflow/` not initialized |
+| E002 | fatal | No wiki entries found |
+| E003 | error | Invalid subcommand |
+| W001 | warning | Health score below 50 |
+| W002 | warning | Cleanup had partial failures |
+</error_codes>
+
+<success_criteria>
+- [ ] Subcommand parsed (health/search/cleanup/stats)
+- [ ] Wiki data loaded via `maestro wiki` CLI
+- [ ] Results displayed in formatted output
+- [ ] If cleanup --fix: issues resolved and delta reported
+- [ ] Next-step suggestions provided
+</success_criteria>