jig-ui 0.24.0 → 0.26.0

package/CHANGELOG.md

@@ -1,5 +1,149 @@
 # Changelog
 
+## 0.26.0 (2026-10-13)
+
+An unbranded page that looks designed, tables that hold together on a phone and
+on a touch screen, and two layout faults the render probe now measures.
+
+### Fixed
+
+- **An unbranded page no longer reads as unstyled.** The default font stack put
+  `system-ui` first, and on Linux that resolves to the desktop's own font,
+  often DejaVu Sans, before any better face is tried. It now names each
+  platform's interface face in turn: San Francisco, Segoe UI, Roboto, then
+  Noto Sans, Helvetica and Arial. The `A-138` serif check knows these names,
+  so the stack is not read as a serif for ending in `sans-serif`.
+- **A table stacked on a phone leads with what each row is.** `L-01`, step 6,
+  told an agent to put each column's name in front of every cell, and a member
+  list on a phone read like a form: "Member:", "Email:", "Role:", "Status:".
+  The row's own name now leads its block with no label, a value that says what
+  it is (an email, a role, a status) gets none, and the row's actions sit
+  together on one line where they fit, with no "Actions" label. In three runs,
+  every row kept its actions on one line at 390px.
+- **A table's rows stay one height.** `operator`'s 36px row is below the 48px
+  touch target, and an agent met the floor with a control's own minimum
+  height, so rows with an action stood taller than rows without one. A control
+  in a row now takes the row's height. For a mouse a dense row is above WCAG
+  2.2's 24px minimum; for a finger it is not, so under a coarse pointer
+  `operator` and `product` raise their row tokens to the touch target, and
+  every row grows together.
+
+### Added
+
+- **The render probe reports a page that scrolls sideways, with or without a
+  review.** A page wider than the screen was reported only when a critique had
+  called it clean; with no critique the measurement was dropped. Help articles
+  built without Jig ran 424 to 478px wide on a 360px phone, with nothing
+  reported. It is now a measured failure in every mode (`D-115`).
+- **The render probe reports a table cell that has left its table.** An agent
+  set a cell to `display: flex` to line up a name and a tag; the cell stopped
+  taking its row's height, and every name drifted above its row's divider. Any
+  `td` or `th` that is not a table cell while its table is drawn as a table is
+  now a measured failure (`P-06`), which also says to put the flex on a wrapper
+  inside the cell. A table stacked on a phone is left out.
+
+## 0.25.0 (2026-10-09)
+
+Link previews, code and tables that reflow on an `editorial` phone, and the
+gate's rules stated before a session stops.
+
+### Added
+
+- **The render probe measures a box that scrolls sideways.** `editorial`
+  allows no scrolling region on a phone (`M-01`), and the probe only measured
+  a page wider than the screen. In a control run on this release's reflow
+  text, a spec said the code would wrap and the built page scrolled it in a
+  box, and nothing caught it. The probe now records each box that scrolls
+  sideways, and on an `editorial` surface at phone width each is a measured
+  failure: a critique reports it, `ship` counts it, and the gate holds make and
+  tweak until the page reflows.
+- **J-164: an indexable page a link preview cannot read.** A page pasted into a
+  message or a post is met as a card before anyone opens it, and the card is
+  built from `og:title` and `og:description`. Section J said it covered the link
+  preview, and no rule asked for one, so `seo` and `check` passed a site with no
+  preview on any page. `check` reports it in a file that writes its own
+  `<head>`, and in a head fragment (`<svelte:head>`, Astro, `next/head`) that
+  writes the page's own description and no `og:description`, which no layout
+  can supply; elsewhere a layout may write it, and the render decides: the probe
+  now reads `og:description`, and a served page missing either tag is a
+  finding on the page. An image and `og:url` need the page's full address, so
+  the rule asks for them once a site has one. 160 rules, 40 of them decided by
+  a machine.
+
+### Changed
+
+- **`editorial` on a phone says what replaces a scrolling box.** `L-01` sent a
+  wide code block or table to scroll inside itself, and the same sentence said
+  `editorial` allows no scrolling region on mobile, naming nothing in its
+  place. `L-01`, `D-115` and `M-01` now say it: a code block keeps its line
+  breaks and indents and wraps its long lines, a table too wide for the screen
+  stacks its rows with each cell's column name in front and stays a `<table>`,
+  and a long identifier breaks where it must.
+- **`E-51`'s near-universal glyphs are a test, not a list.** Close, search and
+  menu were read as the only icon-only controls allowed. The rule now asks
+  whether most readers would name the glyph the same way without its label,
+  with examples that pass (a theme's sun and moon, a well-known service's mark)
+  and that do not.
+- **`E-28` says what a browser's own tab stop on an `<iframe>` gets.** One that
+  only shows something is taken out of the tab order rather than given states;
+  one the reader uses keeps its stop and shows focus.
+- **spec, mockup and tweak each end with what the gate holds them to.** A short
+  "Before you stop" list names the checks the Stop hook makes on what that
+  command records, beyond the shape its steps already teach: where it may write, whose words a quotation is, the check record's
+  format, what counts as the owner's confirmation or approval, and what
+  `tweak.json` holds. Sessions learned these from refusals, and each refusal
+  cost a round of fixing, re-checking and committing. A test pairs each check
+  with its line in the list, so a check added without one fails.
+- **`jig check` exits non-zero on a mechanical error, with or without `--ci`.**
+  It used to exit 0 whatever it found, so a pre-commit hook, a CI step or a
+  script running it as a linter read a run full of errors as a pass. Judgment
+  findings are still reported without failing the run. `--ci` now only limits
+  the run to the mechanical rules.
+
+### Fixed
+
+- **The skill and `spec` say `L-01` has six steps, and `spec` names the sixth.**
+  `L-01` gained step 6, how a screen collapses, and both kept telling the agent
+  to run "its five steps", so it stopped before the one that gives the phone
+  composition. In a control run on this release's reflow text, a spec chose a
+  sideways-scrolling code block for an `editorial` phone. A test now ties the
+  count to `L-01`'s own step headings.
+- **`I-118` exempts quoted output in the rule and in `check`, as the probe
+  already did.** The rule exempted a quotation in `<blockquote>` or `<q>`; the
+  render probe also leaves `<pre>`, `<code>`, `<samp>` and `<kbd>` alone, and
+  `check` exempted none of them. A page quoting a tool's real output was told
+  by `check` to rewrite it, and by the rule to keep the quotation's own
+  punctuation. All three now agree.
+- **A critique is no longer held on what the page fails.** An em dash on the
+  rendered page, a missing or overlong title or description, unresolved tokens
+  or the browser's default font are failures of the page, not of the review.
+  `verdicts` reported them as a critique left incomplete, so the gate held the
+  critique session until they were gone, and the session could clear them only
+  by editing the page, which a critique never does. They are now listed apart,
+  under `!`, as `measured=` on the `JIG_VERDICTS` line, and once each rather than
+  at every width. A critique reports them and finishes; `ship` counts them as
+  findings, and the gate holds make and tweak until the page is fixed. A verdict
+  the probe contradicts still means the review re-runs.
+- **A quoted `mockup:` value reads as the value it holds.** A spec that wrote
+  `mockup: "skipped — the owner: \"…\""`, valid YAML, read to the gate as the
+  word `"skipped`, so every tweak of the page was refused for having no approved
+  drawing, and the check that the owner's words are quoted was silently skipped.
+- **An em dash inside tool output no longer counts as the page's own.** The
+  probe leaves quotations and `<pre>`, `<code>`, `<samp>` and `<kbd>` out of the
+  dash scan, but it cut them out of the page's text one string at a time. An
+  inline `<code>` earlier in the prose, such as a rule id, removed those
+  characters from the output block below it, the block no longer matched, and
+  its dash was reported. Quotations are now left out of the text as it is read.
+- **The README no longer says every command is also a slash command.** `gate`
+  has no slash form (only the Stop hook runs it), and six slash commands are
+  agent procedures with no command of their own in the CLI. The table under it
+  was right; the sentence above it now says what the table does.
+- **`check` no longer says it examined nothing while reporting findings.** A
+  file styled only with utility classes, such as `class="p-[13px]"`, is read by
+  H-47 but was left out of the styled-file count. A change to such a file
+  reported H-47 errors and, below them, that no file carried a style region. The
+  count now includes markup whose class attributes hold classes.
+
 ## 0.24.0 (2026-09-30)
 
 The owner's word held to one rule, Jig's instructions in your project's AGENTS.md,
