@rune-kit/rune 2.7.0 → 2.10.0

package/skills/preflight/SKILL.md

@@ -3,7 +3,7 @@ name: preflight
 description: Pre-commit quality gate that catches "almost right" code. Goes beyond linting — checks logic correctness, error handling, regressions, and completeness.
 metadata:
   author: runedev
-  version: "0.7.0"
+  version: "0.8.0"
   layer: L2
   model: sonnet
   group: quality
@@ -208,6 +208,7 @@ If a domain hook flags BLOCK, the overall preflight verdict is BLOCK regardless
 | `openapi.*`, `*.graphql`, `*.proto` | API Contract | Breaking changes flagged, version bumped, deprecated fields documented |
 | `docs/policies/*`, `PRIVACY*`, `TERMS*` | Legal/Compliance | No placeholder text, review date current, practice matches policy |
 | `**/billing*`, `**/payment*`, `**/invoice*` | Financial | Decimal precision correct, currency locale-aware, no hardcoded rates |
+| `*.tsx`, `*.jsx`, `*.svelte`, `*.vue`, `components/*` | UI/Frontend | Design token compliance, animation a11y, touch targets, visual hierarchy |
 | `skills/*/SKILL.md`, `extensions/*/PACK.md` | Rune Skill | Frontmatter valid, all required sections present, word count within layer budget |
 | `*.test.*`, `*.spec.*`, `__tests__/*` | Test Quality | No `.skip`/`.only` left in, assertions present (not empty tests), no hardcoded timeouts |
 
@@ -221,6 +222,24 @@ For each detected domain, run its checks on the relevant files in the diff:
 4. **Classify** findings: BLOCK (data loss risk, breaking contract) or WARN (best practice, incomplete)
 5. **Append** to preflight report under `### Domain Quality` section
 
+#### UI/Frontend Domain Checks
+
+When UI/Frontend hook is triggered, run these checks on all `.tsx`/`.jsx`/`.svelte`/`.vue` files in the diff:
+
+| Check | What to Scan | Severity |
+|-------|-------------|----------|
+| **Design token compliance** | Hardcoded colors (`#fff`, `rgb(`, `hsl(`) instead of CSS variables or Tailwind tokens | WARN: "Hardcoded color at {file}:{line} — use design token" |
+| **UI-SPEC drift** | If `.rune/ui-spec.md` exists, compare component decisions (card style, form layout, nav type) against spec | BLOCK: "Component at {file} uses bordered cards but UI-SPEC locks elevated cards" |
+| **Animation accessibility** | Animations/transitions without `prefers-reduced-motion` guard | WARN: "Animation at {file}:{line} missing reduced-motion check" |
+| **Touch target size** | Interactive elements with explicit small sizing (`w-5 h-5`, `p-0.5` on buttons/links) < 44×44px | WARN: "Touch target too small at {file}:{line}" |
+| **Missing states** | Components fetching data without loading/error/empty states | WARN: "Async component at {file} missing [loading|error|empty] state" |
+| **Icon accessibility** | Decorative icons without `aria-hidden="true"`, functional icons without `aria-label` | WARN: "Icon at {file}:{line} missing aria attribute" |
+| **Inline styles** | `style={{` or `style=` attribute usage instead of classes/tokens | WARN: "Inline style at {file}:{line} — use CSS class or Tailwind" |
+| **Font loading** | Custom font imports without `font-display: swap` or Next.js font optimization | WARN: "Font at {file} may cause layout shift — add font-display: swap" |
+| **Placeholder content** | Strings like "Lorem ipsum", "TODO", "placeholder", "test text" in JSX/template | BLOCK: "Placeholder content at {file}:{line} — replace before shipping" |
+
+**Skip if**: Diff contains only test files, config files, or non-UI code (detected by absence of JSX/template syntax).
+
 #### Pack Integration
 
 When a domain pack is installed (e.g., `@rune-pro/finance`, `@rune-pro/legal`), preflight checks the pack's **Hard-Stop Thresholds** table and applies matching rules to staged files. This means:

package/skills/rescue/SKILL.md

@@ -5,7 +5,7 @@ context: fork
 agent: general-purpose
 metadata:
   author: runedev
-  version: "0.3.0"
+  version: "0.4.0"
   layer: L1
   model: sonnet
   group: orchestrator
@@ -34,6 +34,7 @@ Legacy refactoring orchestrator for safely modernizing messy codebases. Rescue r
 - `autopsy` (L2): Phase 0 RECON — full codebase health assessment
 - `safeguard` (L2): Phase 1 SAFETY NET — characterization tests and protective measures
 - `surgeon` (L2): Phase 2-N SURGERY — incremental refactoring (1 module per session)
