jig-ui 0.8.0 → 0.8.1

package/CHANGELOG.md

@@ -1,5 +1,65 @@
 # Changelog
 
+## 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();
@@ -3782,7 +3783,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) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jig-ui",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "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,7 +281,7 @@ 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 an alias block can expose any of them as Tailwind utilities without any framework taking a dependency on Tailwind.
 
 | Namespace | Holds | Layer |
 | --- | --- | --- |

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.