@@ -237,8 +381,7 @@ and `jig ship` is where nothing is optional.
 
 ## 0.21.0 (2026-09-28)
 
-Dev builds, so a fix is tried on a real project before it ships, and the gate
-fixes that trial on jig-site turned up.
+Dev builds, so a fix is tried on a real project before it ships, and gate fixes that trial turned up.
 
 ### Added
 
@@ -520,7 +663,7 @@ The gate holds an HTML mockup that does not draw the page at every size.
 
 ## 0.18.4 (2026-09-25)
 
-Every release summary is one or two lines, for jig-site's Versions page.
+Every release summary is one or two lines.
 
 ### Changed
 
@@ -552,8 +695,7 @@ older probe file says it is older rather than forged.
 
 ## 0.18.2 (2026-09-25)
 
-Every release in this changelog now carries its date and a one-line summary,
-for jig-site's Versions page.
+Every release in this changelog now carries its date and a one-line summary.
 
 ### Changed
 
@@ -567,8 +709,7 @@ for jig-site's Versions page.
 
 ## 0.18.1 (2026-09-25)
 
-Two fixes found by jig-site's fourth round: the probe misread a `<details>`
-menu, and the emoji rule missed an arrow that renders as an emoji.
+Two fixes: the probe misread a `<details>` menu, and the emoji rule missed an arrow that renders as an emoji.
 
 ### Fixed
 