+- `retro` (L2): post-rescue retrospective — capture lessons learned
 - `journal` (L3): state tracking across rescue sessions
 - `plan` (L2): create refactoring plan based on autopsy findings
 - `review` (L2): verify each surgery phase
@@ -424,6 +425,29 @@ Rollback point: git tag rune-rescue-baseline (set in Phase 0)
 | Health score comparison | Inline (Rescue Report) | Baseline vs final autopsy scores |
 | Rescue Report | Markdown (inline) | Emitted at session end (per module and final) |
 
+## Document Ownership
+
+| Scope | Access | Files |
+|-------|--------|-------|
+| **Owns** (read + write) | `RESCUE-STATE.md`, `.rune/rescue-*.md`, git tags (`rune-rescue-*`), refactored source files (one module per session) |
+| **Reads** (never writes) | `CLAUDE.md`, autopsy reports, safeguard test files, `.rune/contract.md` |
+| **Never modifies** | Test files written by `safeguard` (characterization tests are the safety net — rescue reads them, never edits), `compiler/**`, `SKILL.md` files |
+
+Rescue delegates to `surgeon` for actual code changes and `safeguard` for test creation. Rescue owns the orchestration state, not the artifacts.
+
+## Anti-Patterns
+
+Common legacy refactoring failures. These turn "rescue" into "make it worse."
+
+| Anti-Pattern | Why It Fails | Correct Approach |
+|---|---|---|
+| **Big bang refactor** — rewriting everything at once | No rollback path. One bug = entire refactor is broken | One module per session. Commit + verify after each module |
+| **Surgery without safety net** — refactoring before characterization tests exist | No way to verify behavior is preserved. "It compiles" ≠ "it works" | HARD-GATE: safeguard tests must pass BEFORE any surgery begins |
+| **Coupled module surgery** — refactoring two interdependent modules simultaneously | Changes in module A break module B mid-surgery. Neither is stable | One module per session. Stabilize A completely before touching B |
+| **Ignoring the autopsy** — starting refactoring without understanding current health | Fixes symptoms not causes. Wastes effort on low-impact modules | Phase 0 autopsy is mandatory. Surgery queue ordered by impact, not convenience |
+| **Prototype patterns in production** — replacing legacy code with quick-and-dirty rewrites | Creates new legacy. The "rescue" becomes the next rescue target | Apply proven refactoring patterns from autopsy recommendations. Clean code, not fast code |
+| **No rollback point** — surgery without a tagged baseline | If surgery goes wrong, no safe state to return to | `git tag rune-rescue-baseline` before ANY code changes |
+
 ## Sharp Edges
 
 Known failure modes for this skill. Check these before declaring done.

package/skills/research/SKILL.md

@@ -3,7 +3,7 @@ name: research
 description: Web search and external knowledge lookup. Gathers data on technologies, libraries, best practices, and competitor solutions.
 metadata:
   author: runedev
-  version: "0.3.0"
+  version: "0.4.0"
   layer: L3
   model: haiku
   group: knowledge
@@ -67,6 +67,29 @@ Call `WebSearch` for each query. Collect result titles, URLs, and snippets. Iden
 - **Diversity: never select 3+ URLs from the same domain** — spread across source types
 
 
+### Step 2b — Diminishing Returns Detection
+
+After each WebSearch call, evaluate whether additional searches are productive:
+
+**Track across search results**:
+- **Entity set**: Extract key entities from each result set (library names, API names, version numbers, technique names, company names)
+- **New entity ratio**: `new_entities_in_this_search / total_entities_found_so_far`
+- **Result overlap**: How many URLs from this search were already seen in previous searches
+
+| Signal | Threshold | Action |
+|--------|-----------|--------|
+| New entity ratio < 10% | Last search added almost nothing new | Skip remaining queries, proceed to Step 3 with existing results |
+| Result overlap > 60% | Most URLs already fetched or seen | Skip this query's results entirely |
+| All 3 queries return same top 3 URLs | Search space is exhausted | Proceed directly to Step 3 — more queries won't help |
+
+**Report when triggered**:
+```
+Note: Research saturation reached after [N] searches — [M] unique entities found.
+Additional queries showed <10% new information. Proceeding with synthesis.
+```
+
+**Why**: Research skills commonly waste 2-3 WebFetch calls on pages that repeat information already gathered. Saturation detection saves tool calls and context tokens while preserving research quality — the first 3 sources typically contain 90%+ of available information.
+
 ### Step 3 — Deep Dive
 
 Call `WebFetch` on the top 3-5 URLs identified in Step 2. Hard limit: **max 5 WebFetch calls** per research invocation. For each fetched page:

