bmad-module-skill-forge 0.9.0 → 0.10.1-alpha.0

package/src/workflows/test-skill/steps-c/step-05-score.md

@@ -1,222 +0,0 @@
----
-name: 'step-05-score'
-description: 'Calculate completeness score from coverage and coherence findings'
-
-nextStepFile: './step-06-report.md'
-outputFile: '{forge_data_folder}/{skill_name}/test-report-{skill_name}.md'
-scoringRulesFile: '../data/scoring-rules.md'
-sourceAccessProtocol: '../data/source-access-protocol.md'
----
-
-# Step 5: Score
-
-## STEP GOAL:
-
-Calculate the overall completeness score by aggregating coverage, coherence, and external validation category scores with the appropriate weight distribution (naive or contextual), apply the pass/fail threshold, and determine the test result.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER invent scores — all values must derive from step 03 and step 04 findings
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step, ensure entire file is read
-- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a subprocess, subagent, or 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 auditor in Ferris's Audit mode — zero hallucination
-- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
-- ✅ Scoring is mechanical — apply the formula, report the math
-- ✅ Do not editorialize on the score — facts and numbers only
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on score calculation — do NOT generate remediation suggestions (that's step 06)
-- 🚫 FORBIDDEN to adjust scores subjectively — the formula determines the result
-- 💬 Show the math: category scores, weights, weighted contributions, total
-- 📋 Score must be reproducible — same inputs always produce same output
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load scoring rules and read findings from {outputFile}
-- 💾 Append Completeness Score section to {outputFile}
-- 📖 Update {outputFile} frontmatter with testResult, score, and stepsCompleted
-- 🚫 FORBIDDEN to proceed without setting testResult to pass or fail
-
-## CONTEXT BOUNDARIES:
-
-- Available: Coverage Analysis (step 03), Coherence Analysis (step 04), and External Validation (step 04b) in {outputFile}
-- Focus: Score calculation and pass/fail determination only
-- Limits: Do NOT generate gap remediation — that's step 06
-- Dependencies: steps 03, 04, and 04b must have appended their analysis sections
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load Scoring Rules
-
-Load `{scoringRulesFile}` to get:
-- Category weights (naive vs contextual distribution)
-- Default threshold (80%)
-- Tier-dependent scoring adjustments
-- Any custom threshold override from workflow input
-
-**Docs-only mode check:** If the Coverage Analysis section in `{outputFile}` notes docs-only mode (set by step-03 for skills with all `[EXT:...]` citations and no local source), apply Quick-tier weight redistribution: Signature Accuracy and Type Coverage are not scored, their weights (22% + 14%) are redistributed proportionally to remaining active categories. Coverage score is based on documentation completeness rather than source coverage (as calculated by step-03).
-
-### 2. Read Category Scores from Output
-
-Read `{outputFile}` and extract the category scores calculated in previous steps:
-
-**From Coverage Analysis (step 03):**
-- Export Coverage: {percentage}%
-- Signature Accuracy: {percentage}% or N/A (Quick tier)
-- Type Coverage: {percentage}% or N/A (Quick tier)
-
-**From Coherence Analysis (step 04):**
-- Combined Coherence: {percentage}% (contextual mode only)
-- Or: not scored (naive mode — weight redistributed)
-
-**From External Validation (step 04b):**
-- External Validation Score: {percentage}% (combined skill-check + tessl average)
-- Or: N/A (if neither tool was available — weight redistributed to other categories)
-
-### 3. Apply Weight Distribution
-
-**Read testMode from {outputFile} frontmatter.**
-
-Apply the weight distribution from `{scoringRulesFile}` for the detected mode (naive or contextual). The scoring rules define category weights, external validation redistribution when unavailable, and Quick tier adjustments. Calculate the weighted score for each category and sum for the total.
-
-### 4. Determine Pass/Fail
-
-```
-threshold = custom_threshold OR default_threshold (80%)
-score = sum of weighted category scores
-
-IF score >= threshold → PASS
-IF score < threshold → FAIL
-```
-
-### 5. Determine Next Workflow Recommendation
-
-Based on test result:
-
-**IF PASS:**
-- `nextWorkflow: 'export-skill'` — skill is ready for export
-
-**IF FAIL:**
-- `nextWorkflow: 'update-skill'` — skill needs remediation before export
-
-### 6. Append Completeness Score to Output
-
-Append the **Completeness Score** section to `{outputFile}`:
-
-```markdown
-## Completeness Score
-
-### Score Breakdown
-
-| Category | Score | Weight | Weighted |
-|----------|-------|--------|----------|
-| Export Coverage | {N}% | {W}% | {WS}% |
-| Signature Accuracy | {N}% | {W}% | {WS}% |
-| Type Coverage | {N}% | {W}% | {WS}% |
-| Coherence | {N}% | {W}% | {WS}% |
-| External Validation | {N}% | {W}% | {WS}% |
-| **Total** | | **100%** | **{total}%** |
-
-### Result
-
-**Score:** {total}%
-**Threshold:** {threshold}%
-**Result:** **{PASS|FAIL}**
-
-**Weight Distribution:** {naive (redistributed) | contextual (full)}
-**Tier Adjustment:** {none | Quick tier — signature and type coverage not scored}
-**External Validators:** {both available | skill-check only | tessl only | none — weight redistributed}
-**Analysis Confidence:** {full | provenance-map | metadata-only | remote-only | docs-only}
-```
-
-If `analysis_confidence` is not `full`, append a degradation notice. **The notice must be confidence-aware** — see the degradation notice rules in `{sourceAccessProtocol}`:
-
-```markdown
-### Access Degradation Notice
-
-**Resolved via:** {analysis_confidence} {confidence breakdown if provenance-map, e.g., "(T1 AST-verified at compilation time)" or "(12 T1, 3 T1-low)"}
-**Impact:** {describe limitation — e.g., "Signature checks limited to name-matching. Source file:line citations from provenance-map, not live AST." — or "Provenance data is at highest confidence; no limitation." for all-T1 provenance-map}
-**Recommendation:** {confidence-dependent — see {sourceAccessProtocol} degradation notice rules. Do NOT recommend local clone when provenance-map entries are already T1.}
-```
-
-### 7. Update Output Frontmatter
-
-Update `{outputFile}` frontmatter:
-- `testResult: '{pass|fail}'`
-- `score: '{total}%'`
-- `threshold: '{threshold}%'`
-- `analysisConfidence: '{analysis_confidence}'`
-- `nextWorkflow: '{export-skill|update-skill}'`
-- Append `'step-05-score'` to `stepsCompleted`
-
-### 8. Report Score
-
-"**Completeness score calculated.**
-
-**{skill_name}:** **{total}%** — **{PASS|FAIL}**
-
-| Category | Score | Weighted |
-|----------|-------|----------|
-| Export Coverage | {N}% | {WS}% |
-| Signature Accuracy | {N}% | {WS}% |
-| Type Coverage | {N}% | {WS}% |
-| Coherence | {N}% | {WS}% |
-| External Validation | {N}% | {WS}% |
-
-**Threshold:** {threshold}%
-**Recommendation:** {export-skill if pass | update-skill if fail}
-
-**Proceeding to gap report...**"
-
-### 9. Auto-Proceed
-
-Display: "**Proceeding to gap report...**"
-
-#### Menu Handling Logic:
-
-- After score is calculated and frontmatter updated, immediately load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-
-- This is an auto-proceed scoring step with no user choices
-- Proceed directly to next step after score is determined
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN the score is calculated, pass/fail is determined, the Completeness Score section is appended to {outputFile}, and frontmatter is updated with testResult and score, will you then load and read fully `{nextStepFile}` to execute gap report generation.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All category scores read from previous steps (not invented)
-- Correct weight distribution applied (naive vs contextual)
-- Tier adjustment applied if Quick tier
-- Score calculated with visible math (show the formula)
-- Pass/fail determined against threshold
-- Completeness Score section appended to output
-- Frontmatter updated with testResult, score, threshold, nextWorkflow
-- Auto-proceeded to step 06
-
-### ❌ SYSTEM FAILURE:
-
-- Inventing category scores not calculated in steps 03/04
-- Using wrong weight distribution for the detected mode
-- Not showing the math (score must be reproducible)
-- Subjectively adjusting the score
-- Not setting testResult in frontmatter
-- Generating remediation suggestions (that's step 06)
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. Scoring is mechanical — apply the formula, report the math.

package/src/workflows/test-skill/steps-c/step-06-report.md

@@ -1,207 +0,0 @@
----
-name: 'step-06-report'
-description: 'Generate gap report with remediation suggestions and finalize test report'
-
-outputFile: '{forge_data_folder}/{skill_name}/test-report-{skill_name}.md'
-scoringRulesFile: '../data/scoring-rules.md'
-outputFormatsFile: '../data/output-section-formats.md'
----
-
-# Step 6: Gap Report
-
-## STEP GOAL:
-
-Generate a detailed gap report listing every issue found during coverage and coherence analysis, assign severity to each gap, provide specific actionable remediation suggestions, and finalize the test report document. This is the final step — no next step file.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER fabricate gaps — every item must trace to findings from steps 03, 04, and 04b
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ⚙️ TOOL/SUBPROCESS FALLBACK: If any instruction references a subprocess, subagent, or 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 auditor in Ferris's Audit mode — zero hallucination
-- ✅ If you already have been given a name, communication_style and identity, continue to use those while playing this new role
-- ✅ Remediation suggestions must be specific and actionable — not vague advice
-- ✅ Each gap tells the user exactly what to fix, where, and how
-
-### Step-Specific Rules:
-
-- 🎯 Focus on gap enumeration, severity classification, and remediation
-- 🚫 FORBIDDEN to recalculate scores — use the score from step 05
-- 💬 Remediation suggestions reference specific files, exports, and line numbers
-- 📋 Gaps are ordered by severity (Critical → High → Medium → Low → Info)
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read all findings from {outputFile} coverage and coherence sections
-- 💾 Append Gap Report section to {outputFile}
-- 📖 Update {outputFile} frontmatter: mark stepsCompleted with all steps, finalize document
-- 🚫 This is the final step — no next step to load
-
-## CONTEXT BOUNDARIES:
-
-- Available: Complete {outputFile} with Test Summary, Coverage Analysis, Coherence Analysis, Completeness Score
-- Focus: Gap enumeration and remediation only
-- Limits: Do NOT re-analyze source code — work from existing findings
-- Dependencies: steps 03, 04, and 05 must have completed their sections
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Collect All Issues
-
-Read `{outputFile}` and extract every issue found across all analysis sections:
-
-**From Coverage Analysis (step 03):**
-- Missing documentation (exports in source but not in SKILL.md)
-- Signature mismatches (documented signature differs from source)
-- Stale documentation (documented but no longer in source)
-- Type coverage gaps (undocumented types/interfaces)
-
-**From Coherence Analysis (step 04):**
-- Broken references (file paths, skill references, type imports that don't resolve)
-- Incomplete integration patterns (contextual mode)
-- Structural issues (naive mode — missing sections, broken examples)
-
-**From External Validation (step 04b):**
-- skill-check diagnostics (unresolved errors and warnings)
-- tessl judge suggestions (content quality and actionability improvements)
-
-### 2. Load Severity Rules
-
-Load `{scoringRulesFile}` for gap severity classification:
-
-| Severity | Criteria |
-|----------|----------|
-| **Critical** | Missing exported function/class documentation |
-| **High** | Signature mismatch between source and SKILL.md |
-| **Medium** | Missing type or interface documentation |
-| **Medium** | Migration section present/absent mismatch with T2-future annotation data (Deep tier) |
-| **Medium** | Script/asset directory exists but no Scripts & Assets section in SKILL.md |
-| **Medium** | Scripts & Assets section references file not found in scripts/ or assets/ directory |
-| **Low** | Script/asset file present without provenance entry in provenance-map.json file_entries |
-| **Low** | Missing optional metadata or examples |
-| **Low** | Description trigger optimization recommended (third-person voice, negative triggers, or keyword coverage gaps) |
-| **Info** | Style suggestions, non-blocking observations |
-| **Info** | Discovery testing not performed — realistic prompt testing recommended before export |
-
-### 3. Classify and Order Gaps
-
-Load `{outputFormatsFile}` for gap entry format and remediation quality rules.
-
-For each issue, assign severity from `{scoringRulesFile}` and generate a specific remediation following the quality rules in `{outputFormatsFile}`. Order gaps by severity: Critical → High → Medium → Low → Info.
-
-### 4. Generate Remediation Summary and Append Gap Report
-
-Load the Gap Report section format from `{outputFormatsFile}`. Count gaps by severity, estimate effort per the guidelines in `{outputFormatsFile}`, and append the complete **Gap Report** section to `{outputFile}`.
-
-If no gaps found, append a clean pass message recommending **export-skill** workflow.
-
-### 4b. Discovery and Description Quality Recommendations
-
-After gap enumeration, append a **Discovery Quality** subsection to the gap report. Use the `Gap Entry Format` from `{outputFormatsFile}` for any Low/Info entries. The prose recommendations below are appended after the gap entries:
-
-**Description optimization:** If tessl `description_score` (from step 04b) is below 90%, or if skill-check flagged description issues, recommend description improvements:
-- Check that the description uses third-person voice consistently
-- Check for specific trigger keywords that match how users would phrase requests
-- Check for negative triggers ("NOT for: ...") to prevent false matches
-- Check for alternative skill references for excluded use cases
-
-**Discovery testing recommendation:** Regardless of pass/fail, always append:
-
-"**Discovery testing recommended.** Before export, test the skill with 3-5 realistic prompts phrased the way real users actually talk — with casual language, typos, incomplete context, and implicit references. A skill tested only with clean prompts may fail to trigger in production. Example realistic prompt patterns:
-- Vague: 'can you help me with this csv file my boss sent'
-- Implicit: 'why did revenue drop last quarter'
-- Abbreviated: 'run the {skill-name} thing on this data'"
-
-Record discovery testing status as Info-level in the gap table. This is advisory — it does not affect the score.
-
-### 5. Finalize Output Document
-
-Update `{outputFile}` frontmatter:
-- Set `stepsCompleted` to `['step-01-init', 'step-02-detect-mode', 'step-03-coverage-check', 'step-04-coherence-check', 'step-04b-external-validators', 'step-05-score', 'step-06-report']`
-
-### 6. Present Final Report
-
-"**Test complete for {skill_name}.**
-
----
-
-**Result:** **{PASS|FAIL}** — **{score}%** (threshold: {threshold}%)
-
-**Gaps Found:** {total_gaps}
-- Critical: {N}
-- High: {N}
-- Medium: {N}
-- Low: {N}
-- Info: {N}
-
-**Report saved to:** `{outputFile}`
-
----
-
-**Recommended next step:**
-
-{IF PASS:}
-**export-skill** — This skill is ready for export. Run the export-skill workflow to package it for distribution.
-
-{IF FAIL:}
-**update-skill** — This skill needs remediation. Review the gap report above and run the update-skill workflow to address the {N} blocking issues (Critical + High).
-
----
-
-**See Discovery Quality section in the report for description optimization and realistic prompt testing recommendations.**
-
-**Test report finalized.**"
-
-### 7. Present MENU OPTIONS
-
-Display: "**Test complete.** [C] Finish"
-
-#### Menu Handling Logic:
-
-- IF C: Workflow is complete. No further steps to load.
-- IF Any other: help user respond, then redisplay menu
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- This is the final step — C ends the workflow
-- User may ask questions about the report before finishing
-
-## CRITICAL STEP COMPLETION NOTE
-
-This is the final step of the test-skill workflow. When the user selects C, the workflow is complete. The test report document at `{outputFile}` contains the full analysis: Test Summary, Coverage Analysis, Coherence Analysis, Completeness Score, and Gap Report.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Every gap traces to a finding from steps 03, 04, or 04b (zero fabrication)
-- Gaps classified by severity using scoring rules
-- Gaps ordered by severity (Critical first)
-- Every gap has a specific, actionable remediation suggestion
-- Discovery quality section appended with description optimization and testing recommendations
-- Remediation summary with counts and effort estimates
-- Output document finalized with all stepsCompleted
-- Correct next workflow recommended (export-skill or update-skill)
-- Report presented clearly to user
-
-### ❌ SYSTEM FAILURE:
-
-- Fabricating gaps not found in analysis steps
-- Vague remediation suggestions ("fix the issue", "add documentation")
-- Not classifying severity
-- Recalculating or modifying the score from step 05
-- Not finalizing the output document frontmatter
-- Missing the next workflow recommendation
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE. Every gap is specific, every remediation is actionable.

package/src/workflows/test-skill/templates/test-report-template.md

@@ -1,28 +0,0 @@
----
-workflowType: 'test-skill'
-skillName: ''
-skillDir: ''
-testMode: ''
-forgeTier: ''
-testResult: ''
-score: ''
-threshold: ''
-analysisConfidence: ''
-testDate: ''
-stepsCompleted: []
-nextWorkflow: ''
----
-
-# Test Report: {{skillName}}
-
-## Test Summary
-
-## Coverage Analysis
-
-## Coherence Analysis
-
-## External Validation
-
-## Completeness Score
-
-## Gap Report

package/src/workflows/test-skill/workflow.md

@@ -1,57 +0,0 @@
----
-name: test-skill
-description: Cognitive completeness verification. Naive and contextual modes.
-web_bundle: true
-installed_path: '{project-root}/_bmad/skf/workflows/skillforge/test-skill'
----
-
-# Test Skill
-
-**Goal:** Verify that a skill is complete enough to be useful to an AI agent by checking coverage of the public API surface (naive mode) or validating SKILL.md + references coherence (contextual mode), producing a completeness score and gap report as a quality gate before export.
-
-**Your Role:** In addition to your name, communication_style, and persona, you are also a skill auditor and completeness analyst operating in Ferris's Audit mode. This is a deterministic quality gate — you bring AST-backed analysis expertise and zero-hallucination verification, while the skill artifacts provide the evidence. Every finding must trace to actual code with file:line citations.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere to 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded, read, and executed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array
-- **Append-Only Building**: Build the test report by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-- ⚙️ **TOOL/SUBPROCESS FALLBACK**: If any instruction references a subprocess, subagent, or tool you do not have access to, you MUST still achieve the outcome in your main context thread
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/_bmad/skf/config.yaml and resolve:
-
-- `project_name`, `user_name`, `communication_language`, `document_output_language`
-- `skills_output_folder`, `forge_data_folder`, `sidecar_path`
-
-### 2. First Step Execution
-
-Load, read the full file and then execute `./steps-c/step-01-init.md` to begin the workflow.

package/src/workflows/update-skill/data/remote-source-resolution.md

@@ -1,57 +0,0 @@
-# Remote Source Resolution (Forge/Deep Tier)
-
-If `source_root` is a local path: proceed with the tier-appropriate strategy as normal.
-
-If `source_root` (from metadata.json) is a remote URL (GitHub URL or owner/repo format) AND tier is Forge or Deep:
-
-1. **Check `git` availability:** Verify `git` is functional (`git --version`). If `git` is not available, skip to the fallback warning below.
-
-2. **Resolve source ref:** Read `source_ref` from the existing `metadata.json`. If the user provided a new `target_version`, resolve its tag first (using the Tag Resolution algorithm in `create-skill/data/source-resolution-protocols.md`).
-
-3. **Ephemeral sparse clone:** Clone only the changed files from the change manifest to a system temp path. Note: at this point in the flow, `{source_root}` is known to be a remote URL (the local-path case was already handled above).
-
-   ```
-   temp_path = {system_temp}/skf-ephemeral-{skill-name}-{timestamp}/
-   ```
-
-   If `source_ref` exists and is not `HEAD`/null/`"local"`:
-   ```
-   git clone --depth 1 --branch {source_ref} --single-branch --filter=blob:none --sparse {source_root} {temp_path}
-   ```
-
-   If `source_ref` is `HEAD`/null/`"local"` (or absent):
-   ```
-   git clone --depth 1 --single-branch --filter=blob:none --sparse {source_root} {temp_path}
-   ```
-
-   ```
-   git -C {temp_path} sparse-checkout set --skip-checks {changed_files_from_manifest}
-   ```
-
-   **Note:** `--skip-checks` is required because `changed_files_from_manifest` contains individual file paths (e.g., `src/core/parser.py`), not directories. Without this flag, `git sparse-checkout set` rejects non-directory entries.
-
-   When `source_ref` is a tag (e.g., `v0.5.0`), the clone targets that specific tag to ensure update-skill extracts from the same source version as the original create-skill run. When `source_ref` is `HEAD`, null, or `"local"`, no `--branch` flag is used — the clone targets the remote's default branch. This scopes the clone to only the files identified in step-02's change manifest, avoiding a full repository download.
-
-4. **If clone succeeds:** Update the working source path to `{temp_path}` for all subsequent AST operations in this step. Proceed with the **Forge tier** extraction strategy below. Mark `ephemeral_clone_active = true` for cleanup.
-
-5. **If clone fails (network error, auth failure, timeout):**
-
-   Warning message: "Ephemeral clone of `{source_root}` failed: {error}. Degrading to source reading (T1-low) for this run. For T1 (AST-verified) confidence, clone the repository locally and re-run [CS] Create Skill with the local path, then re-run this update."
-
-   Override the extraction strategy to Quick tier for this run. Note the degradation reason in context for the evidence report.
-
-## Ephemeral Clone Cleanup
-
-After extraction is complete for all files in scope (whether successful or partially failed), before presenting the extraction summary, if `ephemeral_clone_active`, delete the `{temp_path}` directory. Log: "Ephemeral source clone cleaned up." This ensures cleanup runs even if some extractions failed, as long as the step itself is still executing.
-
-## Version Reconciliation
-
-After the source path is accessible, check whether the source version has changed since the original skill was created. Look for the version file matching the detected language (e.g., `pyproject.toml`, `package.json`, `Cargo.toml`). If the source version differs from the current `metadata.json` version, record `source_version_detected` in context for step-06 to use when updating `metadata.json`. No warning needed here — step-06 handles the version update.
-
-## AST Tool Unavailability (Local Source)
-
-If AST tool is unavailable at Forge/Deep tier with local source:
-
-Warning message: "AST tools are unavailable — extraction will use source reading (T1-low). Run [SF] Setup Forge to detect and configure AST tools for T1 confidence."
-
-Degrade to Quick tier extraction. Note the degradation reason in context for the evidence report.