jig-ui 0.18.0 → 0.18.2

package/CHANGELOG.md

@@ -1,6 +1,56 @@
 # Changelog
 
-## 0.18.0
+## 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.
+
+### Changed
+
+- **Every release heading carries its date**, as `## 0.18.1 (2026-09-25)`,
+  backfilled from the tags. The npm package has no git history, so the
+  CHANGELOG is where a release's date travels with it; jig-site's Versions page
+  lists each release by date. A test keeps every released heading dated.
+- **Every release opens with a one-line summary.** Five had none (0.17.1,
+  0.16.1, 0.15.1, 0.12.0, 0.2.1) and now do, written from their own entries.
+  The Versions page shows the line under each release; a test keeps it there.
+
+## 0.18.1 (2026-09-25)
+
+Two fixes found by jig-site's fourth round: the probe misread a `<details>`
+menu, and `A-05` missed an arrow that renders as an emoji.
+
+### Fixed
+
+- **The probe reads a `<details>` menu the way the browser shows it.** On
+  jig-site's Reference it reported a working phone menu as broken, and
+  `jig verdicts` refused a correct `P-14` verdict on the strength of it. Four
+  defects, each now covered by a browser test:
+  - Where the banner's menu is hidden at a width, the probe took the next
+    disclosure in some other `<nav>` (a docs rail's section tree) as the menu,
+    and reported "a menu button beside links that already show". A menu the
+    page names, or one in its banner, is now the only candidate once it exists.
+  - A closed `<details>` hides its content with `content-visibility` in
+    Chromium, which still gives its links boxes, so the closed menu's links
+    counted as showing and opening it "showed no more links". Visibility now
+    also asks `checkVisibility()`.
+  - A label swapped with CSS ("Menu" to "Close") keeps both words in
+    `textContent`; the label is now read from the rendered text.
+  - A native `<summary>` has no `aria-expanded` attribute; its expanded state
+    is its `<details>`'s `open`, which is what assistive technology is given.
+
+  Probe files are now version 6, so earlier ones are re-recorded.
+
+- **`A-05` catches an arrow that turns into an emoji.** ↔ ↕ ↖ ↗ ↘ ↙ ↩ ↪ ▶ ◀
+  are text by default but have an emoji form, and the detector skipped the
+  whole arrow block so prose arrows would not fire. jig-site marked its
+  external links with `<span aria-hidden="true">↗</span>`, which some platforms
+  draw as a colour emoji, and `check --all` and three critiques passed it. One
+  of these characters now fires when it stands alone as an icon (the whole
+  content of an element, or a pseudo-element's `content`) without U+FE0E. The
+  same arrow in a sentence still does not.
+
+## 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
@@ -36,7 +86,7 @@ it found building jig-site's header and Reference with the full loop.
   one pixel before and at each `--breakpoint-*` the project declares, and the
   gate's refresh keeps those probes current too.
 
-## 0.17.3
+## 0.17.3 (2026-09-25)
 
 Three defects found building jig-site's header with the full loop.
 
@@ -65,7 +115,7 @@ Three defects found building jig-site's header with the full loop.
   said so; only `jig init --yes` refreshed them. `update` now refreshes each
   untouched copy wherever `init` recorded writing it.
 
-## 0.17.2
+## 0.17.2 (2026-09-24)
 
 Four defects found by building one page with the full loop.
 
@@ -93,7 +143,9 @@ Four defects found by building one page with the full loop.
   stated as measured, the two outliers are trimmed, and a test renders all 286
   figures in Chrome and fails any wider or taller.
 
-## 0.17.1
+## 0.17.1 (2026-09-24)
+
+The gate judges only the critiques a session touched.
 
 ### Fixed
 
@@ -106,7 +158,7 @@ Four defects found by building one page with the full loop.
   starts with `_` is set aside and never judged. With no transcript, as when
   the gate is run by hand, it checks every critique as before.
 
-## 0.17.0
+## 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,
@@ -153,7 +205,10 @@ which was not published to npm.
   any count, `I-81` the page's headline, and `I-89` button labels as well as
   links.
 
-## 0.16.1
+## 0.16.1 (2026-09-19)
+
+Jig's own headings drop the em dash, a quotation keeps its own punctuation,
+and a spec's `indexable:` is `true` or `false`.
 
 ### Fixed
 
@@ -171,7 +226,7 @@ which was not published to npm.
   reported as contradicting J-123. Anything else is now a spec-shape problem,
   and an error in `verdicts` that names the field.
 
-## 0.16.0
+## 0.16.0 (2026-09-19)
 
 With more than one mode, every barrel names its mode, and none sits in the
 global stylesheet.
@@ -191,7 +246,9 @@ global stylesheet.
   An edited one is left, with a note on where its edits belong. `check` names a
   `theme.css` left beside two modes.
 
-## 0.15.1
+## 0.15.1 (2026-09-19)
+
+The gate hears a question anywhere in the message, not only on its last line.
 
 ### Fixed
 
@@ -202,7 +259,7 @@ global stylesheet.
   live `/jig decide` three times. Any sentence ending in `?` now counts; a `?`
   in a URL or a code span does not.
 
-## 0.15.0
+## 0.15.0 (2026-09-19)
 
 The gate holds an agent on warnings, waits while it asks the owner a question,
 and reaches projects where the skill is installed globally.
@@ -244,7 +301,7 @@ and reaches projects where the skill is installed globally.
 - **`jig seo` says an endpoint is not a page**, so `pages=` can be checked
   against a site's route files.
 
-## 0.14.1
+## 0.14.1 (2026-09-19)
 
 `jig seo` cites only what a rule says.
 
@@ -269,7 +326,7 @@ and reaches projects where the skill is installed globally.
   as `/pages/admin`, so a `noindex` Astro or Next page listed in the sitemap
   went unreported.
 
-## 0.14.0
+## 0.14.0 (2026-09-18)
 
 What a stranger meets before the page, what the page must not hand them, and a
 project that states its own direction.
@@ -332,7 +389,7 @@ project that states its own direction.
   already have. Redesigning an existing page is its own path, and `spec` asks
   different questions when the page exists.
 
-## 0.13.0
+## 0.13.0 (2026-09-18)
 
 Meaning before presentation, and one fewer step anyone can skip.
 
@@ -374,7 +431,9 @@ Meaning before presentation, and one fewer step anyone can skip.
   `.github`.** Jig's own vendored rules are not the project's interface.
 - **Probe files are version 3.** Older ones no longer validate.
 
-## 0.12.0
+## 0.12.0 (2026-09-18)
+
+One new rule: no em dashes in interface text (`I-118`), with a detector.
 
 ### Added
 
@@ -387,7 +446,7 @@ Meaning before presentation, and one fewer step anyone can skip.
   styles, comments, class names and documentation are not interface text.
   The en dash keeps its one job, a range read as "to" (`2-10 seats`).
 
-## 0.11.1
+## 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.
@@ -406,7 +465,7 @@ once on Haiku, once on Sonnet.
   at a width where the links fit. A false positive is how a gate gets
   ignored.
 
-## 0.11.0
+## 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
@@ -435,7 +494,7 @@ floor the day 0.10.0 shipped.
   critique verdicts. Both are warned about separately, each with what
   ignoring it costs. Since 0.7.0 both had said `.jig/` holds the tokens.
 
-## 0.10.0
+## 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
@@ -501,7 +560,7 @@ because an instruction the agent could choose to ignore was ignored.
 - **`init --yes` says what it did not decide** — no surface mapping, and
   re-running `init` after you declare one.
 
-## 0.9.0
+## 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
@@ -546,7 +605,7 @@ at a token, so an agent reading it literally always produced one.
   it.
 
 
-## 0.8.2
+## 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
@@ -625,7 +684,7 @@ disagreeing without either knowing the other existed.
   guard built on it. Caught by its own canary the moment an option wrapped.
 
 
-## 0.8.1
+## 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
@@ -685,7 +744,7 @@ by inspecting the published tarball rather than the working tree.
   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
+## 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
@@ -821,7 +880,7 @@ Minor rather than patch: `explain` prints lines it did not print before, and
   whether the guard should consult the config first, which is a behaviour
   question rather than a copy one.
 
-## 0.7.1
+## 0.7.1 (2026-09-11)
 
 A rule file that contradicted the tool, and the guard that kept it that way.
 
@@ -875,7 +934,7 @@ to agents that had never seen this repository and asking them to build
 something real. Everyone who could have caught the token-location defect
 already knew where the tokens were.
 
-## 0.7.0
+## 0.7.0 (2026-09-11)
 
 A silent no-op, fixed, plus the missing half of 0.6.0's token-layer move.
 
@@ -917,7 +976,7 @@ to move their token layer should read these notes.
   AFTER   @import "./jig/theme.css";
   ```
 
-## 0.6.0
+## 0.6.0 (2026-09-11)
 
 The token layer stops hiding in a dotfolder, and `check` starts reading it back.
 
@@ -1011,7 +1070,7 @@ move it, because relocating files could break an import you wrote yourself.
   directive it needs. Nothing errors when this bites: the class lands on the
   element, no rule exists to match it, and the style simply does not apply.
 
-## 0.5.0
+## 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 →
@@ -1105,7 +1164,7 @@ ones exist because a guard had been passing vacuously: rule 6's regex was
 line-anchored and so covered 103 of 133 tokens while claiming to cover all of
 them, and nothing at all checked that a token cited in the rules exists.
 
-## 0.4.0
+## 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 —
@@ -1312,7 +1371,7 @@ for you, because you may have edited one and that edit is yours to keep. Run
 `jig install --agent <name>` to place the new bundle, then delete `.jig/rules/`
 and `.jig/rules.index.json` once you have checked them for your own changes.
 
-## 0.3.0
+## 0.3.0 (2026-09-03)
 
 Two new commands. `install` and `update` put the system in place; these two make
 it do something.
@@ -1364,7 +1423,10 @@ it do something.
   not apply to it.
 
 
-## 0.2.1
+## 0.2.1 (2026-09-01)
+
+Two shipped colours failed Jig's own contrast floors. They are darker now,
+and the build does the contrast arithmetic.
 
 ### Fixed
 
@@ -1398,7 +1460,7 @@ it do something.
   no build, not published. It found two gaps on its first run: there is no
   border-width token and no focus-ring geometry tokens.
 
-## 0.2.0
+## 0.2.0 (2026-09-01)
 
 The first release that actually works end to end. `0.1.0` shipped rules that
 cited tokens it never installed, and a token name that did not exist.

package/dist/index.js

@@ -2265,6 +2265,11 @@ function maskProseComments(raw) {
 // src/check/detectors/emoji-icon.ts
 var EMOJI_RE = /[\u{1F300}-\u{1FAFF}\u{1F000}-\u{1F2FF}\u{2600}-\u{27BF}\u{2B00}-\u{2BFF}\u{FE0F}]/gu;
 var TEXTUAL = /* @__PURE__ */ new Set(["\u2192", "\u2190", "\u2191", "\u2193", "\u2194", "\u21D2", "\u21D0", "\u2122", "\u2713", "\u2717", "\u2212", "\u2217", "\u2318", "\u2325", "\u23CE"]);
+var EMOJI_CAPABLE = "\\u2194-\\u2199\\u21A9\\u21AA\\u25B6\\u25C0";
+var LONE_GLYPH = new RegExp(
+  `>\\s*([${EMOJI_CAPABLE}])(?!\\uFE0E)\\s*<|content\\s*:\\s*["']([${EMOJI_CAPABLE}])(?!\\uFE0E)["']`,
+  "gu"
+);
 var emojiIcon = {
   name: "emoji-icon",
   appliesTo: (file) => isStyleBearing(file),
@@ -2289,6 +2294,22 @@ var emojiIcon = {
         )
       );
     }
+    for (const m of masked.matchAll(LONE_GLYPH)) {
+      const glyph = m[1] ?? m[2];
+      const line = masked.slice(0, m.index + m[0].indexOf(glyph)).split("\n").length;
+      if (seen.has(line)) continue;
+      seen.add(line);
+      findings.push(
+        mkFinding(
+          ctx,
+          "emoji-icon",
+          file,
+          line,
+          `A character with an emoji form used as an icon (${glyph}). Standing alone, it renders as a colour emoji on some platforms. Use an icon set, or words.`,
+          lines[line - 1] ?? ""
+        )
+      );
+    }
     return findings;
   }
 };
