super-ux 0.36.0 → 0.36.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +41 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,46 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.36.1 — 2026-08-12
|
|
4
|
+
|
|
5
|
+
Four of the R-14 run's findings actioned, and a defect class ported from the
|
|
6
|
+
sibling repository.
|
|
7
|
+
|
|
8
|
+
### Fixed
|
|
9
|
+
|
|
10
|
+
- **BP-123 described web billing and was applied to "any subscription billed
|
|
11
|
+
self-serve".** On a store-billed subscription the app **cannot cancel**: the
|
|
12
|
+
terminal step hands off to the store's own sheet and the app does not
|
|
13
|
+
synchronously know whether the user went through. A flow designed from the old
|
|
14
|
+
sentence cannot be built on a phone — which is exactly what a fresh-context
|
|
15
|
+
agent produced, correctly, from what the entry said. It now branches on who
|
|
16
|
+
holds the billing and requires the third state, *unverified*, that claims
|
|
17
|
+
neither outcome.
|
|
18
|
+
- **A save offer must name the mechanism that delivers it.** BP-123 listed
|
|
19
|
+
"pause, downgrade, discount" — and **billing pause is not an iOS mechanism**, so
|
|
20
|
+
a product-side pause worded as a billing pause is a lie in copy at the moment
|
|
21
|
+
the user is deciding whether to trust you.
|
|
22
|
+
- **BP-102 and BP-206 collided with no cross-reference.** On a cancellation screen
|
|
23
|
+
the exit is both the destructive action and the thing the user came for. Both
|
|
24
|
+
entries now carry the resolution: destructive *styling* is required, destructive
|
|
25
|
+
*weight* is not — full width, same type size and tap target, reachable without
|
|
26
|
+
scrolling.
|
|
27
|
+
- **"Diverge before converging" had nowhere to land.** `ux-flows` requires two
|
|
28
|
+
structurally different shapes and one line on why the loser lost; the `flows.md`
|
|
29
|
+
contract had no field for it, so the rejected shape evaporated and the next agent
|
|
30
|
+
re-litigated it. The contract gains `Rejected shape:`.
|
|
31
|
+
- **The Figma question said "at the start" from inside step 6.**
|
|
32
|
+
`figma-integration.md` places it at step 0 and is right; the flows skill now says
|
|
33
|
+
so instead of contradicting it.
|
|
34
|
+
|
|
35
|
+
### Added
|
|
36
|
+
|
|
37
|
+
- **A check-count ratchet, ported from `sheleg-design`.** That repository's
|
|
38
|
+
retrospective recorded the class: a gate whose count can fall silently cannot
|
|
39
|
+
detect a deleted requirement. This one had no ratchet at all, so every
|
|
40
|
+
requirement deletion here was invisible **by construction**. `test/floors.json`
|
|
41
|
+
plus `check_floor()` inside `validate.py`, which CI already runs — watched saying
|
|
42
|
+
no against a planted impossible floor.
|
|
43
|
+
|
|
3
44
|
## 0.36.0 — 2026-08-12
|
|
4
45
|
|
|
5
46
|
R-14 was filed `never` this morning and closed the same day, by the only
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "super-ux",
|
|
3
|
-
"version": "0.36.
|
|
3
|
+
"version": "0.36.1",
|
|
4
4
|
"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.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"super-ux": "bin/super-ux.js"
|