anhedral 0.12.0 → 0.15.0

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.
Files changed (184) hide show
  1. package/README.md +35 -172
  2. package/assets/patches/audit-deps.mjs +12 -2
  3. package/assets/ui/LICENSE.shadcn +21 -0
  4. package/assets/ui/UPSTREAM.json +33 -0
  5. package/assets/ui/native/button.tsx +85 -0
  6. package/assets/ui/native/card.tsx +33 -0
  7. package/assets/ui/native/dialog.tsx +75 -0
  8. package/assets/ui/native/input.tsx +27 -0
  9. package/assets/ui/native/label.tsx +4 -0
  10. package/assets/ui/native/layout.tsx +26 -0
  11. package/assets/ui/native/text.tsx +20 -0
  12. package/assets/ui/native/theme-switcher.tsx +22 -0
  13. package/assets/ui/theme-storage.ts +25 -0
  14. package/assets/ui/theme.tsx +66 -0
  15. package/assets/ui/web/button.tsx +59 -0
  16. package/assets/ui/web/input.tsx +21 -0
  17. package/assets/ui/web/label.tsx +19 -0
  18. package/dist/capabilities.d.ts +5 -5
  19. package/dist/capabilities.js +3 -21
  20. package/dist/capability-contract.d.ts +3 -3
  21. package/dist/capability-contract.js +11 -39
  22. package/dist/cli-delivery.d.ts +1 -1
  23. package/dist/cli-delivery.js +5 -65
  24. package/dist/cli-output.js +3 -3
  25. package/dist/command-schema.js +35 -80
  26. package/dist/command.js +9 -11
  27. package/dist/delivery-evidence.d.ts +1 -1
  28. package/dist/delivery-evidence.js +7 -36
  29. package/dist/delivery.d.ts +2 -8
  30. package/dist/delivery.js +23 -102
  31. package/dist/dependencies.d.ts +12 -58
  32. package/dist/dependencies.js +67 -189
  33. package/dist/index.d.ts +1 -3
  34. package/dist/index.js +1 -3
  35. package/dist/inspector-model.d.ts +2 -2
  36. package/dist/integration-service-readers.d.ts +1 -2
  37. package/dist/integration-service-readers.js +3 -84
  38. package/dist/lifecycle-model.d.ts +1 -1
  39. package/dist/lifecycle-model.js +1 -1
  40. package/dist/mobile-delivery.d.ts +1 -1
  41. package/dist/mobile-delivery.js +4 -0
  42. package/dist/platforms/mobile.d.ts +1 -1
  43. package/dist/platforms/mobile.js +64 -114
  44. package/dist/platforms/web.d.ts +3 -0
  45. package/dist/platforms/web.js +299 -0
  46. package/dist/project-config.d.ts +1 -1
  47. package/dist/project-config.js +0 -1
  48. package/dist/project-inspector.js +5 -36
  49. package/dist/project-state.d.ts +1 -3
  50. package/dist/project-state.js +6 -86
  51. package/dist/provider-auth.js +3 -32
  52. package/dist/provider-readiness.d.ts +1 -1
  53. package/dist/provider-readiness.js +5 -24
  54. package/dist/providers/adapters.js +9 -178
  55. package/dist/providers/api.d.ts +1 -1
  56. package/dist/providers/api.js +3 -3
  57. package/dist/providers/config.js +2 -48
  58. package/dist/providers/definitions.d.ts +1 -204
  59. package/dist/providers/definitions.js +0 -85
  60. package/dist/providers/provision.d.ts +1 -1
  61. package/dist/providers/receipts.js +1 -11
  62. package/dist/providers/recovery-verification.js +1 -61
  63. package/dist/providers/runtime.js +15 -35
  64. package/dist/providers/state.js +1 -7
  65. package/dist/provision.d.ts +5 -13
  66. package/dist/provision.js +4 -80
  67. package/dist/readiness.d.ts +1 -1
  68. package/dist/readiness.js +3 -6
  69. package/dist/registry/add.js +11 -38
  70. package/dist/registry/bootstrap.d.ts +3 -2
  71. package/dist/registry/bootstrap.js +4 -13
  72. package/dist/registry/commands.js +8 -10
  73. package/dist/registry/context.js +0 -1
  74. package/dist/registry/options.js +8 -26
  75. package/dist/registry/resolve.d.ts +3 -2
  76. package/dist/registry/resolve.js +26 -82
  77. package/dist/registry/types.d.ts +2 -7
  78. package/dist/registry/usage.js +2 -2
  79. package/dist/runtime-policy.d.ts +0 -2
  80. package/dist/runtime-policy.js +0 -13
  81. package/dist/scaffold/api.js +10 -2
  82. package/dist/scaffold/auth.d.ts +1 -2
  83. package/dist/scaffold/auth.js +57 -116
  84. package/dist/scaffold/backend.d.ts +2 -0
  85. package/dist/scaffold/backend.js +39 -0
  86. package/dist/scaffold/billing-config.d.ts +1 -0
  87. package/dist/scaffold/billing-config.js +73 -0
  88. package/dist/scaffold/billing-contracts.d.ts +2 -0
  89. package/dist/scaffold/billing-contracts.js +48 -0
  90. package/dist/scaffold/billing-providers.d.ts +1 -0
  91. package/dist/scaffold/billing-providers.js +249 -0
  92. package/dist/scaffold/billing-schema.d.ts +1 -0
  93. package/dist/scaffold/billing-schema.js +34 -0
  94. package/dist/scaffold/billing-security.d.ts +1 -0
  95. package/dist/scaffold/billing-security.js +46 -0
  96. package/dist/scaffold/billing-server.d.ts +1 -0
  97. package/dist/scaffold/billing-server.js +139 -0
  98. package/dist/scaffold/billing-store.d.ts +1 -0
  99. package/dist/scaffold/billing-store.js +72 -0
  100. package/dist/scaffold/billing.d.ts +2 -0
  101. package/dist/scaffold/billing.js +208 -0
  102. package/dist/scaffold/bootstrap.d.ts +2 -3
  103. package/dist/scaffold/bootstrap.js +37 -43
  104. package/dist/scaffold/compose.js +2 -12
  105. package/dist/scaffold/database.d.ts +1 -1
  106. package/dist/scaffold/database.js +20 -111
  107. package/dist/scaffold/documentation.d.ts +0 -1
  108. package/dist/scaffold/documentation.js +22 -82
  109. package/dist/scaffold/expo-auth.d.ts +3 -0
  110. package/dist/scaffold/expo-auth.js +203 -0
  111. package/dist/scaffold/expo-billing.d.ts +3 -0
  112. package/dist/scaffold/expo-billing.js +257 -0
  113. package/dist/scaffold/expo-runtime.d.ts +3 -0
  114. package/dist/scaffold/expo-runtime.js +43 -0
  115. package/dist/scaffold/integrations.d.ts +1 -2
  116. package/dist/scaffold/integrations.js +9 -5
  117. package/dist/scaffold/managed-email.d.ts +3 -0
  118. package/dist/scaffold/managed-email.js +47 -0
  119. package/dist/scaffold/native-ui.d.ts +2 -0
  120. package/dist/scaffold/native-ui.js +69 -0
  121. package/dist/scaffold/password-reset.d.ts +1 -0
  122. package/dist/scaffold/password-reset.js +99 -0
  123. package/dist/scaffold/private-files.d.ts +2 -0
  124. package/dist/scaffold/private-files.js +78 -0
  125. package/dist/scaffold/stack-documentation.d.ts +0 -1
  126. package/dist/scaffold/stack-documentation.js +3 -49
  127. package/dist/scaffold/styling.d.ts +1 -1
  128. package/dist/scaffold/styling.js +20 -28
  129. package/dist/scaffold/web-billing.d.ts +2 -0
  130. package/dist/scaffold/web-billing.js +48 -0
  131. package/dist/scaffold/workspace.js +53 -189
  132. package/dist/service-deletion.js +1 -1
  133. package/dist/service-descriptor.js +5 -12
  134. package/dist/service-model.d.ts +1 -1
  135. package/dist/service-operations.js +2 -32
  136. package/dist/service-readers.js +1 -32
  137. package/dist/services-command.d.ts +1 -1
  138. package/dist/services-command.js +3 -9
  139. package/dist/ship.d.ts +3 -316
  140. package/dist/ship.js +13 -143
  141. package/dist/stack-registry.d.ts +2 -43
  142. package/dist/stack-registry.js +80 -308
  143. package/dist/standard.js +7 -14
  144. package/dist/version.d.ts +1 -1
  145. package/dist/version.js +1 -1
  146. package/docs/anhedral-stack.md +23 -0
  147. package/docs/assets/anhedral-stack-light.png +0 -0
  148. package/docs/assets/anhedral-stack.png +0 -0
  149. package/docs/software-factory.md +25 -499
  150. package/docs/stack-standard.md +48 -226
  151. package/docs/verification.md +433 -0
  152. package/package.json +22 -21
  153. package/dist/neon-service-data.d.ts +0 -8
  154. package/dist/neon-service-data.js +0 -117
  155. package/dist/platforms/desktop.d.ts +0 -2
  156. package/dist/platforms/desktop.js +0 -415
  157. package/dist/platforms/extension.d.ts +0 -2
  158. package/dist/platforms/extension.js +0 -328
  159. package/dist/scaffold/lint.d.ts +0 -4
  160. package/dist/scaffold/lint.js +0 -56
  161. package/dist/scaffold/neon-realtime.d.ts +0 -2
  162. package/dist/scaffold/neon-realtime.js +0 -97
  163. package/dist/scaffold/services.d.ts +0 -5
  164. package/dist/scaffold/services.js +0 -108
  165. package/dist/scaffold/stream.d.ts +0 -2
  166. package/dist/scaffold/stream.js +0 -114
  167. package/dist/scaffold/void.d.ts +0 -4
  168. package/dist/scaffold/void.js +0 -256
  169. package/dist/scaffold/web.d.ts +0 -2
  170. package/dist/scaffold/web.js +0 -128
  171. package/dist/vercel-project.d.ts +0 -101
  172. package/dist/vercel-project.js +0 -305
  173. package/dist/vercel.d.ts +0 -67
  174. package/dist/vercel.js +0 -581
  175. package/dist/vinext.d.ts +0 -2
  176. package/dist/vinext.js +0 -86
  177. package/dist/void-execution.d.ts +0 -10
  178. package/dist/void-execution.js +0 -94
  179. package/dist/void-migrations.d.ts +0 -6
  180. package/dist/void-migrations.js +0 -110
  181. package/dist/void-state.d.ts +0 -16
  182. package/dist/void-state.js +0 -65
  183. package/dist/void.d.ts +0 -3
  184. package/dist/void.js +0 -5