@@ -5676,10 +5697,13 @@ import { fileURLToPath as fileURLToPath2 } from "url";
 import { join as join33, relative as relative3, resolve as resolve4, sep as sep5 } from "path";
 
 // src/probe/script.ts
-var PROBE_VERSION = 5;
+var PROBE_VERSION = 6;
 var PROBE_SCRIPT = `(async () => {
   const doc = document.documentElement;
-  const vis = (e) => { const r = e.getBoundingClientRect(); const s = getComputedStyle(e); return r.width > 0 && r.height > 0 && s.visibility !== 'hidden' && s.display !== 'none'; };
+  // checkVisibility also sees content a closed <details> hides: Chromium hides
+  // it with content-visibility, which still gives its links real boxes, so a
+  // closed menu counted as open and an opened one showed "no more links".
+  const vis = (e) => { const r = e.getBoundingClientRect(); const s = getComputedStyle(e); return r.width > 0 && r.height > 0 && s.visibility !== 'hidden' && s.display !== 'none' && (!e.checkVisibility || e.checkVisibility()); };
   const probe = document.createElement('div');
   probe.style.all = 'initial';
   document.body.appendChild(probe);
@@ -5772,19 +5796,32 @@ var PROBE_SCRIPT = `(async () => {
   const inChrome = (b) => !!b.closest('header, [role=banner]') ||
     (!!b.closest('nav, [role=navigation]') && !b.closest('main, article, aside, [role=main]'));
   const named = (b) => /\b(menu|navigation)\b/i.test((b.getAttribute('aria-label') || '') + ' ' + b.textContent);
-  const toggle = [...document.querySelectorAll('button, summary, [role=button]')].find((b) => vis(b) &&
-    (named(b) || (inChrome(b) && (b.tagName === 'SUMMARY' || b.hasAttribute('aria-expanded') || b.hasAttribute('aria-controls')))));
+  const candidates = [...document.querySelectorAll('button, summary, [role=button]')].filter((b) =>
+    named(b) || (inChrome(b) && (b.tagName === 'SUMMARY' || b.hasAttribute('aria-expanded') || b.hasAttribute('aria-controls'))));
+  // A menu the page names, or one in its banner, is the menu. Where it exists
+  // but is hidden at this width, the links show instead and there is no menu
+  // here; the next disclosure in some other <nav> (a docs rail's tree) is not
+  // a stand-in for it.
+  const primary = (b) => named(b) || !!b.closest('header, [role=banner]');
+  const pool = candidates.some(primary) ? candidates.filter(primary) : candidates;
+  const toggle = pool.find(vis);
   let menu = null;
   if (toggle) {
-    const name = () => ((toggle.getAttribute('aria-label') || '') + ' ' + (toggle.textContent || '')).replace(/\\s+/g, ' ').trim();
+    // The label as rendered: a menu that swaps "Menu" for "Close" with CSS keeps
+    // both words in its textContent at all times, so only innerText sees the swap.
+    const name = () => ((toggle.getAttribute('aria-label') || '') + ' ' + (toggle.innerText || toggle.textContent || '')).replace(/\\s+/g, ' ').trim();
+    // A native <summary> carries no aria-expanded attribute; the browser exposes
+    // its <details>'s open state as the expanded state, which is what counts.
+    const expanded = () => toggle.getAttribute('aria-expanded') ??
+      (toggle.tagName === 'SUMMARY' && toggle.parentElement && toggle.parentElement.tagName === 'DETAILS' ? String(toggle.parentElement.open) : null);
     // Opening is judged by what becomes visible anywhere: a menu panel is often
     // a sibling of the header, not inside it (arm test 3, tw-1).
     const allLinks = () => [...document.querySelectorAll('a')].filter(vis).length;
     const controlled = () => { const id = toggle.getAttribute('aria-controls'); const el = id && document.getElementById(id); return el ? vis(el) : null; };
-    const before = { links: allLinks(), controlled: controlled(), expanded: toggle.getAttribute('aria-expanded'), name: name(), html: toggle.innerHTML };
+    const before = { links: allLinks(), controlled: controlled(), expanded: expanded(), name: name(), html: toggle.innerHTML };
     toggle.click();
     await new Promise((r) => setTimeout(r, 350));
-    const after = { links: allLinks(), controlled: controlled(), expanded: toggle.getAttribute('aria-expanded'), name: name(), htmlChanged: toggle.innerHTML !== before.html };
+    const after = { links: allLinks(), controlled: controlled(), expanded: expanded(), name: name(), htmlChanged: toggle.innerHTML !== before.html };
     toggle.focus();
     toggle.dispatchEvent(new KeyboardEvent('keydown', { key: 'Escape', bubbles: true }));
     document.dispatchEvent(new KeyboardEvent('keydown', { key: 'Escape', bubbles: true }));
@@ -5794,7 +5831,7 @@ var PROBE_SCRIPT = `(async () => {
       expandedBefore: before.expanded, expandedAfter: after.expanded,
       opened: after.links > before.links || (before.controlled === false && after.controlled === true),
       labelChanged: after.name !== before.name || after.htmlChanged,
-      escapeCloses: toggle.getAttribute('aria-expanded') !== 'true' && allLinks() <= before.links,
+      escapeCloses: expanded() !== 'true' && allLinks() <= before.links,
       focusReturned: document.activeElement === toggle,
     };
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jig-ui",
-  "version": "0.18.0",
+  "version": "0.18.2",
   "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",