super-ux 0.52.5 → 0.54.0

package/CHANGELOG.md

@@ -1,3 +1,73 @@
+## 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.
+
+**A method told the agent to click through a competitor funnel by hand, in sessions
+where two browser tools are connected.** FR-01 read *"open a competitor's ad, click
+through, and you are in it at step one"* and named no tool for the click — while the
+same repository's neighbours already name `chrome-devtools` for their own crawling and
+`claude-in-chrome` is connected beside it. FR-01's whole output is *a list of live
+funnel URLs with the ad that led to each*: a walk a browser tool performs and a person
+performs slowly.
+
+**The answer is both, and the split is the useful part.** The walk is mechanical until
+it is not:
+
+- a **browser tool** opens the ad's destination, follows the redirect chain and captures
+  four things a screenshot loses — the final URL after redirects, every step's URL in
+  order, the network requests on the paywall step (which processor, which price ids —
+  the one place a funnel states its own price without a human reading it), and the ad
+  that led there;
+- a **human** takes over at three points that are not incidental: consent walls, which
+  vary by geography and are the first thing an automated walk gets stuck in; **sign-in
+  and paywall steps**, where a tool cannot proceed without real credentials or a real
+  card — and where FR-06 already forbids going further; and **ad libraries themselves**,
+  which rate-limit and serve challenges to a driven browser.
+
+So: the library is read by a person, the funnel is walked by a tool, and the walk stops
+at the first wall that asks who you are. **Silence here read as *nobody thought about
+it*, which is worse than either answer** — and the method is otherwise the most
+operationally precise document in the pack.
+
+**Two advertised triggers corrected rather than added.** `copywriting` advertised
+`"пост для твиттера"`, which demands a literal «для» an operator does not type; it now
+reads `"пост в твиттер"`. And `"error text" / "текст ошибки"` is named, closing a route
+the umbrella measured reaching nothing. The description moves 634 → 662 of 1024, leaving
+308 characters — well clear of the 60-character reserve the family's ratchet counts.
+
+## 0.53.0 — a coverage metric is a check, and its matching rule is where the assumptions hide
+
+Closes `ssheleg/sshlg-skills#96`.
+
+A metric is built to end an argument about coverage. Then **the rule that decides what a
+document is ABOUT** turns out to be one line of string handling, and the number reports work
+that exists as work that is missing — and the number now generates work that is fictional.
+
+Measured: a screen inventory decided a screen was documented when a scenario named its path
+as the primary entry point, taking the first backticked path from `Entry point:` **whole**.
+Two scenarios name their subject with a query string — `/reset-password?token=…` and
+`/account/billing/return?invoice=&status=` — so both matched no route, and **two screens
+that had always been documented were published as having no scenario at all.** The board row
+that followed named nine screens needing scenarios: two needed nothing, and a third was one
+component at two addresses, which the rule can only ever name one of. **Three of nine rows
+were fiction, in a number whose whole purpose was to stop people arguing about coverage from
+memory.**
+
+`ux-audit` now carries three rules for any metric over these documents:
+
+- **the aboutness rule is a named, exported function with a table of synthetic inputs,
+  including the negative cases** — query strings, fragments, several paths in one field,
+  prose with no backticks. It was untestable while it was an inline regex, which is exactly
+  why it was never tested;
+- **a metric that cannot express a real state says so beside the number** rather than
+  counting that state as a failure. One screen at two addresses is one screen, and the
+  matrix carries a derived *alias routes* line instead of silently ranking the second
+  address undocumented;
+- **a deliberate, hard-won rule is a reason to test it, not to trust it.** This one had
+  already replaced a looser rule twice, each time after a screen was reported covered on a
+  mention rather than on a subject — and a rule with that history is the last one anybody
+  re-reads.
+
 ## 0.52.5 — the card the umbrella renders, and the half of the role that was copywriting's
 
 The committed social preview is now the umbrella's own render, byte for byte

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "super-ux",
-  "version": "0.52.5",
+  "version": "0.54.0",
   "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"
   },