jig-ui 0.18.2 → 0.18.5

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # Changelog
 
+## 0.18.5 (2026-09-25)
+
+The gate holds an HTML mockup that does not draw the page at every size.
+
+### Fixed
+
+- **The gate holds a mockup that does not show every size.** On jig-site three
+  HTML mockups in a row were single responsive pages, so the owner saw only the
+  width of the window they opened and asked twice where the other sizes were.
+  The procedure's wireframe template draws the page once per size, side by
+  side, in `.frame[data-size]` boxes, and nothing checked a drawing used them.
+  When a `mockup` session stops with an HTML drawing, the gate now requires a
+  frame for phone (360), tablet (768), desktop (1280) and wide (1600).
+
+## 0.18.4 (2026-09-25)
+
+Every release summary is one or two lines, for jig-site's Versions page.
+
+### Changed
+
+- **Every release summary is one or two lines, with no em dash.** jig-site's
+  Versions page shows the summary under each release, so it is interface text.
+  Nine ran to three to thirteen lines; their detail now sits under
+  `### Upgrading` or `### Notes` in the same release. A test keeps summaries
+  short.
+
+## 0.18.3 (2026-09-25)
+
+Recording a decision no longer undoes the critiques written before it, and an
+older probe file says it is older rather than forged.
+
+### Fixed
+
+- **A decision recorded after a critique no longer undoes it.** On jig-site one
+  `/jig decide` session added eight decisions; every finished critique turned
+  "incomplete", and the gate stopped an unrelated spec session over records that
+  could not have judged them. `jig verdicts` now asks git: a decision whose
+  heading was added in a commit the critique's `decisions.json` commit does not
+  contain, or not committed yet, is left for the next critique and listed as
+  such. Without git, or while `decisions.json` has uncommitted changes (a
+  critique in progress), every decision is still required.
+- **An older probe file is called older, not forged.** After a release changed
+  the probe's version, the old files read "not output of `jig probe` … do not
+  write it by hand", and an agent stopped work believing they were fabricated.
+  They now say which version took them and to record them again.
+
 ## 0.18.2 (2026-09-25)
 
 Every release in this changelog now carries its date and a one-line summary,
@@ -52,9 +98,8 @@ menu, and `A-05` missed an arrow that renders as an emoji.
 
 ## 0.18.0 (2026-09-25)
 
-A page's frame gets tokens, a project gets a place to record where its layout
-switches, and keyboard access a rule requires fits every script budget. All of
-it found building jig-site's header and Reference with the full loop.
+A page's frame gets tokens, a project records where its layout switches, and
+keyboard access a rule requires fits every script budget.
 
 ### Added
 
@@ -161,8 +206,12 @@ The gate judges only the critiques a session touched.
 ## 0.17.0 (2026-09-24)
 
 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.
+picture for every rule.
+
+### Notes
+
+Also carries the probe and verdict fixes tagged as 0.16.2, which was not
+published to npm.
 
 ### Added
 
@@ -448,8 +497,8 @@ One new rule: no em dashes in interface text (`I-118`), with a detector.
 
 ## 0.11.1 (2026-09-18)
 
-Two holes in the gate, both found by running the loop twice on 0.11.0 —
-once on Haiku, once on Sonnet.
+Two holes in the gate, found by running the loop twice on 0.11.0: once on
+Haiku, once on Sonnet.
 
 ### Fixed
 
@@ -467,9 +516,8 @@ once on Haiku, once on Sonnet.
 
 ## 0.11.0 (2026-09-18)
 
-One release, one lesson: a measurement an agent can type is not a
-measurement. Everything here came from two live runs at the capability
-floor the day 0.10.0 shipped.
+A measurement an agent can type is not a measurement. Everything here came
+from two live runs at the capability floor.
 
 ### Added
 
@@ -496,9 +544,8 @@ floor the day 0.10.0 shipped.
 
 ## 0.10.0 (2026-09-18)
 
-Mobile-first, and a design loop that a weak model cannot skip. Everything here
-was measured on live runs at the capability floor (Haiku), and most of it exists
-because an instruction the agent could choose to ignore was ignored.
+Mobile-first, and a design loop that a weak model cannot skip, measured on live
+runs with Haiku.
 
 ### Added
 
@@ -562,9 +609,8 @@ because an instruction the agent could choose to ignore was ignored.
 
 ## 0.9.0 (2026-09-13)
 