@@ -637,7 +778,7 @@ keyboard access a rule requires fits every script budget.
 
 ## 0.17.3 (2026-09-25)
 
-Three defects found building jig-site's header with the full loop.
+Three defects found building a site header with the full loop.
 
 ### Fixed
 

package/README.md

@@ -27,13 +27,13 @@ later.
 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 159 rules, **39 can be decided by a machine** — a hard-coded colour, a
+- Of the 160 rules, **40 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 **120 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 39. Running only the agent gets you the 120 with
+Running only the CLI gets you the 40. Running only the agent gets you the 120 with
 no verification. **A clean `jig check` is not a clean review**, and the skill
 says so to every agent that reads it.
 
@@ -406,7 +406,7 @@ overwrites a config or brand file you have edited.
 | --- | --- |
 | `install --agent <name> [--scope project\|global] [--hook]` | Puts the skill and its rules where your agent will find them. At project scope, also keeps Jig's block in `AGENTS.md` (and `CLAUDE.md` for Claude Code); with `--hook`, adds the Stop hook. |
 | `init [--yes]` | Sets the project up: CSS system, brand colour, token files, `jig.config.json`, wired imports, baseline check. |
-| `check [--all] [--ci] [--json]` | Runs the rules a machine can decide. Reports findings by rule id. |
+| `check [--all] [--ci] [--json]` | Runs the rules a machine can decide. Reports findings by rule id, and exits non-zero on any mechanical error. |
 | `update` | Refreshes an install to a newer version, leaving alone any file you have edited. |
 | `seo [--json]` | Audits what a search engine and a link preview read, across the whole project: a route whose metadata says `noindex` sitting in the sitemap, two pages claiming one title, a sitemap that lists nothing or lists paths a crawler drops. Whether a sitemap and a robots file exist is counted, not reported: no rule asks for either, and a site with no domain yet cannot write an honest sitemap. Needs no config, no decisions and no spec. |
 | `checksum <spec>` | Prints a spec's checksum, the value its `.checked.json` records as `spec`, so the spec's reader never computes it by hand. |
@@ -422,7 +422,7 @@ Flags worth knowing:
 | --- | --- |
 | `check --all` | Scan the whole repo instead of just changed files. Use on a first run. |
 | `explain --list` | Every rule id and title. Add a section letter (`explain G --list`) for one section. |
-| `check --ci` | Mechanical bucket only — deterministic, and exits non-zero on any error. |
+| `check --ci` | Mechanical bucket only, so the run is deterministic. |
 | `check --json` | Machine-readable findings, for tooling or for reading every finding when the terminal output elides repeats. |
 | `init --yes` | Non-interactive; accept every derived default. |
 | `install --scope global` | Install once for every project. |
@@ -435,9 +435,12 @@ mean it could never move.
 
 ### As slash commands
 
-Every command is also a slash command in your agent, installed alongside the
-skill. `/jig check --all` does what `npx jig-ui check --all` does, and then acts
-on the result — the CLI reports, the agent applies the judgment half.
+Every command but `gate`, which only the Stop hook runs, is also a slash command
+in your agent, installed alongside the skill. `/jig check --all` does what
+`npx jig-ui check --all` does, and then acts on the result — the CLI reports, the
+agent applies the judgment half. Six slash commands are agent procedures with no
+command of their own in the CLI: `decide`, `spec`, `mockup`, `make`, `critique` and
+`tweak` (`critique` runs `verdicts` and `probe` along the way).
 
 | Slash command | Equivalent |
 | --- | --- |
@@ -642,7 +645,8 @@ metadata in the same change as the headline, and `check` holds the budgets.
 
 **Which pages are meant to be found is decided by mode, not by taste.**
 `editorial` is first-visit content, so it is indexable and needs its own title
-and description. `product` and `operator` are what somebody reaches after signing
+and description, and its own link preview (`og:title` and `og:description`) for
+the card a pasted link shows. `product` and `operator` are what somebody reaches after signing
 in, so they must carry `noindex` — an admin screen in a search result is an
 invitation, and a sign-in page in one invites credential stuffing. A spec
 overrides the default per page, with a reason: a CV shared by link, a
@@ -697,7 +701,7 @@ No agent required. `check` is a linter with a design system behind it.
 ```bash
 npx jig-ui@latest check --all      # everything
 npx jig-ui@latest check            # just what changed
-npx jig-ui@latest check --ci       # for CI: deterministic, non-zero on error
+npx jig-ui@latest check --ci       # for CI: mechanical rules only, deterministic
 npx jig-ui@latest check --json     # for tooling
 ```
 
@@ -793,7 +797,7 @@ treatment.
 
 | File | Contents |
 | --- | --- |
-| `rules/00-anti-patterns.md` | 128 universal rules with corrections |
+| `rules/00-anti-patterns.md` | 129 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 |