package/skills/retro/SKILL.md

@@ -41,6 +41,8 @@ Retro is ENCOURAGING but CANDID. Every critique is anchored in specific commits,
 
 - `audit` (L2): engineering velocity and health dimension
 - `cook` (L1): optional — after completing a multi-phase feature, suggest retro
+- `rescue` (L1): post-rescue retrospective
+- `launch` (L1): post-launch retrospective
 - User: `/rune retro` direct invocation
 
 ## Data Flow

package/skills/review/SKILL.md

@@ -3,13 +3,13 @@ name: review
 description: Code quality review — patterns, security, performance, correctness. Finds bugs, suggests improvements, triggers fix for issues found. Escalates to opus for security-critical code.
 metadata:
   author: runedev
-  version: "0.6.0"
+  version: "0.8.0"
   layer: L2
   model: sonnet
   group: development
   tools: "Read, Glob, Grep"
   emit: review.complete, review.issues
-  listen: code.changed
+  listen: code.changed, docs.updated
 ---
 
 # review
@@ -204,6 +204,36 @@ Identify gaps in test coverage.
 - If untested code found: call `rune:test` with specific instructions on what to test
 - Flag as HIGH if business logic is untested, MEDIUM if utility code is untested
 
+#### Per-Function Test Gap Analysis
+
+Go beyond "test file exists" — check coverage at function granularity:
+
+1. **Extract changed functions** — from the diff, list every function/method that was added or modified (name + file:line)
+2. **Map to test assertions** — for each changed function, Grep the test file for its name. Count distinct test cases (look for `it(`, `test(`, `describe(` blocks that reference the function)
+3. **Classify gap severity**:
+
+| Function Type | 0 tests | 1 test | 2+ tests |
+|--------------|---------|--------|----------|
+| Business logic (money, auth, state) | BLOCK | WARN: "only happy path" | PASS |
+| Data transform (parse, format, map) | HIGH | PASS | PASS |
+| Event handler (onClick, onSubmit) | MEDIUM | PASS | PASS |
+| Pure utility (string, math, date) | MEDIUM | PASS | PASS |
+
+4. **Output per-function table** in review report:
+
+```
+### Test Gap Analysis
+| Function | File | Tests Found | Verdict |
+|----------|------|-------------|---------|
+| calculateTotal | src/billing.ts:42 | 3 (happy, zero, overflow) | PASS |
+| processRefund | src/billing.ts:89 | 0 | BLOCK — business logic untested |
+| formatCurrency | src/utils.ts:12 | 1 | PASS |
+```
+
+5. **Flag untested edge cases** — for functions with only 1 test, check if the test covers: empty/null input, boundary values, error path. If only happy path → WARN: "only happy path tested for {function}"
+
+**Skip if**: Diff only touches config, docs, styles, or test files themselves.
+
 ### Step 5.5: Two-Stage Review Gate
 
 Separate spec compliance from code quality. Most reviews conflate both — this gate forces the distinction.
@@ -503,6 +533,29 @@ When `cook` or `ship` checks review status: compare review commit hash with curr
 | Composite quality score | Markdown table | inline (when `mode: "scored"`) |
 | Blast radius assessment | Markdown table | inline |
 
+## Chain Metadata
+
+Append to Code Review Report when invoked standalone. Suppress when called as sub-skill inside an L1 orchestrator (cook, team, etc.) — the orchestrator emits a consolidated block. See `docs/references/chain-metadata.md`.
+
+```yaml
+chain_metadata:
+  skill: "rune:review"
+  version: "0.8.0"
+  status: "[DONE | DONE_WITH_CONCERNS]"
+  domain: "[area reviewed]"
+  files_changed: []  # review doesn't change files
+  exports:
+    findings_count: { critical: [N], high: [N], medium: [N], low: [N] }
+    findings:
+      - { severity: "[level]", file: "[path]", line: [N], message: "[issue]" }
+    verdict: "[APPROVE | REQUEST_CHANGES | NEEDS_DISCUSSION]"
+    quality_score: [0-100]  # when mode: "scored"
+  suggested_next:
+    - skill: "rune:fix"
+      reason: "[grounded in findings — e.g., '2 HIGH findings in api/users.ts need remediation']"
+      consumes: ["findings"]
+```
+
 ## Sharp Edges
 
 | Failure Mode | Severity | Mitigation |

