anhedral 0.13.0 → 0.16.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 (360) hide show
  1. package/README.md +23 -229
  2. package/assets/patches/audit-deps.mjs +12 -2
  3. package/assets/stack/ai-schema.ts.txt +5 -0
  4. package/assets/stack/ai.ts.txt +30 -0
  5. package/assets/stack/api-index.ts.txt +15 -0
  6. package/assets/stack/auth-features.ts.txt +4 -0
  7. package/assets/stack/auth-journal.json.txt +13 -0
  8. package/assets/stack/auth-migration.sql.txt +53 -0
  9. package/assets/stack/auth-routes.ts.txt +11 -0
  10. package/assets/stack/auth-schema.ts.txt +64 -0
  11. package/assets/stack/auth-snapshot.json.txt +346 -0
  12. package/assets/stack/auth.ts.txt +32 -0
  13. package/assets/stack/billing-mode.ts.txt +8 -0
  14. package/assets/stack/billing-schema.ts.txt +11 -0
  15. package/assets/stack/desktop.rs.txt +21 -0
  16. package/assets/stack/entitlement-guard.ts.txt +32 -0
  17. package/assets/stack/entitlements.ts.txt +8 -0
  18. package/assets/stack/events-schema.ts.txt +12 -0
  19. package/assets/stack/events.ts.txt +59 -0
  20. package/assets/stack/mobile-auth.ts.txt +25 -0
  21. package/assets/stack/mobile-billing.tsx.txt +63 -0
  22. package/assets/stack/mobile-session.tsx.txt +83 -0
  23. package/assets/stack/native-button.tsx.txt +108 -0
  24. package/assets/stack/native-global.css.txt +4 -0
  25. package/assets/stack/native-lib-utils.ts.txt +5 -0
  26. package/assets/stack/native-metro.config.js.txt +6 -0
  27. package/assets/stack/native-nativewind-env.d.ts.txt +1 -0
  28. package/assets/stack/native-tailwind.config.js.txt +73 -0
  29. package/assets/stack/native-text.tsx.txt +89 -0
  30. package/assets/stack/purchases.ts.txt +65 -0
  31. package/assets/stack/revenuecat.ts.txt +88 -0
  32. package/assets/stack/rtc-schema.ts.txt +10 -0
  33. package/assets/stack/rtc.ts.txt +122 -0
  34. package/assets/stack/security.ts.txt +31 -0
  35. package/assets/stack/storage.ts.txt +36 -0
  36. package/assets/stack/stripe.ts.txt +126 -0
  37. package/assets/stack/web-sign-in.tsx.txt +51 -0
  38. package/assets/ui/LICENSE.react-native-reusables +21 -0
  39. package/assets/ui/LICENSE.shadcn +21 -0
  40. package/assets/ui/UPSTREAM.json +39 -0
  41. package/assets/ui/catalog.json +891 -0
  42. package/assets/ui/extensions/registry.json +6 -0
  43. package/assets/ui/native/_controls.tsx +521 -0
  44. package/assets/ui/native/_core.tsx +118 -0
  45. package/assets/ui/native/_data.tsx +200 -0
  46. package/assets/ui/native/_display.tsx +453 -0
  47. package/assets/ui/native/_feedback.tsx +242 -0
  48. package/assets/ui/native/_legacy-dialog.tsx +38 -0
  49. package/assets/ui/native/_motion.tsx +520 -0
  50. package/assets/ui/native/_overlay.tsx +402 -0
  51. package/assets/ui/native/_selection.tsx +366 -0
  52. package/assets/ui/native/accordion.tsx +1 -0
  53. package/assets/ui/native/alert-dialog.tsx +11 -0
  54. package/assets/ui/native/alert.tsx +1 -0
  55. package/assets/ui/native/aspect-ratio.tsx +1 -0
  56. package/assets/ui/native/attachment.tsx +8 -0
  57. package/assets/ui/native/avatar.tsx +8 -0
  58. package/assets/ui/native/badge.tsx +1 -0
  59. package/assets/ui/native/breadcrumb.tsx +9 -0
  60. package/assets/ui/native/bubble.tsx +1 -0
  61. package/assets/ui/native/button-group.tsx +1 -0
  62. package/assets/ui/native/button.tsx +86 -0
  63. package/assets/ui/native/calendar.tsx +170 -0
  64. package/assets/ui/native/card.tsx +44 -0
  65. package/assets/ui/native/carousel.tsx +1 -0
  66. package/assets/ui/native/chart.tsx +193 -0
  67. package/assets/ui/native/checkbox.tsx +1 -0
  68. package/assets/ui/native/code-block.tsx +137 -0
  69. package/assets/ui/native/collapsible.tsx +1 -0
  70. package/assets/ui/native/combobox.tsx +1 -0
  71. package/assets/ui/native/command.tsx +11 -0
  72. package/assets/ui/native/context-menu.tsx +16 -0
  73. package/assets/ui/native/data-table.tsx +1 -0
  74. package/assets/ui/native/date-picker.tsx +43 -0
  75. package/assets/ui/native/dialog.tsx +15 -0
  76. package/assets/ui/native/direction.tsx +1 -0
  77. package/assets/ui/native/drawer.tsx +10 -0
  78. package/assets/ui/native/dropdown-menu.tsx +16 -0
  79. package/assets/ui/native/empty.tsx +8 -0
  80. package/assets/ui/native/field.tsx +13 -0
  81. package/assets/ui/native/hover-card.tsx +1 -0
  82. package/assets/ui/native/input-group.tsx +8 -0
  83. package/assets/ui/native/input-otp.tsx +1 -0
  84. package/assets/ui/native/input.tsx +28 -0
  85. package/assets/ui/native/item.tsx +12 -0
  86. package/assets/ui/native/kbd.tsx +1 -0
  87. package/assets/ui/native/label.tsx +4 -0
  88. package/assets/ui/native/layout.tsx +26 -0
  89. package/assets/ui/native/marker.tsx +1 -0
  90. package/assets/ui/native/menubar.tsx +17 -0
  91. package/assets/ui/native/message-scroller.tsx +6 -0
  92. package/assets/ui/native/message.tsx +10 -0
  93. package/assets/ui/native/native-select.tsx +1 -0
  94. package/assets/ui/native/navigation-menu.tsx +10 -0
  95. package/assets/ui/native/pagination.tsx +9 -0
  96. package/assets/ui/native/popover.tsx +1 -0
  97. package/assets/ui/native/progress.tsx +1 -0
  98. package/assets/ui/native/questionnaire.tsx +130 -0
  99. package/assets/ui/native/radio-group.tsx +1 -0
  100. package/assets/ui/native/registry.json +1103 -0
  101. package/assets/ui/native/resizable.tsx +1 -0
  102. package/assets/ui/native/scroll-area.tsx +1 -0
  103. package/assets/ui/native/select.tsx +11 -0
  104. package/assets/ui/native/separator.tsx +1 -0
  105. package/assets/ui/native/sheet.tsx +10 -0
  106. package/assets/ui/native/sidebar.tsx +22 -0
  107. package/assets/ui/native/skeleton.tsx +1 -0
  108. package/assets/ui/native/slider.tsx +1 -0
  109. package/assets/ui/native/spinner.tsx +1 -0
  110. package/assets/ui/native/switch.tsx +1 -0
  111. package/assets/ui/native/table.tsx +10 -0
  112. package/assets/ui/native/tabs.tsx +1 -0
  113. package/assets/ui/native/text.tsx +20 -0
  114. package/assets/ui/native/textarea.tsx +1 -0
  115. package/assets/ui/native/theme-switcher.tsx +22 -0
  116. package/assets/ui/native/toast.tsx +11 -0
  117. package/assets/ui/native/toggle-group.tsx +1 -0
  118. package/assets/ui/native/toggle.tsx +1 -0
  119. package/assets/ui/native/tooltip.tsx +1 -0
  120. package/assets/ui/native/trace.tsx +20 -0
  121. package/assets/ui/native/typography.tsx +15 -0
  122. package/assets/ui/theme-storage.ts +25 -0
  123. package/assets/ui/theme.tsx +66 -0
  124. package/assets/ui/web/button.tsx +59 -0
  125. package/assets/ui/web/input.tsx +21 -0
  126. package/assets/ui/web/label.tsx +19 -0
  127. package/dist/bin.js +7 -12
  128. package/dist/capabilities.d.ts +4 -33
  129. package/dist/capabilities.js +2 -84
  130. package/dist/capability-catalog.d.ts +83 -0
  131. package/dist/capability-catalog.js +121 -0
  132. package/dist/capability-command.d.ts +3 -0
  133. package/dist/capability-command.js +188 -0
  134. package/dist/capability-editor.d.ts +17 -0
  135. package/dist/capability-editor.js +97 -0
  136. package/dist/capability-recipes.d.ts +4 -0
  137. package/dist/capability-recipes.js +520 -0
  138. package/dist/capability-references.d.ts +4 -0
  139. package/dist/capability-references.js +7 -0
  140. package/dist/cli-commands.d.ts +1 -2
  141. package/dist/cli-commands.js +10 -104
  142. package/dist/cli-output.d.ts +1 -2
  143. package/dist/cli-output.js +6 -251
  144. package/dist/command-schema.js +40 -374
  145. package/dist/dependencies.d.ts +34 -62
  146. package/dist/dependencies.js +112 -199
  147. package/dist/index.d.ts +1 -45
  148. package/dist/index.js +1 -30
  149. package/dist/platforms/mobile.js +29 -139
  150. package/dist/platforms/web.d.ts +3 -0
  151. package/dist/platforms/web.js +251 -0
  152. package/dist/project-config.d.ts +2 -13
  153. package/dist/project-config.js +10 -83
  154. package/dist/registry/context.js +0 -1
  155. package/dist/registry/options.js +6 -40
  156. package/dist/registry/resolve.d.ts +3 -4
  157. package/dist/registry/resolve.js +18 -108
  158. package/dist/registry/types.d.ts +1 -7
  159. package/dist/registry/usage.js +3 -9
  160. package/dist/runtime-policy.d.ts +0 -2
  161. package/dist/runtime-policy.js +0 -16
  162. package/dist/scaffold/backend.d.ts +0 -4
  163. package/dist/scaffold/backend.js +1 -189
  164. package/dist/scaffold/bootstrap.d.ts +2 -3
  165. package/dist/scaffold/bootstrap.js +37 -43
  166. package/dist/scaffold/compose.js +2 -14
  167. package/dist/scaffold/database.d.ts +1 -1
  168. package/dist/scaffold/database.js +19 -126
  169. package/dist/scaffold/documentation.d.ts +0 -1
  170. package/dist/scaffold/documentation.js +82 -84
  171. package/dist/scaffold/expo-runtime.d.ts +2 -2
  172. package/dist/scaffold/expo-runtime.js +9 -101
  173. package/dist/scaffold/native-ui.d.ts +2 -0
  174. package/dist/scaffold/native-ui.js +74 -0
  175. package/dist/scaffold/stack-documentation.d.ts +0 -1
  176. package/dist/scaffold/stack-documentation.js +3 -49
  177. package/dist/scaffold/storage.d.ts +2 -0
  178. package/dist/scaffold/storage.js +21 -0
  179. package/dist/scaffold/styling.d.ts +1 -1
  180. package/dist/scaffold/styling.js +20 -28
  181. package/dist/scaffold/workspace.js +63 -199
  182. package/dist/stack-registry.d.ts +2 -58
  183. package/dist/stack-registry.js +22 -446
  184. package/dist/standard.js +7 -24
  185. package/dist/ui-catalog.d.ts +26 -0
  186. package/dist/ui-catalog.js +31 -0
  187. package/dist/ui-command.d.ts +3 -0
  188. package/dist/ui-command.js +219 -0
  189. package/dist/ui-project.d.ts +22 -0
  190. package/dist/ui-project.js +110 -0
  191. package/dist/version.d.ts +1 -1
  192. package/dist/version.js +1 -1
  193. package/docs/anhedral-stack.md +4 -119
  194. package/docs/capabilities.md +110 -0
  195. package/docs/native-ui.md +102 -0
  196. package/docs/software-factory.md +16 -577
  197. package/docs/stack-standard.md +11 -307
  198. package/docs/ui.md +33 -0
  199. package/docs/verification.md +511 -0
  200. package/package.json +26 -27
  201. package/dist/access.d.ts +0 -10
  202. package/dist/access.js +0 -93
  203. package/dist/auth-schema-snapshot.d.ts +0 -346
  204. package/dist/auth-schema-snapshot.js +0 -347
  205. package/dist/auth-schema.d.ts +0 -1
  206. package/dist/auth-schema.js +0 -57
  207. package/dist/capability-contract.d.ts +0 -47
  208. package/dist/capability-contract.js +0 -168
  209. package/dist/catalog-model.d.ts +0 -24
  210. package/dist/catalog-model.js +0 -1
  211. package/dist/catalog-registration.d.ts +0 -16
  212. package/dist/catalog-registration.js +0 -22
  213. package/dist/catalog-snapshot.d.ts +0 -5
  214. package/dist/catalog-snapshot.js +0 -97
  215. package/dist/cli-delivery.d.ts +0 -3
  216. package/dist/cli-delivery.js +0 -172
  217. package/dist/cloudflare.d.ts +0 -25
  218. package/dist/cloudflare.js +0 -226
  219. package/dist/delivery-evidence.d.ts +0 -62
  220. package/dist/delivery-evidence.js +0 -186
  221. package/dist/delivery.d.ts +0 -88
  222. package/dist/delivery.js +0 -570
  223. package/dist/inspector-model.d.ts +0 -123
  224. package/dist/inspector-model.js +0 -1
  225. package/dist/integration-service-readers.d.ts +0 -13
  226. package/dist/integration-service-readers.js +0 -173
  227. package/dist/lifecycle-model.d.ts +0 -15
  228. package/dist/lifecycle-model.js +0 -20
  229. package/dist/lifecycle.d.ts +0 -11
  230. package/dist/lifecycle.js +0 -91
  231. package/dist/management.d.ts +0 -3
  232. package/dist/management.js +0 -47
  233. package/dist/mobile-delivery.d.ts +0 -77
  234. package/dist/mobile-delivery.js +0 -366
  235. package/dist/neon-service-data.d.ts +0 -8
  236. package/dist/neon-service-data.js +0 -117
  237. package/dist/platforms/desktop.d.ts +0 -2
  238. package/dist/platforms/desktop.js +0 -415
  239. package/dist/platforms/extension.d.ts +0 -2
  240. package/dist/platforms/extension.js +0 -328
  241. package/dist/project-catalog.d.ts +0 -41
  242. package/dist/project-catalog.js +0 -288
  243. package/dist/project-inspector.d.ts +0 -4
  244. package/dist/project-inspector.js +0 -702
  245. package/dist/project-lifecycle.d.ts +0 -25
  246. package/dist/project-lifecycle.js +0 -57
  247. package/dist/project-state.d.ts +0 -49
  248. package/dist/project-state.js +0 -563
  249. package/dist/provider-auth.d.ts +0 -41
  250. package/dist/provider-auth.js +0 -215
  251. package/dist/provider-readiness.d.ts +0 -30
  252. package/dist/provider-readiness.js +0 -104
  253. package/dist/providers/adapters.d.ts +0 -17
  254. package/dist/providers/adapters.js +0 -278
  255. package/dist/providers/api.d.ts +0 -29
  256. package/dist/providers/api.js +0 -253
  257. package/dist/providers/config.d.ts +0 -15
  258. package/dist/providers/config.js +0 -182
  259. package/dist/providers/definitions.d.ts +0 -318
  260. package/dist/providers/definitions.js +0 -127
  261. package/dist/providers/provision.d.ts +0 -24
  262. package/dist/providers/provision.js +0 -76
  263. package/dist/providers/receipts.d.ts +0 -20
  264. package/dist/providers/receipts.js +0 -66
  265. package/dist/providers/recovery-verification.d.ts +0 -7
  266. package/dist/providers/recovery-verification.js +0 -112
  267. package/dist/providers/recovery.d.ts +0 -30
  268. package/dist/providers/recovery.js +0 -34
  269. package/dist/providers/runtime.d.ts +0 -10
  270. package/dist/providers/runtime.js +0 -265
  271. package/dist/providers/schema.d.ts +0 -28
  272. package/dist/providers/schema.js +0 -49
  273. package/dist/providers/state.d.ts +0 -55
  274. package/dist/providers/state.js +0 -289
  275. package/dist/provision.d.ts +0 -55
  276. package/dist/provision.js +0 -284
  277. package/dist/r2-service-data.d.ts +0 -2
  278. package/dist/r2-service-data.js +0 -136
  279. package/dist/readiness.d.ts +0 -23
  280. package/dist/readiness.js +0 -122
  281. package/dist/registry/add.d.ts +0 -24
  282. package/dist/registry/add.js +0 -270
  283. package/dist/registry/bootstrap.d.ts +0 -2
  284. package/dist/registry/bootstrap.js +0 -14
  285. package/dist/registry/commands.d.ts +0 -3
  286. package/dist/registry/commands.js +0 -85
  287. package/dist/registry/presets.d.ts +0 -4
  288. package/dist/registry/presets.js +0 -41
  289. package/dist/registry/preview.d.ts +0 -11
  290. package/dist/registry/preview.js +0 -91
  291. package/dist/registry/receipt.d.ts +0 -3
  292. package/dist/registry/receipt.js +0 -68
  293. package/dist/repository.d.ts +0 -24
  294. package/dist/repository.js +0 -96
  295. package/dist/scaffold/auth.d.ts +0 -3
  296. package/dist/scaffold/auth.js +0 -151
  297. package/dist/scaffold/billing-config.d.ts +0 -1
  298. package/dist/scaffold/billing-config.js +0 -73
  299. package/dist/scaffold/billing-contracts.d.ts +0 -2
  300. package/dist/scaffold/billing-contracts.js +0 -48
  301. package/dist/scaffold/billing-providers.d.ts +0 -1
  302. package/dist/scaffold/billing-providers.js +0 -249
  303. package/dist/scaffold/billing-schema.d.ts +0 -1
  304. package/dist/scaffold/billing-schema.js +0 -34
  305. package/dist/scaffold/billing-security.d.ts +0 -1
  306. package/dist/scaffold/billing-security.js +0 -46
  307. package/dist/scaffold/billing-server.d.ts +0 -1
  308. package/dist/scaffold/billing-server.js +0 -139
  309. package/dist/scaffold/billing-store.d.ts +0 -1
  310. package/dist/scaffold/billing-store.js +0 -72
  311. package/dist/scaffold/billing.d.ts +0 -2
  312. package/dist/scaffold/billing.js +0 -216
  313. package/dist/scaffold/cloudflare-services.d.ts +0 -8
  314. package/dist/scaffold/cloudflare-services.js +0 -198
  315. package/dist/scaffold/expo-auth.d.ts +0 -3
  316. package/dist/scaffold/expo-auth.js +0 -192
  317. package/dist/scaffold/expo-billing.d.ts +0 -3
  318. package/dist/scaffold/expo-billing.js +0 -292
  319. package/dist/scaffold/integrations.d.ts +0 -4
  320. package/dist/scaffold/integrations.js +0 -12
  321. package/dist/scaffold/lint.d.ts +0 -4
  322. package/dist/scaffold/lint.js +0 -56
  323. package/dist/scaffold/neon-realtime.d.ts +0 -2
  324. package/dist/scaffold/neon-realtime.js +0 -97
  325. package/dist/scaffold/services.d.ts +0 -5
  326. package/dist/scaffold/services.js +0 -108
  327. package/dist/scaffold/stream.d.ts +0 -2
  328. package/dist/scaffold/stream.js +0 -114
  329. package/dist/scaffold/void.d.ts +0 -4
  330. package/dist/scaffold/void.js +0 -264
  331. package/dist/scaffold/web.d.ts +0 -2
  332. package/dist/scaffold/web.js +0 -130
  333. package/dist/service-deletion.d.ts +0 -29
  334. package/dist/service-deletion.js +0 -195
  335. package/dist/service-descriptor.d.ts +0 -10
  336. package/dist/service-descriptor.js +0 -78
  337. package/dist/service-model.d.ts +0 -49
  338. package/dist/service-model.js +0 -8
  339. package/dist/service-operations.d.ts +0 -29
  340. package/dist/service-operations.js +0 -78
  341. package/dist/service-readers.d.ts +0 -8
  342. package/dist/service-readers.js +0 -247
  343. package/dist/services-command.d.ts +0 -39
  344. package/dist/services-command.js +0 -102
  345. package/dist/ship.d.ts +0 -348
  346. package/dist/ship.js +0 -239
  347. package/dist/vercel-project.d.ts +0 -101
  348. package/dist/vercel-project.js +0 -305
  349. package/dist/vercel.d.ts +0 -67
  350. package/dist/vercel.js +0 -581
  351. package/dist/vinext.d.ts +0 -2
  352. package/dist/vinext.js +0 -86
  353. package/dist/void-execution.d.ts +0 -10
  354. package/dist/void-execution.js +0 -94
  355. package/dist/void-migrations.d.ts +0 -6
  356. package/dist/void-migrations.js +0 -110
  357. package/dist/void-state.d.ts +0 -16
  358. package/dist/void-state.js +0 -65
  359. package/dist/void.d.ts +0 -3
  360. package/dist/void.js +0 -5
