maestro-flow 0.3.14 → 0.3.16

package/workflows/wiki-manage.md

@@ -28,7 +28,7 @@ Complements `wiki-connect.md` (link discovery) and `wiki-digest.md` (synthesis)
 
 | Flag | Effect |
 |------|--------|
-| `--type <type>` | Filter: spec, memory, note, lesson, issue |
+| `--type <type>` | Filter: spec, knowhow, note, lesson, issue |
 | `--fix` | Auto-fix issues during cleanup |
 | `--json` | JSON output |
 
@@ -38,32 +38,11 @@ Complements `wiki-connect.md` (link discovery) and `wiki-digest.md` (synthesis)
 
 ### Step 1: Gather Data
 
-Run in parallel:
-```bash
-maestro wiki health
-maestro wiki list --json
-maestro wiki orphans
-maestro wiki hubs --top 5
-```
+Run in parallel: `maestro wiki health`, `list --json`, `orphans`, `hubs --top 5`.
 
 ### Step 2: Render Dashboard
 
-```
-== Wiki Health Dashboard ==
-Score:       {score}/100
-Entries:     {total} ({spec} spec, {memory} memory, {note} note, {lesson} lesson, {issue} issue)
-Broken:      {broken_count} broken links
-Orphans:     {orphan_count} entries with no connections
-Top Hubs:    {hub1} ({degree}), {hub2} ({degree}), ...
-
-{score < 50 ? "⚠ Graph needs attention" : score < 75 ? "Graph is fair" : "Graph is healthy"}
-
-Quick actions:
-  Fix connections:  /wiki-connect --fix
-  Generate digest:  /wiki-digest
-  Cleanup orphans:  /manage-wiki cleanup --fix
-  View full graph:  maestro wiki graph
-```
+Display: health score, entry counts by type, broken links, orphan count, top hubs. Include health status message and quick-action commands (`/wiki-connect --fix`, `/wiki-digest`, `/manage-wiki cleanup --fix`, `maestro wiki graph`).
 
 ---
 
@@ -77,20 +56,7 @@ maestro wiki search "<query>" --json
 
 ### Step 2: Display Results
 
-```
-== Wiki Search: "{query}" ({count} results) ==
-
-#  ID                    Type    Title                        Tags
-1  spec-auth-001         spec    JWT token rotation           auth, security, jwt
-2  memory-auth-flow      memory  Auth module implementation   auth, session
-3  note-auth-review      note    Auth code review findings    auth, review
-
-Actions:
-  View:    maestro wiki get <id>
-  Links:   maestro wiki backlinks <id>
-  Follow:  /learn-follow <id>
-  Connect: /wiki-connect --scope <type>
-```
+Show table of results (ID, type, title, tags) with action hints: `maestro wiki get <id>`, `backlinks <id>`, `/learn-follow <id>`, `/wiki-connect --scope <type>`.
 
 ### Step 3: Interactive Follow-up
 
@@ -102,12 +68,7 @@ If not `--json`: offer to view an entry by number selection.
 
 ### Step 1: Scan Issues
 
-Gather:
-```bash
-maestro wiki health          # baseline
-maestro wiki orphans --json  # orphaned entries
-maestro wiki graph           # broken links from graph structure
-```
+Gather baseline via `maestro wiki health`, `orphans --json`, `graph`.
 
 ### Step 2: Categorize Issues
 
@@ -120,33 +81,13 @@ maestro wiki graph           # broken links from graph structure
 
 ### Step 3: Display Issues
 
-```
-== Wiki Cleanup Scan ==
-Baseline health: {score}/100
-
-Issues found:
-  Broken links:   {count}
-  Orphans:        {count}
-  Stale drafts:   {count}
-  Empty bodies:   {count}
-
-{list of issues with entry IDs and descriptions}
-```
+Show baseline health, issue counts by type, and entry-level details.
 
 ### Step 4: Apply Fixes (--fix only)
 
