super-ux 0.36.0 → 0.37.0

package/CHANGELOG.md

@@ -1,5 +1,86 @@
 # Changelog
 
+## 0.37.0 — 2026-08-12
+
+The last five findings from the R-14 run — the ones that needed a **decision**
+rather than a correction. In every case the fresh-context agent had already
+improvised the right answer, said out loud that it was deviating, and explained
+why. The answer was accepted rather than re-invented.
+
+### Added
+
+- **A declared branch for "we know almost nothing".** The Design workflow read
+  *per story* and built its practice profile from `foundation.md`, while the
+  commonest real brief has neither — and nothing said what to do. Step 0 now
+  requires three things instead of silent improvisation: a **provisional
+  profile** where every dimension names its provenance (`brief` / `inferred` /
+  `assumed`, and an assumed dimension that decides the flow's shape is called
+  out), `Traces:` as an **unbacked provisional job** in the user's words, and an
+  **open decisions** list saying what each would change. A flow built this way is
+  honest input; built without the three blocks it is invented personas with a
+  diagram on top.
+- **A granularity rule for the practice pass, because "every practice" does not
+  scale.** A mobile subscription product pulls roughly **150 practices for one
+  flow**; the worked example has four rows. Per-practice verdicts for the artifact
+  row and anything the artifact touches; **one band verdict, with its reason**,
+  per remaining set. A band with no reason is a silent skip wearing a table row.
+- **`blocked` joins the screen status enum** — designed, complete, and unsafe to
+  build because a decision outside UX would change it. Name the decision and its
+  owner on the same line. That state used to live in prose, where no linter and no
+  next agent reliably finds it, and `designed` quietly read as ready.
+- **A state is not a screen, with a test.** One `SCR-ID` per place the user can
+  be; split only when a variation owns distinct copy, distinct elements **and** its
+  own primary action. A confirm dialog with its own words is a screen; a table with
+  no rows is a state. Two agents given the same app produced incompatible
+  `screens.md` files for exactly this.
+- **The platform-permits rule, generalised out of BP-123.** Where a step belongs
+  to the OS or a store — store billing, a permission prompt, a share sheet,
+  biometrics — two non-design questions decide the diagram: can the app perform
+  the action at all, and does it learn the outcome synchronously. A "no" to the
+  second is a **third branch**. Drawing only success and failure there ships a flow
+  that cannot be built.
+
+## 0.36.1 — 2026-08-12
+
+Four of the R-14 run's findings actioned, and a defect class ported from the
+sibling repository.
+
+### Fixed
+
+- **BP-123 described web billing and was applied to "any subscription billed
+  self-serve".** On a store-billed subscription the app **cannot cancel**: the
+  terminal step hands off to the store's own sheet and the app does not
+  synchronously know whether the user went through. A flow designed from the old
+  sentence cannot be built on a phone — which is exactly what a fresh-context
+  agent produced, correctly, from what the entry said. It now branches on who
+  holds the billing and requires the third state, *unverified*, that claims
+  neither outcome.
+- **A save offer must name the mechanism that delivers it.** BP-123 listed
+  "pause, downgrade, discount" — and **billing pause is not an iOS mechanism**, so
+  a product-side pause worded as a billing pause is a lie in copy at the moment
+  the user is deciding whether to trust you.
+- **BP-102 and BP-206 collided with no cross-reference.** On a cancellation screen
+  the exit is both the destructive action and the thing the user came for. Both
+  entries now carry the resolution: destructive *styling* is required, destructive
+  *weight* is not — full width, same type size and tap target, reachable without
+  scrolling.
+- **"Diverge before converging" had nowhere to land.** `ux-flows` requires two
+  structurally different shapes and one line on why the loser lost; the `flows.md`
+  contract had no field for it, so the rejected shape evaporated and the next agent
+  re-litigated it. The contract gains `Rejected shape:`.
+- **The Figma question said "at the start" from inside step 6.**
+  `figma-integration.md` places it at step 0 and is right; the flows skill now says
+  so instead of contradicting it.
+
+### Added
+
+- **A check-count ratchet, ported from `sheleg-design`.** That repository's
+  retrospective recorded the class: a gate whose count can fall silently cannot
+  detect a deleted requirement. This one had no ratchet at all, so every
+  requirement deletion here was invisible **by construction**. `test/floors.json`
+  plus `check_floor()` inside `validate.py`, which CI already runs — watched saying
+  no against a planted impossible floor.
+
 ## 0.36.0 — 2026-08-12
 
 R-14 was filed `never` this morning and closed the same day, by the only

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "super-ux",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "description": "Scenario-driven UI development for AI agents (Claude Code, Cursor, 70+ agents): a versioned design chain in docs/ux/, a scenario-first hard rule, a deterministic drift linter, and evidence-backed UX audits. This package is the installer CLI.",
   "bin": {
     "super-ux": "bin/super-ux.js"