Release v0.20.0 · timessuman/jig

Critiques count owner rulings apart and say what the last round fixed; the gate
keeps decisions the owner's, and tweak works on its first real pages.

A ruled verdict. A finding the owner has already decided is judged
ruled, citing the decision's heading in ruling, and counted apart
(ruled=). On jig-site five of a header critique's 15 findings were the
owner's rulings, counted as findings and sent back to make.
What happened to the last round's findings. jig verdicts compares a
critique with the one before it in git and prints how many were fixed, are
still open, were ruled, and are new, with the ids. The report carries it.
jig verdicts --reprobe re-takes probes taken on an older page. The
gate and --reprobe now find the page from the probes themselves, so a spec
whose surface: is a sentence no longer leaves stale probes blocking.
The probe names text drawn in a weight or style no loaded face covers,
which the browser fakes from the nearest face. It is an error, like a page in
the default font. Probe version 8.
jig update names the tokens each refreshed mode file gained or lost,
and those an edited one did not get, since anything aliasing tokens (a
Tailwind @theme) needs the same change.

decide keeps the owner's reasons apart from its own. A Why: is the
owner's words in quotation marks or not given; anything the agent adds goes
under **Why (inferred):**. The gate checks each decision the session wrote
or changed.
make does not edit DECISIONS.md. The gate stops a make session that
changed it; decisions go through decide or tweak.
A spec that no longer matches its approved drawing is not approved. In
spec and make, each region the spec lists must be labelled in its size's
frame. Region names are read as the spec means them: a parenthetical
qualifies, "(… only)" is conditional, and a list names several regions.
Critique's reader arms do not read the page's history: no earlier
critiques, no git log. Which findings were fixed is the CLI's question.
P-14 says how a menu in a fixed header behaves: it lies over the page, a
tap outside closes it and does nothing else, controls in the header row work
on the first tap, and a long list scrolls inside itself.
M-01's script budget is "none by default", not an absolute zero: a
feature may have script, named in a comment and as small as it allows.

tweak's gate blocked both of its first real uses, on jig-site. Three
causes, all in the gate:
- It took the session's command from any line that mentioned /jig, so the
  command file Jig loads into the session, and tool results quoting it, read
  as /jig critique. Only what the user sent counts now.
- It looked for the critique under the spec's surface: field, which on
  jig-site is a sentence. A critique lives under the spec's file name, as
  the command file says.
- It held the page to its structure at the commit that first approved the
  mockup, before five confirmed, critiqued rounds. It now holds the page to
  its structure at its last critique.
The gate also works on the spec the command names (/jig tweak site-header),
not whichever spec was written last.
jig verdicts refuses reasons that judge nothing. On jig-site a render
arm stopped with 33 of 34 verdicts reading "DRAFT, being refined", and the
review passed with full counts. A placeholder reason is now an error, and so
is one reason given word for word by four or more ok or finding verdicts
in a file. n/a verdicts may still share a reason, since one absence can
clear many rules.

Navigation Menu