rulereceipt 0.1.48 → 0.1.49

package/README.md

@@ -393,6 +393,28 @@ report to the path you name, and `rules --include/--exclude` records a
 correction in `.rulereceipt/overrides.json`. Plain `rulereceipt check` writes
 nothing and makes no network calls.
 
+**Severity, per rule.** A committed, team-shared `.rulereceipt/config.json`
+sets how hard each rule bites in CI, by its stable handle (from `rulereceipt
+rules --list`):
+
+```json
+{
+  "rules": {
+    "a1b2c3": "off",     // hidden from the report, never gates
+    "d4e5f6": "warn",    // shown, but does not fail the build
+    "97h8i9": "error"    // shown, FAILS the build — the default for a checkable rule
+  }
+}
+```
+
+No config means today's behaviour: every checkable FAIL is an `error`. This is
+the one place severity lives — a team marks the must-not-break rules `error`
+and the nice-to-haves `warn`, so CI gates on what matters instead of going red
+on day one. (Refusing a command *before* it runs is separate, and stays with
+the guard's `rules --forbid` clause-mark — a config that could block on any
+rule would refuse far too much.) The older `{"warn": ["a1b2c3"]}` list still
+works and means the same as `"warn"` above.
+
 **You can verify the package came from this source.** Every release from
 0.1.19 on is built and published by GitHub Actions and signed with
 [npm provenance](https://docs.npmjs.com/generating-provenance-statements),

package/dist/cli.js

@@ -33,7 +33,7 @@ import { maybeShowWhatsNew } from "./whatsNew.js";
 import { verifyReceipt, parseReceipt } from "./receipt.js";
 import { buildBadge } from "./badge.js";
 import { buildInitGuidance } from "./init.js";
-import { loadProjectConfig, handleMap, blockingFailures, warningFailures, PROJECT_CONFIG_PATH } from "./projectConfig.js";
+import { loadProjectConfig, handleMap, blockingFailures, warningFailures, visibleResults, PROJECT_CONFIG_PATH } from "./projectConfig.js";
 import { maybeCheckUpdates, isUpdateCheckEnabled } from "./updateCheck.js";
 import { generateDigest } from "./digest.js";
 import { enableSchedule, disableSchedule, scheduleStatus } from "./schedule.js";
@@ -264,12 +264,14 @@ async function runCheck(opts) {
     // sends only a random install ID, never rule text or transcript content,
     // regardless of --llm.
     const judgmentResults = llm ? await runJudgmentChecks(judgment, events) : judgment.map(({ rule }) => needsLlmResult(rule));
-    const results = [...deterministicResults, ...judgmentResults];
-    // Severity: rules a team marked as warnings in .rulereceipt/config.json are
-    // still reported but do not fail the build. handleFor maps a result back to
-    // its stable handle so the mark survives edits that renumber rule ids.
+    const rawResults = [...deterministicResults, ...judgmentResults];
+    // Severity ladder from .rulereceipt/config.json (per rule handle): `off`
+    // rules are hidden entirely, `warn` rules are shown but do not fail the
+    // build, everything else is `error` (the default). handleFor maps a result
+    // back to its stable handle so the mark survives edits that renumber ids.
     const projectConfig = loadProjectConfig(cwd);
     const handleFor = handleMap(rules);
+    const results = visibleResults(rawResults, projectConfig, handleFor);
     const blockingFails = blockingFailures(results, projectConfig, handleFor);
     const warnedFails = warningFailures(results, projectConfig, handleFor);
     const meta = { sessionFilePath, ruleCount: results.length };

package/dist/projectConfig.d.ts

@@ -2,24 +2,49 @@ import type { CheckResult, Rule } from "./types.js";
 /**
  * A committed, team-shared config at .rulereceipt/config.json.
  *
- * Today it holds one thing: rule handles to treat as WARNINGS — a broken
- * "warning" rule is still reported, but it does not fail the build. This is
- * the honest version of "severity": a team marks the must-not-break rules as
- * errors (the default) and the nice-to-have ones as warnings, so CI gates on
- * what actually matters instead of going red on day one.
+ * ONE place for "how hard should this rule bite", a ladder per rule handle:
+ *
+ *   off    hidden from the report, never gates CI
+ *   warn   shown, does not fail the build
+ *   error  shown, FAILS the build (the default for a checkable rule)
+ *
+ * This is the honest version of "severity": a team marks must-not-break rules
+ * as errors (the default) and nice-to-haves as warnings, and silences the
+ * irrelevant ones, so CI gates on what actually matters instead of going red
+ * on day one. It replaces three scattered mechanisms — the old `warn` list,
+ * `rules --exclude` (now `off`), and the plain default — with one field.
+ *
+ * Pre-run BLOCKING is deliberately NOT a mode here: refusing a command before
+ * it runs still goes through the guard's clause-mark (`rules --forbid`),
+ * because a config that could block on any rule would refuse the 62.8% of
+ * commands the measured guard already showed it must not. This file governs
+ * the report and the CI gate; the guard governs refusal.
  *
  * Handles, not rule ids: an id is positional and renumbers when the file is
  * edited above it; a handle is a content hash, so it survives edits. Get one
  * from `rulereceipt rules --list`.
+ *
+ * Backward compatible: the old top-level `warn: [handle, ...]` list still
+ * works and means the same as `rules: { <handle>: "warn" }`.
  */
+export type RuleMode = "off" | "warn" | "error";
 export interface ProjectConfig {
     warn: string[];
+    rules: Record<string, RuleMode>;
 }
 export declare const PROJECT_CONFIG_PATH: string;
 export declare function loadProjectConfig(cwd: string): ProjectConfig;
+/**
+ * The mode for one result. `rules` wins over the legacy `warn` list; anything
+ * unlisted is `error`, so the default is unchanged and no config means today's
+ * behaviour exactly.
+ */
+export declare function modeForResult(result: CheckResult, config: ProjectConfig, handleFor: (r: CheckResult) => string): RuleMode;
+/** Results the report should show — everything except rules set to `off`. */
+export declare function visibleResults(results: CheckResult[], config: ProjectConfig, handleFor: (r: CheckResult) => string): CheckResult[];
 /** A lookup from a result back to its stable rule handle, built from the loaded rules. */
 export declare function handleMap(rules: Rule[]): (r: CheckResult) => string;
-/** FAILs that are NOT configured as warnings — these fail the build. */
+/** FAILs at `error` mode — these fail the build. (`off` never reaches here.) */
 export declare function blockingFailures(results: CheckResult[], config: ProjectConfig, handleFor: (r: CheckResult) => string): CheckResult[];
-/** FAILs that ARE configured as warnings — shown, but they do not fail the build. */
+/** FAILs at `warn` mode — shown, but they do not fail the build. */
 export declare function warningFailures(results: CheckResult[], config: ProjectConfig, handleFor: (r: CheckResult) => string): CheckResult[];

package/dist/projectConfig.js

@@ -1,19 +1,44 @@
 import { readFileSync } from "node:fs";
 import { join } from "node:path";
 import { ruleFingerprint } from "./overrides.js";
+const VALID_MODES = ["off", "warn", "error"];
 export const PROJECT_CONFIG_PATH = join(".rulereceipt", "config.json");
 export function loadProjectConfig(cwd) {
     try {
         const parsed = JSON.parse(readFileSync(join(cwd, PROJECT_CONFIG_PATH), "utf-8"));
-        const warn = parsed?.warn;
-        return { warn: Array.isArray(warn) ? warn.filter((x) => typeof x === "string") : [] };
+        const warn = Array.isArray(parsed?.warn) ? parsed.warn.filter((x) => typeof x === "string") : [];
+        const rules = {};
+        if (parsed?.rules && typeof parsed.rules === "object" && !Array.isArray(parsed.rules)) {
+            for (const [handle, mode] of Object.entries(parsed.rules)) {
+                if (typeof mode === "string" && VALID_MODES.includes(mode))
+                    rules[handle] = mode;
+            }
+        }
+        return { warn, rules };
     }
     catch {
         // Missing or malformed config means no severities configured, never an
         // error — same fail-open discipline as the rest of the tool.
-        return { warn: [] };
+        return { warn: [], rules: {} };
     }
 }
+/**
+ * The mode for one result. `rules` wins over the legacy `warn` list; anything
+ * unlisted is `error`, so the default is unchanged and no config means today's
+ * behaviour exactly.
+ */
+export function modeForResult(result, config, handleFor) {
+    const handle = handleFor(result);
+    if (config.rules[handle])
+        return config.rules[handle];
+    if (config.warn.includes(handle))
+        return "warn";
+    return "error";
+}
+/** Results the report should show — everything except rules set to `off`. */
+export function visibleResults(results, config, handleFor) {
+    return results.filter((r) => modeForResult(r, config, handleFor) !== "off");
+}
 /** A lookup from a result back to its stable rule handle, built from the loaded rules. */
 export function handleMap(rules) {
     const m = new Map();
@@ -21,11 +46,11 @@ export function handleMap(rules) {
         m.set(`${rule.source}:${rule.id}`, ruleFingerprint(rule));
     return (r) => m.get(`${r.ruleSource}:${r.ruleId}`) ?? "";
 }
-/** FAILs that are NOT configured as warnings — these fail the build. */
+/** FAILs at `error` mode — these fail the build. (`off` never reaches here.) */
 export function blockingFailures(results, config, handleFor) {
-    return results.filter((r) => r.status === "FAIL" && !config.warn.includes(handleFor(r)));
+    return results.filter((r) => r.status === "FAIL" && modeForResult(r, config, handleFor) === "error");
 }
-/** FAILs that ARE configured as warnings — shown, but they do not fail the build. */
+/** FAILs at `warn` mode — shown, but they do not fail the build. */
 export function warningFailures(results, config, handleFor) {
-    return results.filter((r) => r.status === "FAIL" && config.warn.includes(handleFor(r)));
+    return results.filter((r) => r.status === "FAIL" && modeForResult(r, config, handleFor) === "warn");
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rulereceipt",
-  "version": "0.1.48",
+  "version": "0.1.49",
   "description": "Checks whether a Claude Code session actually followed your CLAUDE.md / AGENTS.md rules, with evidence.",
   "repository": {
     "type": "git",