@rune-kit/rune 2.29.1 → 2.30.0

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rune",
-  "version": "2.29.1",
+  "version": "2.30.0",
   "description": "66-skill engineering mesh with Codex-native skills, subagents, synchronous lifecycle hooks, security gates, MCP-aware workflows, and project memory.",
   "author": {
     "name": "Rune Contributors"

package/README.md

@@ -103,11 +103,15 @@ Plus **9 domain packs** (product, sales, data-science, support, growth, media, p
 
 ---
 
-## What's New (v2.29.1 — One-Command Update)
+## What's New (v2.30.0 — Tier Restored)
 
-> **v2.29.1 (2026-07-24):** v2.29.0 documented the update flow; this release automates it. New **`rune update`** command — one-shot updater for an already-configured project: `git pull --ff-only` any detected Pro/Business tier repos (env var → sibling dir, same detection as setup; a failed pull **aborts loudly**, never a silent half-update), re-runs the managed setup rewrite in place non-interactively (your installed platforms, preset, and tiers are detected from the existing hook config — no prompts), then verifies with doctor + hook drift and reminds Codex users to re-trust `/hooks` only when `.codex/hooks.json` actually changed. Flags: `--no-pull`, `--preset`, `--tier`, `--dry`. Plus: "Updating" sections in all three tier READMEs. Docs-and-CLI patch — no skill or mesh changes. 1,638 tests.
+> **v2.30.0 (2026-07-29):** Rune's model tier table had quietly stopped applying on Claude Code, and had been wrong in **23 of 66 places** for longer than that. `agents/*.md` is a hand-written parallel copy of each skill's tier; nothing generated it from `skills/` and no check compared the two, so they drifted — `cook` said opus in one file and sonnet in the other, `verification` said sonnet and haiku. `skills/*/SKILL.md` is now the single source of truth, every pair agrees, and a new **`validateAgentSync`** gate fails CI on any future drift, alongside a model-split check and a warning for a top-level `model` that cannot take effect. Where the two disagreed the tier was decided by role, with one rule overriding both old values: **a gate never runs below sonnet** — `completion-gate`, `constraint-check`, `integrity-check`, `hallucination-guard`, and `verification` exist to catch unverified claims, so running them cheaper than the agent they audit defeats the point. Separately: tiering only ever applied through spawned subagents, and on Opus 5 the harness tells the model not to spawn them unless asked — so every tier assignment had become a silent no-op. `scout` and `docs-seeker` now declare `context: fork` + `model: haiku` and route through the Skill tool instead; verified end-to-end on Opus 5 by per-model billing showing `claude-haiku-4-5`. `cook` deliberately declares no model — an orchestrator inherits the session model, because choosing Opus for a session is a deliberate act. 1,647 tests.
 
-### Previous (v2.29.0 — Codex Native)
+### Previous (v2.29.1 — One-Command Update)
+
+> **v2.29.1 (2026-07-24):** v2.29.0 documented the update flow; this release automates it. New **`rune update`** command — one-shot updater for an already-configured project: `git pull --ff-only` any detected Pro/Business tier repos (env var → sibling dir, same detection as setup; a failed pull **aborts loudly**, never a silent half-update), re-runs the managed setup rewrite in place non-interactively (your installed platforms, preset, and tiers are detected from the existing hook config — no prompts), then verifies with doctor + hook drift and reminds Codex users to re-trust `/hooks` only when `.codex/hooks.json` actually changed. Flags: `--no-pull`, `--preset`, `--tier`, `--dry`. Plus: "Updating" sections in all three tier READMEs. Docs-and-CLI patch — no skill or mesh changes. 1,641 tests.
+
+#### Earlier (v2.29.0 — Codex Native)
 
 > **v2.29.0 (2026-07-23):** Codex stops being a compile target that happens to work and becomes a **first-class native runtime**. The Codex adapter now emits everything current Codex supports natively — `.agents/skills/`, project-scoped agent TOML (`.codex/agents/rune-{heavy,standard,fast}.toml`), a dedicated synchronous hook adapter targeting `.codex/hooks.json` (Codex silently skips async handlers), MCP config, and tier-aware compilation so Free/Pro/Business stacks resolve exactly as on Claude Code. The mesh validator was fixed at the root — `Calls (outbound)` is now the single authoritative edge inventory, acknowledged by the target's `Called By` — moving the canonical count from 209 to **248 connections** (same mesh, honest count; doctor now fails CI on any stale claim). Doctor also grew a cross-tier audit: Business metadata (28 pack skills, 4 orchestrators), $149 pricing, 13-platform count, and JSON-schema validation of the new `docs/config-schema.json` + hooks manifest schema. All XLabs remote-MCP references now go through `XLABS_MCP_TOKEN` — plaintext bearer values are forbidden. 1,615 tests pass.
 

package/agents/audit.md

@@ -25,7 +25,7 @@ You are the **audit** skill — Rune's comprehensive project auditor.
 
 **Critical Rules:**
 - MUST complete all 8 phases (explicitly state if skipped)
-- Only findings >80% confidence (no speculation)
+- Drop a finding only on direct counter-evidence, never on uncertainty — an unconfirmable finding is reported and typed `ASSUMED` with its unchecked premise named
 - Include at least 3 positive findings
 - Delegate Phase 1 to dependency-doctor, Phase 2 to sentinel
 

package/agents/cook.md

@@ -1,7 +1,7 @@
 ---
 name: cook
 description: "Feature implementation orchestrator — handles 70% of requests. Full TDD cycle: understand → plan → test → implement → verify → commit. Use for ANY code modification (features, bugs, refactors, security)."
-model: opus
+model: sonnet
 subagent_type: general-purpose
 ---
 

package/agents/journal.md

@@ -1,7 +1,7 @@
 ---
 name: journal
 description: "Persistent state tracking across sessions — records decisions with rationale, progress, risks, ADRs to .rune/ files. Called by surgeon, deploy, rescue for cross-session continuity."
-model: sonnet
+model: haiku
 subagent_type: general-purpose
 ---
 

package/agents/reviewer.md

@@ -9,7 +9,7 @@ You are the **reviewer** subagent — a code review specialist spawned by other
 
 ## Operating Rules
 
-1. **Every finding MUST have file:line reference** — vague observations are rejected
+1. **Every finding MUST carry a verbatim evidence snippet** — vague observations are rejected, and so are line numbers produced from memory (see Evidence & Anchoring below)
 2. Check all 5 areas: correctness, security, performance, conventions, test coverage
 3. Severity levels: CRITICAL (blocks merge) → HIGH → MEDIUM → LOW
 4. Never rubber-stamp — if zero issues found, look harder (default-suspicious mindset)
@@ -17,4 +17,26 @@ You are the **reviewer** subagent — a code review specialist spawned by other
 6. Include at least 1 positive note (what's well-designed)
 7. Verdict: APPROVE / REQUEST CHANGES / NEEDS DISCUSSION
 
+## Falsification Pass (before reporting)
+
+**Falsify, not verify.** Do not filter findings by how confident you feel — you cannot calibrate that. Filter by disproof:
+
+- **DROP** only when the code you read holds **direct counter-evidence** against the finding's key claim. Discard it silently.
+- **KEEP** when the finding rests on context outside the diff that you actually read — that context is evidence.
+- **KEEP** when you can neither confirm nor disprove it. "Unsure" is not grounds to drop.
+
+Type every surviving finding `OBSERVED` (you read the defect), `DERIVED` (follows from what you read, state the mechanism), or `ASSUMED` (rests on an unverified premise — name it). **`ASSUMED` findings are never CRITICAL.**
+
+## Evidence & Anchoring
+
+Report the snippet, not the line number. A line number recalled from a long context drifts, and a correct finding pointing at the wrong line is unactionable.
+
+- **Copy** the offending lines verbatim from the file — no rewriting, no re-indenting, diff markers (`+`/`-`) stripped, max 5 lines. A finding needing more than 5 lines to show is a design comment: report it without evidence at MEDIUM or below.
+- **Anchor** each finding before reporting: `Grep` the exact snippet in its file → hit, use that line. Miss → retry once with whitespace normalised and the first and last lines dropped.
+- **`UNANCHORED`** on a second miss: downgrade one severity level, report as `path (unanchored)` with the snippet shown inline. Never drop it — a failed `Grep` is not counter-evidence.
+
+## Strict Focus
+
+Read anything you need for context. Report findings **only** about files in the stated review scope — an out-of-scope finding is dropped, or noted as a one-line follow-up in the report footer with no severity.
+
 You do NOT fix code. You identify issues with evidence. The parent skill decides next steps.

package/agents/session-bridge.md

@@ -1,7 +1,7 @@
 ---
 name: session-bridge
 description: "Cross-session context persistence — auto-saves decisions, conventions, progress, instincts to .rune/ files. Loads + integrity-checks at session start. Auto-triggered before compaction."
-model: sonnet
+model: haiku
 subagent_type: general-purpose
 ---
 

package/agents/skill-forge.md

@@ -1,7 +1,7 @@
 ---
 name: skill-forge
 description: "The skill that builds skills — TDD-driven: baseline test → write skill → verify → refactor → integrate into mesh. Use for creating or editing Rune skills."
-model: sonnet
+model: opus
 subagent_type: general-purpose
 ---
 

package/agents/skill-router.md

@@ -1,7 +1,7 @@
 ---
 name: skill-router
 description: "Meta-enforcement layer — routes EVERY agent action through the correct skill before any code is written. Always active. Prevents 'just this once' bypasses."
-model: opus
+model: sonnet
 subagent_type: general-purpose
 ---
 

package/agents/trend-scout.md

@@ -1,7 +1,7 @@
 ---
 name: trend-scout
 description: "Market intelligence — competitor analysis, technology trends, community sentiment. Scans Product Hunt, GitHub Trending, HN, Reddit. Use for positioning, not API docs."
-model: sonnet
+model: haiku
 subagent_type: general-purpose
 ---
 

package/agents/worktree.md

@@ -1,7 +1,7 @@
 ---
 name: worktree
 description: "Git worktree lifecycle — create isolated workspaces for parallel development, manage branches, cleanup. Max 3 active worktrees. Called by team for parallel streams."
-model: sonnet
+model: haiku
 subagent_type: general-purpose
 ---
 

package/compiler/__tests__/skill-attribution.test.js

@@ -0,0 +1,109 @@
+/**
+ * Attribution hygiene — skills and agents must not carry graft-source credits.
+ *
+ * Rune skills present their guidance as Rune's own. A `> From <repo> (N★): "…"`
+ * blockquote leaks where a pattern was grafted from, dates the file with a star
+ * count, and reads as borrowed authority. The prose stays; the credit line goes.
+ *
+ * Guards the patterns removed in a2df7b5 so they cannot drift back in.
+ *
+ * Legitimate credits are NOT attribution: a license obligation for redistributed
+ * data (skills/design), a descriptive "Source patterns:" lead-in, and a filename
+ * cited inside a config example all stay. Each is asserted explicitly below so a
+ * future tightening of the rules cannot silently outlaw them.
+ */
+
+import assert from 'node:assert';
+import { readdirSync, readFileSync, statSync } from 'node:fs';
+import { dirname, join, relative, resolve } from 'node:path';
+import { describe, test } from 'node:test';
+import { fileURLToPath } from 'node:url';
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const REPO_ROOT = resolve(__dirname, '../..');
+const SCAN_DIRS = ['skills', 'agents'];
+
+/**
+ * Each rule matches a single line. Keep them shape-based: a rule that keys on a
+ * repo name rots the moment a different repo is grafted.
+ */
+const FORBIDDEN = [
+  { name: 'blockquote "> From <repo>"', re: /^\s*>\s*From\s+\S/ },
+  { name: 'blockquote "> Inspired by"', re: /^\s*>\s*Inspired by\s/ },
+  { name: 'blockquote "> Source:"', re: /^\s*>\s*Source:/ },
+  { name: 'bare "Source: … ★"', re: /^\s*Source:\s.*★/ },
+  { name: 'blockquote carrying a star count', re: /^\s*>\s.*★/ },
+];
+
+/** Lines that look adjacent to the rules above and must keep passing. */
+const MUST_PASS = [
+  'Design intelligence data from [UI/UX Pro Max](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) (MIT, 42.8k★).',
+  '> Source patterns: production-proven PostgreSQL scaling strategies.',
+  'Source: compliance-soc2.yaml',
+];
+
+function walkMarkdown(dir) {
+  const out = [];
+  for (const entry of readdirSync(dir)) {
+    const full = join(dir, entry);
+    if (statSync(full).isDirectory()) {
+      out.push(...walkMarkdown(full));
+    } else if (entry.endsWith('.md')) {
+      out.push(full);
+    }
+  }
+  return out;
+}
+
+function findViolations(text, file) {
+  const hits = [];
+  text.split(/\r?\n/).forEach((line, i) => {
+    for (const rule of FORBIDDEN) {
+      if (rule.re.test(line)) {
+        hits.push(`${file}:${i + 1} — ${rule.name} → ${line.trim()}`);
+      }
+    }
+  });
+  return hits;
+}
+
+describe('attribution hygiene', () => {
+  test('no source-attribution lines in skills/ or agents/', () => {
+    const violations = [];
+    for (const dirName of SCAN_DIRS) {
+      const dir = join(REPO_ROOT, dirName);
+      for (const file of walkMarkdown(dir)) {
+        violations.push(...findViolations(readFileSync(file, 'utf8'), relative(REPO_ROOT, file)));
+      }
+    }
+
+    assert.deepStrictEqual(
+      violations,
+      [],
+      `Attribution lines found — delete the credit, keep the prose:\n${violations.join('\n')}`,
+    );
+  });
+
+  test('rules fire on the exact lines removed in a2df7b5', () => {
+    const removed = [
+      '> From goclaw (nextlevelbuilder/goclaw, 832★): "Compact during run, not just at session boundary."',
+      '> From superpowers (obra/superpowers, 84k★): "Each fix revealing new problems elsewhere = structural issue."',
+      '> Inspired by CLI-Anything (HKUDS/CLI-Anything, 14.5k★): "Never trust exit 0."',
+      'Source: goclaw (832★) — SHA256-based loop detection distinguishes true stuck loops.',
+    ];
+
+    for (const line of removed) {
+      assert.ok(
+        FORBIDDEN.some((rule) => rule.re.test(line)),
+        `no rule caught a known attribution line: ${line}`,
+      );
+    }
+  });
+
+  test('legitimate credits and lookalikes are not flagged', () => {
+    for (const line of MUST_PASS) {
+      const caught = FORBIDDEN.filter((rule) => rule.re.test(line)).map((rule) => rule.name);
+      assert.deepStrictEqual(caught, [], `false positive on a legitimate line: ${line}`);
+    }
+  });
+});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rune-kit/rune",
-  "version": "2.29.1",
+  "version": "2.30.0",
   "description": "66-skill mesh for AI coding assistants — native lifecycle hooks for Claude Code and Codex, 5-layer architecture, 248 connections + 45 signals, and a 13-platform compiler.",
   "type": "module",
   "bin": {

package/skills/audit/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "0.5.0"
   layer: L2
-  model: sonnet
+  model: opus
   group: quality
   tools: "Read, Bash, Glob, Grep"
   emit: audit.complete
@@ -585,7 +585,7 @@ LOW      — Nice to have. Style inconsistencies, minor refactors, doc gaps.
 INFO     — Observation only. Architecture notes, tech debt acknowledgment.
 ```
 
-Apply confidence filtering: only report findings with >80% confidence. Consolidate similar issues (e.g., "12 functions missing error handling in src/services/" — not 12 separate findings). Adapt judgment to project type (a `console.log` in a CLI tool is fine; in a production API handler, it's not).
+Apply the Falsification Pass (`../review/SKILL.md` → Step 6): drop a finding only when what you read contains direct counter-evidence against its key claim — never merely because you are unsure. A finding you cannot disprove is reported and typed `ASSUMED` with the unchecked premise named. Consolidate similar issues (e.g., "12 functions missing error handling in src/services/" — not 12 separate findings). Adapt judgment to project type (a `console.log` in a CLI tool is fine; in a production API handler, it's not).
 
 ## Output Format
 
@@ -644,7 +644,7 @@ Report saved to: AUDIT-REPORT.md
 
 1. MUST complete all 8 phases (Phase 8 may report "no data" if .rune/metrics/ doesn't exist yet) — if any phase is skipped, state explicitly which phase and why
 2. MUST delegate Phase 1 to dependency-doctor and Phase 2 to sentinel — no manual replacements
-3. MUST apply confidence filter — only report findings with >80% confidence; consolidate similar issues
+3. MUST apply the Falsification Pass — drop findings only on direct counter-evidence, never on uncertainty; consolidate similar issues
 4. MUST include at least 3 positive findings — an audit with no positives is incomplete
 5. MUST produce quantified health scores (1-10 per dimension) — not vague "needs work"
 6. MUST NOT fabricate findings — every finding requires a specific file:line citation

package/skills/completion-gate/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   author: runedev
   version: "1.10.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: validation
   tools: "Read, Bash, Glob, Grep"
 ---

package/skills/constraint-check/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   author: runedev
   version: "1.1.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: validation
   tools: "Read, Glob, Grep"
 ---

package/skills/context-engine/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   author: runedev
   version: "1.3.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: state
   tools: "Read, Glob, Grep"
   emit: context.preview, output.density.set
@@ -321,7 +321,7 @@ When ORANGE or RED is reached, use this table to determine whether compaction is
 
 ### Mid-Loop Compaction (Phase 4 Emergency)
 
-> From goclaw (nextlevelbuilder/goclaw, 832★): "Compact during run, not just at session boundary."
+Compact during the run, not just at the session boundary.
 
 When context hits RED during Phase 4 (implementation), compaction IS possible at **clean split points**:
 

package/skills/cook/SKILL.md

@@ -640,7 +640,7 @@ Escalation chain: debug-fix (3x) → re-plan (1x) → brainstorm rescue (1x) →
 
 ### Structured Escalation Report
 
-> From agency-agents (msitarzewski/agency-agents, 50.8k★): "After 3 retry failures, structured escalation prevents cargo-cult retrying."
+After 3 retry failures, structured escalation prevents cargo-cult retrying.
 
 When escalation chain exhausts (all retries hit) or cook returns `BLOCKED`, produce a Structured Escalation Report instead of a vague "I can't do this":
 
@@ -678,7 +678,7 @@ When escalation chain exhausts (all retries hit) or cook returns `BLOCKED`, prod
 
 ### Subagent Question Gate
 
-> From superpowers (obra/superpowers, 84k★): "Subagents that start work without asking questions produce the wrong thing 40% of the time."
+Subagents that start work without asking questions frequently produce the wrong thing.
 
 Before dispatching a sub-skill (fix, test, review) for a non-trivial task (3+ files OR ambiguous scope):
 

package/skills/cook/references/loop-detection.md

@@ -4,7 +4,7 @@ The Analysis Paralysis Guard (5-read counter in SKILL.md) catches obvious paraly
 This catches **same-input-same-output loops** — where the agent keeps calling the same tool
 with the same arguments and getting the same result, making zero progress.
 
-Source: goclaw (832★) — SHA256-based loop detection distinguishes true stuck loops from productive retries.
+Hash-based detection distinguishes true stuck loops from productive retries.
 
 ## Detection Logic
 

package/skills/cook/references/mid-run-signals.md

@@ -1,7 +1,7 @@
 # Mid-Run Signal Detection — Two-Stage Intent Classification
 
 When user sends a message DURING cook execution (mid-phase), classify intent before acting.
-Source: goclaw (832★) — two-stage intent classification prevents expensive LLM calls for simple signals.
+Two-stage intent classification prevents expensive LLM calls for simple signals.
 
 ## Stage 1 — Keyword Fast-Path
 

package/skills/debug/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "1.4.0"
   layer: L2
-  model: sonnet
+  model: opus
   group: development
   tools: "Read, Bash, Glob, Grep"
   emit: bug.diagnosed, agent.stuck
@@ -282,7 +282,7 @@ Track fix attempts in the Debug Report. If this is attempt N>1 for the same symp
 
 ### 3+ Fixes as Architectural Signal
 
-> From superpowers (obra/superpowers, 84k★): "Each fix revealing new problems elsewhere = structural issue, not a bug hunt."
+Each fix revealing new problems elsewhere is a structural issue, not a bug hunt.
 
 When 3+ **distinct** fixes fail (not retries of the same fix), STOP treating it as a bug:
 

package/skills/dependency-doctor/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "0.2.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: deps
   tools: "Read, Bash, Glob, Grep"
 ---

package/skills/design/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "0.9.0"
   layer: L2
-  model: sonnet
+  model: opus
   group: creation
   tools: "Read, Write, Edit, Glob, Grep"
 ---

package/skills/docs/SKILL.md

@@ -177,7 +177,7 @@ Delegate to `rune:git changelog` to produce a changelog entry from commits since
 
 #### Step 4 — Cross-Doc Consistency Pass
 
-> From gstack (garrytan/gstack, 50.9k★): "Cross-document consistency prevents the #2 docs problem: docs that exist but contradict each other."
+Cross-document consistency prevents the second-most-common docs problem: docs that exist but contradict each other.
 
 After updating any doc, verify consistency across all project documentation:
 

package/skills/docs-seeker/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: docs-seeker
 description: "Find documentation for APIs, libraries, and error messages. Looks up official docs, changelog entries, and migration guides."
+context: fork
+agent: general-purpose
+model: haiku
 metadata:
   author: runedev
   version: "0.2.0"

package/skills/hallucination-guard/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "0.3.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: validation
   tools: "Read, Bash, Glob, Grep"
 ---
@@ -78,7 +78,7 @@ If export not found → mark as **WARN** (symbol may not be exported).
 
 ### Step 3 — Verify external packages (Dependency Check Before Import)
 
-> From taste-skill (Leonxlnx/taste-skill, 3.4k★): "Before importing ANY 3rd party lib, check package.json."
+Before importing ANY third-party library, check the dependency manifest.
 
 Use `Read` on the project's dependency manifest to confirm each external package is listed:
 

package/skills/incident/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   author: runedev
   version: "0.2.0"
   layer: L2
-  model: sonnet
+  model: opus
   group: delivery
   tools: "Read, Write, Edit, Bash, Glob, Grep"
   listen: incident.detected

package/skills/integrity-check/SKILL.md

@@ -6,7 +6,7 @@ metadata:
   author: runedev
   version: "0.2.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: validation
   tools: "Read, Glob, Grep"
   listen: quarantine.notice.emitted

package/skills/launch/SKILL.md

@@ -8,7 +8,7 @@ metadata:
   author: runedev
   version: "0.4.0"
   layer: L1
-  model: sonnet
+  model: opus
   group: orchestrator
   tools: "Read, Write, Edit, Bash, Glob, Grep"
   listen: audit.complete

package/skills/preflight/SKILL.md

@@ -103,7 +103,7 @@ const permissions = await fetchPermissions(id); // waits unnecessarily
 const [user, permissions] = await Promise.all([fetchUser(id), fetchPermissions(id)]);
 ```
 
-Flag each issue with: file path, line number, category (null-deref | missing-await | off-by-one | type-coerce), and a one-line description.
+Flag each issue with: file path, a **verbatim evidence snippet** copied from the file, category (null-deref | missing-await | off-by-one | type-coerce), and a one-line description. Record the snippet, not a line number — Step 6's Anchor Pass resolves the line with `Grep`.
 
 ### Step 2 — Error Handling
 For every changed file, verify:
@@ -132,7 +132,7 @@ app.use((err, req, res, next) => {
 });
 ```
 
-Flag each violation with: file path, line number, category (bare-catch | missing-status-check | raw-error-exposure), and description.
+Flag each violation with: file path, a **verbatim evidence snippet**, category (bare-catch | missing-status-check | raw-error-exposure), and description. Same rule as Step 1 — the snippet is what you produce; the line number comes from Step 6's Anchor Pass.
 
 ### Step 3 — Regression Check
 Use `rune:scout` to identify all files that import or depend on the changed files/functions.
@@ -337,7 +337,21 @@ Score is appended to the Preflight Report footer. Useful for tracking quality tr
 Invoke `rune:sentinel` on the changed files. Attach sentinel's output verbatim under the "Security" section of the preflight report. If sentinel returns BLOCK, preflight verdict is also BLOCK.
 
 ### Step 6 — Generate Verdict
-Aggregate all findings:
+
+**Falsification Pass first.** Before aggregating, filter findings by disproof, not by confidence — the same rule `review` applies (`../review/SKILL.md` → Step 6):
+
+- **DROP** a finding only when the code you read contains **direct counter-evidence** against its key claim (the null check exists, the `await` is present, the caller validates the input).
+- **KEEP** a finding that depends on context outside the diff which you did read via tools — that context is evidence.
+- **KEEP** a finding you can neither verify nor disprove. "Unsure" is not grounds to drop; only counter-evidence is.
+- Dropped findings are discarded silently, never listed as considered-and-dismissed.
+
+Type each surviving finding `OBSERVED | DERIVED | ASSUMED` per `../completion-gate/references/claim-discipline.md`. An `ASSUMED` finding — one resting on a premise you could not check — names that premise and **never escalates the verdict to BLOCK on its own**. It reports as WARN with the premise stated.
+
+**Anchor Pass second.** Every finding you collected in Steps 1-4 carries an evidence snippet, not a line number. Resolve each one now via the Anchor Ladder defined in `../review/SKILL.md` → Step 6: `Grep` the exact snippet, retry once whitespace-normalised with the outer lines dropped, and on a second miss mark the finding `UNANCHORED`.
+
+`UNANCHORED` behaves here exactly as it does in `review` — downgrade one level (BLOCK → WARN → INFO), report as `path (unanchored)` with the snippet inline, never drop. A finding that will not anchor **cannot carry the BLOCK verdict on its own**, for the same reason an `ASSUMED` one cannot: halting a pipeline on a claim nobody can locate spends the developer's trust faster than the bug would have.
+
+Then aggregate all surviving findings:
 - Any BLOCK from sentinel OR a logic issue that would cause data corruption or security bypass OR a dead interactive element (Step 4 cross-layer pairing / Step 4.5 dead-interactive check) OR a BLOCK from any domain hook → overall **BLOCK**
 - Any missing error handling, regression risk with no tests, or incomplete feature (other than the BLOCK cases above) → **WARN**
 - Only style or best-practice suggestions → **PASS**
@@ -346,18 +360,28 @@ Report PASS, WARN, or BLOCK. For WARN, list each item the developer must acknowl
 
 ## Output Format
 
-```
+````
 ## Preflight Report
 - **Status**: PASS | WARN | BLOCK
 - **Files Checked**: [count]
 - **Changes**: +[added] -[removed] lines across [files] files
+- **Unanchored**: [count — findings whose evidence did not resolve to a line]
 
 ### Logic Issues
-- `path/to/file.ts:42` — null-deref: `user.name` accessed without null check
-- `path/to/api.ts:85` — missing-await: async database call not awaited
+- `path/to/file.ts:42` — [OBSERVED] null-deref: `user.name` accessed without null check
+  ```ts
+  return user.name.trim();
+  ```
+- `path/to/api.ts (unanchored)` — [ASSUMED: caller in job.ts not read] missing-await: async database call not awaited
+  ```ts
+  db.orders.insert(row);
+  ```
 
 ### Error Handling
 - `path/to/handler.ts:20` — bare-catch: error swallowed silently
+  ```ts
+  } catch (e) {}
+  ```
 
 ### Regression Risk
 - `utils/format.ts` — changed function used by 5 modules, 2 have tests, 3 untested (WARN)
@@ -379,12 +403,14 @@ Report PASS, WARN, or BLOCK. For WARN, list each item the developer must acknowl
 
 ### Verdict
 WARN — 3 issues found (0 blocking, 3 must-acknowledge). Resolve before commit or explicitly acknowledge each WARN.
-```
+````
+
+Findings under Logic Issues and Error Handling show their evidence block; the Regression, Completeness, and Coherence sections describe file-level or structural gaps that have no single line to anchor, so they carry a path only.
 
 ## Constraints
 
 1. MUST check: logic errors, error handling, edge cases, type safety, naming conventions
-2. MUST reference specific file:line for every finding
+2. MUST anchor every line-level finding to a verbatim evidence snippet, resolving the line via the Anchor Pass rather than recall — unresolved findings report `(unanchored)`, downgraded one level, and cannot carry BLOCK alone
 3. MUST NOT skip edge case analysis — "happy path works" is insufficient
 4. MUST verify error messages are user-friendly and don't leak internal details
 5. MUST check that async operations have proper error handling and cleanup
@@ -424,7 +450,7 @@ WARN — 3 issues found (0 blocking, 3 must-acknowledge). Resolve before commit
 - Cross-layer pairing checked (Step 4): every new interactive component's handler chain reaches a real endpoint/service or has an explicit UI-only scope
 - Dead-interactive scan done (Step 4.5 UI hook) on all UI files in the diff
 - Sentinel invoked and its output attached in Security section
-- Structured report emitted with PASS / WARN / BLOCK verdict and file:line for every finding
+- Structured report emitted with PASS / WARN / BLOCK verdict, and every line-level finding anchored to a verbatim snippet (or reported `(unanchored)` and downgraded)
 
 ## Cost Profile
 

package/skills/rescue/SKILL.md

@@ -7,7 +7,7 @@ metadata:
   author: runedev
   version: "0.4.0"
   layer: L1
-  model: sonnet
+  model: opus
   group: orchestrator
   tools: "Read, Write, Edit, Bash, Glob, Grep"
 ---

package/skills/research/SKILL.md

@@ -5,7 +5,7 @@ metadata:
   author: runedev
   version: "0.4.0"
   layer: L3
-  model: haiku
+  model: sonnet
   group: knowledge
   tools: "Read, Glob, Grep, WebFetch, WebSearch"
 ---