-One new rule and one amended correction, both from the same afternoon of
-dogfooding and both about the same blind spot: H-47's correction always pointed
-at a token, so an agent reading it literally always produced one.
+One new rule and one amended correction, both about the same blind spot: H-47's
+correction always pointed an agent at a token.
 
 ### Added
 
@@ -607,12 +653,12 @@ at a token, so an agent reading it literally always produced one.
 
 ## 0.8.2 (2026-09-12)
 
-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.
+Four fixes found by following Jig's Tailwind guidance end to end on its own
+documentation site.
+
+### Notes
 
-Three of the four are the same shape — two places answering one question, and
+Three of the four are the same shape: two places answering one question, and
 disagreeing without either knowing the other existed.
 
 ### Fixed
@@ -686,10 +732,8 @@ disagreeing without either knowing the other existed.
 
 ## 0.8.1 (2026-09-12)
 
-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.
+Two fixes where 0.8.0 corrected one instance and left the class alone, both
+found by inspecting the published tarball.
 
 ### Fixed
 
@@ -746,9 +790,10 @@ by inspecting the published tarball rather than the working tree.
 
 ## 0.8.0 (2026-09-11)
 
-Everything here was found by handing Jig to agents that had never seen it and
-asking them to build something real — its own documentation site. None of it
-was found by the test suite, which passed throughout.
+Fixes found by agents new to Jig building its documentation site. The test
+suite passed throughout and caught none of them.
+
+### Notes
 
 Minor rather than patch: `explain` prints lines it did not print before, and
 `init` can write a file it did not write before.
@@ -884,6 +929,8 @@ Minor rather than patch: `explain` prints lines it did not print before, and
 
 A rule file that contradicted the tool, and the guard that kept it that way.
 
+### Notes
+
 Patch: the shipped rules change, but no command writes anything different.
 
 ### Fixed
@@ -936,7 +983,9 @@ already knew where the tokens were.
 
 ## 0.7.0 (2026-09-11)
 
-A silent no-op, fixed, plus the missing half of 0.6.0's token-layer move.
+A silent no-op, fixed, and the missing half of 0.6.0's token-layer move.
+
+### Notes
 
 Minor rather than patch, and the call is arguable. The non-TTY fix is a
 correction; the relocation offer is new behaviour that can move files, though
@@ -978,19 +1027,25 @@ to move their token layer should read these notes.
 
 ## 0.6.0 (2026-09-11)
 
-The token layer stops hiding in a dotfolder, and `check` starts reading it back.
+The token layer leaves its dotfolder, and `check` reads the layer's own
+declarations back.
 
-Both came from the same question: who should write the tokens. The answer turned
-out to depend on something that did not exist — **nothing validated the token
-layer's own declarations.** `init` checked a brand colour once, at write time,
-and no command ever looked again. A generated file edited afterwards, by a person
-or an agent, went unexamined: `--color-text-weak` dropped to 22% opacity and
-`check` reported "No findings". With that closed, where the files live and who
-writes them become ordinary decisions rather than load-bearing ones.
+### Upgrading
 
-**Upgrading:** run `npx jig-ui@latest update`, then `npx jig-ui@latest init`.
-Existing installs keep their `.jig/tokens/` layout — nothing moves unless you
-move it, because relocating files could break an import you wrote yourself.
+Run `npx jig-ui@latest update`, then `npx jig-ui@latest init`. Existing installs
+keep their `.jig/tokens/` layout. Nothing moves unless you move it, because
+relocating files could break an import you wrote yourself.
+
+### Notes
+
+Both changes came from the same question: who should write the tokens. The
+answer turned out to depend on something that did not exist: **nothing
+validated the token layer's own declarations.** `init` checked a brand colour
+once, at write time, and no command ever looked again. A generated file edited
+afterwards, by a person or an agent, went unexamined: `--color-text-weak`
+dropped to 22% opacity and `check` reported "No findings". With that closed,
+where the files live and who writes them become ordinary decisions rather than
+load-bearing ones.
 
 ### Added
 
@@ -1072,18 +1127,24 @@ move it, because relocating files could break an import you wrote yourself.
 
 ## 0.5.0 (2026-09-10)
 
