jig-ui 0.14.0 → 0.15.0

package/package.json

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

package/rules/00-anti-patterns.md

@@ -608,9 +608,9 @@ The budget is not a style preference; it is the width of the box someone else re
 `robots.txt` is not this. It is public, advisory, and read by strangers as a list of interesting places: naming `/admin` there tells everyone where it is. A path is safe to name only when something else protects it — a session guard, an authenticating API — and never because the file asked politely.
 
 ### J-124 A sitemap that contradicts the page
-❌ A route listed in the sitemap whose own metadata says `noindex`; a sitemap entry for a page that does not exist
-✅ One answer per route. The sitemap lists what is indexable, and nothing else.
-Contradicting yourself in two files tells a crawler you do not know which is true, and it will decide for you.
+❌ A route listed in the sitemap whose own metadata says `noindex`; a sitemap entry for a page that does not exist; a `<loc>` written as a path, `/pricing`, which the format does not accept and a crawler drops
+✅ One answer per route. The sitemap lists what is indexable, as full URLs, and nothing else.
+Contradicting yourself in two files tells a crawler you do not know which is true, and it will decide for you. A sitemap needs the site's origin, so a project that has none yet has nothing to write: no sitemap is honest, and one full of paths is not.
 
 ### J-125 Invented facts in metadata
 ❌ `lastModified: new Date()` in a sitemap; a `datePublished` filled in because the field existed; an author, rating or price nobody supplied

package/templates/COMMAND.md.tmpl

@@ -759,8 +759,9 @@ menu and reported "matched exactly".
 **1. `check` passes.** Run `{{scripts_path}} check --all` and paste its
 `JIG_CHECK:` line into your report, as printed. `mechanical=fail:<n>` means not done:
 fix every error and run it again. No mechanical finding is non-blocking, and you do
-not get to decide one is. Warnings are listed and either fixed or explained one by
-one. A report with no `JIG_CHECK:` line, or one you typed yourself, is not a finished
+not get to decide one is. Every warning is fixed, or waived on its own line with
+`jig-allow <ID>: <why>` (see `gate`); an explanation in your report is not a waiver.
+A report with no `JIG_CHECK:` line, or one you typed yourself, is not a finished
 build.
 
 **2. The build matches the approved mockup at each size.** Skip only when
@@ -1160,8 +1161,12 @@ Run `{{scripts_path}} seo` and report what it says. It needs no `DECISIONS.md`,
 no spec and no confirmation: it reads what the project already serves, so it is
 safe to run on the first day and on somebody else's codebase. It audits the whole project,
 which is what one file cannot: a route whose metadata says `noindex` sitting in
-the sitemap, two pages claiming the same title, indexable pages with no sitemap,
-a sitemap that lists nothing.
+the sitemap, two pages claiming the same title, a sitemap that lists nothing or
+lists paths instead of full URLs. It counts the pages it found, a dynamic route
+once and an endpoint (`rss.xml.ts`, `[id].txt.ts`, `api/`) not at all, since it
+serves no page. It also counts whether a sitemap and a robots file exist;
+neither is a finding, since no rule asks for them and a project with no domain
+yet cannot write an honest sitemap. Do not invent one to clear a count.
 
 It is not a phase. The per-page half belongs where the copy is decided and
 written — `spec` records whether a page is indexable and what it claims, `make`
@@ -1173,10 +1178,18 @@ positioning it had already dropped.
 ## gate
 
 Not a command to run. In Claude Code, `install` adds a Stop hook that runs
-`{{scripts_path}} gate` whenever you try to finish. If files you changed fail `check`,
-or a critique's verdict files fail `verdicts`, it refuses to let you stop and hands
-you the failures as the reason. **Fix what it names.** Do not edit verdict files to
-satisfy it, and do not report the work as done while it is blocking. After three
+`{{scripts_path}} gate` whenever you try to finish. If files you changed have a
+`check` error or warning, or a critique's verdict files fail `verdicts`, it refuses
+to let you stop and hands you the failures as the reason. **Fix what it names.** Do
+not edit verdict files to satisfy it, and do not report the work as done while it is
+blocking.
+
+A warning you are sure is right as it stands, because the detector guessed and the
+guess is wrong here, is waived on its own line or the line above, in the file's
+comment syntax: `jig-allow <ID>: <why>`. The reason is what the user reads, so write
+the case, not "intended". An error cannot be waived, a waiver with no reason waives
+nothing, and `check` prints every waiver it honoured. Waiving a warning to get past
+the gate, when the fix was available, is the failure the gate exists to catch. After three
 refusals in one session it lets you stop; then tell the user plainly that the work is
 not finished and what is still failing.
 

package/templates/SKILL.md.tmpl

@@ -14,18 +14,21 @@ cite the number when you follow or deliberately break one.
    b. `DECISIONS.md` exists beside the token files — `jig/DECISIONS.md` by
       default, or wherever `brand` in `{{config_file}}` puts them — and has
       substance: not empty, no `[TODO]` markers left in it, more than a few
-      lines. If it does not, run `{{command_prefix}}decide` and stop until it has
-      been written. Do not write it yourself from this task's prompt — it records
-      decisions the project has made, and a file you author alone records
-      decisions *you* have made, which is the opposite thing wearing the same
-      name.
+      lines. If it does not, stop and ask the user to run
+      `{{command_prefix}}decide`. The interview lives in that command, not in
+      this file: questions you make up from here are not `decide`, and neither
+      is a file written from their answers. Do not write it yourself from this
+      task's prompt — it records decisions the project has made, and a file you
+      author alone records decisions *you* have made, which is the opposite
+      thing wearing the same name.
 1. Load `{{rules_path}}/00-anti-patterns.md` and `{{rules_path}}/01-modes.md`.
 2. Determine the mode from `{{config_file}}`, or infer it using the procedure in
    `{{rules_path}}/01-modes.md` and state the inference in one line before building.
-3. **Building a page, feature or functionality?** Run it through
+3. **Building a page, feature or functionality?** It goes through
    `{{command_prefix}}spec` → `{{command_prefix}}mockup` (low fidelity) →
    `{{command_prefix}}make` (high fidelity) → `{{command_prefix}}critique`, one at a
-   time. Never design the whole product up front. Critique findings go back to
+   time, each one run by the user. The procedure for each step is in the command,
+   so ask for the step you need rather than doing it from this summary. Never design the whole product up front. Critique findings go back to
    `make`, then `critique` again, until clean or accepted by the user — then the
    next feature.
    **Building a screen rather than a single component?** Read `L-01 · Layout

package/templates/command-metadata.json

@@ -25,7 +25,7 @@
     "status": "available"
   },
   "seo": {
-    "description": "Audit what a search engine and a link preview read, across the whole project: a noindex route in the sitemap, two pages with one title, indexable pages with no sitemap, a sitemap that lists nothing. The per-page half lives in spec, make and check.",
+    "description": "Audit what a search engine and a link preview read, across the whole project: a noindex route in the sitemap, two pages with one title, a sitemap that lists nothing or lists paths instead of URLs. The per-page half lives in spec, make and check.",
     "argumentHint": "[--json]",
     "status": "available"
   },