jig-ui 0.8.0 → 0.8.2

package/CHANGELOG.md

@@ -1,5 +1,144 @@
 # Changelog
 
+## 0.8.2
+
+Every fix here was found by a consumer using Jig rather than by Jig checking
+itself: the documentation site was upgraded to 0.8.1 and then styled in
+Tailwind, which is the first time Jig's Tailwind guidance had been followed
+end to end by anything other than its own tests.
+
+Three of the four are the same shape — two places answering one question, and
+disagreeing without either knowing the other existed.
+
+### Fixed
+
+- **`H-47` read a value differently depending on how it was spelled.**
+  `00-anti-patterns.md:11` sets the scope of the whole rule file: "**Framework:**
+  agnostic. […] Where a utility-class framework is in use, translate — the rule
+  is about the resulting style, not the syntax." The detector was the exact
+  inverse, in both directions at once. Its CSS branch matched `px` alone and
+  excluded `0/1px/2px`; its Tailwind branch matched ten units and excluded
+  nothing. So `font-size: 0.9em` was silent while `text-[0.9em]` was an error,
+  and `p-[1px]` was an error while `padding: 1px` was not.
+
+  A project on plain CSS got a clean `check` for code a Tailwind project got
+  eight errors for. Found by converting a real stylesheet to utilities without
+  changing one computed value and watching the report go from `No findings` to
+  eight; the two declarations responsible had been in that file since it was
+  written and had never been flagged. Both branches now read one definition.
+
+  **This widens what `check` reports.** A stylesheet carrying `1rem` or `0.9em`
+  past the token layer was always an H-47 violation and is now reported as one,
+  so a repo that was clean under 0.8.1 can have findings here without its CSS
+  having moved.
+
+- **The naming contract named namespaces Tailwind does not have.**
+  `02-tokens.md` opened with "an alias block can expose **any of them** as
+  Tailwind utilities" over a table of thirteen. Three generate nothing in
+  Tailwind v4 — `--duration-*`, `--measure-*` and `--focus-ring-*` — and
+  `--duration-*` shared a row with `--ease-*`, so only half of that row worked.
+  Aliasing one is accepted, emits the custom property, and produces no rule, so
+  the class lands on the element and does nothing: the same silent failure the
+  file warns about 190 lines later, reached from the opposite direction. The
+  table now carries a **Utility** column, and the three say how to be read from
+  a class instead — `max-w-(--measure-prose)`, which keeps the semantic token
+  and satisfies `H-47` without going through `@theme`.
+
+  `init`'s own generator was wrong in both directions. It correctly filtered
+  `--measure-*` and `--focus-ring-*`, and it also filtered `--size-*` and
+  `--border-width-*`, which both generate working utilities — `size-control`
+  sets width and height, `border-hairline` sets a border width. Jig was
+  withholding correct aliases for its own tokens, and a test asserted that as
+  correct, which is how it survived.
+
+- **`check` did not say which files it had looked at.** It defaults to the
+  files changed since HEAD and falls back to the whole repo when that diff is
+  empty. Nothing in the output said so, so the same repo reported `files=31` on
+  a clean tree and `files=9` with nine files touched, minutes apart, with
+  nothing committed — and a consumer bisected it by reverting files one at a
+  time to find out why.
+
+  Worse, `mechanical=pass:0` on a dirty tree means "nothing in your diff
+  fired", not "the project is clean", and the skill tells an agent to run
+  `check` before finishing — exactly when the tree is dirty and the scope is
+  narrowest. The exempt line compounded it: `src/content/rules.ts (matches
+  nothing — check the path)` was printed for a path that exists, is tracked,
+  and had matched a file on the previous run. The glob was fine; it matched
+  nothing *within the narrowed set*, and "check the path" sends you to debug a
+  correct config.
+
+  The summary now names the scope, a narrowed run says a clean result is not a
+  clean project, the exempt note distinguishes "no such path" from "not in this
+  scan", and `--all`'s help says it widens the files rather than the rules —
+  which is how it had been read.
+
+- **A flag written across two lines vanished from the metadata guard.**
+  `registeredFlags` read `src/index.ts` line by line and required the flag
+  string to sit on the same line as `.option(`, so reformatting one option to
+  fit a longer description dropped `--all` from the parsed set and from every
+  guard built on it. Caught by its own canary the moment an option wrapped.
+
+
+## 0.8.1
+
+Both fixes here are the same shape: 0.8.0 corrected the instance it was looking
+at and left the class alone, and in each case the commit message claimed a
+verification that had only checked the file it had just edited. Both were found
+by inspecting the published tarball rather than the working tree.
+
+### Fixed
+
+- **Four rule files still shipped author notes.** 0.7.x removed the section
+  headed "Notes for the author (not for the agent)" from `00-anti-patterns.md`
+  after an agent read it as "license to go tighter than the shared default" and
+  halved the radius scale on that authority. `01-modes.md`, `03-patterns.md`,
+  `04-principles.md` and `05-copy.md` carried a section under the same heading
+  and kept shipping it to every agent that installed Jig.
+
+  `01-modes.md` was the worst of them: it told the reader to **"Change them in
+  `tokens/mode.*.css`"** and closed with **"it is your call"** — an invitation
+  to edit the token layer, which is the one thing Jig's architecture reserves
+  for a human. `03-patterns.md` described navigation and cards as "deliberately
+  absent… add them once you have built enough". `05-copy.md` pointed at
+  `03-brand.md`, which does not exist. The content moves to
+  `docs/house-positions.md` unchanged; only its audience changes.
+
+- **`02-tokens.md` contradicted its own Tailwind fix 352 lines earlier.** The
+  compatibility table near the top still read *"Tailwind v4 | Wrap in
+  `@theme { }`"* — the exact instruction the section below it retracts with
+  *"Earlier versions of this file told you to, and Tailwind rejects it
+  outright."* The table is the part an agent reads first, so the correction
+  shipped underneath the error it corrected. A second, softer restatement
+  ("the same file can be wrapped in `@theme`") is gone too. `@theme` now first
+  appears in the section that explains it correctly.
+
+- **`jig explain` rendered a dangling `---` in 14 of the 15 pattern and mode
+  specs.** `parse.ts` has always dropped bare separator lines; `specs.ts` is a
+  separate code path and never did, so every `P-` and `M-` spec that is
+  followed by a separator in the source carried it into the rendered body,
+  between the last paragraph and the footer. Spotted on `P-12`, but it was
+  never about `P-12`. Table separators (`| --- |`) are untouched.
+
+- **`jig init`'s refusal without a terminal offered a way out that does not
+  work.** The message ended *"(To choose the mode without a terminal, write
+  jig.config.json first — init honours it.)"* The guard runs before any config
+  is read, so a config alone still exits 1. The sentence was true about mode
+  selection and false in a paragraph about not having a terminal, so it read as
+  a third alternative when it is a modifier on the first — a cold agent
+  followed it literally, hit the identical error, and allocated a
+  pseudo-terminal with Python's `pty` to get past it. It now says a config does
+  not replace `--yes`, and what the two do together. Nothing covered this path;
+  three tests now do.
+
+### Added
+
+- **`check-tokens` rule 13 — no shipped rule file addresses the author.** The
+  guard that should have existed for the 0.7.x fix. It reads `rules/` from disk
+  rather than a hardcoded list, so a rule file added later cannot escape it the
+  way those four did, and it checks the second-person tells ("your taste", "it
+  is your call", "my inclination is") as well as the heading, because a rename
+  would otherwise defeat it. Each tell is verified to fire on reintroduction.
+
 ## 0.8.0
 
 Everything here was found by handing Jig to agents that had never seen it and

package/dist/index.js

@@ -1125,6 +1125,7 @@ function parseSpecs(markdown, sourceFile) {
       current = null;
       continue;
     }
+    if (current && /^-{3,}$/.test(line.trim())) continue;
     if (current) body.push(line);
   }
   push();