@@ -1,7 +1,160 @@
1
+ # Progressive init and thin Anhedral UI — October 26, 2026
2
+
3
+ Prepared on `codex/progressive-ui` from staging `97c4f28` in an isolated checkout. The primary checkout's ongoing native port is preserved. New init generates only Next.js/OpenNext/Workers with editable Anhedral UI (three reviewed web starter components), shared tokens and tooling. The CLI adds ui init/add/list/diff/doctor, a packaged upstream catalog and an empty reviewed native extension registry. Web uses official shadcn; native falls back to RNR NativeWind 4. No new whole-library fork or runtime UI package is introduced. Existing Platform pins and installed plugins are unchanged.
4
+
5
+ Validation: CLI build; 106 unit tests passed with zero failures and one existing conditional skip; lint/typecheck/format/hygiene/release policy; static security; plugin package; packed consumer; and packlist checks. A real generated web consumer installed official Card, passed typecheck/lint and built an OpenNext Worker. Repeated add preserved a customization in Card; diff preview reported it. A real two-conflict batch and an offline colored-prompt regression verify that the wrapper declines each overwrite and closes installer input after the completed file report. The compiled minimal runtime smoke passed prerender, SSR/RSC, server action/cookie round-trip and asset headers, and confirmed that no backend API exists. Measured Worker: 4,877,700 raw bytes / 1,000,286 individually gzipped bytes, below 4 MiB. The fresh minimal generated consumer also passed its full pnpm check and cold/warm Next type-generation cache restoration. Retained Hono proxy and explicit legacy full-stack/native source tests remain separate.
6
+
7
+ A prepared Expo 56 / React Native 0.85.3 / React 19.2.3 / NativeWind 4.2.7 consumer used native ui init and installed RNR Button plus its Text/slot dependency. It passed TypeScript and an iOS Metro/Hermes export. The first export identified a missing direct react-native-css-interop dependency under pnpm; adding the matching NativeWind dependency to this fixture resolved it. This is consumer setup evidence, not a new native project generator or device acceptance claim. Fixtures and logs are retained locally under `.artifacts/progressive-{web,native}` and `/tmp/anhedral-progressive-*`; they are not shipped assets.
8
+
9
+ The first hosted CI run failed because the retained native harness still invoked default init and expected packages/native-ui. Its fixture now selects the explicit legacy recipe; the public default remains minimal. The generated cache helper likewise handles web-only projects. After the harness correction, the preserved legacy native suite passed typechecking and 144 tests on each simulated platform (iOS and Android); these are RNTL tests, not device acceptance. The original failure log is retained locally at /tmp/anhedral-progressive-ci-failure.log.
10
+
11
+ Limits: native init requires upstream Expo/NativeWind/RNR setup, uses one styling engine, and does not rewrite native app layouts. Catalog availability is not parity. Registry endpoints remain live upstream sources; the inventory revision is not a downloaded-source integrity pin. Cross-target preflight prevents setup errors from mutating earlier targets, but upstream installs are not a cross-project transaction. No Android/iOS interaction acceptance, exhaustive native suite, live provider checks, remote migrations, package publication, installed-plugin update or Platform artifact adoption was performed. Release checks and version preparation remain required before publication.
12
+
13
+ # UI source and Expo SDK boundaries — October 25, 2026
14
+
15
+ Prepared on an isolated branch from staging `5e211c0`, coordinated with the active native UI chat. The stack standard, generated README/AGENTS guidance and design skill now distinguish editable reviewed DOM/native source, shared tokens, the upstream review fork, host-owned Expo/React Native/React peers and direct Expo SDK capability usage. Application permissions, background work, uploads and push registration remain application responsibilities. Expo UI adoption is selective; custom native bridges and the ongoing native port are preserved.
16
+
17
+ Validation: CLI build; all four standard scaffold tests; lint/typecheck/format/hygiene/release policy; static security; skills-only plugin check; skill frontmatter validation; and packlist policy (189 files, 462,179 packed bytes) passed. The stack-standard plugin reference was refreshed by the build. The skill validator initially lacked PyYAML; validation passed using an isolated temporary dependency directory without changing project dependencies. No runtime/component/dependency changes, new native acceptance claim, package publication, installed plugin update or Platform deployment occurred. The active native checkout was not edited, built or packaged. Its remaining OS/parity work is independent of this guidance change.
18
+
19
+ # Next/OpenNext runtime gate — October 25, 2026
20
+
21
+ Implemented in an isolated branch from staging; unrelated native registry work remains untouched. Relevant PRs compile the current init-only foundation and exercise actual OpenNext/workerd: prerendered home, dynamic SSR/RSC, synthetic Server Action/cookie round-trip, Hono service binding and immutable asset headers. The fixture remains local and has no configured database migrations or provider calls.
22
+
23
+ Validation: CLI build, lint/typecheck/format/hygiene, static security/release policy, packed consumer and packlist passed. Unit suite: 99 passed, zero failed, one conditional skip. Compiled runtime smoke passed; final emitted Worker measured 5,219,988 raw bytes and 1,078,898 individually gzipped bytes, below the initial 4 MiB regression ceiling. Budget boundary/overflow and scope-selection regressions passed. The public homepage is proven prerendered from Next's manifest; request-dependent fixture routes remain dynamic. No npm publication, deployment or installed plugin update occurred. CI is configured in source; hosted acceptance remains separate.
24
+
25
+ # Scaffold-only CLI preparation — October 24, 2026
26
+
27
+ Prepared on `codex/scaffold-only` from staging in an isolated checkout. The actively edited CLI checkout and its native UI work are preserved. This is an unpublished breaking 0.16.0 candidate; no installed plugin, Platform image, provider account, remote database or deployment was changed.
28
+
29
+ Scope: `init` is the sole product command; npm exports expose generation only. Removed provider authentication, delivery/provisioning/operations, payments additions, inspection/catalog/MCP and their retired tests. Generated applications retain Next.js/OpenNext, native Expo, web shadcn and native ports, Hono/workerd, Drizzle/D1 and a private R2 binding, contracts/tokens and explicit consumer migration/configuration scripts. They contain no auth/email/billing integration or public object routes. The skills-only Codex plugin explains this stack, initializes it, starts local development/opens the browser, and recommends separately installed provider plugins when requested. Historical evidence below remains unchanged.
30
+
31
+ Validation: CLI build/typecheck, lint/format/source hygiene, static security and release policy pass. The unit suite passes with one existing conditional skip. Skills-only packaging and published-file policy pass. The packed npm consumer successfully installs the package and initializes the foundation with real dependencies; generation does not register a catalog. The generated HTTP contracts pass six positive/negative semantic compiler cases without source rewriting. A fresh application passes lint, typecheck, strict dead-code analysis, configured dependency-audit policy, and serial production builds including Next/OpenNext and the Hono Worker. An isolated local Next → Hono/workerd health request succeeds without application credentials; removed auth, file and payment routes return 404. Test servers stop after acceptance. No configured remote migrations run.
32
+
33
+ Limit: full generated `pnpm check` still fails Fallow's health complexity threshold on the unchanged native port catalog (28 findings in the initial fresh run). The scope change's unused web UI/helpers were repaired; final strict dead-code analysis passes. Native UI source is deliberately unchanged because separate active work owns it. The raw dependency audit reports the reviewed node-forge advisory (accepted only with the existing exact local patch) and two moderate transitive advisories; the existing policy preserves the raw report and passes. No new exceptions or weakened thresholds were introduced. Browser interaction, physical-device/store acceptance, live providers and production operation are not claimed. Existing Platform runtime pins keep the prior generator and inspect command until a separate explicit adoption.
34
+
35
+ # Expo native shadcn catalog — October 24, 2026
36
+
37
+ The CLI now maintains native semantic adaptations for all 66 entries in the shadcn Components catalog reviewed on 2026-10-24. `assets/ui/native/registry.json` pins the IDs, exports, shared helpers and evidence status; [Native UI](native-ui.md) is its generated parity checklist. This baseline excludes separately maintained AI Elements, form-library integrations and ecosystem registries. Native style/events, SVG chart data and touch/menu interactions deliberately have native APIs rather than DOM/Recharts compatibility.
38
+
39
+ - The real offline generator is used by both the contract tests and native test harness. Tests compare copied sources, explicit helper inventory, all public exports/module paths, an independent upstream ID snapshot, examples and Expo-compatible dependency pins. Fresh applications receive all source, attribution, inventory and native guidance. Application edits are never overwritten by CLI upgrades.
40
+ - React Native Testing Library: 144 tests in nine suites pass under both iOS and Android module resolution (288 executions), using real generated components. Tests exercise controlled values, disabled inputs, long press, native back/escape, menus/filtering, calendar bounds/leap dates/ranges, cumulative drag state, adjustable actions, table selection/sort/pagination, timers, source-preserving syntax/diff highlighting, clipboard failure/retry, six SVG chart types, questionnaire submission, safe areas, themes and reduced-motion subscriptions. Native persistence/clipboard bridges are isolated at the platform boundary. Coverage gates require 90% lines, 85% statements, 75% functions and 70% branches.
41
+ - Strict TypeScript 6 includes the generated mobile application's `noUncheckedIndexedAccess` setting. A fresh installed core application passes native-package ESLint, native-package typechecking and mobile typechecking. Expo SDK 57 exports Hermes bundles for iOS and Android for that application and the complete 66-component gallery. SVG is pinned to the SDK's 15.15.4 native ABI and Clipboard to 57.0.2.
42
+ - CLI build, lint, source hygiene, static security and release policy pass. The full root unit run initially had two failures: the isolated plugin fixture omitted the newly required native guide and the bundled stack-standard link lacked that reference. Both were fixed at their source; the full rerun reports 560 tests, 559 passed and one existing optional runtime test skipped. Plugin checks, packed CLI smoke and explicit packlist checks pass. Live upstream comparison reports exactly the 66 pinned IDs. Native changes run the test harness within the existing single Linux CI gate; no hosted device/build matrix is added.
43
+
44
+ The gallery is maintained in `tests/native-ui` for native review. Interactive device acceptance remains pending for every component: neither JavaScript tests nor Hermes exports establish VoiceOver/TalkBack, physical gestures, OS focus restoration, dynamic type or hardware behavior. A local test simulator could boot, but the Simulator application was unavailable and the existing development client lacked the new Clipboard module; no interactive acceptance is claimed. The temporary Metro server was stopped and the simulator returned to its prior shutdown state. No provider configuration, store submission, production deployment or package publication occurred.
45
+
46
+ # Next.js web and Expo native architecture — October 23, 2026
47
+
48
+ CLI 0.15 source preparation separates full Next.js App Router web (SSR/RSC through
49
+ Cloudflare OpenNext) from Expo iOS/Android. The UI contracts are DOM shadcn for web
50
+ and the Anhedral-maintained React Native port of shadcn for native, with shared
51
+ semantic tokens and public API contracts. Hono, Drizzle/D1 and private R2 remain
52
+ core; Stripe and RevenueCat remain the only additions.
53
+
54
+ The canonical diagram was regenerated in both themes as self-contained SVG and
55
+ 1920×1080 PNG using the existing local Chrome renderer. The same SVG bytes are
56
+ mirrored by the Platform landing. This is documentation/artwork verification;
57
+ it does not establish generated-app, installed-plugin, native-device, provider,
58
+ hosted-image or production acceptance. Record runtime evidence separately.
59
+
60
+ ## Next development proxy response framing — October 23, 2026
61
+
62
+ The Platform Linux image proof reproduced a failed `/api/health` response through
63
+ actual Next dev: Node fetch decoded the Hono sidecar's gzip body, but the generated
64
+ proxy retained its compressed `Content-Encoding` and `Content-Length`. The next
65
+ HTTP client attempted to decode the already-decoded response and failed.
66
+
67
+ The development HTTP proxy now removes those stale wire headers before Next
68
+ frames the response. The production service-binding path retains its existing
69
+ response handling. A real loopback HTTP server supplies a gzip response in the
70
+ regression test; all five Next web tests pass. `pnpm build` and `pnpm lint` also
71
+ pass, including typecheck, formatting, source hygiene and release-policy checks.
72
+ This evidence does not establish a deployed Platform runtime; its image and live
73
+ initialization are verified separately in the Platform repository.
74
+
75
+ The full `pnpm release:check` passed: 550 unit tests passed with one existing
76
+ skip, frozen patch installation checks passed, and packed CLI smoke and packlist
77
+ checks passed. Linux Next dev returned `200 {"ok":true}` through `/api/health`
78
+ and `200 null` through `/api/auth/get-session` after applying the generated fix.
79
+
80
+ ## CLI 0.15 generated runtime acceptance — October 23, 2026
81
+
82
+ The implementation agent recorded the following local evidence for the unpublished
83
+ 0.15 source preview, with Next.js web separate from Expo native:
84
+
85
+ - Complete generated `pnpm check` passed: lint, typechecks, Fallow with zero issues,
86
+ dependency audit, available tests and builds. A manual fixture rsync temporarily
87
+ overwrote its patch policy; after restoring the ordinary-init policy, the full
88
+ check passed. This was a test-harness issue, not an initialization result.
89
+ - The packed tarball completed ordinary initialization, including staged dependency
90
+ resolution, patches and frozen installation; doctor and target checks passed.
91
+ - Both iOS and Android Hermes exports passed, with output retained locally at
92
+ `/tmp/anhedral-next-native-final-export`. This is export evidence, not device,
93
+ screen-reader, store or native interaction acceptance.
94
+ - Production OpenNext running in local workerd passed SSR/RSC, guarded account,
95
+ cookie roundtrip, signup, reload, sign-in/sign-out and rejected native-origin
96
+ checks. Browser acceptance reported zero errors. The final typography-only
97
+ OpenNext rebuild passed: 5474.81 KiB upload, 1130.07 KiB gzip and 44 assets;
98
+ its additional browser/layout rerun was still pending when this entry was written.
99
+ - Root Turbopack development reached first compile/browser readiness in 4825 ms.
100
+ A source edit reached HMR in 790 ms, preserving window state with zero browser
101
+ errors. Webpack development failed reproducibly in
102
+ `WasmHash._updateWithBuffer` with an undefined `length`; production webpack and
103
+ OpenNext builds passed. The supported default development path uses Turbopack.
104
+
105
+ A small warm-workerd comparison used three fresh Chrome contexts before the final
106
+ heading CSS adjustment. Next readiness was 115/90/78 ms, transferred bytes were
107
+ 172418/172089/172092 and FCP was 72/40/40 ms. The earlier Expo baseline medians
108
+ were 149 ms readiness, 438928 transferred bytes and 48 ms FCP. These are tiny local
109
+ samples with a warm server, not universal performance claims or live deployment
110
+ measurements. They do not establish a consistent FCP improvement.
111
+
112
+ No npm publication, installed-plugin update, hosted-image activation, production
113
+ deployment, real payment or physical-device acceptance is established by these
114
+ checks. Final serialized CLI/plugin/reference checks follow this documentation
115
+ update and must be recorded separately if they expose further failures.
116
+
117
+ # Focused core verification — October 23, 2026
118
+
119
+ 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.
120
+
121
+ Validation of this change:
122
+
123
+ - CLI build, typecheck, formatting/hygiene, release policy and static security passed.
124
+ - Complete CLI unit suite after the streamlining pass: 545 passed, one platform-conditional skip, zero failures (546 tests).
125
+ - Codex plugin check: typecheck/build and 61 tests passed; browser smoke 11/11 passed using installed Chrome.
126
+ - Packed CLI installed/executed successfully; packlist allowlist passed (222 files, approximately 543 KB compressed at this validation).
127
+ - OSV audit passed for all 56 unique locked/catalog dependency versions.
128
+ - Generated all four supported selections in isolated tests; offline init, authored-source preservation, addition rollback/conflicts, private secret exclusion and generator provenance covered.
129
+ - 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.
130
+ - 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.
131
+ - Real local workerd: exported Expo routes, gateway service binding, isolated local D1 authentication/session/revocation and native scheme/origin handling passed.
132
+ - 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.
133
+
134
+ 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.
135
+
136
+ 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.
137
+
138
+ 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.
139
+
140
+ 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).
141
+
142
+ 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.
143
+
144
+ 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.
145
+
146
+ ---
147
+
1
148
  # Verification record
