vigiles 13.0.0 → 14.0.0

package/README.md

@@ -38,7 +38,7 @@
   all agree.
 
   SPINE = proof/demo-led. Real, screenshotable catches on shipped plugins, THEN
-  mechanism. Every proof traces to a real dogfood run (research/dogfood/) — NEVER
+  mechanism. Every proof traces to a real dogfood run (research/audit-captures/) — NEVER
   fabricate one. Order = most-RELATABLE first (broken tool ref → skill collision →
   rules-not-enforced → secrets-exfil gotcha LAST as the bite). The intro triplet
   maps to the three "vibes break silently" proofs (1, 2, 4); Proof 3 (your rules →
@@ -54,8 +54,11 @@
   init/compile/eject manage the spec layer (personas noticed the verb-count gap).
 
   DON'T SHAME OSS: catches are ANONYMIZED (no obra/superpowers, madappgang,
-  claude-flow by name) — real names live only in research/dogfood/.
-  Guard/compiled-hooks + the 2/7→7/7 battery are PARKED FOR LAUNCH — not the hero.
+  claude-flow by name) — real names live only in research/audit-captures/.
+  Guard/compiled-hooks stay PARKED FOR LAUNCH as a hero section; the 2/7→7/7 finding is
+  surfaced as ONE supporting, receipts-linked evidence line under Proof 4 (→
+  docs/compiled-hooks.md §disler battery + src/hook-dogfood.test.ts) — reachable
+  evidence under the Lighthouse umbrella, not the hero, not the brand.
 
   RULES: lead with the reader's CONCRETE PAIN; ≤ ~3-line paragraphs; ONE bold per
   block; ONE idea per sentence; NO internal vocabulary (moat/flywheel) / NO
@@ -152,7 +155,7 @@ Your rules → enforced   1 of 4 enforced · 2 one line away · 1 contradicted b
        your CLAUDE.md says enforce it; your config quietly turns it off
 ```
 
-You wrote the rule. Your agent treats it as gospel and follows it — until it doesn't, and nothing tells you which time. vigiles checks each mapped rule three ways: enforced, **one line away**, or — the one people screenshot — documented but silently **turned off**. Deterministic, no model. Want the rest compiled — a custom rule for a rule no linter ships, a hook for `git push`, the judgment calls honestly left alone? That's the opt-in `compile` tier (one model pass, then CI is plain lint).
+You wrote the rule. Your agent treats it as gospel and follows it — until it doesn't, and nothing tells you which time. vigiles checks each mapped rule three ways: enforced, **one line away**, or — the one people screenshot — documented but silently **turned off**. Deterministic, no model. Acting on the map is **opt-in and agent-driven**: enable a rule in one line (the `strengthen` skill does it for you), turn an action rule like `git push` into a compiled hook, leave judgment calls as prose. Nothing runs a model — or changes your config — unless you ask.
 **[How enforcement works →](docs/verifying-instruction-files.md)**
 
 ## Proof 4 — it can quietly read your secrets and send them out
@@ -166,6 +169,9 @@ You wrote the rule. Your agent treats it as gospel and follows it — until it d
 
 Hand one subagent all three powers and a poisoned web page can make it read your `.env` and POST it anywhere — no exploit code, just the tools it was given. The **80 looks like a B** — and that's the trap: a healthy grade hiding a subagent that's a data-leak waiting to happen. vigiles spots it from the tool list alone, free, no model.
 
+And the guard you'd write to stop it usually doesn't work: a widely-copied "safety hook" pattern blocks only **2 of 7** classic dangerous commands in our battery — the other five sail through while the hook _looks_ like it's working. A hook vigiles compiles for you blocks **7 of 7**, because the exit code and JSON contract are generated, not hand-written.
+**[The safety-hook battery →](docs/compiled-hooks.md)**
+
 That's the whole idea: it checks your harness against **reality, not style**. Every tool, hook, file, script, and skill you reference is verified to actually resolve — and where you name a linter rule, it's checked to exist _and_ be enabled (ESLint, Ruff, Clippy, and more).
 **[Everything it catches →](docs/what-vigiles-catches.md)** · point `audit` at a whole marketplace and it ranks every plugin the same way.
 

package/dist/audit-report.d.ts

@@ -20,8 +20,13 @@ import type { ScanReport, MarketplaceInfo } from "./scan.js";
 import type { PluginScore } from "./leaderboard.js";
 import type { RuleInventoryItem } from "./rule-inventory.js";
 import type { RuleRouting } from "./rule-routing.js";
-/** The current schema version. Bump only on a BREAKING change to the shape. */
-export declare const AUDIT_SCHEMA_VERSION = 1;
+/**
+ * The current schema version. Bump only on a BREAKING change to the shape.
+ * v2 (2026-07-15): the rule-map `mechanism` enum value for an unrouted rule
+ * changed `"compile"` → `"synthesize"` (a non-additive enum change), so a v1
+ * consumer that gated on `meta.schemaVersion` would mis-handle it — hence the bump.
+ */
+export declare const AUDIT_SCHEMA_VERSION = 2;
 export interface AuditReportMeta {
     /** Wire-format version — consumers gate on this. */
     readonly schemaVersion: typeof AUDIT_SCHEMA_VERSION;
@@ -126,9 +131,10 @@ export interface AuditReport {
     readonly rulesInventory?: readonly RuleInventoryItem[];
     /**
      * The deterministic State-B routing PREVIEW — the instruction file segmented
-     * into atomic rules, each routed (reuse / hook / semantic / unrouted) to how
+     * into atomic rules, each routed (reuse / hook / meta / semantic / unrouted) to how
      * it would be enforced, with per-category counts. No model, fs-only. Grounds
-     * the report's "compile" upsell in real numbers instead of generic copy.
+     * the report's "rule map" (strengthen / hook / prose / synthesize) in real
+     * numbers instead of generic copy.
      * Present only when at least one atomic rule was segmented. Additive/optional.
      */
     readonly ruleRouting?: RuleRouting;

package/dist/audit-report.js

@@ -20,8 +20,13 @@ exports.buildMarketplaceReport = buildMarketplaceReport;
 const audit_score_js_1 = require("./audit-score.js");
 const optimize_js_1 = require("./optimize.js");
 const audit_verdict_js_1 = require("./audit-verdict.js");
-/** The current schema version. Bump only on a BREAKING change to the shape. */
-exports.AUDIT_SCHEMA_VERSION = 1;
+/**
+ * The current schema version. Bump only on a BREAKING change to the shape.
+ * v2 (2026-07-15): the rule-map `mechanism` enum value for an unrouted rule
+ * changed `"compile"` → `"synthesize"` (a non-additive enum change), so a v1
+ * consumer that gated on `meta.schemaVersion` would mis-handle it — hence the bump.
+ */
+exports.AUDIT_SCHEMA_VERSION = 2;
 /** The one command that adopts every un-spec'd surface (bare `init`). */
 const CREATE_ALL_COMMAND = "npx vigiles init";
 /** The command that adopts ONE surface at a given repo-relative path. */