@@ -1447,7 +1448,7 @@ function formatReport(findings, meta) {
   if (notes > 0) summaryParts.push(plural(notes, "note"));
   const rulesFired = new Set(findings.map((f) => f.ruleId)).size;
   const scope = meta.totalSpecs ? `${meta.totalRules} rules (+ ${meta.totalSpecs} pattern and mode specs)` : `${meta.totalRules} rules`;
-  const examined = meta.scanned === void 0 ? "" : ` \xB7 ${plural(meta.scanned, "file")}, ${meta.withStyles ?? 0} with styles`;
+  const examined = meta.scanned === void 0 ? "" : ` \xB7 ${plural(meta.scanned, "file")}${meta.scope === "changed" ? " changed since HEAD" : ""}, ${meta.withStyles ?? 0} with styles`;
   lines.push(`  ${summaryParts.join(", ")} \xB7 ${scope}${examined}, ${rulesFired} fired`);
   if (meta.scanned !== void 0 && meta.withStyles === 0) {
     lines.push("");
@@ -1455,11 +1456,17 @@ function formatReport(findings, meta) {
       `  No file carried a style region, so the detectors examined nothing. This is not a pass \u2014 a project with no styling and a project with clean styling report the same findings, and only one of them has been checked.`
     );
   }
+  if (meta.scope === "changed") {
+    lines.push("");
+    lines.push(
+      `  Scope: files changed since HEAD, not the whole project \u2014 this is the inner-loop default. A clean result here means nothing in your diff fired, not that the project is clean. Run 'jig check --all' for that.`
+    );
+  }
   if (meta.exemptPatterns && meta.exemptPatterns.length > 0) {
     const n = meta.exempt?.length ?? 0;
     lines.push(`  ${n} file(s) exempt via jig.config.json and not scanned:`);
     for (const { pattern, count, tooBroad } of meta.exemptPatterns) {
-      const note = count === 0 ? "matches nothing \u2014 check the path" : tooBroad ? `${count} files \u2014 likely too broad, review it` : `${count} file${count > 1 ? "s" : ""}`;
+      const note = count === 0 ? meta.scope === "changed" ? "matches nothing among the changed files \u2014 not necessarily wrong" : "matches nothing \u2014 check the path" : tooBroad ? `${count} files \u2014 likely too broad, review it` : `${count} file${count > 1 ? "s" : ""}`;
       lines.push(`    ${pattern}  (${note})`);
     }
     if (n > 0) {
@@ -2360,6 +2367,35 @@ var pureBlackWhite = {
   }
 };
 
+// src/check/length.ts
+var LENGTH_UNITS = [
+  "px",
+  "rem",
+  "em",
+  "pt",
+  "vh",
+  "vw",
+  "vmin",
+  "vmax",
+  "ch",
+  "ex"
+];
+var UNITS = LENGTH_UNITS.join("|");
+var LENGTH_RE = new RegExp(`^-?\\d*\\.?\\d+(?:${UNITS})$`, "i");
+var LENGTH_SCAN_RE = new RegExp(`(-?\\d*\\.?\\d+)(${UNITS})`, "gi");
+function isExcludedLength(value, unit) {
+  if (value === 0) return true;
+  return unit.toLowerCase() === "px" && (Math.abs(value) === 1 || Math.abs(value) === 2);
+}
+function hasHardCodedLength(value) {
+  LENGTH_SCAN_RE.lastIndex = 0;
+  let m;
+  while (m = LENGTH_SCAN_RE.exec(value)) {
+    if (!isExcludedLength(parseFloat(m[1]), m[2])) return true;
+  }
+  return false;
+}
+
 // src/check/tailwind.ts
 var CLASS_ATTR = /\b(?:class|className)\s*=\s*/g;
 function readBraced(source, open) {
@@ -2403,15 +2439,21 @@ function classAttributeValues(source) {
 }
 var ARBITRARY = /(?:^|\s)(?:[\w-]+:)*([a-z][\w-]*)-\[([^\]\s]+)\]/gi;
 var COLOUR = /^(?:#[0-9a-f]{3,8}|(?:rgba?|hsla?|oklch|oklab|lab|lch|color)\()/i;
-var LENGTH = /^-?\d*\.?\d+(?:px|rem|em|pt|vh|vw|vmin|vmax|ch|ex)$/i;
+var LENGTH_PARTS = /^(-?\d*\.?\d+)([a-z]+)$/i;
 function arbitraryValues(classes) {
   const out = [];
   for (const m of classes.matchAll(ARBITRARY)) {
     const [, utility, rawValue] = m;
     const value = rawValue.replace(/_/g, " ");
     if (/var\(|--/.test(value)) continue;
-    if (COLOUR.test(value)) out.push({ utility, value, kind: "colour" });
-    else if (LENGTH.test(value)) out.push({ utility, value, kind: "length" });
+    if (COLOUR.test(value)) {
+      out.push({ utility, value, kind: "colour" });
+      continue;
+    }
+    if (!LENGTH_RE.test(value)) continue;
+    const parts = LENGTH_PARTS.exec(value);
+    if (isExcludedLength(parseFloat(parts[1]), parts[2])) continue;
+    out.push({ utility, value, kind: "length" });
   }
   return out;
 }
@@ -2603,8 +2645,6 @@ var SPACING_PROPS = /* @__PURE__ */ new Set([
 ]);
 var DECL_RE2 = /(?<![-\w])([a-zA-Z-]+)\s*:\s*([^;]+)(?:;|$)/g;
 var COLOR_LITERAL_RE = /#[0-9a-fA-F]{3,8}\b|(?:rgb|hsl)a?\([^)]*\)/;
-var PX_RE = /(-?\d*\.?\d+)px/g;
-var EXCLUDED_PX = /* @__PURE__ */ new Set([0, 1, 2]);
 var KEYFRAME_STEP_RE = /^(from|to|\d+(\.\d+)?%)$/i;
 var PRIMITIVE_RE = /var\(\s*(--(?:brand|error|warning|success|info)-(?:h|s|l|fill-a))\s*[,)]/g;
 var TOKEN_LAYER_RE = /(^|\/)(\.jig\/tokens|jig)\/[^/]+\.css$/;
@@ -2661,16 +2701,7 @@ var hardcodedValue = {
           continue;
         }
         if (SPACING_PROPS.has(prop)) {
-          PX_RE.lastIndex = 0;
-          let px;
-          let flagged = false;
-          while (px = PX_RE.exec(value)) {
-            if (!EXCLUDED_PX.has(Math.abs(parseFloat(px[1])))) {
-              flagged = true;
-              break;
-            }
-          }
-          if (flagged) {
+          if (hasHardCodedLength(value)) {
             const line = lineOfOffset(block, m.index);
             findings.push(
               mkFinding(
@@ -3131,7 +3162,8 @@ function check(opts) {
     scanned: files.length,
     withStyles,
     exempt,
-    exemptPatterns: byPattern
+    exemptPatterns: byPattern,
+    scope: selection.mode
   });
   return { findings, report, hasError };
 }
@@ -3546,7 +3578,9 @@ var TAILWIND_NAMESPACES = [
   "--perspective-",
   "--aspect-",
   "--ease-",
-  "--animate-"
+  "--animate-",
+  "--size-",
+  "--border-width-"
 ];
 function tailwindNamespaced(names) {
   const kept = names.filter((n) => TAILWIND_NAMESPACES.some((ns) => n.startsWith(ns)));
@@ -3586,8 +3620,10 @@ function utilitiesBody(names, version2) {
    order, so Jig's value always wins. Do not "fix" it \u2014 deleting the alias
    removes the utility, deleting Jig's removes the value.
 
-   Only tokens in a Tailwind namespace are listed. \`--size-*\`, \`--measure-*\`,
-   \`--focus-ring-*\` and \`--border-width-*\` have none, so they stay \`var()\`-only.
+   Only tokens in a Tailwind namespace are listed. \`--measure-*\`, \`--focus-ring-*\`
+   and \`--duration-*\` have none, so they stay \`var()\`-only \u2014 read them from a class
+   with Tailwind's custom-property form instead: \`max-w-(--measure-prose)\`,
+   \`duration-(--duration-fast)\`.
 
    Regenerate with \`jig init\` after the token layer changes; a token missing here
    is a class that renders and matches nothing. */
@@ -3782,7 +3818,7 @@ async function init(opts) {
   const prompt = opts.prompt ?? defaultPrompt;
   if (!opts.yes && !opts.prompt && !process.stdin.isTTY) {
     throw new Error(
-      "'jig init' asks questions and stdin is not a terminal, so it cannot. Re-run with --yes to accept the derived defaults, or run it in a terminal. (To choose the mode without a terminal, write jig.config.json first \u2014 init honours it.)"
+      "'jig init' asks questions and stdin is not a terminal, so it cannot. Re-run with --yes to accept the derived defaults, or run it in a terminal. A jig.config.json does not replace --yes, because this check runs before it is read. With both, init takes the mode from the config instead of deriving it."
     );
   }
   const migrateLegacy = async (report, describe) => {
@@ -4239,7 +4275,13 @@ program.command("update").description("Update vendored Jig rules, skipping files
     process.exit(1);
   }
 });
-program.command("check").description("Check the repo against Jig's mechanical + hybrid rules.").option("--all", "check the whole repo instead of just changed files", false).option("--ci", "mechanical bucket only; exits non-zero on any error, deterministic", false).option("--json", "emit findings as JSON", false).action((opts) => {
+program.command("check").description("Check the repo against Jig's mechanical + hybrid rules.").option(
+  "--all",
+  // Names the files, because the default scope surprised a user who read
+  // this as widening the RULES and attested a clean diff as a clean project.
+  "scan every file in the repo, not just those changed since HEAD (same rules either way)",
+  false
+).option("--ci", "mechanical bucket only; exits non-zero on any error, deterministic", false).option("--json", "emit findings as JSON", false).action((opts) => {
   const projectRoot = findProjectRoot(process.cwd());
   try {
     const result = check({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jig-ui",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "A design system for coding agents. 104 numbered UI rules, brand x mode design tokens, and an installer for Claude Code, Codex, Cursor and opencode.",
   "license": "Apache-2.0",
   "type": "module",

package/rules/01-modes.md

@@ -205,17 +205,3 @@ Per project, one file supplying:
 - **Voice** — sentence case or title case, contraction policy, error-message tone.
 
 Default when no brand is supplied: warm neutral ramp anchored on `--color-bg-base` (`oklch(0.980 0.004 95)`, a warm off-white), no accent, 8px base radius (`--radius-sm`), border-led elevation. Greyscale output plus a stated question beats an invented purple (`A-01`).
-
----
-
-## Notes for the author (not for the agent)
-
-**Decided, not derived.** These numbers are internally consistent and defensible, but several are judgement calls that should be tuned once you have run real work through them: the operator row height, the three section-rhythm values, and the motion durations. Change them in `tokens/mode.*.css`, never at the call site — this file describes them, `02-tokens.md` resolves them, and neither is where they live.
-
-**Where your taste is recorded here:**
-- The zero-JS default in `editorial` — a stronger position than most systems take, and consistent with your writing on JS-dependent forms.
-- Absolute-first timestamps in `operator` — that is the procurement instinct: the record is evidence before it is a convenience.
-- Typed confirmation for destructive operator actions, and no hover-hidden information in all-day tools.
-- Border-led elevation as the unbranded default.
-
-**Open question worth resolving before tokens.** `product` is currently defined as the midpoint of the other two, which is how it earns its place, but it is also the mode that most often needs to lean. A customer dashboard leans editorial; a billing admin screen leans operator. Consider whether `product` needs a documented `dense` variant, or whether such surfaces should simply be declared `operator`. My inclination is the latter — three modes you apply confidently beat five you deliberate over — but it is your call, and it affects how many token sets `02` has to emit.

package/rules/02-tokens.md

@@ -48,7 +48,7 @@ They are the only token format every web framework consumes natively with no bui
 | Consumer | Usage |
 | --- | --- |
 | Plain CSS / any framework | `color: var(--color-text-strong)` |
-| Tailwind v4 | Wrap in `@theme { }` — generates utilities automatically |
+| Tailwind v4 | `@import` the barrel flat, alongside `@import "tailwindcss"` — see [Colour architecture](#colour-architecture). Utility classes are opt-in and need an alias block |
 | CSS-in-JS (styled-components, emotion) | `color: var(--color-text-strong)` inside template literals |
 | Vue / Svelte / Angular | Identical to plain CSS, scoped or global |
 | React inline styles | `style={{ color: 'var(--color-text-strong)' }}` |
@@ -281,23 +281,32 @@ Resist per-component tokens (`--button-bg`). They multiply fast and rarely earn
 
 ## Naming contract
 
-Names align to Tailwind v4's theme namespaces. This is free for other frameworks — they are ordinary custom properties — and means the same file can be wrapped in `@theme` to generate utilities without any framework taking a dependency on Tailwind.
+Names align to Tailwind v4's theme namespaces. This is free for other frameworks — they are ordinary custom properties — and means most of them can be exposed as Tailwind utilities through an alias block, without any framework taking a dependency on Tailwind.
 
-| Namespace | Holds | Layer |
-| --- | --- | --- |
-| `--color-*` | All colour | brand |
-| `--font-*` | Font families | brand |
-| `--text-*` | Font sizes | mode |
-| `--leading-*` | Line heights | mode |
-| `--tracking-*` | Letter spacing | mode |
-| `--spacing-*` | Spacing values | mode |
-| `--radius-*` | Corner radii | brand scale, mode selection |
-| `--border-width-*` | Stroke widths | brand options, mode selection |
-| `--focus-ring-*` | Focus indicator geometry | brand — an accessibility floor, so not mode-negotiable |
-| `--shadow-*` | Elevation | brand |
-| `--duration-*`, `--ease-*` | Motion | mode |
-| `--size-*` | Control and row heights | mode |
-| `--measure-*` | Line length caps | mode |
+**Most, not all.** Three of the namespaces below are Jig's own and have no utility behind them in Tailwind v4 — the **Utility** column says which. Aliasing one is accepted silently, emits the custom property, and generates no rule, so the class lands on the element and does nothing. That is the same silent failure this file warns about under [Optional: Tailwind utility classes](#optional-tailwind-utility-classes), reached from the other direction: there the alias is missing, here the alias is present and the utility does not exist.
+
+| Namespace | Holds | Layer | Utility |
+| --- | --- | --- | --- |
+| `--color-*` | All colour | brand | yes |
+| `--font-*` | Font families | brand | yes |
+| `--text-*` | Font sizes | mode | yes |
+| `--leading-*` | Line heights | mode | yes |
+| `--tracking-*` | Letter spacing | mode | yes |
+| `--spacing-*` | Spacing values | mode | yes |
+| `--radius-*` | Corner radii | brand scale, mode selection | yes |
+| `--border-width-*` | Stroke widths | brand options, mode selection | yes |
+| `--focus-ring-*` | Focus indicator geometry | brand — an accessibility floor, so not mode-negotiable | **no** |
+| `--shadow-*` | Elevation | brand | yes |
+| `--ease-*` | Motion easing | mode | yes |
+| `--duration-*` | Motion duration | mode | **no** |
+| `--size-*` | Control and row heights | mode | yes |
+| `--measure-*` | Line length caps | mode | **no** |
+
+`--duration-*` and `--ease-*` had one row between them and only one half of it works, which is why they are separated here.
+
+**Reading a `no` token from a class.** Use Tailwind's custom-property value form, which needs no alias and keeps the semantic name: `max-w-(--measure-prose)`, `duration-(--duration-fast)`, `outline-(--focus-ring-width)`. That satisfies `H-47` — the value is still the token — it simply does not route through `@theme`. The same form covers any token a mode file adds that has no namespace at all, such as the `--grid-*` values.
+
+Verified by compiling one alias per namespace against `tailwindcss@4.3.3` and reading the output. Probe each namespace with a *distinct* token name if you re-check this: `text-*`, `border-*`, `outline-*` and `max-w-*` each read more than one namespace, so a shared suffix makes a colour alias look like proof that four other namespaces work.
 
 **Rules**
 1. Semantic names only at the point of use. `--color-text-strong`, not `--color-neutral-900`, in component code. Primitives exist to build semantics, not to be consumed directly.

package/rules/03-patterns.md

@@ -510,17 +510,3 @@ Before writing a new component, check whether it is a composite of things that a
 A new pattern earns a place here when it has been built three times. Before then it is a component, not a pattern.
 
 Each entry states: anatomy in order, complete state list, rules that are decidable, and mode variance. If a rule cannot be checked by looking at the output, it belongs in `04-principles.md`.
-
----
-
-## Notes for the author (not for the agent)
-
-**Where your taste is recorded here:**
-- `P-01` — the whole feedback table is a position. Toasts are over-used because they are easy to build and require no layout decisions; treating them as the narrowest case rather than the default is deliberate.
-- `P-03` help-text-before-control. Contested — many systems put it after. Placing it before means it is read before the user commits to typing, which matters more in forms people fill once.
-- `P-04` one-column forms, and the no-JS baseline for the primary action.
-- `P-06` stable row identity, absolute timestamps, no hover-only truncation. The procurement instinct again: the record is evidence before it is a convenience.
-
-**Deliberately absent.** Navigation, cards, tabs, and toasts-as-a-component. Navigation and cards vary too much by project to have decidable rules yet — they would produce prose, not constraints. Add them once you have built enough to see the invariant.
-
-**Worth testing before extending.** These 12 cover most of what generated UI gets wrong. Point an agent at a form and a table with `00`, `01`, `02` and `03` loaded, and compare against the same task with nothing loaded. If `P-03` and `P-05` do not visibly change the output, the rules are not decidable enough and the fix is more specificity, not more patterns.

package/rules/04-principles.md

@@ -138,17 +138,3 @@ An invented accent, a decorative animation, a gradient filling an empty space
 A codebase with one consistent approach is more maintainable than one with a better approach applied to 30% of it. Note the divergence, raise it, change it deliberately as its own work — not silently, mid-task.
 
 **This tiebreaker outranks the other six.** It does not outrank Part 1: a local convention creating a genuine accessibility risk is a defect to raise, not a convention to match.
-
----
-
-## Notes for the author (not for the agent)
-
-**What changed in v0.2.** Part 1 did not exist. The file was adjudicative only — seven tiebreakers that fire when rules collide, with no method for producing a rule not yet written. That meant the system handed an agent 51 known failures and no way to recognise the 52nd. The four frames are that method.
-
-Frame 3 is the most immediately useful, because it is the only idea here that produces a number. Everything else in this system is checked by inspection; interaction cost is checked by counting, which makes it the one principle an agent can be held to objectively.
-
-Frames 1 and 2 are close to reasoning already embedded in `00` — the risk frame is *why* most of those rules exist, and the rationale requirement is the decidability test that let them in. Stating them explicitly means the next rule can be derived rather than remembered.
-
-**Tiebreaker 7 remains the one to argue about**, and now has a stated ceiling: it loses to Frame 1. Without that boundary, "match the codebase" would license inheriting anything.
-
-Tiebreakers 1 and 2 are the same instinct from two directions, and both come from outside software — a document that looks wrong gets marked and filed, never destroyed.

package/rules/05-copy.md

@@ -141,13 +141,3 @@ See `P-01` for *where* the message goes and `F-37` for field-level validation te
 6. Numerals as figures, formatted consistently? (`I-83`)
 7. One word per concept across the whole product? (`I-87`)
 8. Every error saying what happened and what to do next? (`I-90`)
-
----
-
-## Notes for the author (not for the agent)
-
-**Where your taste is recorded here:** the ban on apology words in errors, and `I-90`'s requirement that the heading and button work without the body text. Both come from the same instinct as the rest of the system — the person reading is trying to get something done, and the interface should not make them wade.
-
-`I-87` is the rule most likely to need a project-specific companion. A term list belongs in the brand file's voice section, not here; this rule only says that one must exist and be followed.
-
-Deliberately absent: tone-of-voice guidance beyond plain language. Tone is a brand decision and varies per client, so it belongs in `03-brand.md` when that file exists.

package/templates/SKILL.md.tmpl

@@ -89,3 +89,13 @@ check that never inspected anything.
 
 A skipped check must say `skipped` and give the reason. Do not report `ran` for
 a check you did not perform.
+
+**`files=` and `styled=` describe a scope, and the scope is not fixed.**
+`jig check` defaults to the files changed since HEAD and falls back to the
+whole repo only when that diff is empty. So the same project reports a
+different `files=` before and after a commit with nothing else having moved,
+and two `JIG_CHECK:` lines are comparable only when both runs had the same
+scope. Run `jig check --all` for a number that describes the project rather
+than your diff — `--all` widens the files, not the rules. A narrowed run says
+so in its own output; attest from what it printed, not from what you assumed
+it looked at.