2
149
 
3
150
  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
151
 
152
+ ## README stack catalog and static artwork — 2026-10-19
153
+
154
+ 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.
155
+
156
+ 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.
157
+
5
158
  ## Full Cloudflare default and optional shared billing — 2026-10-18
6
159
 
7
160
  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.
@@ -555,3 +708,361 @@ hosted CI and publication are recorded separately after they actually complete.
555
708
  - 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.
556
709
  - Provider-call assertions in billing fixtures now compare exact hostnames, addressing CodeQL substring findings without changing provider transport.
557
710
  - 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.
711
+
712
+ ## 2026-10-21 — focused staging releases and CI tiers
713
+
714
+ Adopted topic PRs into `staging` and focused staging-to-main release PRs. Routine
715
+ code CI uses one Linux Node 24 CLI lane and one plugin lane; release candidates
716
+ retain supported Node, macOS/Windows, both plugin toolchains and all generated
717
+ profiles. Removed the duplicate E2E packed-CLI job. Stable `CI gate` fails on scope
718
+ errors or applicable failed/skipped jobs. Candidate upload is restricted to trusted
719
+ main CI. Reviewed-integrity dispatch, npm OIDC/provenance, immutable tags and
720
+ existing maintainer/CodeQL review requirements are preserved. Renovate targets staging.
721
+
722
+ Local build, typecheck, lint, release-policy and release-tooling checks passed.
723
+ Scope/promotion, candidate and plugin packaging regression checks passed. Full unit
724
+ suite passed with pinned pnpm 10.34.5: 750 passed, two optional runtime checks
725
+ skipped, zero failures. actionlint 1.7.12 passed (optional shellcheck/pyflakes disabled).
726
+ Initial checks caught a broken bundled relative documentation link and an obsolete
727
+ candidate-condition expectation; both were corrected. The host's pnpm 11 first
728
+ rejected the inspector's pnpm-10 override configuration; rerunning with the declared
729
+ version avoided a lockfile change. This is source/fixture evidence, not live provider
730
+ acceptance or a new npm publication. Adoption source takes effect on main after its
731
+ release PR merges; main remains the default branch.
732
+
733
+ Hosted adoption PR #39 subsequently exposed generated-project blockers: desktop
734
+ rejected Vite advisory GHSA-587h-7wmj-h5pm, and clients rejected duplicate affected
735
+ versions in advisory data. The generated dependency/advisory sources are unchanged
736
+ by this conventions diff; these failures are retained as release blockers for a
737
+ separate focused maintenance PR. Added fail-fast matrices and made portability/
738
+ generated jobs wait for primary checks to avoid spending on an already-failing
739
+ candidate. Hosted checks must pass before promotion/publication.
740
+
741
+ GitHub settings could not be applied: the authenticated account reports push access
742
+ but admin=false, and the attempted ruleset update returned HTTP 404. Existing rules
743
+ are unchanged. PR #39 lists the exact administrator prerequisites, including both
744
+ main rulesets, CI gate, merge commits and disabling automatic staging deletion.
745
+
746
+
747
+ ## 2026-10-21 correction — lightweight hosted checks on both branches
748
+
749
+ The owner clarified that large hosted checks are unacceptable on staging **and**
750
+ production. Earlier release-matrix proposals above are superseded. Automatic PR
751
+ CI now has one Linux CI gate on both branches; no full suite, generated project,
752
+ browser or platform matrix expands at promotion. Expensive validation is optional
753
+ and explicitly manual, or local. Main has no duplicate push check. CLI candidate
754
+ packaging is requested manually on main; publication keeps exact SHA/artifact,
755
+ secret/integrity, protected npm approval, provenance and tag checks while using a
756
+ single Linux artifact smoke lane instead of the six-job native matrix. Main repo
757
+ PRs fetch only the formatter, not the full application dependency graph. Its deploy
758
+ scripts no longer repeat full checks/tests, while retaining main/source guards,
759
+ affected-service detection and the selected app's necessary build/typecheck/upload.
760
+
761
+ The corrected lightweight CLI gate passed locally: compile, formatting, source
762
+ hygiene, static security/release policy, fast contract tests and release-tooling
763
+ negative paths. actionlint passed for automatic, manual-validation and publishing
764
+ workflows. The dependency/advisory repair remains a separate staging PR.
765
+
766
+ ## 2026-10-21 — generated dependency/advisory repair
767
+
768
+ Reproduced three live OSV findings on desktop's pinned Vite 7.3.6:
769
+ GHSA-587h-7wmj-h5pm, GHSA-698v-4r3x-3vcv and GHSA-r825-w8mm-5pxw.
770
+ The upstream repaired 7.x release is 7.3.7; the desktop recipe now pins it without
771
+ a major upgrade. Sources: https://github.com/advisories/GHSA-587h-7wmj-h5pm
772
+ and https://github.com/vitejs/vite/releases/tag/v7.3.7.
773
+
774
+ A real pnpm 10.34.5 clients audit also emitted two Vite 7.3.6 findings for the
775
+ extension and desktop dependency paths. Its severity metadata counted both
776
+ instances. The audit verifier now permits repeated versions at distinct paths,
777
+ preserves both counts and the raw report, and rejects duplicate version/path
778
+ entries. New regressions cover count mismatches, unknown high advisories and
779
+ exact reviewed-patch requirements with repeated versions. No advisory was added
780
+ to an exception list and no severity threshold changed.
781
+
782
+ Validation used Node 24.21.0 and pnpm 10.34.5. `pnpm test:all` passed: build, lint,
783
+ static security policy, live OSV audit of 110 locked/catalog coordinates, 751 unit
784
+ passes with two optional skips, frozen patch probes, packed CLI installation and
785
+ packlist checks. The 12 focused audit/scaffold checks passed. Fresh real desktop
786
+ and clients profiles passed generation, frozen install, lint/type/audit/tests/build
787
+ and unsigned macOS Electron packaging; clients also exercised Expo and WXT outputs.
788
+ The clients gate still requires its existing reviewed braces/node-forge patches;
789
+ raw advisories remain visible. Initial parallel generator runs collided in shadcn's
790
+ shared temporary clone directory; rerunning sequentially resolved that setup failure
791
+ without changing tests or adding retries. These results do not establish Windows,
792
+ Linux, signed macOS distribution or store acceptance. Hosted PR checks provide
793
+ separate evidence. This focused repair has no version bump or npm publication.
794
+
795
+
796
+ ## 2026-10-23 — Product family naming
797
+
798
+ 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.
799
+
800
+
801
+ ## 2026-10-23 — Generated audit dependency security recovery
802
+
803
+ The managed-email recovery release check refreshed OSV and found two advisories
804
+ against the existing generated Fallow 3.33.1 pin: GHSA-h4fr-cmh5-qr62 and
805
+ GHSA-jfwm-3p3c-6hx5. Both upstream advisories identify 3.34.0 as the patched
806
+ version. Pin the generated audit tool to that version; keep audit admission and
807
+ all existing security gates enabled. No provider resources or databases changed.
808
+
809
+ CLI build, lint/typecheck/format/hygiene/release policy, focused dependency/Next
810
+ contracts (11 tests) and refreshed OSV audit (61 locked/catalog versions) passed.
811
+ Publication of the integrated candidate remains separate.
812
+
813
+
814
+ ## 2026-10-23 — Managed authentication email recovery
815
+
816
+ Recover the scoped email adapter and verification/password-reset flows from the
817
+ preserved `4a48ca3` snapshot against the current Next web/native-only Expo stack.
818
+ Use an optional, fully validated API binding/scope/capability; empty standalone
819
+ setup retains current sessions, partial setup fails closed, and configured setup
820
+ requires verification with reset session revocation. All generated session
821
+ consumers pass the same server environment, including private files and billing.
822
+ The adapter uses deterministic send identities and bounded requests; broker error
823
+ bodies and credential/token-bearing transport errors never reach clients.
824
+
825
+ Next and native signup wait for verification rather than trying to open Account
826
+ without a session. Resend and reset flows use exact same-origin/native callbacks.
827
+ The framework-independent reset transport is shared through contracts; each
828
+ platform owns its controls. Nova Input/Label integrate with the reviewed form PR.
829
+
830
+ Validation: focused generator/broker/Next tests (8), complete CLI unit suite
831
+ (553 passed, one optional skip), unchanged CLI release gate including OSV, patch
832
+ regressions, packed CLI and packlist passed again on the final combined Nova/email/tooling source. The
833
+ installed generated core fixture passed full checks including Fallow, dependency
834
+ audit, types, lint, OpenNext/API builds; iOS/Android Hermes exports passed.
835
+ Compiled Worker plus real Better Auth/Drizzle/in-memory SQLite proved signup,
836
+ verification, denied unverified login, reset, single-use/expired tokens, session
837
+ revocation, incorrect password, unknown-user privacy, foreign callback denial and
838
+ exact native return scheme. Default unconfigured auth acceptance also passed.
839
+ Browser testing verified the signup prompt, verification link, authenticated
840
+ Account and sign-out with the isolated sink. No real email or configured database
841
+ was used. Physical-device, inbox delivery and hosted-image activation are separate.
842
+
843
+ Initial checks retained failures for synthetic email strings in the security
844
+ scanner, screen/adapter complexity and cross-platform duplication; fixture
845
+ addresses were assembled and shared reset transport extracted without relaxing
846
+ checks. Fresh advisory refresh required separately reviewed Fallow, Expo-Zod and
847
+ Miniflare-Undici fixes. A local UI HTTP harness initially wrote cookie headers
848
+ after committing response headers; fixing that fixture restored sign-in. The
849
+ product's compiled-Worker authentication tests already passed independently.
850
+
851
+ ## 2026-10-23 — Nova authentication form recovery
852
+
853
+ The current Next/native default already contains the recovered native shadcn
854
+ foundation and Base Nova Button (#49). Recover the source-owned Base UI Nova
855
+ Input and Label from the retained CLI snapshot and use them on generated web
856
+ sign-in forms. Preserve the existing MIT notice and upstream provenance hashes;
857
+ adapt only the local utility import, client boundary and focus ownership. Input
858
+ delegates keyboard focus to the generated global rule rather than adding a
859
+ second focus-only border/ring layer. Other historical components remain preserved
860
+ in the recovery branch and are not installed as unused starter code.
861
+
862
+ CLI build/lint/typecheck/format/hygiene and five Next contract tests passed.
863
+ The integrated generated web fixture passed Next route/type generation and lint
864
+ with these recovered controls. Browser interaction and final integrated release
865
+ checks are recorded with the managed-email recovery.
866
+
867
+ ## 2026-10-23 — Expo CLI validation dependency recovery
868
+
869
+ A fresh installed core fixture failed the unchanged dependency audit on
870
+ GHSA-mrhx-c7xc-m3w5: Expo CLI 57.0.32 pulls Zod 3.25.76 although application
871
+ contracts already use patched Zod 4.6.6. Add a narrow @expo/cli>zod override to
872
+ the existing catalog pin. Expo SDK stays at 57. Audit admission remains enabled.
873
+ The actual CLI plugin/MCP schemas and native exports are tested before promotion;
874
+ this does not claim upstream Expo has migrated its declared range.
875
+
876
+ The next audit also identified GHSA-xjj6-f33q-929c in Miniflare's Undici
877
+ 7.29.1. A same-major, consumer-scoped miniflare>undici 7.30.1 override uses
878
+ the upstream patched version and also removes the related moderate Undici
879
+ findings. No high/critical advisory is waived. Existing exact reviewed
880
+ node-forge/braces patches remain unchanged.
881
+
882
+ The installed generated core fixture passed the unchanged high/critical audit
883
+ gate with only the existing exact verified node-forge patch acceptance. Both
884
+ Hermes native exports passed. The actual Expo plugin and MCP schemas passed
885
+ positive/negative parsing against scoped Zod 4.6.6; CLI build/lint and 11 focused
886
+ contract tests passed, and OSV passed for 62 locked/catalog versions.
887
+
888
+ Final integrated acceptance: the unchanged full CLI release gate passed, including
889
+ 553 unit passes/one optional skip, refreshed OSV (62 locked/catalog versions),
890
+ exact patch regressions, packed installation and strict packlist (249 files).
891
+ Inspector/plugin check passed all 61 tests. Both core and Stripe+RevenueCat
892
+ generated profiles passed full local checks and builds. The payment profile also
893
+ passed real workerd SSR/RSC, protected account, D1 session/revocation, native
894
+ scheme/origin rejection, compiled email acceptance and synthetic billing tests.
895
+ The 28 generated browser JavaScript assets contain no managed-email broker
896
+ configuration/module or native purchase modules. Browser reset-request confirmation
897
+ passed; native exports do not establish physical-device acceptance.
898
+
899
+ The final strict packlist initially rejected the recovered Input/Label paths;
900
+ PR #62 requires and allowlists exactly those two files without widening exclusions.
901
+ Nova form recovery is #60; security prerequisites are #58/#59. Storage safeguards
902
+ were already recovered/shipped as anhedral-main#201: nine regressions, root
903
+ check (26 tasks) and serial root build (five tasks) passed again at Platform
904
+ source 822825e9; later observed staging changes did not touch those safeguards.
905
+ No Comms source, retained recovery snapshot or stash was changed by this work.
906
+ Publication and provider state are verified separately after promotion.
907
+
908
+ Final React review gives web/native reset forms a token/error-derived route key,
909
+ so following a new recovery link resets prior completion, input and error state.
910
+ Only the used token/error fields cross the Next server/client boundary.
911
+
912
+
913
+ ## 2026-10-23 — Immutable release smoke prerequisite
914
+
915
+ The first 0.15.0 publication attempt (run 40056207567, source 4557627f) stopped
916
+ before npm publishing. Hash and secret checks passed; exact-artifact smoke failed
917
+ while spawning pnpm for the installed CLI's normal initialization. Main candidate
918
+ CI had pnpm setup, but the isolated release verification and exact-artifact jobs
919
+ provisioned only Node. Add the same pinned pnpm action/version to those jobs, with
920
+ run_install disabled. Keep normal init, artifact integrity, npm environment/OIDC
921
+ and exact-artifact checks intact. A workflow regression covers all three smoke
922
+ locations. A fresh main candidate must be reviewed again after this correction.
923
+
924
+
925
+ ## 2026-10-24 — Published 0.15.0 artifact identity
926
+
927
+ Read-only release verification resolved tag `v0.15.0` to source
928
+ `2c06f4eb528da0ba404212298fc57e1a2287f22e`. The npm registry serves 0.15.0;
929
+ its tarball and the GitHub release tarball both match the release metadata:
930
+
931
+ - CLI SHA-512: `sha512-1D2XHnw4QSDYXfNigt7YBdv5N8Y8ANOpaoSb38xlqEvv1uq7VHFurx+lAsX0IpB4Jf2R5PISitx2Fs6cDyJ4KQ==`.
932
+ - Plugin SHA-512: `sha512-G3/obSaCpHv+AvitX/Xtb34ChmsBc+7NrV7WHDDNEyqZkOin6CH4MSDgqu4lJnCdUn6dxCN06mFckBadwqlwgg==`.
933
+
934
+ The downloaded plugin ZIP matches both release metadata and plugin metadata.
935
+ The npm and GitHub package checks hashed the actual bytes in memory; the tag
936
+ was checked against the remote repository. This establishes published artifact
937
+ agreement, not independent provenance-signature verification or a rebuilt source
938
+ comparison. Release assets and metadata are available at
939
+ [the 0.15.0 release](https://github.com/anhedral/anhedral-cli/releases/tag/v0.15.0);
940
+ [registry metadata](https://registry.npmjs.org/anhedral/0.15.0) records the npm integrity.
941
+
942
+ This supersedes unpublished-preview wording, not the dated runtime evidence
943
+ above. Publication does not update existing applications, installed plugins or
944
+ Platform images. Platform's separately recorded Next generator at `2280c3b` has
945
+ a different integrity and must retain its own acceptance evidence until an
946
+ explicit artifact adoption is verified. No publication, deployment, provider
947
+ mutation or payment operation was performed during this verification.
948
+
949
+ Documentation correction validation: CLI build, documentation/plugin contract
950
+ checks (two passing test entries) and `git diff --check` passed in an isolated
951
+ checkout. No runtime behavior changed.
952
+
953
+
954
+ ## 2026-10-24 — Addition post-commit installation recovery
955
+
956
+ Focused addition regressions now inject a failure in the final frozen install,
957
+ after the actual staged source transaction commits. They verify PostCommitError,
958
+ retained billing source/receipts, removal of stale dependency links, released
959
+ transaction lock, preservation of authored/private files and a successful
960
+ idempotent retry that still invokes the installer. A second regression rejects
961
+ an installer that mutates the reviewed lockfile after source commit.
962
+
963
+ The dependency runner is injected: these checks exercise the real addition and
964
+ transaction paths, not a real pnpm dependency installation or application runtime.
965
+ No generator behavior change was required. Build and lint (typecheck, formatting,
966
+ source hygiene and release policy) passed; the focused addition, transaction
967
+ rollback and CLI-output run passed all 36 test entries. `git diff --check` passed.
968
+ No provider, publication, deployment, database or payment operation occurred.
969
+
970
+
971
+ ## 2026-10-24 — Recovered embedded inspector contracts
972
+
973
+ Compared the preserved user-work snapshot at `4a48ca3` with the current CLI.
974
+ Its embedded-host fixture and browser regressions had not landed. Recovered them
975
+ against the current synthetic core-stack fixture, retaining its lockfile evidence
976
+ and supported init options. The installed MCP Apps SDK now exercises project
977
+ context updates, advertised desktop unsent drafts for both active/new targets,
978
+ unsupported/web-host fallback, failed-composer fallback and actual safe-area layout.
979
+ The production preview CSP remains unchanged; embedding is test-fixture-only.
980
+ Recovered service-argument descriptions now explain catalog/service identities,
981
+ D1's complete-UTC-day analytics windows, pagination and app-only deletion inputs;
982
+ obsolete Vercel guidance was removed.
983
+
984
+ CLI build, root lint/static security, plugin check (61 tests) and the browser suite
985
+ (17 tests, including four recovered host tests) passed. Browser execution used
986
+ installed Google Chrome via PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH because the pinned
987
+ Playwright browser binary is absent. An initial fixture port attempted obsolete
988
+ init flags; it was corrected to preserve the current fixture before acceptance.
989
+ This is synthetic browser/SDK evidence, not live Codex-host or provider acceptance.
990
+ No installed-plugin update, publication, deployment or provider operation occurred.
991
+
992
+
993
+ ## 2026-10-24 — Recovered generated-type cache restoration
994
+
995
+ The historical cache-restoration check in `0f827d9` remains useful for the maintained
996
+ core stack. A real installed pre-fix generated workspace failed its warm Next
997
+ cache-HIT assertion after generated type files were removed. Worker typecheck also
998
+ had no declared outputs. The corrected generator caches Worker binding types,
999
+ Next environment types and production route types; it ignores next-env.d.ts so a
1000
+ generated file cannot become a changing task input. The regression uses a fresh
1001
+ local-only Turbo cache, requires both application tasks to report HIT in the actual
1002
+ warm-run JSON summary, and compares every restored file byte-for-byte. It runs in
1003
+ the generated-profile integration runner and can target an installed local fixture.
1004
+
1005
+ The same pre-fix fixture passed after applying only the reviewed output/ignore
1006
+ settings. A fresh core application generated by the corrected CLI passed its full
1007
+ check, confirmed cache restoration, dynamic SSR/RSC, workerd service-binding and
1008
+ D1 authentication/authorization, protected contracts, session revocation, native
1009
+ scheme transport and origin rejection. Migration fixtures were explicitly local.
1010
+ CLI build/lint/static security, the unit suite (556 pass, one existing skip), plugin
1011
+ check (61 pass), packed CLI smoke and packlist policy (249 files) also passed.
1012
+ This does not update existing customer projects or establish device, store or live
1013
+ provider acceptance. No remote migration, deployment, payment or publication ran.
1014
+
1015
+
1016
+ ## 2026-10-24 — Preserved-work disposition and service-tool guidance
1017
+
1018
+ Compared all preserved snapshots against the maintained CLI, its registered
1019
+ commands/plugin tools, emitted source, packaging and tests. Patch IDs alone were
1020
+ insufficient because the repository squashes topic PRs. Exact Git tree comparison
1021
+ established the following dispositions:
1022
+
1023
+ | Preserved source | Disposition |
1024
+ | --- | --- |
1025
+ | Maintainer-policy `f7e51c8` | Exactly the tree of merged PR #24 (`723a213`): architecture, lifecycle, security/toolchain and review work landed historically. PR #46 later retired the old control-panel/alternative-stack layout. The still-useful cache regression was adapted for the current API/Next stack. |
1026
+ | Former local staging `91ec88f` | Exactly the tree of merged PR #37 (`fc721c9`). Maintenance guidance, CI scope, Windows PATH ordering, release-artifact/profile fixes, README and artwork changes were already incorporated. Current command resolution, CI scope and preview discovery retain their relevant fixes. |
1027
+ | Older control-panel variant `d7ac371` | Its 28 changed paths belong to the retired apps/control-panel/plugin layout and an independent anhedral.progress.json report/discovery store. Current project inspection/lifecycle, provider records, delivery evidence, catalog and transaction locks own those concerns. Do not restore a parallel writable evidence store or unsupported capabilities. Original variant remains archived. |
1028
+ | User-work snapshot `4a48ca3` | Reviewed all 114 changed paths. Recovered embedded-host browser coverage, service-argument descriptions and per-operation service-tool descriptions. Nova auth controls/packaging (#60/#62), managed auth email (#61), security pins (#58/#59), approved branding (#47), contract checks (#44), UI inspection/substitution (#41/#43) and owned Next/native components (#49) already landed in focused form. |
1029
+ | User-work UI/generator alternatives | Generic ui/expo-ui packages, native web adapters, duplicate token JSON, unused component inventory, selectable provider/preset recipes and mobile-web bootstrap variants are superseded by separate DOM/native UI, shared tokens, offline core bootstrap and mandatory Next/Expo/Hono/D1/R2. Preserve originals in the archive; no current runtime consumer requires restoring them. |
1030
+ | Attached completed worktree branches | Addition recovery, dependency fixes, Nova packlist and product positioning have exactly the trees of merged PRs #67, #59, #62 and #56 respectively. Retiring their refs does not require removing their worktree files. |
1031
+ | Existing user-work stash | Shared tracked paths match the recovery snapshot, and all 39 untracked stash files are byte-identical to files in that snapshot. Keep the stash unchanged and independently backed up. |
1032
+
1033
+ The recovered service-tool descriptions distinguish existence from application
1034
+ health, explain catalog/service identities, supported Worker/D1 analytics windows,
1035
+ offset/cursor paging, app-only private data, and reviewed single-use deletion
1036
+ plans. Obsolete Vercel wording was removed. Input validation, visibility,
1037
+ permissions, confirmation requirements and provider behavior are unchanged. Plugin
1038
+ check passed all 61 tests after the description recovery. No additional tests were
1039
+ added merely to compare documentation strings.
1040
+
1041
+ Before branch retirement, retain verified self-contained Git bundles containing
1042
+ all original refs (including stash), original ref/object inventories and checksums.
1043
+ The detailed path inventory covers the 142 changed paths in the two independent
1044
+ snapshots. The approved disposition is to retire accounted-for recovery and
1045
+ completed-topic refs after the focused patches merge to staging, keeping old
1046
+ worktrees detached at their original commits so source and ignored material remain
1047
+ intact. Keep main/staging unchanged on the remote except for reviewed staging PRs.
1048
+ The old implementations remain recoverable; this is not proof of current device,
1049
+ store, live-provider or payment acceptance. No publication or deployment occurred.
1050
+
1051
+
1052
+ ## 2026-10-26: Progressive source additions for the complete stack
1053
+
1054
+ The public CLI now composes selected capability source after minimal Next.js/OpenNext/Workers + Anhedral UI initialization. The strict builder progression is Hono, then Drizzle/D1/Better Auth, followed by independently selected R2, Stripe, events, RTC, AI, Expo, native UI, RevenueCat, WXT, Side Panel and GPUI branches. See [the owning capability contract](capabilities.md). This extends the earlier thin UI work without adopting the separate native port or changing Platform’s immutable generator pin.
1055
+
1056
+ Validation on the isolated `codex/progressive-ui` checkout:
1057
+
1058
+ - CLI build and 114 unit tests passed; zero failed, one existing conditional skip. Eight addition regressions cover prerequisites, whole-plan collisions, JSONC/user edits, offline dry runs, symlinks, repeat additions, retained source and retry after install failure, client customization and file permissions.
1059
+ - CLI lint/typecheck, asset formatting, hygiene, security/release policy, plugin validation and OSV audit of 77 exact locked/catalog versions passed. Frozen braces/node-forge patch installation and Node/browser signature regressions passed.
1060
+ - Published package allowlist and installed-tarball smoke passed. The installed CLI initializes the minimal app, lists all 13 additions and installs Hono source with bundled capability references. No package was published.
1061
+ - A fresh `.artifacts/stack-acceptance` consumer installed all 13 additions through the normal CLI dependency/patch path. Its full `pnpm check` passed: lint, types, Fallow source/dead-code/duplication/health checks, dependency audit, tests and serial builds. Fallow reported zero above-threshold files and maintainability 94.3. The dependency audit retains raw reports and accepts only the existing reviewed node-forge patch; no advisory policy or quality threshold was weakened.
1062
+ - Builds produced the Next/OpenNext Worker, Hono Worker, iOS and Android Metro/Hermes bundles, Chromium MV3 popup/Side Panel/background and a native GPUI executable. GPUI uses upstream runtime shaders. The initial desktop format failure was corrected to Rust 2024 formatting before the full check. An exploratory Expo `--platform all` command requested unsupported web dependencies; the generated mobile build correctly targets iOS and Android, and both passed.
1063
+ - `node tests/test-capability-runtime.mjs .artifacts/stack-acceptance` passed against fresh in-memory Miniflare D1/R2 bindings. It generates SQL and explicitly applies only fixture migrations. Auth defaults remain disabled; a temporary fixture-only password opt-in proves real registration/session flows and is restored in `finally`. Checks cover owner-scoped storage, CSRF/forged bearer rejection, raw Stripe signatures through the actual generated Next proxy, tamper/environment rejection, scoped RevenueCat webhooks, durable duplicate receipts and resumable owner events. A forced clock-skew fixture verifies that atomic owner cursors increase monotonically, so later equal-millisecond or backward-clock events remain replayable.
1064
+ - Canonical billing fixtures made 12 intercepted local read requests, granting active access and rejecting cancellation, wrong identity/environment, expiry and provider outage. Unexpected outbound requests were zero. Unconfigured AI fails closed; RTC cross-user session and track operations are rejected before provider access. AI inference, RTC media and live billing services were not exercised.
1065
+
1066
+ After the recovery/cursor corrections, the real repeated-add dependency retry and `stack doctor` passed. Focused API lint, bundle, runtime and Fallow checks passed again.
1067
+
1068
+ Logs and runtime evidence are retained locally in `.artifacts/verification/2026-10-26-progressive-stack/`. Earlier dated failures and the separate native work are preserved. Source recipes and client builds do not establish live provider activation, physical device interaction, browser-store acceptance, native signing/distribution or production readiness. No provider resources, credentials, real payments, remote migrations, deployments, installed-plugin updates or Platform artifact adoption were performed. The PR remains a draft for review.