super-ux 0.63.0 → 0.65.0

package/CHANGELOG.md

@@ -1,3 +1,14 @@
+## 0.65.0 (2026-10-22): subscription economics, cohorts and four practices from GP Bullhound (2025)
+
+- **`funnel-research.md` → *Your own numbers*:** the unit economics a running subscription funnel is read by, each with its formula and the investor band it is judged against (LTV/CAC under 3x weak, 6x strong; CAC payback under 3 months; first-period annual retention under 30% weak, over 60% strong; renewal of 60%+ of each annual cohort and 40% of year 2; free-to-paid under 2% weak, 10%+ strong; organic share under 20% weak, over 50% strong), and two cohort cuts: the four states (new, current, reactivated, resurrected) and the locals/tourists split, with LTV per cohort and acquisition judged by the locals a channel brings rather than by ROAS. Cited by page from GP Bullhound's *Consumer Subscription Software* (October 2025), pp. 39, 65 to 67 and 71.
+- **Four practices, BP-242..245** (source key `[GPB25]`): a trial is three decisions (length, card at start, upgrade at decision points); one plan for everyone, because every extra structure is a growth cost; lead to the aha moment through a win and frame outcomes from what went right; invisible AI that adapts the paywall, trigger and onboarding per user. Routed in `practice-selection.md`; the catalog holds 245 practices.
+- **The test panel** (`templates/test-panel.md`, `ux-foundation` → *The test panel*): at least two locals and two tourists among the ten portraits, marked at the start of each `retention` line.
+
+## 0.64.0 (2026-10-22): the test panel, and a voice checker named by its tools
+
+- **The test panel** (`templates/test-panel.md`, `ux-foundation` → *The test panel*): ten portraits the task-pipeline design-tester walks through the scenarios before and after a build, each with its basis (evidence or hypothesis), situation, goals, features, composite scenarios by SCR- id, activation funnel, retention loop and needs. A test instrument: it decides what to test, never what to build. Its gate is task-pipeline's `design_gate.py panel`.
+- **`copywriting`** describes the optional tone-of-voice checker by its tools instead of a private product name.
+
 ## 0.63.0 (2026-10-20): short descriptions, triggers in the body
 
 - **Every skill description is a router of 279 to 393 characters** (was 332 to

package/README.md

@@ -264,7 +264,7 @@ The contracts every skill reads:
 | [ux_doctor.py](plugins/super-ux/scripts/ux_doctor.py) | Contract doctor. It reports mixed or stale contract versions across a project's artifacts, files the tooling cannot find under their contract names, and audits produced against a base that is not there. `/ux-lint` checks a chain against itself; this checks it against the contract. Installed as `docs/ux/doctor.py`, read-only unless `--fix` |
 | [best-practices-index.md](plugins/super-ux/skills/references/best-practices-index.md) | Generated tag index over the catalog: tag → ids, id → title. Read it to decide which entries to open; regenerated by `plugins/super-ux/scripts/bp_index.py` and checked for drift by the validator |
 | [ux-design-principles.md](plugins/super-ux/skills/references/ux-design-principles.md) | How the agent thinks: the design pipeline (forward and backwards), task analysis, flow rules, heuristics PRN-01..24, the improvement procedure, anti-patterns |
-| [best-practices.md](plugins/super-ux/skills/references/best-practices.md) | Living, tag-indexed catalog of 241 proven practices: subscription-app laws, mobile/web/voice guidance (Apple HIG 2025, M3 Expressive, NN/g, Baymard, WCAG 2.2), monetization economics (RevenueCat/PLG 2025 benchmarks, ASO, freemium boundaries), web funnels end to end (landing, pricing, checkout, dunning, cancel), web2app (paid handoff, deferred deep links, storefront rules) and the funnel wiring that fails invisibly (what a personalization branch may vary, stand-up order, the three decisions a stored answer carries, GDPR Art. 13/17 timing, the access ladder), motion and page weight (HTTP Archive field data, W3C sustainability), accessibility as it actually fails (WebAIM Million, EAA/ADA exposure), frustration telemetry, gamification and trend governance, growth loops and referral mechanics, empty states, authentication (NIST SP 800-63B rev 4) and form recovery, motion craft and perceived quality, the defaults that make an interface read as generated, interface state, locale and platform surfaces (Web Interface Guidelines), visual craft, Figma structure |
+| [best-practices.md](plugins/super-ux/skills/references/best-practices.md) | Living, tag-indexed catalog of 245 proven practices: subscription-app laws, mobile/web/voice guidance (Apple HIG 2025, M3 Expressive, NN/g, Baymard, WCAG 2.2), monetization economics (RevenueCat/PLG 2025 benchmarks, ASO, freemium boundaries), web funnels end to end (landing, pricing, checkout, dunning, cancel), web2app (paid handoff, deferred deep links, storefront rules) and the funnel wiring that fails invisibly (what a personalization branch may vary, stand-up order, the three decisions a stored answer carries, GDPR Art. 13/17 timing, the access ladder), motion and page weight (HTTP Archive field data, W3C sustainability), accessibility as it actually fails (WebAIM Million, EAA/ADA exposure), frustration telemetry, gamification and trend governance, growth loops and referral mechanics, empty states, authentication (NIST SP 800-63B rev 4) and form recovery, motion craft and perceived quality, the defaults that make an interface read as generated, interface state, locale and platform surfaces (Web Interface Guidelines), visual craft, Figma structure |
 | [practice-selection.md](plugins/super-ux/skills/references/practice-selection.md) | The deterministic bridge: product profile → mandatory consideration sets → per-artifact checklists → a compliance table where every pulled practice gets a verdict. No silent skips, no cargo cult |
 | [funnel-research.md](plugins/super-ux/skills/references/funnel-research.md) | Reading a funnel market before designing one, `FR-01..FR-07`: where competitor funnels are visible, the four signals that survive when revenue is invisible, the fields that make a corpus comparable, which adjacent categories transfer, the stop before copying, and where each finding lands in the chain. Carried by `ux-foundation` and `ux-flows` |
 | [component-guidelines.md](plugins/super-ux/skills/references/component-guidelines.md) | Which control for which job (radios/select/switch, sheet/alert, modal/disclosure, combobox, nav bar/rail, FAB, dates, toasts) and the platform rules of Apple HIG, Material 3, W3C ARIA APG and GOV.UK |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "super-ux",
-  "version": "0.63.0",
+  "version": "0.65.0",
   "scripts": {
     "test": "python3 test/validate.py && python3 test/brand_lint_test.py && python3 test/display_copy_test.py && python3 test/ux_lint_test.py && python3 docs/ux/lint.py && python3 docs/brand/lint.py && node test/installer_test.js && npm run test:audit",
     "test:audit": "for t in test/audit_regressions/*.py; do python3 \"$t\" || exit 1; done"

package/templates/test-panel.md

@@ -0,0 +1,44 @@
+# Test panel: <product>
+
+Ten portraits the design-tester walks through the scenarios before and after a build
+(task-pipeline `references/design-review.md`). A panel is a **test instrument**: it decides
+what to test, never what to build. Each portrait says its basis: `evidence RE-NN` when the
+research ledger supports it, `hypothesis` when it is a reasoned guess filling coverage.
+
+Revision: <date> · confirmed by the operator: <yes/no> · foundation: `docs/ux/foundation.md`
+
+Every portrait keeps these eight lines, in this form, so `design_gate.py panel` can read them.
+The `retention` line opens with `local` or `tourist`, and the panel carries at least two of
+each (see the note at the end).
+
+## P-01 <short name>
+
+- **basis**: evidence RE-01, RE-04 | hypothesis
+- **situation**: <who, where, on what, under what pressure>
+- **goals**: <the jobs they hire the product for, in their words>
+- **features**: <the features they actually use, by name>
+- **scenarios**: <two to four composite chains across features, by SCR- id: SCR-03 → SCR-07>
+- **activation**: <steps to first value, and the step they are likely to drop at>
+- **retention**: local | tourist: <trigger → action → reward → what brings them back, and what makes them leave>
+- **needs**: <device and engine, locale, text size, accessibility, connection>
+
+## P-02 <short name>
+
+- **basis**: …
+- **situation**: …
+- **goals**: …
+- **features**: …
+- **scenarios**: …
+- **activation**: …
+- **retention**: …
+- **needs**: …
+
+<!-- … through P-10. Spread the ten across the foundation's personas, the activation stages
+(new, activating, active, at risk, returning), and the needs that change a screen: small
+phone, large text, keyboard only, a second locale, a slow connection.
+
+Locals and tourists: at least two portraits are locals (high engagement, enter their data or
+connect sources, arrived through a friend, build the product into their routine) and at least
+two are tourists (low engagement, enter little, arrived through an ad or a discount, try many
+services). Locals are who the product's lifetime value rests on; tourists are most of its churn.
+Source: GP Bullhound, Consumer Subscription Software, October 2025, p. 71. -->