bmad-module-skill-forge 0.2.0

package/src/workflows/create-skill/steps-c/step-05-compile.md

@@ -0,0 +1,198 @@
+---
+name: 'step-05-compile'
+description: 'Assemble SKILL.md, context-snippet, metadata, and references from extraction inventory'
+nextStepFile: './step-06-validate.md'
+skillSectionsData: '../data/skill-sections.md'
+---
+
+# Step 5: Compile
+
+## STEP GOAL:
+
+To assemble the complete skill content from the extraction inventory and enrichment annotations — building SKILL.md sections, context-snippet.md, metadata.json, and references/ content according to the agentskills.io format.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🎯 ALWAYS follow the exact instructions in the step file
+- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a skill compilation engine performing structured assembly
+- ✅ Every instruction in SKILL.md must trace to source code with a provenance citation
+- ✅ Uncitable content is excluded, not guessed — zero hallucination
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on assembling content from extraction inventory + enrichment
+- 🚫 FORBIDDEN to include any content without a provenance citation
+- 🚫 FORBIDDEN to write files — content stays in context until step-07
+- 🚫 FORBIDDEN to fabricate examples not found in source tests or docs
+- ⚒️ Seed `<!-- [MANUAL] -->` markers for future update-skill compatibility
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow MANDATORY SEQUENCE exactly
+- 💾 Build all content in context — do not write files
+- 📖 Follow agentskills.io section structure from data file
+- 🚫 Do not write any output files — that's step-07
+
+## CONTEXT BOUNDARIES:
+
+- Available: extraction_inventory, enrichment_annotations (if Deep), brief_data, tier
+- Focus: Assembling structured content from verified data
+- Limits: Do NOT write files, validate spec compliance, or report
+- Dependencies: Extraction inventory from step-03 (enrichment from step-04 if Deep)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Load Section Structure
+
+Load `{skillSectionsData}` completely. This defines the agentskills.io-compliant format for all output artifacts.
+
+### 2. Build SKILL.md Content
+
+Assemble each section in order from the skill-sections data file:
+
+**Frontmatter:**
+```yaml
+---
+name: {brief.name}
+version: {brief.version}
+description: {brief.name} — {export_count} verified functions
+author: {source_author}
+---
+```
+
+**Section 1 — Overview:**
+- What this skill provides
+- Source repo, version, branch
+- Forge tier used for compilation
+- Export count and confidence summary
+
+**Section 2 — Quick Start:**
+- Select the 3-5 most commonly used functions (by import frequency or documentation prominence)
+- Minimal usage examples — ONLY from source tests or official docs
+- If no examples exist in source, show signature-only quick start
+- Provenance citation for each function
+
+**Section 3 — API Reference:**
+- Group by module/file
+- For each exported function:
+  - Full signature with types
+  - Parameters table (name, type, required/optional, description)
+  - Return type
+  - Usage example (from source tests/docs ONLY — omit if none found)
+  - Provenance citation: `[AST:{file}:L{line}]` or `[SRC:{file}:L{line}]`
+  - T2 annotations (Deep tier only): temporal context from enrichment
+
+**Section 4 — Type Definitions:**
+- All exported types, interfaces, enums
+- Full type signatures with provenance citations
+
+**Section 5 — Integration Patterns (Forge/Deep only):**
+- Co-import patterns detected by ast_bridge
+- Common usage combinations
+- Skip for Quick tier (no co-import data available)
+
+**Section 6 — Manual Sections:**
+- Seed empty `<!-- [MANUAL] -->` markers:
+```markdown
+<!-- [MANUAL:additional-notes] -->
+<!-- Add custom notes here. This section is preserved during skill updates. -->
+<!-- [/MANUAL:additional-notes] -->
+```
+- Place after Quick Start and after API Reference sections
+
+### 3. Build context-snippet.md Content
+
+Compressed 2-line format for CLAUDE.md managed section:
+
+```markdown
+{skill-name} -> skills/{skill-name}/
+  exports: {comma-separated top 10 function names}
+```
+
+### 4. Build metadata.json Content
+
+Following the structure from the skill-sections data file:
+- Populate all fields from brief_data, extraction inventory, and tier
+- Set `generated_at` to current ISO-8601 timestamp
+- Set `source_commit` from resolved source (if available)
+- Set `stats` from extraction aggregate counts
+- Set `tool_versions` based on tier and available tools
+
+### 5. Build references/ Content
+
+Create one reference file per major function group or type:
+- Full function signatures with detailed parameter descriptions
+- Complete usage examples (from source only)
+- Related functions cross-references
+- Temporal annotations (Deep tier: T2-past, T2-future)
+
+Group functions logically by module, file, or functional area.
+
+### 6. Build provenance-map.json Content
+
+One entry per extracted claim:
+- claim text
+- source_file and source_line
+- confidence tier (T1, T1-low, T2)
+- extraction_method (ast_bridge.scan_definitions, gh_bridge.read_file, qmd_bridge.search)
+- ast_node_type (if AST-extracted)
+
+### 7. Build evidence-report.md Content
+
+Compilation audit trail:
+- Generation date, forge tier, source info
+- Tool versions used
+- Extraction summary (files scanned, exports found, confidence breakdown)
+- Validation results (populated in step-06)
+- Warnings from extraction or enrichment
+
+### 8. Menu Handling Logic
+
+**Auto-proceed step — no user interaction.**
+
+After all content is assembled in context, immediately load, read entire file, then execute `{nextStepFile}`.
+
+#### EXECUTION RULES:
+
+- This is an auto-proceed assembly step with no user choices
+- All content stays in context — no files are written yet
+- Proceed directly to validation after assembly is complete
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN all 7 content artifacts (SKILL.md, context-snippet.md, metadata.json, references/, provenance-map.json, evidence-report.md, extraction-rules.yaml) are assembled in context will you proceed to load `{nextStepFile}` for spec validation.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Skill-sections data file loaded and followed
+- SKILL.md assembled with all required sections in agentskills.io format
+- Every function entry has a provenance citation
+- [MANUAL] markers seeded for update-skill compatibility
+- context-snippet.md, metadata.json, references/, provenance-map.json, evidence-report.md all assembled
+- No content without provenance citations included
+- Auto-proceeded to step-06
+
+### ❌ SYSTEM FAILURE:
+
+- Including functions or examples without provenance citations
+- Fabricating usage examples not found in source
+- Writing files to disk (that's step-07)
+- Missing required SKILL.md sections
+- Not seeding [MANUAL] markers
+- Not building all 7 content artifacts
+
+**Master Rule:** Zero hallucination — every line of SKILL.md must trace to source code. Compile from data, not imagination.

package/src/workflows/create-skill/steps-c/step-06-validate.md

@@ -0,0 +1,162 @@
+---
+name: 'step-06-validate'
+description: 'Validate compiled skill content against agentskills.io spec via skills_ref'
+nextStepFile: './step-07-generate-artifacts.md'
+---
+
+# Step 6: Validate
+
+## STEP GOAL:
+
+To validate the compiled SKILL.md content against the agentskills.io specification using skills_ref, auto-fix any validation failures, and confirm spec compliance before artifact generation.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🎯 ALWAYS follow the exact instructions in the step file
+- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a skill compilation engine performing quality assurance
+- ✅ Validation ensures spec compliance — it does not modify content semantics
+- ✅ Tool unavailability means skip validation, not halt workflow
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on validating compiled content against spec
+- 🚫 FORBIDDEN to add new content — only fix spec compliance issues
+- 🚫 FORBIDDEN to write files — content stays in context until step-07
+- 💬 If auto-fix fails, report issues clearly but proceed (warn, don't halt)
+- ⚙️ If skills_ref unavailable: skip validation, add warning to evidence report
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow MANDATORY SEQUENCE exactly
+- 💾 Validation results are added to evidence-report content in context
+- 📖 Auto-fix pattern: validate → fix → re-validate (once)
+- 🚫 Maximum one auto-fix attempt per validation failure
+
+## CONTEXT BOUNDARIES:
+
+- Available: All compiled content from step-05 (SKILL.md, metadata.json, etc.)
+- Focus: Spec compliance validation and auto-fix
+- Limits: Do NOT add new content or modify extraction data
+- Dependencies: Compiled content must exist from step-05
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Check Tool Availability
+
+**If skills_ref tool is available:**
+Continue to validation steps.
+
+**If skills_ref tool is NOT available:**
+- Add warning to evidence-report content: "Spec validation skipped — skills_ref tool unavailable"
+- Auto-proceed to next step
+
+### 2. Validate Schema
+
+Use `skills_ref.validate_schema()` against the compiled SKILL.md content.
+
+**Check:**
+- Required sections present (Overview, Quick Start, API Reference, Type Definitions)
+- Section order follows agentskills.io standard
+- Frontmatter contains required fields (name, version, description, author)
+- Provenance citations present in API Reference entries
+
+**If validation passes:** Record "Schema: PASS" in evidence-report content.
+
+**If validation fails:**
+1. Identify specific failures
+2. Attempt auto-fix (structural adjustments only — never invent content)
+3. Re-validate once
+4. If still failing: record "Schema: FAIL — {specific issues}" in evidence-report, add warnings, but proceed
+
+### 3. Validate Frontmatter
+
+Use `skills_ref.validate_frontmatter()` against the SKILL.md frontmatter.
+
+**Check:**
+- `name` matches brief.name (kebab-case)
+- `version` matches brief.version
+- `description` follows format: "{name} — {count} verified functions"
+- `author` is set
+
+**If validation passes:** Record "Frontmatter: PASS" in evidence-report content.
+
+**If validation fails:**
+1. Auto-fix frontmatter (these are deterministic fixes)
+2. Re-validate once
+3. Record result in evidence-report
+
+### 4. Validate metadata.json
+
+Cross-check metadata.json content against extraction inventory:
+- `stats.exports_documented` matches actual documented exports
+- `stats.exports_total` matches total extracted exports
+- `stats.coverage` is accurate (documented / total)
+- `confidence_t1`, `confidence_t2`, `confidence_t3` match actual counts
+- `spec_version` is "1.3"
+
+Auto-fix any discrepancies (these are computed values).
+
+### 5. Update Evidence Report
+
+Add validation results to the evidence-report content in context:
+
+```markdown
+## Validation Results
+- Schema: {pass/fail}
+- Frontmatter: {pass/fail}
+- Metadata: {pass/fail}
+
+## Warnings
+- {any warnings from validation}
+```
+
+### 6. Menu Handling Logic
+
+**Auto-proceed step — no user interaction.**
+
+After validation is complete (or skipped if tools unavailable), immediately load, read entire file, then execute `{nextStepFile}`.
+
+#### EXECUTION RULES:
+
+- This is an auto-proceed validation step with no user choices
+- Tool unavailability is a skip, not a halt
+- Validation failures are warnings — proceed to artifact generation
+- Proceed directly to next step after validation completes
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN validation is complete (or skipped) and evidence-report content is updated will you proceed to load `{nextStepFile}` for artifact generation.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Schema validation attempted (or skipped with warning if tool unavailable)
+- Frontmatter validation attempted
+- Metadata cross-check performed
+- Auto-fix applied for deterministic failures
+- Evidence report updated with validation results
+- Warnings recorded for any failures
+- Auto-proceeded to step-07
+
+### ❌ SYSTEM FAILURE:
+
+- Halting the workflow on validation failure (should warn and proceed)
+- Halting on skills_ref unavailability (should skip with warning)
+- Adding new content during validation (only structural fixes allowed)
+- Not recording validation results in evidence report
+- Attempting more than one auto-fix cycle per failure
+
+**Master Rule:** Validation informs, it does not block. Record results, fix what's deterministic, warn about the rest, and proceed.

package/src/workflows/create-skill/steps-c/step-07-generate-artifacts.md

@@ -0,0 +1,165 @@
+---
+name: 'step-07-generate-artifacts'
+description: 'Write all output files — 4 deliverables to skills/ and 3 workspace artifacts to forge-data/'
+nextStepFile: './step-08-report.md'
+---
+
+# Step 7: Generate Artifacts
+
+## STEP GOAL:
+
+To write all compiled content to disk — 4 deliverable files to `skills/{name}/` and 3 workspace artifacts to `forge-data/{name}/`, creating directories as needed.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🎯 ALWAYS follow the exact instructions in the step file
+- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a skill compilation engine performing artifact generation
+- ✅ All content was assembled in step-05 and validated in step-06
+- ✅ This step ONLY writes — it does not modify, compile, or validate content
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on writing files from the compiled content in context
+- 🚫 FORBIDDEN to modify content during writing — write exactly what was compiled
+- 🚫 FORBIDDEN to skip any artifact — all 7 files must be written
+- 💬 Report each file written with its path
+- 📁 Create directories before writing files
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow MANDATORY SEQUENCE exactly
+- 💾 Write files using the compiled content from context
+- 📖 Create directory structure first, then write files
+- 🚫 Halt with error if a file write fails — do not continue with partial output
+
+## CONTEXT BOUNDARIES:
+
+- Available: All compiled content from step-05, validation results from step-06
+- Focus: File system operations — create directories, write files
+- Limits: Do NOT modify content during writing
+- Dependencies: All content must be compiled and validated in context
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Create Directory Structure
+
+Create the following directories at `{project-root}/`:
+
+```
+skills/{name}/
+skills/{name}/references/
+forge-data/{name}/
+```
+
+Where `{name}` is the skill name from the brief (kebab-case).
+
+If directories already exist, do not error — proceed with file writing (overwrites existing files).
+
+### 2. Write Deliverables to skills/{name}/
+
+Write these 4 files from the compiled content:
+
+**File 1:** `skills/{name}/SKILL.md`
+- The complete compiled skill document
+- agentskills.io-compliant format with all sections
+- [MANUAL] markers seeded
+
+**File 2:** `skills/{name}/context-snippet.md`
+- Compressed 2-line format for CLAUDE.md integration
+
+**File 3:** `skills/{name}/metadata.json`
+- Machine-readable birth certificate with stats and provenance
+
+**File 4:** `skills/{name}/references/*.md`
+- One file per function group or type
+- Progressive disclosure detail files
+
+### 3. Write Workspace Artifacts to forge-data/{name}/
+
+Write these 3 files from the compiled content:
+
+**File 5:** `forge-data/{name}/provenance-map.json`
+- Per-claim source map with AST bindings and confidence tiers
+
+**File 6:** `forge-data/{name}/evidence-report.md`
+- Build artifact with extraction summary, validation results, warnings
+
+**File 7:** `forge-data/{name}/extraction-rules.yaml`
+- Language and ast-grep schema used for this extraction (for reproducibility)
+
+### 4. Verify Write Completion
+
+After all files are written, verify:
+- All 7 files exist at their expected paths
+- List each file with its path and size
+
+**If any write failed:**
+Halt with: "Artifact generation failed: could not write `{file_path}`. Check permissions and disk space."
+
+**If all writes succeeded:**
+Display brief confirmation:
+
+"**Artifacts generated.**
+
+**Deliverables (skills/{name}/):**
+- SKILL.md
+- context-snippet.md
+- metadata.json
+- references/ ({reference_count} files)
+
+**Workspace (forge-data/{name}/):**
+- provenance-map.json
+- evidence-report.md
+- extraction-rules.yaml
+
+Proceeding to compilation report..."
+
+### 5. Menu Handling Logic
+
+**Auto-proceed step — no user interaction.**
+
+After all artifacts are written and verified, immediately load, read entire file, then execute `{nextStepFile}`.
+
+#### EXECUTION RULES:
+
+- This is an auto-proceed file writing step with no user choices
+- All 7 files must be written before proceeding
+- File write failures are real errors — halt, do not proceed with partial output
+- Proceed directly to next step after successful generation
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN all 7 artifact files are written and verified will you proceed to load `{nextStepFile}` for the compilation report.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Directory structure created (skills/{name}/, forge-data/{name}/)
+- All 4 deliverable files written to skills/{name}/
+- All 3 workspace artifact files written to forge-data/{name}/
+- Write completion verified — all 7 files exist
+- Brief confirmation displayed with file list
+- Auto-proceeded to step-08
+
+### ❌ SYSTEM FAILURE:
+
+- Modifying content during the write step
+- Skipping any of the 7 required files
+- Proceeding with partial output if a write fails
+- Not creating directories before writing
+- Not verifying all files were written
+
+**Master Rule:** This step ONLY writes. All content was compiled and validated in previous steps. Write faithfully, verify completely.

package/src/workflows/create-skill/steps-c/step-08-report.md

@@ -0,0 +1,160 @@
+---
+name: 'step-08-report'
+description: 'Display compilation summary with confidence tiers, suggest next steps'
+---
+
+# Step 8: Report
+
+## STEP GOAL:
+
+To display the final compilation summary — skill name, version, source, export count, confidence distribution, tier used, file list, and any warnings — and suggest next steps for the user.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🎯 ALWAYS follow the exact instructions in the step file
+- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a tool you do not have access to, you MUST still achieve the outcome in your main context thread
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a skill compilation engine delivering the final report
+- ✅ This is the completion step — celebrate the forged skill
+- ✅ Positive capability framing — describe what was achieved
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on reporting compilation results
+- 🚫 FORBIDDEN to modify any files — reporting only
+- 🚫 FORBIDDEN to re-run extraction or compilation
+- 💬 Deliver structured report with confidence breakdown
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow MANDATORY SEQUENCE exactly
+- 💾 No file operations — display only
+- 📖 This is the final step — no next step to load
+- 🚫 Do not modify any output files
+
+## CONTEXT BOUNDARIES:
+
+- Available: All data from previous steps — brief, extraction, enrichment, compilation, validation, artifacts
+- Focus: Summarizing and reporting
+- Limits: Do NOT modify files or re-run any previous step
+- Dependencies: All artifacts must have been generated in step-07
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Display Forge Completion Banner
+
+"**Skill forged: {name} v{version} — {export_count} functions, {primary_confidence} confidence.**"
+
+Where `{primary_confidence}` is the predominant confidence tier (T1 if Forge/Deep, T1-low if Quick).
+
+### 2. Display Compilation Summary
+
+"**Compilation Summary**
+
+| Field | Value |
+|-------|-------|
+| **Skill** | {name} v{version} |
+| **Source** | {source_repo} @ {branch} ({commit_short}) |
+| **Language** | {language} |
+| **Forge Tier** | {tier} — {tier_description} |
+| **Files Scanned** | {file_count} |
+| **Exports Documented** | {documented_count} of {total_count} ({coverage}%) |
+
+**Confidence Distribution:**
+| Tier | Count | Description |
+|------|-------|-------------|
+| T1 (AST) | {t1_count} | Structurally verified via ast-grep |
+| T1-low (Source) | {t1_low_count} | Inferred from source reading |
+| T2 (QMD) | {t2_count} | Enriched with temporal context |
+
+**Output Files:**
+- `skills/{name}/SKILL.md` — Active skill with trigger-based usage
+- `skills/{name}/context-snippet.md` — Passive context for CLAUDE.md
+- `skills/{name}/metadata.json` — Machine-readable birth certificate
+- `skills/{name}/references/` — Progressive disclosure ({ref_count} files)
+- `forge-data/{name}/provenance-map.json` — Source map with AST bindings
+- `forge-data/{name}/evidence-report.md` — Build audit trail
+- `forge-data/{name}/extraction-rules.yaml` — Reproducible extraction schema"
+
+### 3. Display Warnings (If Any)
+
+If there were warnings from extraction, validation, or enrichment, display them:
+
+"**Warnings:**
+- {warning_1}
+- {warning_2}
+- ..."
+
+If no warnings, omit this section entirely.
+
+### 4. Suggest Next Steps
+
+"**Recommended next steps:**
+- **[TS] Test Skill** — verify completeness and accuracy before export
+- **[ES] Export Skill** — publish to your skill library or agentskills.io
+- **[US] Update Skill** — edit specific sections or add manual content
+
+To use this skill immediately, add the context snippet to your CLAUDE.md:
+```
+{context_snippet_content}
+```"
+
+### 5. Batch Mode Status (If Applicable)
+
+**If running in --batch mode:**
+
+"**Batch progress:** {completed_count} of {total_count} skills compiled.
+
+{If more remaining:} Proceeding to next brief: {next_skill_name}..."
+
+Update sidecar checkpoint with batch progress, then loop back to step-01 for the next brief.
+
+**If not batch mode or all batch briefs complete:**
+
+End workflow. No further steps.
+
+### 6. Workflow Complete
+
+This is the final step. No `{nextStepFile}` to load.
+
+Display: "Forge session complete. Return to Ferris menu for further actions."
+
+## CRITICAL STEP COMPLETION NOTE
+
+This is the FINAL STEP of the create-skill workflow. After displaying the compilation report and next steps, the workflow is complete. No further steps are loaded.
+
+For batch mode: loop back to step-01 for remaining briefs via sidecar checkpoint.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Forge completion banner displayed with skill name, version, export count
+- Full compilation summary with confidence distribution
+- All output file paths listed
+- Warnings displayed (if any)
+- Next steps suggested (test-skill, export-skill, update-skill)
+- Context snippet provided for immediate use
+- Batch progress updated (if applicable)
+- Workflow ended gracefully
+
+### ❌ SYSTEM FAILURE:
+
+- Not displaying the forge completion banner
+- Missing confidence distribution in summary
+- Modifying any files during the report step
+- Not listing all output file paths
+- Not suggesting next steps
+- Not ending the workflow (attempting to load nonexistent next step)
+
+**Master Rule:** This step reports and celebrates. It does not modify, re-extract, or re-compile. The skill is forged.