-Four things shipped in 0.4.0 were broken in ways that reported success. `/jig
-update` refreshed to the version already installed and said "Updated Jig →
-0.4.0". Dark mode could not be reached by choosing it. `check` skipped nearly
-every colour in a project that had not run `init`. And the reconciliation of
-every numeric default against an external reference is finished — 0 rows open —
-which is where most of the rest of this release came from.
+Four things 0.4.0 reported as working did not, and the reconciliation of every
+numeric default against an external reference is finished.
+
+### Upgrading
 
 **If you are on 0.4.0, run `npx jig-ui@latest update` from a terminal.** The
 `/jig update` fix cannot deliver itself: your command file is the broken one, so
 the slash command will keep reporting a successful no-op until the CLI replaces
 it. Once, from the terminal, and the slash command works from then on.
 
+### Notes
+
+The four: `/jig update` refreshed to the version already installed and said
+"Updated Jig → 0.4.0". Dark mode could not be reached by choosing it. `check`
+skipped nearly every colour in a project that had not run `init`. And the
+reconciliation ended with 0 rows open, which is where most of the rest of this
+release came from.
+
 ### Fixed
 
 - **`/jig update` could never upgrade anyone.** Every subcommand is invoked at
@@ -1166,11 +1227,14 @@ them, and nothing at all checked that a token cited in the rules exists.
 
 ## 0.4.0 (2026-09-04)
 
-Jig stops copying itself into your project. It is a skill an agent reads, and
-0.3.0 wrote 220KB across 17 files into every consuming repo to deliver it —
-roughly 200KB of that Jig's own property, read by an agent that already had it
-from the skill install. A single-mode project now gets **three** files, all of
-them its own.
+Jig stops copying itself into your project. A single-mode project now gets
+**three** files, all of them its own.
+
+### Notes
+
+Jig is a skill an agent reads, and 0.3.0 wrote 220KB across 17 files into every
+consuming repo to deliver it. Roughly 200KB of that was Jig's own, read by an
+agent that already had it from the skill install.
 
 ### Changed
 

package/dist/index.js