@@ -1,7 +1,175 @@
1
+ # Next.js web and Expo native architecture — October 23, 2026
2
+
3
+ CLI 0.15 source preparation separates full Next.js App Router web (SSR/RSC through
4
+ Cloudflare OpenNext) from Expo iOS/Android. The UI contracts are DOM shadcn for web
5
+ and the Anhedral-maintained React Native port of shadcn for native, with shared
6
+ semantic tokens and public API contracts. Hono, Drizzle/D1 and private R2 remain
7
+ core; Stripe and RevenueCat remain the only additions.
8
+
9
+ The canonical diagram was regenerated in both themes as self-contained SVG and
10
+ 1920×1080 PNG using the existing local Chrome renderer. The same SVG bytes are
11
+ mirrored by the Platform landing. This is documentation/artwork verification;
12
+ it does not establish generated-app, installed-plugin, native-device, provider,
13
+ hosted-image or production acceptance. Record runtime evidence separately.
14
+
15
+ ## Next development proxy response framing — October 23, 2026
16
+
17
+ The Platform Linux image proof reproduced a failed `/api/health` response through
18
+ actual Next dev: Node fetch decoded the Hono sidecar's gzip body, but the generated
19
+ proxy retained its compressed `Content-Encoding` and `Content-Length`. The next
20
+ HTTP client attempted to decode the already-decoded response and failed.
21
+
22
+ The development HTTP proxy now removes those stale wire headers before Next
23
+ frames the response. The production service-binding path retains its existing
24
+ response handling. A real loopback HTTP server supplies a gzip response in the
25
+ regression test; all five Next web tests pass. `pnpm build` and `pnpm lint` also
26
+ pass, including typecheck, formatting, source hygiene and release-policy checks.
27
+ This evidence does not establish a deployed Platform runtime; its image and live
28
+ initialization are verified separately in the Platform repository.
29
+
30
+ The full `pnpm release:check` passed: 550 unit tests passed with one existing
31
+ skip, frozen patch installation checks passed, and packed CLI smoke and packlist
32
+ checks passed. Linux Next dev returned `200 {"ok":true}` through `/api/health`
33
+ and `200 null` through `/api/auth/get-session` after applying the generated fix.
34
+
35
+ ## CLI 0.15 generated runtime acceptance — October 23, 2026
36
+
37
+ The implementation agent recorded the following local evidence for the unpublished
38
+ 0.15 source preview, with Next.js web separate from Expo native:
39
+
40
+ - Complete generated `pnpm check` passed: lint, typechecks, Fallow with zero issues,
41
+ dependency audit, available tests and builds. A manual fixture rsync temporarily
42
+ overwrote its patch policy; after restoring the ordinary-init policy, the full
43
+ check passed. This was a test-harness issue, not an initialization result.
44
+ - The packed tarball completed ordinary initialization, including staged dependency
45
+ resolution, patches and frozen installation; doctor and target checks passed.
46
+ - Both iOS and Android Hermes exports passed, with output retained locally at
47
+ `/tmp/anhedral-next-native-final-export`. This is export evidence, not device,
48
+ screen-reader, store or native interaction acceptance.
49
+ - Production OpenNext running in local workerd passed SSR/RSC, guarded account,
50
+ cookie roundtrip, signup, reload, sign-in/sign-out and rejected native-origin
51
+ checks. Browser acceptance reported zero errors. The final typography-only
52
+ OpenNext rebuild passed: 5474.81 KiB upload, 1130.07 KiB gzip and 44 assets;
53
+ its additional browser/layout rerun was still pending when this entry was written.
54
+ - Root Turbopack development reached first compile/browser readiness in 4825 ms.
55
+ A source edit reached HMR in 790 ms, preserving window state with zero browser
56
+ errors. Webpack development failed reproducibly in
57
+ `WasmHash._updateWithBuffer` with an undefined `length`; production webpack and
58
+ OpenNext builds passed. The supported default development path uses Turbopack.
59
+
60
+ A small warm-workerd comparison used three fresh Chrome contexts before the final
61
+ heading CSS adjustment. Next readiness was 115/90/78 ms, transferred bytes were
62
+ 172418/172089/172092 and FCP was 72/40/40 ms. The earlier Expo baseline medians
63
+ were 149 ms readiness, 438928 transferred bytes and 48 ms FCP. These are tiny local
64
+ samples with a warm server, not universal performance claims or live deployment
65
+ measurements. They do not establish a consistent FCP improvement.
66
+
67
+ No npm publication, installed-plugin update, hosted-image activation, production
68
+ deployment, real payment or physical-device acceptance is established by these
69
+ checks. Final serialized CLI/plugin/reference checks follow this documentation
70
+ update and must be recorded separately if they expose further failures.
71
+
72
+ # Focused core verification — October 23, 2026
73
+
74
+ The 0.14.0 source intentionally narrows initialization to Expo + Hono + Drizzle/D1 + private R2, supporting Better Auth and styling, with only Stripe and RevenueCat additions. This supersedes the older catalog scope in the historical evidence below. Existing applications/resources were not migrated or deleted. Compiled 0.13 output was preserved locally before rebuilding; output and credentials remain ignored rather than committed.
75
+
76
+ Validation of this change:
77
+
78
+ - CLI build, typecheck, formatting/hygiene, release policy and static security passed.
79
+ - Complete CLI unit suite after the streamlining pass: 545 passed, one platform-conditional skip, zero failures (546 tests).
80
+ - Codex plugin check: typecheck/build and 61 tests passed; browser smoke 11/11 passed using installed Chrome.
81
+ - Packed CLI installed/executed successfully; packlist allowlist passed (222 files, approximately 543 KB compressed at this validation).
82
+ - OSV audit passed for all 56 unique locked/catalog dependency versions.
83
+ - Generated all four supported selections in isolated tests; offline init, authored-source preservation, addition rollback/conflicts, private secret exclusion and generator provenance covered.
84
+ - Private-file route tests against real Hono passed: anonymous and cross-user rejection, upload/download/delete, origin protection, actual streamed size enforcement and misleading Content-Length.
85
+ - Installed generated both-payment workspace: lint and typecheck across seven packages, Fallow audit with zero issues, dependency audit under existing reviewed local-patch policy, Hono Worker bundle, Expo web export and gateway bundle passed. Generated pnpm test currently has no default product tests; successful execution alone is not test coverage.
86
+ - Real local workerd: exported Expo routes, gateway service binding, isolated local D1 authentication/session/revocation and native scheme/origin handling passed.
87
+ - Actual generated Hono/Better Auth/Drizzle signup/login/session/revocation passed with in-memory SQLite. Generated Stripe/RevenueCat billing reconciliation tests passed with synthetic vendor responses, including idempotency, webhook replay/order, ownership/CSRF, expiry/revocation, provider union and outage/retry recovery.
88
+
89
+ The follow-up streamlining pass removed obsolete alternate-stack adapters and unused bootstrap test fixtures, aligned human help/plugin defaults with the supported stack, and removed a retired dependency's secret-scanner exemption. Regression tests cover actual core catalog paths and payment-only suggestions. CLI build/lint/static security, all unit tests, plugin check (61 tests), packed smoke and package allowlist passed again. The final package remains 222 files, approximately 543 KB compressed. README instructions distinguish the source candidate from a published npm release.
90
+
91
+ Worktree recovery review also recovered a one-line inspector safe-area correction: project details now retain host top padding through the shared CSS variable. Two new browser regressions exercise 24px and 112px insets through project/tab/list navigation. Plugin typecheck/build and all 61 plugin tests passed; browser smoke passed 13/13 using installed Chrome. This simulates the host layout contract and does not claim installed native-host acceptance.
92
+
93
+ The CLI presentation follow-up restores a connected static default-stack diagram in both themes, with only Stripe and RevenueCat marked optional. The README, stack guide, npm documentation and plugin references carry valid image targets. Only the two PNGs are added to the npm package; editable SVG/layout/logo source remains documentation source. CLI build/lint, documentation/plugin contracts, packed smoke and packlist passed (224 files, approximately 793 KB compressed). The platform landing mirrors the canonical SVGs rather than maintaining a second diagram layout. Artwork does not certify provider activation or deployment.
94
+
95
+ Local staging acceptance generated a fresh core application through ordinary init, including dependency installation and Git initialization. Drizzle generation reported no schema changes; the generated lint, typechecks, Fallow/dependency audit and web/Worker builds passed. Local D1 migrations were applied explicitly. Browser acceptance reproduced a return-to-sign-in race after sign-out: the API accepted the new session while the account hook still held the earlier anonymous state. The generator now mounts the session hook on sign-in and awaits its refresh after server verification, before navigating. This follows the supported [Better Auth session hook](https://better-auth.com/docs/basic-usage#use-session).
96
+
97
+ The expanded real-workerd browser regression passed signup, protected account, reload, sign-out, sign-in again, another reload and mobile viewport checks in a newly generated application. Local D1 session/revocation and native scheme/origin transport checks passed. Independent live local R2 checks exercised upload/download/delete, forced attachment headers, anonymous rejection, cross-user read/delete isolation, mutation-origin rejection and the 1 MiB bound. CLI build/lint and all 545 unit tests passed with one conditional skip. Logs are retained locally under `/tmp/anhedral-staging-init-*` and `/tmp/anhedral-staging-default-flow*.log`; generated applications and private local state remain ignored. These checks exercise web and API transport, not native-device execution.
98
+
99
+ No cloud provisioning, real payment, configured-database migration, deployment, app-store/device acceptance, npm publication or installed-plugin update occurred. Existing installed runtimes remain separate from this source candidate. Historical provider reports below are dated evidence, not current live verification.
100
+
101
+ ---
102
+
1
103
  # Verification record
2
104
 
3
105
  Dated records below describe the source and environment exercised at that time. Earlier results are historical evidence, not acceptance of a later release. Current architecture and operating instructions live in the stack standard and software factory.
4
106
 
107
+ ## README stack catalog and static artwork — 2026-10-19
108
+
109
+ Replaced the README Mermaid diagram with dark/light static artwork. After reviewing the earlier connected reference, refined the illustration to Expo web/iOS/Android → Hono → Better Auth / Drizzle + D1 / private R2, with Cloudflare hosting, native distribution, shared UI/contracts and workspace tools. Large icons, short labels and thin curves follow the landing hero style. The caption explicitly preserves plain init's Expo-only selection; backend/auth/data are added when needed. The README retains the under-construction notice, early starting commands, all CLI selections and upstream documentation for 117 named ecosystem options.
110
+
111
+ Local validation: all 38 registry entries remain represented in the retained catalog; CLI build, four documentation-contract tests and the npm packlist policy passed. Inspected rendered artwork for icons, connections and label spacing. No CLI runtime behavior, provider configuration or deployment changed. GitHub/npm image URLs will show this artwork after the assets reach main.
112
+
113
+ ## Full Cloudflare default and optional shared billing — 2026-10-18
114
+
115
+ New plain initialization and new Expo selections include Expo web/iOS/Android, Hono, Better Auth, Drizzle/D1 and private R2. Explicit Neon replaces D1. WXT-only initialization adds an extension to that default; explicit primary applications preserve their compatibility selection. Existing saved selections and unrelated additions do not receive new profile defaults. Legacy billing SDK/guidance projects require their pinned CLI or an explicit reviewed migration; strict provenance was preserved.
116
+
117
+ Stripe and RevenueCat are independently optional. Generated shared contracts, Expo web/native billing adapters, authenticated Hono Checkout/portal/identity/entitlement routes and a server enforcement example are connected. The authenticated subject is the RevenueCat App User ID. Server-only Drizzle tables store account/customer ownership, fenced reconciliation snapshots and an idempotent webhook inbox. Stripe signatures use raw request bodies; RevenueCat requires configured Authorization and supports HMAC with timestamp checks. Canonical provider reads reconcile grants instead of trusting event order or client purchase state. A bounded scheduled retry drains pending events. Access caches expire within sixty seconds and never outlive provider expiry; stale access fails closed during outages. Provider environments and native public keys remain isolated from private credentials.
118
+
119
+ Checkout guards nonterminal subscriptions independently of entitlement state, including refunded or past-due subscriptions. Verified open same-plan sessions are reused across distinct intents; another pending plan returns a conflict. Root client error handling gives safe conflict guidance. SDK operations fence native identity changes; RevenueCat logout failure cannot prevent Better Auth session revocation. R2 remains a private binding: each product must implement file ownership checks before exposing file routes.
120
+
121
+ Local evidence:
122
+
123
+ - CLI build, lint and static security checks passed. The full unit suite passed with 743 passing, zero failures and two existing skips (745 total); the focused release-scanner regression also passed. The scanner correction exempts only adjacent empty assignments in example files; populated secrets and JavaScript multiline credentials remain detected.
124
+ - Retained `examples/billing-reference` was generated with `--stripe --revenuecat`; its final full `pnpm check` passed, including client/server/Worker types, Fallow, dependency audit, static web export and both Worker dry builds. Reviewed reference migration source is `0001_billing.sql`; no configured database was migrated. Final iOS/Android Hermes exports passed with the real optional RevenueCat native package and account-transition adapters.
125
+ - `pnpm test:billing` passed against the compiled generated Hono Worker, real Better Auth/Drizzle SQL and Stripe SDK, with synthetic vendor HTTP responses and in-memory SQLite. It covered authenticated account isolation, strict plans/body/origins, deterministic retries, open-session reuse, duplicate-sale guards, server enforcement, independent optional providers, Stripe/RevenueCat grant union, refund/revocation, cancellation versus expiry, trial/past-due behavior, native transfers, invalid/stale signatures, environment/app scope, duplicate/out-of-order events, concurrent lease fencing, stale-cache outage denial and durable scheduled recovery. SQLite fixtures do not certify Cloudflare D1 semantics; vendor fixtures do not certify provider/store acceptance.
126
+ - A final fresh `node tests/test-generated-apps.mjs universal-billing` passed initialization/install, generated SQL/check/build, local workerd/D1/R2 auth and the compiled billing proof, including open-session reuse and duplicate-sale guards. The hosted CI matrix now includes this reproducible profile.
127
+ - Real local workerd, service bindings, D1 and private R2 loaded successfully. Chrome verified signup, protected account/reload, sign-out and mobile viewport behavior. An initial concurrent-edit run observed Worker reload/session unavailability; the unchanged assertions passed after source writers stopped. No timeout or security assertions were relaxed.
128
+ - Main repository `pnpm check` and `pnpm build` passed. The five local Anhedral skills passed frontmatter/UI-metadata YAML and local-reference checks. CLI build refreshes bundled references; an installed plugin is not silently updated.
129
+
130
+ Billing provider products/prices, webhook ingress and credentials, RevenueCat project/store policy, signed native builds and real sandbox purchases still require owner configuration and acceptance. Native exports are not device tests. Nothing was provisioned, deployed or published; no financial provider writes, charges or remote migrations were performed. Earlier dated records remain historical evidence of their own source/environment.
131
+
132
+ ## Universal Expo default — 2026-10-18
133
+
134
+ New plain initialization selects Expo web/iOS/Android in `apps/mobile`, Hono in `apps/api`, shared contracts/styling and Wrangler delivery on Cloudflare. SDK 57 exports static web assets behind a thin API-binding gateway. Explicit Vinext/Next.js selections and existing projects remain supported. Better Auth selects a database and generates browser/native session adapters, exact application-scheme trust, SecureStore integration and account screens. Billing entitlements and the portal publisher remain separate implementation work.
135
+
136
+ Local evidence:
137
+
138
+ - CLI build, lint, static security policy and the full unit suite passed: 740 passing, zero failures and two existing conditional skips (742 total). Coverage includes gateway forwarding/caching/failure behavior, API-first target order, public build-variable isolation, native cookie rotation and server/browser/native auth boundaries.
139
+ - Retained `examples/universal-reference` was generated from the local CLI with `--better-auth --no-git`. Its complete `pnpm check` passed, including lint, client/server/gateway types, Fallow, dependency audit, static web export and both Worker dry builds. Its lockfile and source are retained; generated outputs remain ignored.
140
+ - `pnpm test:reference --browser` passed against real local workerd, an API service binding and disposable D1. It exercised health/exported routes, signup/login, protected contracts, incorrect-password rejection, sign-out/revocation, forged identity-header rejection, native scheme/cookie transport and untrusted-scheme rejection. Headless installed Chrome verified account creation, the protected account screen, reload, sign-out and a 390px viewport without horizontal overflow. The helper creates local synthetic credentials/state, applies migrations only with `--local`, refuses existing configured private files and cleans its processes/files.
141
+ - A second fresh `node tests/test-generated-apps.mjs universal-auth` passed initialization, installation, full generated `pnpm check` and the real workerd/D1 gateway acceptance flow, proving the retained example does not depend on manual source repairs.
142
+ - Final iOS and Android Hermes exports passed with the platform-specific auth and development-client modules. This proves bundler compatibility, not an installed native build or device session persistence.
143
+ - Main repository `pnpm check` and `pnpm build` passed. Five local Anhedral skills passed YAML/frontmatter/UI-metadata and local-reference validation.
144
+
145
+ The browser preview currently needs a new static export for changes; it does not provide web HMR. Arbitrary unknown dynamic URLs require explicit routing/rendering design. Physical-device/simulator native acceptance, native compilation/signing, deployed Cloudflare behavior, store purchase sandboxes and complete billing synchronization remain unverified. No cloud provisioning, remote migration, deployment, package publication or installed-plugin update occurred. Earlier records below retain their original source/environment scope.
146
+
147
+ ## Default Hono backend — 2026-10-18
148
+
149
+ New initialization includes Hono and framework-independent Zod/HTTP contracts. Web remains Vinext/Cloudflare by default; explicit native Next.js/Vercel calls the API through a server-only configured URL. Cloudflare web/API service bindings, cookie-preserving same-origin transport, selected database bindings/factories and Better Auth routes/session UI are generated together. Database and identity remain opt-in. New routes still need product authorization. Existing registry metadata remains compatible; readiness and additions do not apply new backend defaults to old selections.
150
+
151
+ Local validation:
152
+
153
+ - CLI build and lint (types, formatting, source hygiene and release policy) passed. The unit suite passed with 738 passing and two skipped tests, including shared-client response validation and Vercel server-credential transport checks. The composition matrix now validates 200 supported combinations.
154
+ - A fresh `node tests/test-generated-apps.mjs web-auth` completed initialization/install, generated `pnpm check` (including Fallow and dependency audit), build, real Vite/workerd web→API service binding, rendered auth screen, signup/login, protected session, invalid-password rejection, signout and revocation. Compiled Worker/Drizzle auth also passed against isolated in-memory SQLite; both generated Workers passed production-runtime local previews. Test data and credentials were synthetic/local; migrations were never applied to a configured production database.
155
+ - An isolated generated native Next.js/Vercel + Hono/Neon profile passed its full `pnpm check` and build after regeneration with the current scaffold. No live Neon database or protected Vercel-to-Cloudflare deployment was exercised. Its API URL and optional Access service credentials remain explicit deployment configuration.
156
+ - A copy of the original HEAD generator produced real old web-only, Hono-only and combined Hono/web/auth receipts. Current readiness accepted each; adding Resend preserved its API source and did not silently generate/migrate contracts. Pre-contracts Hono web/auth additions require an explicit migration.
157
+ - The five local skills in the main repository passed frontmatter/UI-metadata parsing and local-reference checks. Main repository `pnpm check` and `pnpm build` passed for the checked working state. Historical verification records remain intact.
158
+
159
+ The Expo/RevenueCat/Stripe sequence is a documented implementation roadmap, not generated native authentication, store purchases or verified billing behavior. No cloud provisioning, remote migrations, deployment, package publication or installed-plugin update occurred. Provider access/protection, native/device acceptance, store sandboxes and real billing remain separate verification work.
160
+
161
+ ## Maintenance practices — 2026-10-18
162
+
163
+ Added the software factory's evidence-driven maintenance workflow and connected it to the CLI's root `AGENTS.md`, contribution/PR guidance, shipped Anhedral skill and generated application instructions. It covers removal evidence for published/generated consumers, operational flag dependencies, focused changes, causal flaky-test diagnosis and controlled instruction comparisons. Existing uncommitted CI work was preserved. These instruction changes have not been evaluated through comparative agent task replays; no model cost or quality improvement is claimed.
164
+
165
+ Local CLI build, generator and plugin package contracts (`node --test tests/test-standard.test.mjs tests/test-plugin.test.mjs`, two tests passed), source hygiene, changed TypeScript formatting and `git diff --check` passed. Build refreshed bundled canonical references. Skill YAML parsing passed using the repository's YAML library, and package contracts checked bundled Markdown reference targets. The skill-creator Python validator could not start because PyYAML is unavailable. No full release gate, provider acceptance, publication or installed-plugin update was performed for this local workflow change.
166
+
167
+ ### CLI integration verification — 2026-10-18
168
+
169
+ Reviewed the pending maintenance guidance and documentation-only CI changes together with the Windows pnpm PATH fix. Ordinary contribution and PR-template Markdown now takes the documentation path; registry matrix preparation is skipped for that path. Source, shipped plugin instructions, unknown comparison history and manual runs retain full checks. Regression coverage includes source-to-document renames, whitespace failures, generated instructions preserving existing framework guidance, and earlier pnpm shims taking precedence over later native executables.
170
+
171
+ Local CLI and optional inspector builds passed with a 384 MB Node heap cap. All 16 targeted tests passed across CI scope, release-candidate policy, command execution, generated guidance, documentation contracts, plugin packaging/workflow and standard generation. Root lint (types, formatting, hygiene and release policy), static security policy, package allowlist (227 files, 607781 packed bytes) and `git diff --check` passed. The first plugin workflow check correctly rejected a stale runtime; rebuilding the inspector resolved it. Frozen inspector dependency installation changed no lockfiles. Build refreshed bundled references. Hosted CI, the full cross-platform/generated-app matrix, browser acceptance, current external advisory refresh, publication and installed-plugin updates were not performed in this focused pass.
172
+
5
173
  ## Release candidate 0.12.0 — 2026-10-16
6
174
 
7
175
  This candidate combines the CLI/service refactor with optional Cloudflare Stream live video and consolidated documentation. Stream supplies a server-only management factory; billing activation, input ownership, broadcast/player UI, signed playback and live media acceptance remain explicit integration work. The README links into three maintained documents: the stack standard, software factory and this dated evidence record. Provider, CLI, dashboard, Void and codebase-review material is retained in those documents; packaging and plugin references use the same sources.
@@ -442,3 +610,268 @@ The listener and empty-cache failures are environment limitations, not proven ap
442
610
  4. For an implemented product, verify protected business data, denied users, tenant isolation and any cross-app/native/extension identity flows. The scaffold's auth session smoke does not implement or certify those product behaviors.
443
611
 
444
612
  No provider resources, publication, production deployment or source commit were performed during this review. Detailed local evidence and prior pass results are recorded in `docs/verification.md`.
613
+
614
+
615
+ ## Progressive stack — local checkout, 2026-10-18
616
+
617
+ Plain initialization now selects Expo only. Capability dependencies resolve to a
618
+ fixed point; the compatible full-product preset includes Cloudflare AI, analytics,
619
+ media, realtime and jobs plus WXT, billing, email and monitoring. Existing edited
620
+ source and backend/delivery ownership remain protected. Legacy full-stack records
621
+ above describe earlier defaults and are retained as historical evidence.
622
+
623
+ Real generated `universal` (minimal) and `full-product` profiles passed dependency
624
+ installation and `pnpm check`, including lint, type checks, Fallow, dependency audit,
625
+ tests and builds. Full-product built Expo web, WXT, Hono and service Workers. These
626
+ were isolated temporary projects; no configured database was migrated or provider
627
+ resource deployed. The full-product check exposed unused helper dependencies and
628
+ duplicate transport code; shared server transport and lazy Hono adapters fixed the
629
+ actual findings without suppressing the generated checks.
630
+
631
+ Focused regressions exercise minimal selection, provider independence, preset
632
+ overrides, read-only previews, adding auth/billing without overwriting an edited
633
+ home screen, data added after service adapters, scoped media calls, private image
634
+ responses and redacted invalid provider JSON. The stack page's Mermaid diagram was
635
+ rendered locally. The six local plugin skills passed frontmatter/link validation.
636
+
637
+ Remaining acceptance: account/service activation and permissions, actual AI/event
638
+ receipt/image/video behavior, RealtimeKit calls, app room authorization, native
639
+ build/device/store flows and live payment reconciliation. No release, installation,
640
+ publication, production deployment or source commit was performed.
641
+
642
+ Final regression run: `pnpm test:unit` reported 750 tests, 748 passed, two skipped,
643
+ zero failures. `pnpm typecheck`, `pnpm format:check`, `pnpm check:hygiene`,
644
+ `pnpm check:security`, `pnpm check:release-policy`, CLI build and inspector/plugin
645
+ build passed. Additional growth coverage confirms direct billing additions retain
646
+ native RevenueCat key examples in the consuming app and preserve API-origin entries.
647
+
648
+ ## 0.13.0 release preparation
649
+
650
+ The candidate changes plain init to a minimal Expo app, adds dependency-resolving
651
+ capabilities and a full-product preset, and packages six focused skills with shared
652
+ plugin-wide references. README and the concise stack page use the same progressive
653
+ diagram. Historical generated reference apps retain their original provenance.
654
+
655
+ Local `pnpm release:check` passed: lint/typecheck/format/hygiene/release policy,
656
+ static security policy, refreshed OSV audit, 748 passing tests (two skipped), exact
657
+ braces/node-forge patch regressions, packed CLI installation and package allowlist.
658
+ `pnpm plugin:check` passed, including 62 inspector tests. Release artifact creation,
659
+ hosted CI and publication are recorded separately after they actually complete.
660
+
661
+ ### 2026-10-19 — release CI corrections and artifact reuse
662
+
663
+ - Hosted generated-profile checks exposed an unused web API-client stub in Clerk builds and Wrangler ready URLs without trailing slashes. Emit the web client/dependency only for its Better Auth consumer; normalize both Vite and Wrangler loopback URLs. Both Clerk profiles subsequently passed real local generation, check, build and Worker preview. Universal auth and billing reference previews passed with the corrected readiness parser.
664
+ - Provider-call assertions in billing fixtures now compare exact hostnames, addressing CodeQL substring findings without changing provider transport.
665
+ - Publication consumes the immutable candidate from successful trusted main CI for the exact reviewed SHA instead of reinstalling and rebuilding it. CLI/plugin integrity pins, secret scan, package smoke, cross-platform artifact checks, protected npm environment and OIDC publication remain required. Negative policy checks reject staging, PR-run or unpinned candidate selection.
666
+
667
+ ## 2026-10-21 — focused staging releases and CI tiers
668
+
669
+ Adopted topic PRs into `staging` and focused staging-to-main release PRs. Routine
670
+ code CI uses one Linux Node 24 CLI lane and one plugin lane; release candidates
671
+ retain supported Node, macOS/Windows, both plugin toolchains and all generated
672
+ profiles. Removed the duplicate E2E packed-CLI job. Stable `CI gate` fails on scope
673
+ errors or applicable failed/skipped jobs. Candidate upload is restricted to trusted
674
+ main CI. Reviewed-integrity dispatch, npm OIDC/provenance, immutable tags and
675
+ existing maintainer/CodeQL review requirements are preserved. Renovate targets staging.
676
+
677
+ Local build, typecheck, lint, release-policy and release-tooling checks passed.
678
+ Scope/promotion, candidate and plugin packaging regression checks passed. Full unit
679
+ suite passed with pinned pnpm 10.34.5: 750 passed, two optional runtime checks
680
+ skipped, zero failures. actionlint 1.7.12 passed (optional shellcheck/pyflakes disabled).
681
+ Initial checks caught a broken bundled relative documentation link and an obsolete
682
+ candidate-condition expectation; both were corrected. The host's pnpm 11 first
683
+ rejected the inspector's pnpm-10 override configuration; rerunning with the declared
684
+ version avoided a lockfile change. This is source/fixture evidence, not live provider
685
+ acceptance or a new npm publication. Adoption source takes effect on main after its
686
+ release PR merges; main remains the default branch.
687
+
688
+ Hosted adoption PR #39 subsequently exposed generated-project blockers: desktop
689
+ rejected Vite advisory GHSA-587h-7wmj-h5pm, and clients rejected duplicate affected
690
+ versions in advisory data. The generated dependency/advisory sources are unchanged
691
+ by this conventions diff; these failures are retained as release blockers for a
692
+ separate focused maintenance PR. Added fail-fast matrices and made portability/
693
+ generated jobs wait for primary checks to avoid spending on an already-failing
694
+ candidate. Hosted checks must pass before promotion/publication.
695
+
696
+ GitHub settings could not be applied: the authenticated account reports push access
697
+ but admin=false, and the attempted ruleset update returned HTTP 404. Existing rules
698
+ are unchanged. PR #39 lists the exact administrator prerequisites, including both
699
+ main rulesets, CI gate, merge commits and disabling automatic staging deletion.
700
+
701
+
702
+ ## 2026-10-21 correction — lightweight hosted checks on both branches
703
+
704
+ The owner clarified that large hosted checks are unacceptable on staging **and**
705
+ production. Earlier release-matrix proposals above are superseded. Automatic PR
706
+ CI now has one Linux CI gate on both branches; no full suite, generated project,
707
+ browser or platform matrix expands at promotion. Expensive validation is optional
708
+ and explicitly manual, or local. Main has no duplicate push check. CLI candidate
709
+ packaging is requested manually on main; publication keeps exact SHA/artifact,
710
+ secret/integrity, protected npm approval, provenance and tag checks while using a
711
+ single Linux artifact smoke lane instead of the six-job native matrix. Main repo
712
+ PRs fetch only the formatter, not the full application dependency graph. Its deploy
713
+ scripts no longer repeat full checks/tests, while retaining main/source guards,
714
+ affected-service detection and the selected app's necessary build/typecheck/upload.
715
+
716
+ The corrected lightweight CLI gate passed locally: compile, formatting, source
717
+ hygiene, static security/release policy, fast contract tests and release-tooling
718
+ negative paths. actionlint passed for automatic, manual-validation and publishing
719
+ workflows. The dependency/advisory repair remains a separate staging PR.
720
+
721
+ ## 2026-10-21 — generated dependency/advisory repair
722
+
723
+ Reproduced three live OSV findings on desktop's pinned Vite 7.3.6:
724
+ GHSA-587h-7wmj-h5pm, GHSA-698v-4r3x-3vcv and GHSA-r825-w8mm-5pxw.
725
+ The upstream repaired 7.x release is 7.3.7; the desktop recipe now pins it without
726
+ a major upgrade. Sources: https://github.com/advisories/GHSA-587h-7wmj-h5pm
727
+ and https://github.com/vitejs/vite/releases/tag/v7.3.7.
728
+
729
+ A real pnpm 10.34.5 clients audit also emitted two Vite 7.3.6 findings for the
730
+ extension and desktop dependency paths. Its severity metadata counted both
731
+ instances. The audit verifier now permits repeated versions at distinct paths,
732
+ preserves both counts and the raw report, and rejects duplicate version/path
733
+ entries. New regressions cover count mismatches, unknown high advisories and
734
+ exact reviewed-patch requirements with repeated versions. No advisory was added
735
+ to an exception list and no severity threshold changed.
736
+
737
+ Validation used Node 24.21.0 and pnpm 10.34.5. `pnpm test:all` passed: build, lint,
738
+ static security policy, live OSV audit of 110 locked/catalog coordinates, 751 unit
739
+ passes with two optional skips, frozen patch probes, packed CLI installation and
740
+ packlist checks. The 12 focused audit/scaffold checks passed. Fresh real desktop
741
+ and clients profiles passed generation, frozen install, lint/type/audit/tests/build
742
+ and unsigned macOS Electron packaging; clients also exercised Expo and WXT outputs.
743
+ The clients gate still requires its existing reviewed braces/node-forge patches;
744
+ raw advisories remain visible. Initial parallel generator runs collided in shadcn's
745
+ shared temporary clone directory; rerunning sequentially resolved that setup failure
746
+ without changing tests or adding retries. These results do not establish Windows,
747
+ Linux, signed macOS distribution or store acceptance. Hosted PR checks provide
748
+ separate evidence. This focused repair has no version bump or npm publication.
749
+
750
+
751
+ ## 2026-10-23 — Product family naming
752
+
753
+ Positioned Anhedral CLI as the starter foundation in the README and software factory, alongside Anhedral Platform, Anhedral Agents, and Anhedral Cloud. This documentation change does not publish a package or activate provider services. Validation: Git whitespace checks; canonical software-factory reference refreshed through the normal build.
754
+
755
+
756
+ ## 2026-10-23 — Generated audit dependency security recovery
757
+
758
+ The managed-email recovery release check refreshed OSV and found two advisories
759
+ against the existing generated Fallow 3.33.1 pin: GHSA-h4fr-cmh5-qr62 and
760
+ GHSA-jfwm-3p3c-6hx5. Both upstream advisories identify 3.34.0 as the patched
761
+ version. Pin the generated audit tool to that version; keep audit admission and
762
+ all existing security gates enabled. No provider resources or databases changed.
763
+
764
+ CLI build, lint/typecheck/format/hygiene/release policy, focused dependency/Next
765
+ contracts (11 tests) and refreshed OSV audit (61 locked/catalog versions) passed.
766
+ Publication of the integrated candidate remains separate.
767
+
768
+
769
+ ## 2026-10-23 — Managed authentication email recovery
770
+
771
+ Recover the scoped email adapter and verification/password-reset flows from the
772
+ preserved `4a48ca3` snapshot against the current Next web/native-only Expo stack.
773
+ Use an optional, fully validated API binding/scope/capability; empty standalone
774
+ setup retains current sessions, partial setup fails closed, and configured setup
775
+ requires verification with reset session revocation. All generated session
776
+ consumers pass the same server environment, including private files and billing.
777
+ The adapter uses deterministic send identities and bounded requests; broker error
778
+ bodies and credential/token-bearing transport errors never reach clients.
779
+
780
+ Next and native signup wait for verification rather than trying to open Account
781
+ without a session. Resend and reset flows use exact same-origin/native callbacks.
782
+ The framework-independent reset transport is shared through contracts; each
783
+ platform owns its controls. Nova Input/Label integrate with the reviewed form PR.
784
+
785
+ Validation: focused generator/broker/Next tests (8), complete CLI unit suite
786
+ (553 passed, one optional skip), unchanged CLI release gate including OSV, patch
787
+ regressions, packed CLI and packlist passed again on the final combined Nova/email/tooling source. The
788
+ installed generated core fixture passed full checks including Fallow, dependency
789
+ audit, types, lint, OpenNext/API builds; iOS/Android Hermes exports passed.
790
+ Compiled Worker plus real Better Auth/Drizzle/in-memory SQLite proved signup,
791
+ verification, denied unverified login, reset, single-use/expired tokens, session
792
+ revocation, incorrect password, unknown-user privacy, foreign callback denial and
793
+ exact native return scheme. Default unconfigured auth acceptance also passed.
794
+ Browser testing verified the signup prompt, verification link, authenticated
795
+ Account and sign-out with the isolated sink. No real email or configured database
796
+ was used. Physical-device, inbox delivery and hosted-image activation are separate.
797
+
798
+ Initial checks retained failures for synthetic email strings in the security
799
+ scanner, screen/adapter complexity and cross-platform duplication; fixture
800
+ addresses were assembled and shared reset transport extracted without relaxing
801
+ checks. Fresh advisory refresh required separately reviewed Fallow, Expo-Zod and
802
+ Miniflare-Undici fixes. A local UI HTTP harness initially wrote cookie headers
803
+ after committing response headers; fixing that fixture restored sign-in. The
804
+ product's compiled-Worker authentication tests already passed independently.
805
+
806
+ ## 2026-10-23 — Nova authentication form recovery
807
+
808
+ The current Next/native default already contains the recovered native shadcn
809
+ foundation and Base Nova Button (#49). Recover the source-owned Base UI Nova
810
+ Input and Label from the retained CLI snapshot and use them on generated web
811
+ sign-in forms. Preserve the existing MIT notice and upstream provenance hashes;
812
+ adapt only the local utility import, client boundary and focus ownership. Input
813
+ delegates keyboard focus to the generated global rule rather than adding a
814
+ second focus-only border/ring layer. Other historical components remain preserved
815
+ in the recovery branch and are not installed as unused starter code.
816
+
817
+ CLI build/lint/typecheck/format/hygiene and five Next contract tests passed.
818
+ The integrated generated web fixture passed Next route/type generation and lint
819
+ with these recovered controls. Browser interaction and final integrated release
820
+ checks are recorded with the managed-email recovery.
821
+
822
+ ## 2026-10-23 — Expo CLI validation dependency recovery
823
+
824
+ A fresh installed core fixture failed the unchanged dependency audit on
825
+ GHSA-mrhx-c7xc-m3w5: Expo CLI 57.0.32 pulls Zod 3.25.76 although application
826
+ contracts already use patched Zod 4.6.6. Add a narrow @expo/cli>zod override to
827
+ the existing catalog pin. Expo SDK stays at 57. Audit admission remains enabled.
828
+ The actual CLI plugin/MCP schemas and native exports are tested before promotion;
829
+ this does not claim upstream Expo has migrated its declared range.
830
+
831
+ The next audit also identified GHSA-xjj6-f33q-929c in Miniflare's Undici
832
+ 7.29.1. A same-major, consumer-scoped miniflare>undici 7.30.1 override uses
833
+ the upstream patched version and also removes the related moderate Undici
834
+ findings. No high/critical advisory is waived. Existing exact reviewed
835
+ node-forge/braces patches remain unchanged.
836
+
837
+ The installed generated core fixture passed the unchanged high/critical audit
838
+ gate with only the existing exact verified node-forge patch acceptance. Both
839
+ Hermes native exports passed. The actual Expo plugin and MCP schemas passed
840
+ positive/negative parsing against scoped Zod 4.6.6; CLI build/lint and 11 focused
841
+ contract tests passed, and OSV passed for 62 locked/catalog versions.
842
+
843
+ Final integrated acceptance: the unchanged full CLI release gate passed, including
844
+ 553 unit passes/one optional skip, refreshed OSV (62 locked/catalog versions),
845
+ exact patch regressions, packed installation and strict packlist (249 files).
846
+ Inspector/plugin check passed all 61 tests. Both core and Stripe+RevenueCat
847
+ generated profiles passed full local checks and builds. The payment profile also
848
+ passed real workerd SSR/RSC, protected account, D1 session/revocation, native
849
+ scheme/origin rejection, compiled email acceptance and synthetic billing tests.
850
+ The 28 generated browser JavaScript assets contain no managed-email broker
851
+ configuration/module or native purchase modules. Browser reset-request confirmation
852
+ passed; native exports do not establish physical-device acceptance.
853
+
854
+ The final strict packlist initially rejected the recovered Input/Label paths;
855
+ PR #62 requires and allowlists exactly those two files without widening exclusions.
856
+ Nova form recovery is #60; security prerequisites are #58/#59. Storage safeguards
857
+ were already recovered/shipped as anhedral-main#201: nine regressions, root
858
+ check (26 tasks) and serial root build (five tasks) passed again at Platform
859
+ source 822825e9; later observed staging changes did not touch those safeguards.
860
+ No Comms source, retained recovery snapshot or stash was changed by this work.
861
+ Publication and provider state are verified separately after promotion.
862
+
863
+ Final React review gives web/native reset forms a token/error-derived route key,
864
+ so following a new recovery link resets prior completion, input and error state.
865
+ Only the used token/error fields cross the Next server/client boundary.
866
+
867
+
868
+ ## 2026-10-23 — Immutable release smoke prerequisite
869
+
870
+ The first 0.15.0 publication attempt (run 40056207567, source 4557627f) stopped
871
+ before npm publishing. Hash and secret checks passed; exact-artifact smoke failed
872
+ while spawning pnpm for the installed CLI's normal initialization. Main candidate
873
+ CI had pnpm setup, but the isolated release verification and exact-artifact jobs
874
+ provisioned only Node. Add the same pinned pnpm action/version to those jobs, with
875
+ run_install disabled. Keep normal init, artifact integrity, npm environment/OIDC
876
+ and exact-artifact checks intact. A workflow regression covers all three smoke
877
+ locations. A fresh main candidate must be reviewed again after this correction.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "anhedral",
3
- "version": "0.12.0",
4
- "description": "Build and deliver applications with Cloudflare-first Vinext, selected services, optional Next.js on Vercel, and verified release evidence.",
3
+ "version": "0.15.0",
4
+ "description": "Create a Next.js web + native Expo + Hono + Drizzle/D1 + private R2 application. Add Stripe and RevenueCat when needed.",
5
5
  "type": "module",
6
6
  "exports": {
7
7
  ".": {
@@ -25,7 +25,11 @@
25
25
  "README.md",
26
26
  "docs/stack-standard.md",
27
27
  "docs/software-factory.md",
28
- "docs/verification.md"
28
+ "docs/verification.md",
29
+ "docs/anhedral-stack.md",
30
+ "docs/assets/anhedral-stack.png",
31
+ "docs/assets/anhedral-stack-light.png",
32
+ "assets/ui"
29
33
  ],
30
34
  "homepage": "https://github.com/anhedral/anhedral-cli#readme",
31
35
  "repository": {
@@ -58,6 +62,7 @@
58
62
  "pretest": "pnpm build",
59
63
  "prepublishOnly": "pnpm test:all",
60
64
  "test:cli:validation": "node --test tests/test-cli-validation.test.mjs",
65
+ "test:contracts:types": "node tests/test-generated-contracts-types.mjs",
61
66
  "test:pack": "pnpm build && node tests/test-packed-cli.js",
62
67
  "test:pack:exact": "node tests/test-packed-cli.js .artifacts/release/metadata.json",
63
68
  "test:packlist": "pnpm build && node tests/test-packlist.js",
@@ -70,46 +75,42 @@
70
75
  "test:standard": "pnpm build && node --test tests/test-standard.test.mjs",
71
76
  "test:unit": "node scripts/prepare-test-runtime.mjs && node --test --test-concurrency=4 --test-reporter=spec tests/*.test.mjs",
72
77
  "test:integration": "pnpm build && node tests/test-generated-apps.mjs",
73
- "test:runtime:void": "node tests/test-void-runtime.mjs",
74
- "test:runtime:void:generated": "node tests/test-void-runtime-generated.mjs",
75
78
  "test:live:delivery": "pnpm build && node tests/test-live-delivery.mjs",
76
- "test:live:vercel": "pnpm build && node tests/test-live-vercel.mjs",
77
- "test:live:vercel:git": "pnpm build && node tests/test-live-vercel-git.mjs",
78
- "format": "prettier --write src scripts tests plugins/codex/inspector \"assets/patches/*.mjs\"",
79
- "format:check": "prettier --check src scripts tests plugins/codex/inspector \"assets/patches/*.mjs\"",
79
+ "format": "prettier --write src scripts tests plugins/codex/inspector \"assets/patches/*.mjs\" assets/ui",
80
+ "format:check": "prettier --check src scripts tests plugins/codex/inspector \"assets/patches/*.mjs\" assets/ui",
80
81
  "plugin:build": "pnpm --dir plugins/codex/inspector build",
81
82
  "plugin:check": "pnpm --dir plugins/codex/inspector check",
82
83
  "plugin:preview": "pnpm --dir plugins/codex/inspector start",
83
- "test:patch": "node tests/test-braces-install.mjs && node tests/test-forge-install.mjs"
84
+ "test:patch": "node tests/test-braces-install.mjs && node tests/test-forge-install.mjs",
85
+ "test:billing": "node tests/test-generated-apps.mjs billing"
84
86
  },
85
87
  "keywords": [
86
88
  "cli",
87
89
  "scaffold",
88
90
  "typescript",
89
- "nextjs",
91
+ "expo",
90
92
  "hono",
91
93
  "cloudflare",
92
- "opennext",
93
- "expo",
94
- "electron",
95
- "wxt",
96
- "neon",
94
+ "d1",
95
+ "r2",
97
96
  "drizzle",
98
- "shadcn",
97
+ "stripe",
98
+ "revenuecat",
99
99
  "turborepo",
100
- "vinext"
100
+ "nextjs",
101
+ "opennext"
101
102
  ],
102
103
  "license": "Apache-2.0",
103
104
  "packageManager": "pnpm@10.34.5",
104
105
  "devDependencies": {
105
106
  "@types/node": "20.19.43",
107
+ "hono": "4.13.13",
106
108
  "prettier": "3.9.10",
107
109
  "typescript": "5.9.3"
108
110
  },
109
111
  "dependencies": {
110
- "@neondatabase/serverless": "1.2.0",
111
112
  "jsonc-parser": "3.3.1",
112
- "zod": "4.6.6",
113
- "yaml": "2.9.1"
113
+ "yaml": "2.9.1",
114
+ "zod": "4.6.6"
114
115
  }
115
116
  }
@@ -1,8 +0,0 @@
1
- import { neon } from '@neondatabase/serverless';
2
- import type { ApiRequest } from './providers/api.js';
3
- import { type IntegrationService } from './integration-service-readers.js';
4
- import type { ServiceData } from './service-model.js';
5
- export type NeonRead = (query: string, params?: unknown[]) => Promise<Record<string, unknown>[]>;
6
- export declare function neonReadConnection(service: IntegrationService, api: ApiRequest, env?: NodeJS.ProcessEnv, createClient?: typeof neon): Promise<NeonRead>;
7
- export declare function listNeonTables(read: NeonRead): Promise<string[]>;
8
- export declare function browseNeonData(read: NeonRead, table: string, offset?: number): Promise<ServiceData>;