super-ux 0.54.0 → 0.55.1

package/CHANGELOG.md

@@ -1,3 +1,52 @@
+## 0.55.1 — the opt-out the router promises now lives in the bodies that honor it
+
+Family audit 2026-09-06, wave AUDIT-WAVE-0906. **The operator's routing block
+promises a spoken refusal for each chain — "no scenarios" / «без сценариев» for
+the UX chain, "no brand" / «без бренда» (plus "draft it" / «черновиком» for
+copywriting) for the copy chain — and no skill text in this pack carried any of
+them.** With the routing block installed the promise held one layer up; a
+standalone install advertised no opt-out at all, so an operator who wanted the
+route skipped had no phrase the skill had agreed to hear.
+
+One sentence in each of the seven bodies now states it: the operator declines
+the route by saying the phrase, and the skill proceeds without the chain while
+saying so — never silently. Measured before and after with the house auditor:
+every body stays inside its working limit, the tightest being `ux-audit`
+~4626/4750 and `ux-flows` ~4529/4750 tokens.
+
+**No `description:` changed, by decision rather than accident.** Descriptions
+pair with the umbrella's trigger table, and a dropped advertised phrase refuses
+the family pin. `ux-flows`'s description stands at 965/1024 — 965 of the 970
+working limit — and is recorded here untouched for exactly that reason:
+`git diff -U0` over the skills shows zero changed `description:` lines.
+
+`repo validator checks` re-measured at 4623 by running the command
+`docs/brand/facts.md` names — the count did not move with this change, and
+that is a measurement, not a restatement.
+
+## 0.55.0 — the ledger names the version it was measured on, because 0.54.0's did not
+
+**A repair for what the previous release shipped, and the gate that would have caught
+it.** `0.54.0` went out with its verification ledger's newest section naming **v0.53.0**.
+This repository's own gate said nothing; the umbrella's cross-member ratchet caught it one
+layer up — *3 member ledgers describe a version older than they ship, and the ratchet
+stands at 2* — which is the right backstop and the wrong first line.
+
+`validate_ledger_names_its_version` reads the newest `## …` section, resolves the version
+it names and compares it with `package.json`. A ledger whose newest section names an older
+artifact is a release nobody re-confirmed against anything.
+
+**The first draft crashed instead of refusing.** It called a `fail()` this module does not
+have — the name belongs to a sibling repository's validator — so the plant raised
+`NameError` and the run stopped. `rc=1` either way, which is exactly why the plant looked
+like it had worked. **A guard that crashes has not refused anything**: it stops the suite
+before the rest of it can speak, and it reports a defect in itself as a defect in the
+tree. Rewritten through `check()`, watched refusing its plant with no traceback.
+
+Ledger section added for `0.54.0`'s own content, so the release it repairs is recorded
+rather than skipped. `repo validator checks` recomputed 4621 → 4623 by running the command
+`docs/brand/facts.md` names, not by adding two.
+
 ## 0.54.0 — FR-01 says who does the clicking, and where the tool has to stop
 
 Closes `ssheleg/sshlg-skills#B-87` (board row), and widens two advertised triggers.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "super-ux",
-  "version": "0.54.0",
+  "version": "0.55.1",
   "scripts": {
     "test": "python3 test/validate.py && python3 test/brand_lint_test.py && python3 test/ux_lint_test.py && python3 docs/ux/lint.py && python3 docs/brand/lint.py && node test/installer_test.js"
   },