jig-ui 0.16.1 → 0.17.0

package/CHANGELOG.md

@@ -1,5 +1,52 @@
 # Changelog
 
+## 0.17.0
+
+Thirteen more tells of a generated page, ten of them caught by `check`, and a
+picture for every rule. Also carries the probe and verdict fixes tagged as 0.16.2,
+which was not published to npm.
+
+### Added
+
+- **Thirteen rules.** `A-135` a kicker above every heading, `A-136` an eyebrow
+  chip over the headline, `A-137` cream and beige by reflex, `A-138` an italic
+  serif display headline, `A-139` a side-tab accent border, `A-140` a thick
+  coloured border on a rounded element, `A-141` cards inside cards, `A-142` the
+  soft rounded card, `A-143` a decorative grid or stripe background, `A-144`
+  dark mode with glowing accents, `G-145` a pulsing status dot, `A-146`
+  numbered section labels, `F-147` asking for more than the task needs.
+- **Ten detectors for them**, reading both the CSS and the utility classes in
+  markup, and joining the two where a page splits them (a pulse or a serif
+  declared on a class, worn by the element). All warnings; the rules are hybrid.
+  On seven pages built with no guidance, every instance of these tells found by
+  eye was reported, and every report was a real instance.
+- **`examples/`: a dont and a do for all 143 rules**, shipped in the package.
+  Each is a small self-contained HTML fragment that renders the same in a
+  sandboxed frame or an inert box. `jig explain <ID>` names the file, and
+  `packages/preview/examples.html` shows them all side by side.
+
+### Fixed
+
+- **A probe no longer fails while Chrome shuts down.** Its temporary profile
+  was deleted the moment Chrome was killed; under load the delete raced
+  Chrome's last writes, threw, and failed a probe whose measurement had
+  succeeded. It now waits for Chrome to exit and retries the delete.
+- **`jig probe --run <page> --serve <dir>` measures a built static site.** A
+  build links its styles from the site root, so opened as a file nothing loaded
+  and the probe measured an unstyled page. The CLI now serves the build
+  directory on a local port. The stamp is still the page file's checksum on
+  disk, and the gate re-renders a served probe the same way.
+- **Verdicts are `critique`'s own.** `make`, fixing three findings, rewrote
+  those verdicts to `ok` itself and the gate accepted it. The gate now records
+  the verdict files when a `critique` session stops, and stops any later
+  session that changed them without running `critique`.
+
+### Changed
+
+- `A-04` names glass applied everywhere, `A-06` the same equal-card reflex at
+  any count, `I-81` the page's headline, and `I-89` button labels as well as
+  links.
+
 ## 0.16.1
 
 ### Fixed

package/README.md

@@ -12,13 +12,13 @@ Installed as `npx jig-ui` — the bare name was taken on npm.
 Jig is **a skill your coding agent reads**, and **a CLI you can run yourself**.
 They are two halves of the same thing, and the split is not arbitrary:
 
-- Of the 130 rules, **26 can be decided by a machine** — a hard-coded colour, a
+- Of the 143 rules, **36 can be decided by a machine** — a hard-coded colour, a
   contrast ratio below the floor, a removed focus ring. The CLI decides those.
-- The other **104 are judgment** — whether an empty state says anything useful,
+- The other **107 are judgment** — whether an empty state says anything useful,
   whether a label reads as an instruction, whether motion earns its place. No
   regex settles those. An agent reads the rules and applies them.
 
-Running only the CLI gets you the 26. Running only the agent gets you the 104 with
+Running only the CLI gets you the 36. Running only the agent gets you the 107 with
 no verification. **A clean `jig check` is not a clean review**, and the skill
 says so to every agent that reads it.
 
@@ -285,7 +285,7 @@ what Jig knows about your project.
 The opposite job, and the loop runs in its ordinary order. The difference is what
 the old page counts as: **content and constraints, not a target.**
 
-1. **Measure the page as it is, first.** `jig probe --run <page> --save <slug>`
+1. **Measure the page as it is, first.** `jig probe --run <page> --save <slug>` (add `--serve <build dir>` for a built site)
    records what it does today at each width — whether it scrolls sideways, whether
    the menu opens, what order it reads in. Keep it. It is the only way to say
    afterwards whether the redesign improved anything or merely changed it.
@@ -403,7 +403,7 @@ on the result — the CLI reports, the agent applies the judgment half.
 | Slash command | Equivalent |
 | --- | --- |
 | `/jig init` | `jig init` — then states the mode it chose and what it wired |
-| `/jig check` | `jig check` — then applies the 104 judgment rules and reports both halves |
+| `/jig check` | `jig check` — then applies the 107 judgment rules and reports both halves |
 | `/jig explain C-19` | `jig explain C-19` — prints the rule as-is, without paraphrasing it |
 | `/jig explain contrast` | `jig explain contrast` — every rule matching a word, when you do not have an id |
 | `/jig install --agent cursor` | `jig install --agent cursor` |
@@ -601,12 +601,13 @@ treatment.
 
 | File | Contents |
 | --- | --- |
-| `rules/00-anti-patterns.md` | 112 universal rules with corrections |
+| `rules/00-anti-patterns.md` | 125 universal rules with corrections |
 | `rules/01-modes.md` | `editorial` / `product` / `operator` profiles |
 | `rules/02-tokens.md` | Token contract, naming, consumption |
 | `rules/03-patterns.md` | Component anatomy and behaviour |
 | `rules/04-principles.md` | Five frames + seven tiebreakers |
 | `rules/05-copy.md` | Interface text rules |
+| `examples/<ID>.html` | For every rule, a small dont and do: self-contained HTML fragments that render in a sandboxed frame. `jig explain <ID>` names the file. |
 | `<css dir>/jig/brand.*.css` | Identity. One per project. |
 | `<css dir>/jig/mode.*.css` | Density, scale, rhythm, motion |
 | `<css dir>/jig/theme.css` | The barrel — brand + mode. This is what you import. With more than one mode, `theme.<mode>.css`, one per mode, each imported by its routes' layout. |