package/skills/scaffold/SKILL.md

@@ -33,6 +33,7 @@ Generated projects MUST build and pass tests. A scaffold that produces broken co
 - `research` (L3): Phase 2 — best practices, starter templates, library comparison
 - `plan` (L2): Phase 3 — architecture and implementation plan
 - `design` (L2): Phase 4 — design system (frontend projects only)
+- `skill-forge` (L2): when scaffolded project includes custom skills or plugin structure
 - `fix` (L2): Phase 5 — code generation (implements the plan)
 - `team` (L1): Phase 5 — parallel implementation when 3+ independent modules
 - `test` (L2): Phase 6 — test suite generation

package/skills/scope-guard/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: scope-guard
-description: "Detects scope creep. Auto-triggered by L1 orchestrators when files exceed the original plan. Compares current git changes against plan, flags out-of-scope files, reports IN_SCOPE or CREEP_DETECTED."
+description: "Detects scope creep by quantifying drift percentage. Auto-triggered by L1 orchestrators when files exceed the original plan. Compares git changes against plan, classifies drift into 4 tiers: ON_TRACK, MINOR_DRIFT, SIGNIFICANT_DRIFT, OUT_OF_CONTROL."
 user-invocable: false
 metadata:
   author: runedev
-  version: "0.3.0"
+  version: "0.4.0"
   layer: L3
   model: haiku
   group: monitoring
@@ -73,13 +73,28 @@ Rules for OUT_OF_SCOPE (counts as creep):
 - New dependencies added without a planned feature requiring them
 - Documentation files for unplanned features
 
-### Step 4: Flag Creep
+### Step 4: Quantify Drift
 
-If any OUT_OF_SCOPE files are detected:
-- List each out-of-scope file with the reason it is flagged
-- Classify as: `MINOR CREEP` (1-2 unplanned files) or `SIGNIFICANT CREEP` (3+ unplanned files)
+Compute **Drift Percentage** — the ratio of out-of-scope changes to total changes:
 
-If zero OUT_OF_SCOPE files: status is `IN_SCOPE`.
+```
+drift_pct = (out_of_scope_files / total_files_changed) × 100
+```
+
+Classify drift into a 4-tier system:
+
+| Drift % | Level | Status | Action |
+|---------|-------|--------|--------|
+| **< 10%** | ON TRACK | `ON_TRACK` | No action needed. Proceed normally. |
+| **10-25%** | MINOR DRIFT | `MINOR_DRIFT` | Flag out-of-scope files. Suggest trim or acknowledge as intentional. Continue. |
+| **25-50%** | SIGNIFICANT DRIFT | `SIGNIFICANT_DRIFT` | **Pause recommended.** Present drift report to user. Re-scope before continuing. |
+| **> 50%** | OUT OF CONTROL | `OUT_OF_CONTROL` | **Block.** More unplanned work than planned. Escalate to orchestrator. Require re-alignment before ANY further work. |
+
+**Edge case**: If total planned files = 0 (no plan loaded), use file count thresholds instead:
+- 0 out-of-scope → ON_TRACK
+- 1-2 out-of-scope → MINOR_DRIFT
+- 3-5 out-of-scope → SIGNIFICANT_DRIFT
+- 6+ out-of-scope → OUT_OF_CONTROL
 
 ### Step 5: Report
 
@@ -91,7 +106,8 @@ Output the following structure:
 - **Planned files**: [count from plan]
 - **Actual files changed**: [count from git diff]
 - **Out-of-scope files**: [count]
-- **Status**: IN_SCOPE | MINOR CREEP | SIGNIFICANT CREEP
+- **Drift**: [X]% ([level])
+- **Status**: ON_TRACK | MINOR_DRIFT | SIGNIFICANT_DRIFT | OUT_OF_CONTROL
 
 ### In-Scope Changes
 - [file] — [matches planned task]
@@ -100,9 +116,10 @@ Output the following structure:
 - [file] — [reason: unplanned feature | unrelated refactor | unplanned dep]
 
 ### Recommendations