-For each fixable issue:
-1. Broken links: `maestro wiki update <id> --frontmatter '{"related": [filtered_list]}'`
-2. Orphans: run mini wiki-connect for each orphan (BM25 search + tag match)
-3. Stale/empty: flag but don't auto-delete (too destructive)
+Broken links: remove from frontmatter via `maestro wiki update`. Orphans: mini wiki-connect (BM25 + tag match). Stale/empty: flag only (no auto-delete).
 
-Report delta:
-```
-== Cleanup Complete ==
-Fixed:     {fixed_count} issues
-Remaining: {remaining_count} (manual review needed)
-Health:    {old_score} → {new_score} ({delta})
-```
+Report: fixed count, remaining count, health delta.
 
 ---
 
@@ -158,47 +99,9 @@ Health:    {old_score} → {new_score} ({delta})
 maestro wiki list --json
 ```
 
-### Step 2: Compute Statistics
-
-- **Type distribution**: count per type (spec, memory, note, lesson, issue)
-- **Tag frequency**: top 20 most-used tags
-- **Category distribution**: entries per category (for specs)
-- **Connectivity**: average in-degree, average out-degree, max hub size
-- **Growth**: entries created per week (from timestamps)
+### Step 2: Compute & Display Statistics
 
-### Step 3: Display
-
-```
-== Wiki Statistics ==
-
-Type Distribution:
-  spec      ████████████████  32 (40%)
-  memory    ████████          16 (20%)
-  note      ██████████        20 (25%)
-  lesson    ████              8 (10%)
-  issue     ██                4 (5%)
-  Total:    80
-
-Top Tags:
-  auth (12), performance (8), error-handling (7), testing (6), ...
-
-Connectivity:
-  Avg in-degree:  2.3
-  Avg out-degree: 1.8
-  Hub:            spec-auth (in=12)
-
-Growth (last 4 weeks):
-  Week 1: +5  |  Week 2: +8  |  Week 3: +3  |  Week 4: +12
-```
-
----
+Compute: type distribution (count/%), top 20 tags, category distribution (specs), connectivity (avg in/out-degree, max hub), growth (entries/week).
 
-## Error Codes
+Display as bar charts and summary tables.
 
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | fatal | `.workflow/` not initialized | Run `/maestro-init` |
-| E002 | fatal | No wiki entries found | Create wiki content first |
-| E003 | error | Invalid subcommand | Valid: health, search, cleanup, stats |
-| W001 | warning | Health score below 50 | Run `/wiki-connect --fix` |
-| W002 | warning | Cleanup had partial failures | Retry manually |

package/.claude/commands/maestro-coordinate.md

@@ -1,63 +0,0 @@
----
-name: maestro-coordinate
-description: CLI-based coordinator - analyze intent → select command chain → execute sequentially via maestro delegate with auto-confirm
-argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Orchestrate maestro commands via external CLI (`maestro delegate`) with async state machine.
-Classifies intent, reads project state, selects command chain, then executes each step
-through `maestro delegate --to <tool> --mode write` with a universal prompt template.
-Auto-confirm injection ensures non-blocking background execution. Structured return
-format enables context propagation between steps.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/maestro-coordinate.md
-</required_reading>
-
-<deferred_reading>
-- [coordinate template](~/.maestro/templates/cli/prompts/coordinate-step.txt) — read when filling step prompts
-</deferred_reading>
-
-<context>
-$ARGUMENTS — user intent text, or special keywords (`continue`/`next`/`status`).
-
-**Flags:**
-- `-y` / `--yes` — Auto mode: skip clarification and confirmation
-- `-c` / `--continue` — Resume previous session
-- `--dry-run` — Show planned chain without executing
-- `--chain <name>` — Force a specific chain
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/maestro-coordinate.md' completely.
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Recovery |
-|------|----------|-------------|----------|
-| E001 | error | No intent and project not initialized | Suggest maestro-init |
-| E002 | error | Clarity too low after 2 rounds | Ask to rephrase |
-| E003 | error | Step failed + abort | Suggest resume with -c |
-| E004 | error | Resume session not found | Show available sessions |
-</error_codes>
-
-<success_criteria>
-- [ ] Intent classified and chain selected via detectTaskType + chainMap
-- [ ] Each step executed via `maestro delegate` with coordinate-step template
-- [ ] Auto-confirm injected, structured return parsed
-- [ ] Each completed step analyzed via `maestro delegate --to gemini --mode analysis`
-- [ ] Analysis hints injected into next step prompt via `{{ANALYSIS_HINTS}}`
-- [ ] Gemini sessions chained via `--resume` for accumulated context
-- [ ] Session state at .workflow/.maestro-coordinate/{session_id}/
-- [ ] Completion report with per-step status and quality scores
-</success_criteria>

package/.claude/commands/manage-memory-capture.md

@@ -1,59 +0,0 @@
----
-name: manage-memory-capture
-description: Capture session memory (compact mode) into .workflow/memory/ with JSON index
-argument-hint: "[compact] [description]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-<purpose>
-Capture session working memory into `.workflow/memory/` for cross-session recovery. Compact mode only: full session compression for recovery. Entries are created via `maestro wiki create --type memory` and automatically indexed in `.workflow/wiki-index.json`. Invoked when saving session state before context loss.
-
-**Note:** Quick tips/notes have been moved to `manage-learn tip <text>`. Use that command for atomic knowledge capture.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/memory.md
-</required_reading>
-
-<context>
-Arguments: $ARGUMENTS
-
-**Mode:**
-- `compact` — Full session memory compression (files, decisions, plan state, pending work)
-- No arguments — Defaults to compact mode
-
-**Storage:**
-- `.workflow/memory/` — Memory entries directory (via `maestro wiki create --type memory`)
-- `.workflow/wiki-index.json` — Unified wiki index (auto-updated on create)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/memory.md' Part B (Memory Capture) completely.
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Stage |
-|------|----------|-------------|-------|
-| E001 | error | `.workflow/` not initialized — run `/maestro-init` first | parse_input |
-| E002 | error | Tip mode removed — use `/manage-learn tip <text>` instead | parse_input |
-| W001 | warning | No active workflow session found — compact will capture conversation only | analyze_session |
-| W002 | warning | Plan detection found no explicit plan — using inferred plan | analyze_session |
-</error_codes>
-
-<success_criteria>
-- [ ] Compact mode executed
-- [ ] Entry markdown file written to `.workflow/memory/`
-- [ ] `wiki-index.json` auto-updated via wiki create
-- [ ] All session fields populated (objective, files, decisions, plan)
-- [ ] Execution plan preserved VERBATIM (not summarized)
-- [ ] All file paths are ABSOLUTE
-- [ ] Confirmation banner displayed with entry ID
-- [ ] Next step: `/manage-status` to resume workflow, or `/manage-memory view <entry_id>` to verify captured memory
-- [ ] For tips: redirect user to `/manage-learn tip <text>`
-</success_criteria>

package/.codex/skills/maestro-coordinate/SKILL.md

@@ -1,213 +0,0 @@
----
-name: maestro-coordinate
-description: CLI-based coordinator — analyze intent → select command chain → execute sequentially via maestro delegate with auto-confirm. Async state machine with template-driven prompts and gemini analysis between steps.
-argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Sequential CLI-delegate coordinator. Each chain step executes via `maestro delegate "prompt" --to <tool> --mode write`
-with a template-driven prompt. After each step, gemini analysis evaluates output quality and generates
-optimization hints for subsequent steps. All execution is background-async with hook callbacks.
-
-```
-Intent  →  Resolve Chain  →  Step 1  →  Analysis  →  Step 2  →  Analysis  →  …  →  Report
-              (chainMap)     delegate    gemini       delegate    gemini
-                             callback   callback     callback    callback
-```
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/maestro-coordinate.codex.md — authoritative `detectTaskType`, `detectNextAction`, `chainMap` (35+ intent patterns, 40+ chain types). Read before executing any step.
-</required_reading>
-
-<deferred_reading>
-- [coordinate template](~/.maestro/templates/cli/prompts/coordinate-step.txt) — read when filling step prompts
-</deferred_reading>
-
-<context>
-$ARGUMENTS — user intent text, or special flags.
-
-**Flags:**
-- `-y, --yes` — Auto mode: skip all prompts, inject auto-confirm into delegates
-- `-c, --continue` — Resume previous session from last incomplete step
-- `--dry-run` — Show planned chain without executing
-- `--chain <name>` — Force specific chain (skips intent classification)
-
-**Session state**: `.workflow/.maestro-coordinate/{session-id}/state.json`
-</context>
-
-<invariants>
-1. **STOP after each delegate call**: Background execution via `run_in_background: true`, wait for hook callback.
-2. **State machine**: Advance via `current_step`, no sync loops for async operations.
-3. **Template-driven**: All steps use `coordinate-step.txt`, no per-command prompt assembly.
-4. **Context propagation**: Parse PHASE / spec session ID / scratch_dir / issue_id from each step output, feed to next step.
-5. **Gemini analysis after each step**: Evaluate output quality, generate hints for next step, chain via `--resume`.
-6. **Auto-confirm injection**: `{{AUTO_DIRECTIVE}}` in template prevents blocking during background execution.
-7. **Resumable**: `-c` reads `state.json`, jumps to first pending step.
-8. **Delegate tool**: `maestro delegate --to codex` for all execution steps; `--to gemini` only for post-step analysis.</invariants>
-
-<execution>
-
-### Step 1: Parse Arguments
-
-```javascript
-const args = $ARGUMENTS.trim();
-const AUTO_YES = /\b(-y|--yes)\b/.test(args);
-const RESUME = /\b(-c|--continue)\b/.test(args);
-const DRY_RUN = /\b--dry-run\b/.test(args);
-const forcedChain = args.match(/--chain\s+(\S+)/)?.[1] || null;
-const intent = args
-  .replace(/\b(-y|--yes|-c|--continue|--dry-run)\b/g, '')
-  .replace(/--chain\s+\S+/g, '')
-  .trim();
-```
-
-**If RESUME**: Find latest `state.json` in `.workflow/.maestro-coordinate/`, load → jump to Step 6.
-
-### Step 2–4: Classify Intent → Confirm
-
-1. Read `.workflow/state.json` + `.workflow/roadmap.md` + current phase
-2. If `--chain` given → use directly; else classify via `detectTaskType` + `chainMap`
-3. If clarity < 2 and not AUTO_YES → clarify via AskUserQuestion (max 2 rounds)
-4. **`--dry-run`**: Display chain and exit
-5. **User confirmation** (skip if AUTO_YES): Execute / Execute from step N / Cancel
-
-### Step 5: Setup Session
-
-```javascript
-const sessionId = `coord-${new Date().toISOString().replace(/[-:T]/g, '').slice(0, 15)}`;
-const sessionDir = `.workflow/.maestro-coordinate/${sessionId}`;
-
-const state = {
-  session_id: sessionId, status: 'running',
-  created_at: new Date().toISOString(),
-  intent, task_type: taskType, chain_name: chainName,
-  auto_mode: AUTO_YES, phase: resolvedPhase,
-  current_step: 0, gemini_session_id: null, step_analyses: [],
-  steps: chain.map((s, i) => ({
-    index: i, cmd: s.cmd, args: s.args || '',
-    status: 'pending', exec_id: null, analysis: null
-  }))
-};
-Write(`${sessionDir}/state.json`, JSON.stringify(state, null, 2));
-```
-
-### Step 6: Execute Step via maestro delegate
-
-#### 6a: Assemble args
-
-```javascript
-const AUTO_FLAG_MAP = {
-  'maestro-analyze': '-y', 'maestro-brainstorm': '-y', 'maestro-ui-design': '-y',
-  'maestro-plan': '--auto', 'maestro-spec-generate': '-y', 'quality-test': '--auto-fix',
-  'quality-retrospective': '--auto-yes',
-};
-
-function assembleArgs(step) {
-  let a = (step.args || '')
-    .replace(/\{phase\}/g, context.phase || '')
-    .replace(/\{description\}/g, context.user_intent || '')
-    .replace(/\{issue_id\}/g, context.issue_id || '')
-    .replace(/\{spec_session_id\}/g, context.spec_session_id || '')
-    .replace(/\{scratch_dir\}/g, context.scratch_dir || '');
-  if (state.auto_mode) {
-    const flag = AUTO_FLAG_MAP[step.cmd];
-    if (flag && !a.includes(flag)) a = a ? `${a} ${flag}` : flag;
-  }
-  return a.trim();
-}
-```
-
-#### 6b: Build prompt from template + launch
-
-Read `~/.maestro/templates/cli/prompts/coordinate-step.txt`, fill placeholders.
-If previous step has analysis hints, inject as `{{ANALYSIS_HINTS}}`.
-
-```javascript
-const prompt = template
-  .replace('{{COMMAND}}', `/${step.cmd}`)
-  .replace('{{ARGS}}', assembledArgs)
-  .replace('{{STEP_N}}', `${state.current_step + 1}/${state.steps.length}`)
-  .replace('{{AUTO_DIRECTIVE}}', state.auto_mode ? 'Auto-confirm all prompts. No interactive questions.' : '')
-  .replace('{{CHAIN_NAME}}', state.chain_name)
-  .replace('{{ANALYSIS_HINTS}}', analysisHints);
-
-Bash({
-  command: `maestro delegate ${escapeForShell(prompt)} --to codex --mode write`,
-  run_in_background: true, timeout: 600000
-});
-// ■ STOP — wait for hook callback
-```
-
-### Step 7: Post-Step Callback
-
-```javascript
-// Context propagation from output
-const phaseMatch = output.match(/PHASE:\s*(\d+)/m);
-if (phaseMatch) context.phase = phaseMatch[1];  // derived from output, not stored in state
-const specMatch = output.match(/SPEC-[\w-]+/);
-if (specMatch) context.spec_session_id = specMatch[0];
-const scratchMatch = output.match(/scratch_dir:\s*(.+)/m);
-if (scratchMatch) context.scratch_dir = scratchMatch[1].trim();
-
-// Success/failure
-const failed = /^STATUS:\s*FAILURE/m.test(output);
-if (!failed) { step.status = 'completed'; }
-else if (state.auto_mode && !step.retried) { step.retried = true; /* re-execute Step 6 */ return; }
-else { step.status = 'skipped'; /* or AskUserQuestion: Retry / Skip / Abort */ }
-
-Write(`${sessionDir}/step-${stepIdx + 1}-output.txt`, output);
-// → Step 7b (gemini analysis) if completed + multi-step chain
-// → else advance current_step, loop to Step 6 or Step 8
-```
-
-### Step 7b: Analyze Step Output (via gemini)
-
-```javascript
-let delegateCmd = `maestro delegate ${escapeForShell(analysisPrompt)} --to gemini --mode analysis --rule analysis-review-code-quality`;
-if (state.gemini_session_id) delegateCmd += ` --resume ${state.gemini_session_id}`;
-Bash({ command: delegateCmd, run_in_background: true, timeout: 300000 });
-// ■ STOP — wait for hook callback
-```
-
-Post-analyze: store quality_score + issues + next_step_hints in `state.step_analyses[]`, chain gemini sessions via `--resume`.
-
-### Step 8: Completion Report
-
-```
-============================================================
-  MAESTRO-COORDINATE COMPLETE
-============================================================
-  Session: {session_id}
-  Chain:   {chain_name} ({done}/{total})
-
-  Steps:
-    [✓] 1. maestro-plan — completed (quality: 85/100)
-    [✓] 2. maestro-execute — completed (quality: 78/100)
-
-  Avg Quality: {avg_score}/100
-  Next: $maestro-coordinate --continue
-============================================================
-```
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Recovery |
-|------|----------|-------------|----------|
-| E001 | error | No intent and project not initialized | Suggest $maestro-init |
-| E002 | error | Clarity too low after 2 rounds | Ask to rephrase |
-| E003 | error | Step failed + abort | Suggest resume with -c |
-| E004 | error | Resume session not found | Show available sessions |
-</error_codes>
-
-<success_criteria>
-- [ ] Intent classified and chain selected via detectTaskType + chainMap
-- [ ] Each step executed via `maestro delegate` with coordinate-step template
-- [ ] Auto-confirm injected, structured return parsed
-- [ ] Each completed step analyzed via `maestro delegate --to gemini --mode analysis`
-- [ ] Analysis hints injected into next step prompt via `{{ANALYSIS_HINTS}}`
-- [ ] Gemini sessions chained via `--resume` for accumulated context
-- [ ] Session state at .workflow/.maestro-coordinate/{session_id}/
-- [ ] Completion report with per-step status and quality scores
-</success_criteria>

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

@@ -1,93 +0,0 @@
----
-name: manage-memory-capture
-description: Capture session memory (compact or tip) into .workflow/memory/ with JSON index
-argument-hint: "[compact|tip] [description] [--tag tag1,tag2]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Capture session memory into `.workflow/memory/` with JSON index. Two modes: `compact` (full session compression) or `tip` (quick note with tags). Auto-detects mode or asks user when ambiguous.
-</purpose>
-
-<context>
-$ARGUMENTS — mode token followed by description and optional flags.
-
-```bash
-$manage-memory-capture
-$manage-memory-capture "compact"
-$manage-memory-capture "tip Always check state.json before phase operations --tag workflow,state"
-$manage-memory-capture "compact Full auth implementation session"
-```
-
-**Modes**: `compact` (full session compression) or `tip` (quick note with tags).
-No arguments: auto-detect or ask user.
-
-**Flags**:
-- `--tag tag1,tag2` — Comma-separated tags for the entry
-</context>
-
-<execution>
-
-### Step 1: Validate
-
-```bash
-test -d .workflow || exit 1  # E001: not initialized
-```
-
-Create `.workflow/memory/` if it does not exist.
-
-### Step 2: Detect Mode
-
-Parse first token as mode (`compact` or `tip`).
-If absent or ambiguous, ask user via AskUserQuestion.
-
-### Step 3: Capture Content
-
-**Compact mode**:
-1. Analyze current conversation for: objective, key decisions, modified files, current plan state, pending work
-2. Generate entry ID: `MEM-{YYYYMMDD}-{NNN}`
-3. Write `.workflow/memory/MEM-{id}.md` with sections:
-   - Objective, Key Decisions, Files Modified (absolute paths), Execution Plan (verbatim), Pending Work, Context Notes
-
-**Tip mode**:
-1. Extract content (everything after `tip`) and parse `--tag` flag
-2. Generate entry ID: `TIP-{YYYYMMDD}-{NNN}`
-3. Write `.workflow/memory/TIP-{id}.md` with: content, tags, timestamp, context
-
-### Step 4: Wiki Index Invalidation
-
-Memory files are automatically indexed by WikiIndexer. No manual index update needed — the persistent `wiki-index.json` at `.workflow/` root is regenerated on next `maestro wiki` access.
-
-For immediate visibility, use:
-```bash
-maestro wiki get memory-{slug}         # verify entry exists in wiki
-maestro wiki list --type memory        # list all memory entries
-```
-
-### Step 5: Confirm
-
-```
-=== MEMORY CAPTURED ===
-ID: {entry_id}
-Type: {compact|tip}
-File: .workflow/memory/{filename}
-```
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | `.workflow/` not initialized -- run `Skill({ skill: "maestro-init" })` first |
-| E002 | error | Empty note content in tip mode |
-| W001 | warning | No active workflow session -- compact captures conversation only |
-| W002 | warning | No explicit plan found -- using inferred plan |
-</error_codes>
-
-<success_criteria>
-- [ ] `.workflow/` existence validated; `.workflow/memory/` created if missing
-- [ ] Mode detected or prompted (compact vs tip)
-- [ ] Compact: conversation analyzed, MEM-id generated, markdown file written with all sections
-- [ ] Tip: content extracted, TIP-id generated, markdown file written
-- [ ] Index updated with new entry metadata
-- [ ] Confirmation displayed with ID, type, and file path
-</success_criteria>