@@ -5673,8 +5673,9 @@ Could not write to ${wireTarget}: ${err.message}`);
 }
 
 // src/commands/verdicts.ts
+import { execFileSync as execFileSync3 } from "child_process";
 import { existsSync as existsSync23, readFileSync as readFileSync30 } from "fs";
-import { join as join37, resolve as resolve5 } from "path";
+import { join as join37, relative as relative4, resolve as resolve5 } from "path";
 
 // src/rules/citations.ts
 import { join as join29 } from "path";
@@ -6258,6 +6259,10 @@ function readProbes(projectRoot, dir, errors) {
   for (const f of readdirSync13(dir).filter((n) => /^probe-\d+\.json$/.test(n)).sort()) {
     try {
       const p = JSON.parse(readFileSync27(join34(dir, f), "utf8"));
+      if (typeof p.jigProbe === "number" && p.jigProbe < PROBE_VERSION && typeof p.width === "number") {
+        errors.push(`${f} was taken by an older \`jig probe\` (version ${p.jigProbe}; this Jig reads version ${PROBE_VERSION}). Record it again with \`jig probe --run\`.`);
+        continue;
+      }
       if (p.jigProbe !== PROBE_VERSION || typeof p.width !== "number") {
         errors.push(`${f} is not output of \`jig probe\` (version ${PROBE_VERSION}). Re-run the probe; do not write it by hand.`);
         continue;
@@ -6366,21 +6371,24 @@ function decisionsFile(projectRoot) {
   return void 0;
 }
 function decisionNames(projectRoot) {
+  return [...decisionHeadings(projectRoot).keys()];
+}
+function decisionHeadings(projectRoot) {
+  const headings = /* @__PURE__ */ new Map();
   const path = decisionsFile(projectRoot);
-  if (!path) return [];
+  if (!path) return headings;
   let body;
   try {
     body = readFileSync28(join35(projectRoot, path), "utf8");
   } catch {
-    return [];
+    return headings;
   }
-  const names = [];
   for (const match of body.matchAll(HEADING3)) {
     const name = match[2].replace(/[`*]/g, "").trim();
     if (!name || NOT_A_DECISION.test(name)) continue;
-    if (!names.includes(name)) names.push(name);
+    if (!headings.has(name)) headings.set(name, match[0].trim());
   }
-  return names;
+  return headings;
 }
 
 // src/check/spec-shape.ts
@@ -6583,11 +6591,41 @@ function checkDecisions(projectRoot, dir, errors) {
     else if (ABSENCE.test(reason)) errors.push(`decisions.json: "${match}" \u2014 "${reason}" says the decision was not read.`);
     if (v.verdict === "finding") findings++;
   }
-  const missing = required.filter((r) => !seen.has(r));
+  const unjudged = required.filter((r) => !seen.has(r));
+  const since = decisionsSince(projectRoot, dir, unjudged);
+  const missing = unjudged.filter((r) => !since.includes(r));
+  const total = required.length - since.length;
   if (missing.length) {
-    errors.push(`decisions.json: ${missing.length} of ${required.length} decisions have no verdict: ${missing.join(", ")}.`);
+    errors.push(`decisions.json: ${missing.length} of ${total} decisions have no verdict: ${missing.join(", ")}.`);
+  }
+  return { state: missing.length ? "incomplete" : "ran", judged: total - missing.length, total, findings, ...since.length ? { since } : {} };
+}
+function decisionsSince(projectRoot, dir, unjudged) {
+  if (unjudged.length === 0) return [];
+  const path = decisionsFile(projectRoot);
+  if (!path) return [];
+  const git = (args) => execFileSync3("git", args, { cwd: projectRoot, encoding: "utf8", stdio: ["ignore", "pipe", "ignore"] }).trim();
+  try {
+    const verdictFile = relative4(projectRoot, join37(dir, "decisions.json"));
+    if (git(["status", "--porcelain", "--", verdictFile])) return [];
+    const judgedIn = git(["log", "-1", "--format=%H", "--", verdictFile]);
+    if (!judgedIn) return [];
+    const headings = decisionHeadings(projectRoot);
+    return unjudged.filter((name) => {
+      const line = headings.get(name);
+      if (!line) return false;
+      const addedIn = git(["log", "--format=%H", "-S", line, "--", path]).split("\n").filter(Boolean).pop();
+      if (!addedIn) return true;
+      try {
+        git(["merge-base", "--is-ancestor", addedIn, judgedIn]);
+        return false;
+      } catch {
+        return true;
+      }
+    });
+  } catch {
+    return [];
   }
-  return { state: missing.length ? "incomplete" : "ran", judged: required.length - missing.length, total: required.length, findings };
 }
 function verifyVerdicts(opts) {
   const root = opts.packageRoot ?? assetRoot();
@@ -6760,6 +6798,7 @@ function commandProblems(root, command) {
       else if (!/^https?:/i.test(at) && !existsSync24(join38(root, at))) problems.push(`${spec.path}: \`mockup_at: ${at}\` does not exist.`);
       else if (!/^https?:/i.test(at) && !at.startsWith(".jig/mockups/")) problems.push(`The drawing is at ${at}. A mockup lives in .jig/mockups/, outside what check scans and outside what ships.`);
     }
+    if (at && /\.html?$/i.test(at) && existsSync24(join38(root, at))) problems.push(...mockupFrameProblems(root, at));
   }
   if (command === "critique") {
     const dir = join38(root, ".jig", "critique");
@@ -6867,6 +6906,20 @@ ${problems.join("\n\n")}`
 ${problems.join("\n\n")}`
   };
 }
+var MOCKUP_FRAMES = [["phone", 360], ["tablet", 768], ["desktop", 1280], ["wide", 1600]];
+function mockupFrameProblems(root, at) {
+  let html;
+  try {
+    html = readFileSync31(join38(root, at), "utf8");
+  } catch {
+    return [];
+  }
+  const missing = MOCKUP_FRAMES.filter(([size]) => !new RegExp(`data-size\\s*=\\s*["']${size}["']`).test(html));
+  if (missing.length === 0) return [];
+  return [
+    `${at} has no frame for ${missing.map(([size, px2]) => `${size} (${px2}px)`).join(", ")}. A mockup draws the page once per size, side by side, in the wireframe template's \`<div class="frame" data-size="\u2026">\` boxes, so the owner sees every size at once. A single responsive page shows only the width of the window it is opened in.`
+  ];
+}
 var VERDICT_FILES = ["screen.json", "code.json", "decisions.json"];
 var LOCK = "verdicts.lock";
 function verdictChecksum(dir) {
@@ -7120,6 +7173,8 @@ program.command("verdicts").description("Verify a critique's verdict files and c
     const result = verifyVerdicts({ projectRoot, surface });
     for (const error of result.errors) console.error(`  \u2717 ${error}`);
     if (result.ok) console.log(`  Every rule in both passes has a verdict.`);
+    const since = result.decisions.since ?? [];
+    if (since.length) console.log(`  ${since.length} decision(s) recorded after this critique, for the next one to judge: ${since.join(", ")}.`);
     console.log(`  ${result.line}`);
     process.exit(result.ok ? 0 : 1);
   } catch (err) {

package/package.json

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