-- [If IN_SCOPE]: No action needed. Proceed.
-- [If MINOR CREEP]: Review [file] — consider reverting or acknowledging as intentional.
-- [If SIGNIFICANT CREEP]: STOP. Re-align with original plan before continuing. [list files to revert]
+- [ON_TRACK]: No action needed. Proceed.
+- [MINOR_DRIFT]: Review [file] — consider reverting or acknowledging as intentional.
+- [SIGNIFICANT_DRIFT]: PAUSE. Drift is [X]%. Re-align scope with original plan. Suggested cuts: [files to revert]
+- [OUT_OF_CONTROL]: STOP. [X]% of changes are unplanned — more drift than planned work. Present full report to user/orchestrator. Do NOT continue until re-scoped.
 ```
 
 ## Output Format
@@ -110,14 +127,15 @@ Output the following structure:
 ```
 ## Scope Report
 - Planned files: 3 | Actual: 5 | Out-of-scope: 2
-- Status: MINOR CREEP
+- Drift: 40% (SIGNIFICANT_DRIFT)
 
 ### Out-of-Scope Changes
 - src/components/NewWidget.tsx — unplanned feature
 - docs/new-feature.md — documentation for unplanned feature
 
 ### Recommendations
-- Review src/components/NewWidget.tsx — revert or log as intentional scope change.
+- PAUSE. Drift is 40%. Re-align scope with original plan.
+- Suggested cuts: revert src/components/NewWidget.tsx + docs/new-feature.md (reduces drift to 0%)
 ```
 
 ## Constraints
@@ -134,7 +152,7 @@ Known failure modes for this skill. Check these before declaring done.
 |---|---|---|
 | Classifying test files for planned code as out-of-scope | MEDIUM | Test files for planned source files are always IN_SCOPE — natural dependency |
 | Classifying lock file changes as out-of-scope | LOW | package-lock.json, yarn.lock, Cargo.lock are always IN_SCOPE |
-| SIGNIFICANT CREEP threshold applied to 1-2 unplanned files | LOW | MINOR = 1-2 files, SIGNIFICANT = 3+ files — don't escalate prematurely |
+| Over-escalating drift (e.g., 1 extra file = OUT_OF_CONTROL) | LOW | Use drift percentage, not gut feeling. 1 extra file out of 10 = 10% = MINOR_DRIFT, not panic |
 | Plan not loadable (no TodoWrite, no progress.md) | MEDIUM | Ask calling skill for plan as text description before proceeding |
 | Scope check against plan but not against stated intent | MEDIUM | Plan-based scope guard catches file drift; review Step 6.6 (Scope Drift Detection) catches intent drift. Both should run for full coverage |
 
@@ -143,14 +161,14 @@ Known failure modes for this skill. Check these before declaring done.
 - Plan loaded from TodoWrite active tasks or .rune/progress.md
 - git diff --stat and --cached output parsed for all changed files
 - Each changed file classified IN_SCOPE or OUT_OF_SCOPE with reasoning
-- Creep severity classified (IN_SCOPE / MINOR CREEP / SIGNIFICANT CREEP)
-- Scope Report emitted with recommendations
+- Drift percentage computed and classified (ON_TRACK / MINOR_DRIFT / SIGNIFICANT_DRIFT / OUT_OF_CONTROL)
+- Scope Report emitted with drift %, level, and actionable recommendations
 
 ## Returns
 
 | Artifact | Format | Location |
 |----------|--------|----------|
-| Scope Report | Markdown (IN_SCOPE / MINOR CREEP / SIGNIFICANT CREEP) | inline |
+| Scope Report | Markdown (drift %, 4-tier level, recommendations) | inline |
 | In-scope file list | Classified list | inline |
 | Out-of-scope drift report | File list with reasons | inline |
 | Recommendations | Actionable list | inline |

package/skills/scout/SKILL.md

@@ -3,7 +3,7 @@ name: scout
 description: "Fast codebase scanner. Use when any skill needs codebase context. Finds files, patterns, dependencies, project structure. Pure read-only — never modifies files."
 metadata:
   author: runedev
-  version: "0.2.0"
+  version: "0.3.0"
   layer: L2
   model: haiku
   group: creation
@@ -79,6 +79,27 @@ Based on the scan request, run focused searches:
 
 **Verification gate**: At least 1 relevant file found, OR confirm the target does not exist.
 
+#### Info Saturation Detection (Know When to Stop)
+
+Scout's default is "max 10 file reads" — but the real question is whether additional reads are productive. Track saturation across Phase 2 searches:
+
+**Entity tracking**: As you scan files, extract key entities (function names, class names, imports, API endpoints, config keys). Maintain a running set of discovered entities.
+
+| Signal | Threshold | Meaning | Action |
+|--------|-----------|---------|--------|
+| **New entity ratio** | Last 2 file reads added <2 new entities | Search is exhausted for this domain | STOP scanning, move to Phase 3 |
+| **Content similarity** | Last 2 files share >70% of the same imports/patterns | Files are in the same module, redundant reads | Skip remaining files in this directory |
+| **Query variation** | 3+ Glob/Grep queries with different patterns all return the same files | All search angles converge | Domain is fully mapped, proceed |
+
+**When saturation detected**: Emit in Scout Report:
+```
+### Saturation
+- Reached after [N] file reads — last 2 reads added [M] new entities
+- Recommendation: synthesize_and_report (further scanning unlikely to yield new insights)
+```
+
+**Why**: Without saturation detection, scout reads its full budget of 10 files even when 3 files already contain everything needed. This wastes context tokens and delays the calling skill. Early saturation detection returns control faster.
+
 ### Phase 3: Dependency Mapping
 
 1. Use `Grep` to find import/require/use statements in identified files

package/skills/sentinel/SKILL.md

@@ -3,7 +3,7 @@ name: sentinel
 description: Automated security gatekeeper. Blocks unsafe code before commit — secret scanning, OWASP top 10, dependency audit, permission checks. A GATE, not a suggestion.
 metadata:
   author: runedev
-  version: "0.9.0"
+  version: "1.0.0"
   layer: L2
   model: sonnet
   group: quality
@@ -198,6 +198,34 @@ If `.rune/contract.md` exists, validate staged changes against project contract
 
 If `.rune/contract.md` does not exist, skip and log INFO: "no project contract, contract validation skipped".
 
+### Step 4.87 — Config Leak Threshold Detection
+
+Detect when agent output or code changes accidentally expose internal configuration files, skill definitions, or sensitive project structure to end users.
+
+**Why**: Agents processing SKILL.md, CLAUDE.md, `.rune/` files may copy-paste internal content into user-facing output (chat responses, generated docs, UI strings). This leaks architecture details, security rules, and proprietary skill content.
+
+**Detection patterns** (scan agent output + staged files):
+
+| Pattern | What to Detect | Severity |
+|---------|---------------|----------|
+| **Internal file exposure** | 3+ distinct internal file names mentioned in plain text (not code blocks): `CLAUDE.md`, `SKILL.md`, `PACK.md`, `.rune/contract.md`, `.rune/runbook.md` | WARN |
+| **Skill content leak** | Verbatim SKILL.md content (>50 chars) appearing in user-facing strings, README, or generated docs | BLOCK |
+| **Config path exposure** | Absolute paths containing user home directory (`/Users/`, `C:\Users\`) in committed code or output | WARN |
+| **Environment variable dump** | `process.env` or `os.environ` iterated/serialized without filtering (exposes all env vars) | BLOCK |
+| **Debug config in production** | `DEBUG=true`, `LOG_LEVEL=debug`, `NODE_ENV=development` in committed config files | WARN |
+| **Connection string patterns** | Strings matching `://user:pass@host` or `mongodb+srv://` or `postgres://` in non-.env files | BLOCK |
+
+**Threshold rules:**
+- Single mention of an internal file name → PASS (could be legitimate reference)
+- 3+ distinct internal file names in one output → WARN: "Agent may be leaking internal config"
+- Any SKILL.md verbatim content in user-facing code → BLOCK: "Skill content leaked to output"
+
+**Exclusions** (prevent false positives):
+- Code blocks in architecture docs (legitimate documentation)
+- References inside other SKILL.md files (internal cross-references)
+- Test fixtures explicitly testing config handling
+- `.env.example` files (intentionally public)
+
 ### Step 4.86 — Organization Policy Enforcement (Business)
 
 If `.rune/org/org.md` exists, load organization security policies and enforce them as additional gates.

package/skills/sentinel-env/SKILL.md

@@ -112,8 +112,6 @@ Detect and verify tools the project depends on:
 5. **Build tools**: Check for `turbo.json` (turborepo), `nx.json` (Nx), `Makefile`, etc.
 
 6. **Hard dependencies** — tools the project WRAPS (not just uses as dev dependency):
-   > From CLI-Anything (HKUDS/CLI-Anything, 17.4k★): "The software is a required dependency, not optional."
-
    Scan for evidence that the project wraps an external tool:
    - `Grep` for `shutil.which(`, `which `, `command -v ` → project looks up an executable at runtime
    - `Grep` for `subprocess.run(`, `child_process.exec(`, `Deno.Command(` → project invokes external CLI