anhedral 0.12.0 → 0.13.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 (73) hide show
  1. package/README.md +99 -39
  2. package/dist/capabilities.d.ts +3 -3
  3. package/dist/capability-contract.js +12 -1
  4. package/dist/command-schema.js +8 -2
  5. package/dist/command.js +9 -11
  6. package/dist/delivery.js +3 -1
  7. package/dist/dependencies.d.ts +6 -1
  8. package/dist/dependencies.js +13 -1
  9. package/dist/index.d.ts +1 -0
  10. package/dist/index.js +1 -0
  11. package/dist/platforms/mobile.d.ts +1 -1
  12. package/dist/platforms/mobile.js +44 -3
  13. package/dist/project-state.js +4 -1
  14. package/dist/provider-auth.js +6 -0
  15. package/dist/providers/adapters.js +9 -3
  16. package/dist/providers/runtime.js +11 -0
  17. package/dist/readiness.js +4 -2
  18. package/dist/registry/add.js +40 -7
  19. package/dist/registry/options.js +12 -0
  20. package/dist/registry/presets.d.ts +4 -0
  21. package/dist/registry/presets.js +41 -0
  22. package/dist/registry/resolve.d.ts +3 -1
  23. package/dist/registry/resolve.js +40 -14
  24. package/dist/registry/types.d.ts +1 -0
  25. package/dist/registry/usage.js +1 -1
  26. package/dist/runtime-policy.js +4 -1
  27. package/dist/scaffold/api.js +10 -2
  28. package/dist/scaffold/auth.d.ts +1 -1
  29. package/dist/scaffold/auth.js +22 -6
  30. package/dist/scaffold/backend.d.ts +6 -0
  31. package/dist/scaffold/backend.js +224 -0
  32. package/dist/scaffold/billing-config.d.ts +1 -0
  33. package/dist/scaffold/billing-config.js +73 -0
  34. package/dist/scaffold/billing-contracts.d.ts +2 -0
  35. package/dist/scaffold/billing-contracts.js +48 -0
  36. package/dist/scaffold/billing-providers.d.ts +1 -0
  37. package/dist/scaffold/billing-providers.js +249 -0
  38. package/dist/scaffold/billing-schema.d.ts +1 -0
  39. package/dist/scaffold/billing-schema.js +34 -0
  40. package/dist/scaffold/billing-security.d.ts +1 -0
  41. package/dist/scaffold/billing-security.js +46 -0
  42. package/dist/scaffold/billing-server.d.ts +1 -0
  43. package/dist/scaffold/billing-server.js +139 -0
  44. package/dist/scaffold/billing-store.d.ts +1 -0
  45. package/dist/scaffold/billing-store.js +72 -0
  46. package/dist/scaffold/billing.d.ts +2 -0
  47. package/dist/scaffold/billing.js +216 -0
  48. package/dist/scaffold/cloudflare-services.d.ts +8 -0
  49. package/dist/scaffold/cloudflare-services.js +198 -0
  50. package/dist/scaffold/compose.js +2 -0
  51. package/dist/scaffold/database.js +19 -2
  52. package/dist/scaffold/documentation.js +10 -6
  53. package/dist/scaffold/expo-auth.d.ts +3 -0
  54. package/dist/scaffold/expo-auth.js +192 -0
  55. package/dist/scaffold/expo-billing.d.ts +3 -0
  56. package/dist/scaffold/expo-billing.js +292 -0
  57. package/dist/scaffold/expo-runtime.d.ts +3 -0
  58. package/dist/scaffold/expo-runtime.js +134 -0
  59. package/dist/scaffold/integrations.d.ts +2 -1
  60. package/dist/scaffold/integrations.js +7 -2
  61. package/dist/scaffold/void.js +13 -5
  62. package/dist/scaffold/web.js +2 -0
  63. package/dist/scaffold/workspace.js +6 -1
  64. package/dist/ship.js +3 -1
  65. package/dist/stack-registry.d.ts +11 -2
  66. package/dist/stack-registry.js +136 -16
  67. package/dist/version.d.ts +1 -1
  68. package/dist/version.js +1 -1
  69. package/docs/anhedral-stack.md +122 -0
  70. package/docs/software-factory.md +67 -8
  71. package/docs/stack-standard.md +126 -57
  72. package/docs/verification.md +113 -0
  73. package/package.json +7 -4
@@ -1,3 +1,4 @@
1
+ import { scaffoldCloudflareTransport, scaffoldAnalyticsEngine, scaffoldImages, scaffoldRealtimeKit, scaffoldVideo, } from './scaffold/cloudflare-services.js';
1
2
  import { usesVoidSelection } from './runtime-policy.js';
2
3
  import { scaffoldStyling } from './scaffold/styling.js';
3
4
  import { resourceName } from './render.js';
@@ -14,11 +15,26 @@ import { scaffoldRealtime, scaffoldQueues, scaffoldCron, scaffoldWorkflows, } fr
14
15
  import { scaffoldExpo } from './platforms/mobile.js';
15
16
  import { scaffoldElectron } from './platforms/desktop.js';
16
17
  import { scaffoldWxt } from './platforms/extension.js';
17
- import { scaffoldPrivateFiles, scaffoldRevenueCat } from './scaffold/integrations.js';
18
+ import { scaffoldPrivateFiles, scaffoldStripe, scaffoldRevenueCat, } from './scaffold/integrations.js';
18
19
  import { sharedPackage } from './scaffold/files.js';
19
20
  function requirements(purpose, tools, access, credentials, resources, verify) {
20
21
  return { purpose, tools, access, credentials, resources, verify };
21
22
  }
23
+ function billingDependencies({ has }) {
24
+ return [
25
+ 'hono',
26
+ has('neon') ? 'neon' : 'd1',
27
+ has('clerk') ? 'clerk' : 'better-auth',
28
+ ...(has('expo') ? ['expo'] : []),
29
+ ];
30
+ }
31
+ const BILLING_ENVIRONMENT_KEYS = [
32
+ 'BILLING_ORIGIN',
33
+ 'BILLING_ENVIRONMENT',
34
+ 'BILLING_PLANS_JSON',
35
+ 'BILLING_ENTITLEMENTS_JSON',
36
+ 'BILLING_PREMIUM_ENTITLEMENT',
37
+ ];
22
38
  function packageSource(name, source, dependencies) {
23
39
  return { name, source, dependencies };
24
40
  }
@@ -62,11 +78,17 @@ const PRODUCT_ITEMS = defineItems({
62
78
  },
63
79
  expo: {
64
80
  type: 'application',
65
- description: 'Expo mobile application with native UI',
81
+ description: 'Universal Expo web, iOS and Android client with a Cloudflare asset/API gateway',
66
82
  targets: ['apps/mobile'],
67
83
  registryDependencies: ['workspace', 'typescript', 'eslint', 'styling'],
68
- setup: requirements('Mobile application', ['Expo/EAS CLI', 'Xcode or Android SDK'], ['Client-owned Apple/Google developer accounts for store delivery'], ['Platform signing credentials; EAS access when used'], ['Expo app; native adapters, signing, store configuration'], ['Native simulator/device flows and signed native build; web export alone is insufficient']),
84
+ setup: requirements('Universal web, iOS and Android application', ['Browser control', 'Wrangler'], ['For requested native distribution only: client-owned Apple/Google developer accounts'], ['For requested native builds only: platform signing credentials and EAS access when used'], [
85
+ 'Expo universal client, Cloudflare web assets/API gateway; native adapters, signing and store configuration',
86
+ ], [
87
+ 'Static web export/runtime; requested native delivery additionally needs simulator/device and signed-build acceptance',
88
+ ]),
69
89
  install: scaffoldExpo,
90
+ environment: [],
91
+ resolveEnvironment: ({ has }) => (has('hono') ? ['EXPO_PUBLIC_API_URL'] : []),
70
92
  },
71
93
  electron: {
72
94
  type: 'application',
@@ -195,8 +217,16 @@ export interface LocalDataStore {
195
217
  fallbackDependency: 'd1',
196
218
  environment: ['BETTER_AUTH_SECRET', 'BETTER_AUTH_URL'],
197
219
  runtime: 'server',
198
- resolveDependencies: ({ has }) => [has('neon') ? 'neon' : 'd1'],
199
- resolveTargets: ({ runtimeApp }) => ['packages/auth', 'packages/db', `apps/${runtimeApp}`],
220
+ resolveDependencies: ({ has }) => [
221
+ has('neon') ? 'neon' : 'd1',
222
+ ...(has('expo') ? ['expo'] : []),
223
+ ],
224
+ resolveTargets: ({ runtimeApp, has }) => [
225
+ 'packages/auth',
226
+ 'packages/db',
227
+ `apps/${runtimeApp}`,
228
+ ...(has('expo') ? ['apps/mobile'] : []),
229
+ ],
200
230
  },
201
231
  r2: {
202
232
  type: 'integration',
@@ -281,8 +311,61 @@ export interface LocalDataStore {
281
311
  setup: requirements('Durable multi-step processing', ['Wrangler'], ['Cloudflare Workflows deployment access'], [], ['Workflow Worker/binding and resumable steps'], ['Retry/resume, idempotency, cancellation and failure recovery']),
282
312
  install: scaffoldWorkflows,
283
313
  },
314
+ 'analytics-engine': {
315
+ selection: { requiresAll: ['hono'] },
316
+ type: 'integration',
317
+ description: 'Workers Analytics Engine dataset binding and server event helper',
318
+ targets: ['packages/analytics-engine'],
319
+ runtime: 'worker',
320
+ install: scaffoldAnalyticsEngine,
321
+ configure: ({ options }) => ({
322
+ analytics_engine_datasets: [
323
+ { binding: 'EVENTS', dataset: resourceName(options.name, 'events').replaceAll('-', '_') },
324
+ ],
325
+ }),
326
+ setup: requirements('Custom server-side analytics', ['Wrangler'], ['Cloudflare Analytics Engine access'], [], ['EVENTS dataset binding; define event semantics and privacy policy'], [
327
+ 'Dataset ingestion, sampled query semantics and privacy filtering; not transactional billing state',
328
+ ]),
329
+ },
330
+ images: {
331
+ selection: { requiresAll: ['hono'] },
332
+ type: 'integration',
333
+ description: 'Cloudflare Images binding and private image transform helper',
334
+ targets: ['packages/images'],
335
+ runtime: 'worker',
336
+ install: scaffoldImages,
337
+ configure: () => ({ images: { binding: 'IMAGES' } }),
338
+ setup: requirements('Image optimization', ['Wrangler'], ['Cloudflare Images account eligibility'], [], ['IMAGES binding; authorize source objects and define transform/usage limits'], ['Real transforms, source ownership and cache isolation']),
339
+ },
340
+ realtimekit: {
341
+ registryDependencies: ['workspace', 'typescript', 'eslint', 'cloudflare-api'],
342
+ selection: { requiresAll: ['hono'] },
343
+ type: 'integration',
344
+ description: 'Cloudflare RealtimeKit server meeting and participant-token helpers',
345
+ targets: ['packages/realtimekit'],
346
+ runtime: 'worker',
347
+ install: scaffoldRealtimeKit,
348
+ environment: ['REALTIMEKIT_ACCOUNT_ID', 'REALTIMEKIT_APP_ID', 'REALTIMEKIT_API_TOKEN'],
349
+ setup: requirements('Audio/video conferencing', ['Cloudflare RealtimeKit API or dashboard'], ['Cloudflare RealtimeKit app and scoped Realtime permissions'], ['Server-only account/app ID and API token'], [
350
+ 'Manual app activation and presets; implement authorized token routes and platform client SDK',
351
+ ], ['Meeting isolation, permissions, reconnect and actual device media/teardown']),
352
+ },
353
+ video: {
354
+ registryDependencies: ['workspace', 'typescript', 'eslint', 'cloudflare-api'],
355
+ selection: { requiresAll: ['hono'] },
356
+ type: 'integration',
357
+ description: 'Cloudflare Stream private on-demand direct video upload helper',
358
+ targets: ['packages/video'],
359
+ runtime: 'worker',
360
+ install: scaffoldVideo,
361
+ environment: ['STREAM_ACCOUNT_ID', 'STREAM_API_TOKEN'],
362
+ setup: requirements('Uploaded video processing and delivery', ['Cloudflare Stream API or dashboard'], ['Cloudflare Stream activation and scoped Stream Write access'], ['Server-only Stream account ID and API token'], [
363
+ 'Authorized one-time upload issuance; implement processing checks, signed playback and retention',
364
+ ], ['Creator ownership, upload/processing limits and private playback on selected devices']),
365
+ },
284
366
  openai: {
285
367
  type: 'package',
368
+ runtime: 'server',
286
369
  description: 'Server-side OpenAI SDK factory',
287
370
  targets: ['packages/ai'],
288
371
  selection: { conflicts: ['ai-sdk'] },
@@ -293,6 +376,7 @@ export interface LocalDataStore {
293
376
  },
294
377
  'ai-sdk': {
295
378
  type: 'package',
379
+ runtime: 'server',
296
380
  description: 'Server-side AI SDK and provider exports',
297
381
  targets: ['packages/ai'],
298
382
  selection: { conflicts: ['openai'] },
@@ -314,6 +398,7 @@ export interface LocalDataStore {
314
398
  },
315
399
  resend: {
316
400
  type: 'package',
401
+ runtime: 'server',
317
402
  description: 'Server-side email SDK factory',
318
403
  targets: ['packages/email'],
319
404
  registryDependencies: ['workspace', 'typescript', 'eslint'],
@@ -324,23 +409,49 @@ export interface LocalDataStore {
324
409
  environment: ['RESEND_API_KEY'],
325
410
  },
326
411
  stripe: {
327
- type: 'package',
328
- description: 'Server-side billing SDK factory',
329
- targets: ['packages/billing'],
412
+ type: 'integration',
413
+ description: 'Authenticated Stripe checkout, portal and server entitlement projection',
414
+ targets: ['packages/billing', 'packages/contracts', 'apps/api'],
415
+ selection: { requiresAll: ['hono'], requiresAny: ['better-auth', 'clerk'] },
330
416
  registryDependencies: ['workspace', 'typescript', 'eslint'],
417
+ resolveDependencies: billingDependencies,
418
+ resolveTargets: ({ has }) => [
419
+ 'packages/billing',
420
+ 'packages/contracts',
421
+ 'apps/api',
422
+ ...(has('expo') ? ['apps/mobile'] : []),
423
+ ],
331
424
  setup: requirements('Web payments and subscriptions', ['Stripe integration or CLI'], ['Client-owned Stripe account; test/live access as required'], ['STRIPE_SECRET_KEY; STRIPE_WEBHOOK_SECRET'], ['Products/prices, signed webhooks and entitlement implementation'], ['Test purchase/cancellation, webhook replay and transactional idempotency']),
332
- package: packageSource('billing', "import Stripe from 'stripe';\nexport function createBilling(apiKey: string) { return new Stripe(apiKey); }\n", { stripe: STACK_DEPENDENCIES['stripe'] }),
333
- environment: ['STRIPE_SECRET_KEY', 'STRIPE_WEBHOOK_SECRET'],
425
+ install: scaffoldStripe,
426
+ environment: [...BILLING_ENVIRONMENT_KEYS, 'STRIPE_SECRET_KEY', 'STRIPE_WEBHOOK_SECRET'],
334
427
  },
335
428
  revenuecat: {
336
429
  type: 'integration',
337
- description: 'Cross-store entitlement integration guidance',
338
- targets: ['packages/billing/revenuecat.md'],
339
- selection: { requiresAll: ['stripe'] },
340
- registryDependencies: ['stripe'],
341
- setup: requirements('Cross-store subscription entitlements alongside Stripe', ['RevenueCat integration or API', 'Selected mobile store tooling'], ['RevenueCat project; App Store/Play Store product access'], ['Platform public SDK keys; server API/webhook credentials as required'], ['Integration guidance only; install platform SDKs and configure offerings/store products'], ['Sandbox purchase/restore, verified webhooks and entitlement reconciliation']),
430
+ description: 'Native purchases, restore and server-enforced cross-store entitlements',
431
+ targets: ['packages/billing', 'packages/contracts', 'apps/api'],
432
+ selection: { requiresAll: ['hono'], requiresAny: ['better-auth', 'clerk'] },
433
+ registryDependencies: ['workspace', 'typescript', 'eslint'],
434
+ resolveDependencies: billingDependencies,
435
+ resolveTargets: ({ has }) => [
436
+ 'packages/billing',
437
+ 'packages/contracts',
438
+ 'apps/api',
439
+ ...(has('expo') ? ['apps/mobile'] : []),
440
+ ],
441
+ setup: requirements('Cross-store subscription entitlements; Stripe is optional', ['RevenueCat integration or API', 'Selected mobile store tooling'], ['RevenueCat project; App Store/Play Store product access'], ['Platform public SDK keys; server API/webhook credentials as required'], [
442
+ 'Native purchase SDK and authenticated entitlement APIs; configure offerings/store products before acceptance',
443
+ ], ['Sandbox purchase/restore, verified webhooks and entitlement reconciliation']),
342
444
  install: scaffoldRevenueCat,
343
- environment: ['EXPO_PUBLIC_REVENUECAT_IOS_API_KEY', 'EXPO_PUBLIC_REVENUECAT_ANDROID_API_KEY'],
445
+ environment: [
446
+ ...BILLING_ENVIRONMENT_KEYS,
447
+ 'REVENUECAT_SECRET_KEY',
448
+ 'REVENUECAT_WEBHOOK_AUTHORIZATION',
449
+ 'REVENUECAT_WEBHOOK_SIGNING_SECRET',
450
+ 'REVENUECAT_APP_IDS_JSON',
451
+ 'REVENUECAT_PROJECT_ID',
452
+ 'EXPO_PUBLIC_REVENUECAT_IOS_API_KEY',
453
+ 'EXPO_PUBLIC_REVENUECAT_ANDROID_API_KEY',
454
+ ],
344
455
  },
345
456
  sentry: {
346
457
  type: 'package',
@@ -379,6 +490,7 @@ export async function recordEvents(stream: EventStream, events: Record<string, u
379
490
  },
380
491
  posthog: {
381
492
  type: 'package',
493
+ runtime: 'server',
382
494
  description: 'Server-side product analytics factory',
383
495
  targets: ['packages/analytics'],
384
496
  registryDependencies: ['workspace', 'typescript', 'eslint'],
@@ -428,6 +540,14 @@ const FOUNDATION_ITEMS = defineItems({
428
540
  targets: ['packages/eslint-config'],
429
541
  registryDependencies: ['workspace'],
430
542
  },
543
+ 'cloudflare-api': {
544
+ type: 'foundation',
545
+ installer: 'recipe',
546
+ description: 'Shared server-only Cloudflare media management transport',
547
+ targets: ['packages/cloudflare-api'],
548
+ registryDependencies: ['workspace', 'typescript', 'eslint'],
549
+ install: scaffoldCloudflareTransport,
550
+ },
431
551
  ui: {
432
552
  type: 'foundation',
433
553
  description: 'Shared shadcn/ui, React, Tailwind and Lucide foundation for web apps',
package/dist/version.d.ts CHANGED
@@ -1 +1 @@
1
- export declare const GENERATOR_VERSION = "0.12.0";
1
+ export declare const GENERATOR_VERSION = "0.13.0";
package/dist/version.js CHANGED
@@ -1 +1 @@
1
- export const GENERATOR_VERSION = '0.12.0';
1
+ export const GENERATOR_VERSION = '0.13.0';
@@ -0,0 +1,122 @@
1
+ # Anhedral progressive stack
2
+
3
+ **Start minimal. Add capabilities for real needs. Select `--preset full-product`
4
+ when the complete foundation is appropriate.**
5
+
6
+ ```mermaid
7
+ %%{init: {"flowchart": {"curve": "linear", "nodeSpacing": 35, "rankSpacing": 50, "padding": 18}}}%%
8
+ flowchart TB
9
+ subgraph minimal["1 · Minimal default"]
10
+ client["Expo · web / iOS / Android<br/>React Native Reusables · shadcn conventions<br/>NativeWind · shared tokens"]
11
+ web["Cloudflare static web Worker"]
12
+ client -->|"web export"| web
13
+ end
14
+
15
+ subgraph optional["2 · Optional capabilities · choose independently"]
16
+ backend["Hono API · Cloudflare Workers<br/>Public contracts · authorization"]
17
+ core["Data, accounts and files<br/>Drizzle / D1 · Better Auth · private R2 · KV"]
18
+ compute["AI, analytics and processing<br/>Workers AI · Analytics Engine · Basin<br/>Images · Queues · Cron · Workflows"]
19
+ media["Realtime and video<br/>Durable Object rooms · RealtimeKit<br/>Stream live / uploaded video"]
20
+ payments["Payments<br/>Stripe web · RevenueCat native<br/>Shared entitlements enforced by Hono"]
21
+ clients["Additional client<br/>WXT browser side panel"]
22
+ operations["External operations<br/>Resend email · Sentry monitoring"]
23
+ backend -.-> core
24
+ backend -.-> compute
25
+ backend -.-> media
26
+ backend -.-> payments
27
+ backend -.-> operations
28
+ clients -.->|"when a backend is needed"| backend
29
+ end
30
+
31
+ web ~~~ clients
32
+ web -.->|"add API service binding"| backend
33
+ client -.->|"native HTTPS when selected"| backend
34
+
35
+ subgraph full["3 · Full-product preset · selection summary"]
36
+ preset["Minimal app + all capabilities above<br/>22 selected products · no provider activation"]
37
+ end
38
+ core ~~~ preset
39
+ compute ~~~ preset
40
+ media ~~~ preset
41
+ payments ~~~ preset
42
+ operations ~~~ preset
43
+ ```
44
+
45
+ Solid lines show the minimal delivery path. Dashed lines summarize optional
46
+ integrations, not every network request or deployment. The full-product group is a
47
+ selection summary, not another runtime. Grouped capabilities remain separate
48
+ services; their exact connections depend on the implemented product.
49
+
50
+ ## Minimal default
51
+
52
+ | Part | Default |
53
+ | --- | --- |
54
+ | Client | Expo + React Native + Expo Router |
55
+ | Components | React Native Reusables with **shadcn conventions** |
56
+ | Styling | NativeWind + shared design tokens |
57
+ | Workspace | TypeScript + pnpm + Turborepo; shared TypeScript/ESLint configuration |
58
+ | Web hosting | Static Expo export on a Cloudflare asset Worker |
59
+ | Native delivery | Local development; EAS and app stores when requested |
60
+
61
+ Plain `anhedral init my-app` creates no API, auth, database, storage binding or
62
+ billing package. Static dynamic routes need build-time paths; SSR is a deliberate
63
+ alternative.
64
+
65
+ **Growth is additive.** `hono` adds the API and contracts. `d1` adds Hono and SQL.
66
+ `better-auth` adds Hono and a database. `r2` adds private server-side file storage.
67
+ Dependencies resolve automatically: an AI tool can have an API without accounts,
68
+ and an anonymous app can use SQL. Additions preserve edited source; backend or
69
+ hosting-engine migrations require explicit review.
70
+
71
+ ## Payments and AI
72
+
73
+ | Add | What it supplies |
74
+ | --- | --- |
75
+ | `stripe` | Web Checkout/customer portal; Hono, identity and durable billing state |
76
+ | `revenuecat` | Native purchase/restore/manage flows; shared identity and entitlements |
77
+ | `workers-ai` | Hono + AI binding; no implicit accounts, database or subscriptions |
78
+
79
+ Stripe and RevenueCat are independent. Hono verifies webhooks, reconciles provider
80
+ state and enforces paid access. Native purchases use Apple/Google billing;
81
+ RevenueCat synchronizes subscription state. Client purchase results never authorize
82
+ server operations. AI routes still need models, validation and usage limits.
83
+
84
+ ## Services, add-ons and alternatives
85
+
86
+ | Capability | Selection | Scope |
87
+ | --- | --- | --- |
88
+ | Analytics | `analytics-engine`, `basin` | Event dataset/helper; private Pipelines stream |
89
+ | Images | `images` | Binding and private raw-byte transform helper |
90
+ | Video | `video`, `stream` | Private uploaded-video helper; WHIP/WHEP live input helper |
91
+ | Conferencing | `realtimekit` | Server meeting and participant-token helpers |
92
+ | App messaging | `realtime` | Durable Object room Worker |
93
+ | Jobs | `queues`, `cron`, `workflows` | Queue/DLQ, scheduled and durable Worker foundations |
94
+ | Cache | `kv` | Eventually consistent configuration/cache |
95
+ | Extension | `wxt` | Browser side panel API, entrypoints and permissions |
96
+ | Operations | `resend`, `sentry` | Email factory and monitoring integration boundary |
97
+ | **Next.js on Vercel** | `next` | Usual explicit web frontend alternative |
98
+ | **Vinext on Cloudflare** | `vinext` | Additional explicit web frontend alternative |
99
+ | Data / identity alternatives | `neon`, `clerk` | Replace D1 / Better Auth |
100
+ | Specialized additions | `neon-realtime`, `openai` / `ai-sdk`, `posthog`, `electron`, `local-data` | Live SQL, alternative AI, product analytics, desktop or local persistence |
101
+
102
+ **Full-product includes:** Expo, WXT, Hono, Better Auth, D1, R2, KV, Stripe,
103
+ RevenueCat, Workers AI, Analytics Engine, Basin, Images, RealtimeKit, Durable Object
104
+ rooms, uploaded video, live Stream video, Queues, Cron, Workflows, Resend and Sentry.
105
+ Explicit Next.js/Vinext, Neon and Clerk replace their corresponding preset defaults.
106
+
107
+ Cloudflare hosts selected web/API, data, storage, AI and media services. Payment
108
+ providers, app stores, Resend, Sentry and Vercel remain external. Media travels
109
+ directly between clients and media services; Hono handles authorization and token
110
+ issuance. Provider activation, product routes/UI and real acceptance remain work
111
+ after scaffolding—especially room authorization, media clients and job processing.
112
+
113
+ ```sh
114
+ anhedral init my-app
115
+ anhedral add better-auth --cwd my-app --dry-run --json
116
+ anhedral init complete --preset full-product --dry-run --json
117
+ ```
118
+
119
+ Deployable code lives in `apps/*`; shared code lives in `packages/*`. Contracts,
120
+ database, auth, billing and service packages appear when selected. Small apps avoid
121
+ unneeded infrastructure; complex products use the same boundaries with more
122
+ capabilities.
@@ -10,6 +10,7 @@ Use the numbered workflow for application delivery, then the reference sections
10
10
  - [Application implementation and validation](#3-implement-the-product-and-integrations)
11
11
  - [Source, access and delivery](#5-establish-source-access-and-delivery-authority)
12
12
  - [Maintenance and recovery](#8-maintain-and-recover)
13
+ - [Evidence-driven maintenance](#evidence-driven-maintenance)
13
14
  - [Provider configuration](#provider-configuration)
14
15
  - [CLI behavior](#cli-behavior)
15
16
  - [Project dashboard](#project-dashboard)
@@ -23,7 +24,7 @@ For a booking app, “a member can create a booking, see it after reload, and ca
23
24
 
24
25
  Choose only the necessary catalog components. Decide whether the app is public or private, whether several clients share an API, and who owns production operations. Resolve decisions that materially affect architecture, access or cost before creating resources.
25
26
 
26
- Use the complete [stack catalog](stack-standard.md#defaults-and-foundations) to choose applications, data/identity, services and SDK integrations. Plain initialization supplies the Vinext web foundation without a database or identity provider. Include the web flag when combining it with another interface; for example, `--vinext --hono --expo --neon` selects web, API, mobile and PostgreSQL. Better Auth defaults to D1, Neon Realtime adds Neon, and RevenueCat requires an explicit Stripe selection. Review the [composition rules](stack-standard.md#composition-and-compatibility) before choosing a delivery engine: OpenNext, Queues and Basin use Wrangler, and later additions do not switch an existing Void workspace to Wrangler.
27
+ Choose the smallest sufficient capability set from the [stack catalog](stack-standard.md#progressive-selection-and-full-product-preset). Plain init creates only Expo, shared styling and workspace tooling. Add Hono for server logic, Drizzle/D1 for persistence, Better Auth for accounts and private R2 for uploads only when needed. Dependencies are resolved automatically; no accounts or billing are inferred for an AI-only app. Use `--preset full-product` for the complete compatible foundation including Cloudflare AI, analytics, realtime/conferencing, image/video, jobs and both payment providers. Explicit provider/frontend alternatives replace preset defaults. Inspect generated guides and support metadata; scaffolding does not activate services or establish product behavior. Existing backend ownership and edited source remain protected. New Expo/Images/Analytics Engine/Queues/Basin use Wrangler; additions do not silently migrate an existing Void workspace.
27
28
 
28
29
  Record what each recipe supplies and what the product still needs. Sentry, device-local data and RevenueCat require platform integration work; SDK factories need consumers; room messaging, live video, job processing and workflows need product behavior. Select `--stream` for one-to-many WHIP/WHEP broadcasts; Stream activation, live input ownership, creator/player UI and private playback verification remain explicit integration work. The catalog's generated-scope and setup columns describe these boundaries.
29
30
 
@@ -34,8 +35,8 @@ Record what each recipe supplies and what the product still needs. Sentry, devic
34
35
  Use Node.js `24.21.0+` and pnpm `10.34.5` for the default stack. Match the installed CLI version to the plugin's bundled registry `cliVersion` when using Codex. Pin that version for repeatable automation. For unpublished checkout work, run `pnpm build` and use `node dist/bin.js`; building does not update installed releases.
35
36
 
36
37
  ```sh
37
- anhedral init my-app --vinext --hono --d1 --better-auth --r2 --dry-run --json
38
- anhedral init my-app --vinext --hono --d1 --better-auth --r2
38
+ anhedral init my-app --expo --d1 --better-auth --r2 --dry-run --json
39
+ anhedral init my-app --expo --d1 --better-auth --r2
39
40
  cd my-app
40
41
  pnpm dev
41
42
  ```
@@ -57,6 +58,8 @@ Additions use the bundled catalog and preserve edited source. Resolve conflicts
57
58
 
58
59
  **Ready to implement:** the workspace starts, the selected packages have clear consumers, and remaining setup is understood.
59
60
 
61
+ Root `pnpm dev` exports Expo web and runs its Wrangler gateway on port 3000 with Hono on port 8787 when selected. Native Metro remains `pnpm --dir apps/mobile start`; use the iOS/Android scripts for native development. Browser changes initially require `pnpm --dir apps/mobile build:web` to re-export; this is not HMR. The gateway entry is `apps/mobile/worker/index.ts`, static assets are `apps/mobile/dist`, and the Worker service name is `<project>-mobile`. New Expo workspaces use Wrangler for both targets; preserve existing delivery-engine selections.
62
+
60
63
  ## 3. Implement the product and integrations
61
64
 
62
65
  Build the acceptance flows with real persistence, validation and server-side authorization. Include loading, empty and failure states. Exercise denied access and cross-user/tenant isolation, not just the successful path. Keep shared contracts in packages and privileged code on servers.
@@ -81,7 +84,7 @@ anhedral inspect --json
81
84
 
82
85
  `pnpm check` runs lint, types, Fallow analysis, dependency audit, tests and builds; the explicit OpenNext profile also builds its Worker output. Add meaningful product tests as you implement features. `doctor` checks local readiness and provenance. `inspect` reads local selection, setup and recorded delivery evidence offline; neither certifies live product behavior.
83
86
 
84
- Exercise the actual runtime as well as compilation: Vinext/Vite workerd preview, OpenNext Worker preview, or native Next.js as selected. For mobile, desktop and extensions, check relevant device/packaged behavior and permissions. Verify retry, webhook duplication, private files, AI limits and recovery for the services you selected.
87
+ Exercise the actual runtime as well as compilation: Expo static web behind its Cloudflare gateway plus Hono, or explicit Vinext/Vite workerd preview, OpenNext Worker preview, or native Next.js as selected. A reference app should prove browser/API calls and separately export iOS/Android bundles; native export success is not device acceptance. For mobile, desktop and extensions, check relevant device/packaged behavior and permissions. Verify retry, webhook duplication, private files, AI limits and recovery for the services you selected.
85
88
 
86
89
  Record commands, results and gaps in the application's `docs/verification.md`. Distinguish local, preview and live results. A smoke check or HTTP 200 establishes availability of that route, not completion of the product.
87
90
 
@@ -130,7 +133,7 @@ anhedral status --refresh --json
130
133
 
131
134
  The dry run previews setup and delivery without provider operations. Actual `ship` coordinates supported integration setup, private runtime configuration, checks and hosting delivery. In mixed projects it handles Cloudflare services before the Vercel web app; provider flags select one target explicitly.
132
135
 
133
- For supported Cloudflare selections, Void owns provisioning and deployment. `provision` reports the plan and defers writes to Void. Explicit OpenNext, Queues/DLQ and Basin use Wrangler; standalone `provision` reconciles Cloudflare resources only. The integration adapters and their limits are documented in the provider reference.
136
+ New Expo workspaces use Wrangler for Hono and the web gateway. For other supported Cloudflare selections, Void owns provisioning and deployment. `provision` reports the plan and defers writes to Void. New Expo workspaces, explicit OpenNext, Queues/DLQ and Basin use Wrangler; standalone `provision` reconciles Cloudflare resources only. The integration adapters and their limits are documented in the provider reference.
134
137
 
135
138
  **Treat `configuration-required` as a checkpoint.** Wrangler can stop before deployment when resolved resource IDs change tracked bindings. Void can activate a target before recording new resource identities in `void.lock.json`; Anhedral retains activation receipts and then requires review and a commit. Inspect those results, commit the expected changes, and ship the clean configuration again. Do not assume a nonzero result means nothing happened. Anhedral never commits source automatically. Multiple Workers are not an atomic release.
136
139
 
@@ -206,6 +209,60 @@ Keep alerts, dependency updates, quotas, retry/concurrency limits and shutdown c
206
209
 
207
210
  Use `anhedral help <command>` for exact options. See [provider configuration](software-factory.md#provider-configuration) for integration setup/retries and [CLI behavior](https://github.com/anhedral/anhedral-cli/blob/main/docs/software-factory.md#cli-behavior) for machine output and previews. The optional [Codex inspector](software-factory.md#project-dashboard) uses the same project logic; it does not replace runtime or product acceptance.
208
211
 
212
+ ## Evidence-driven maintenance
213
+
214
+ Use this workflow for maintenance in the CLI, plugin and generated applications. It adapts lessons from OpenAI's [Maintaining software with the GPT-6 family](https://developers.openai.com/blog/maintaining-software-with-the-gpt-6-family) to Anhedral's source generators, published contracts and provider boundaries. It does not authorize a new audit, external mutation or release outside the requested work.
215
+
216
+ ### Establish the case before editing
217
+
218
+ Inspect the current branch, working tree, owning instructions and relevant history. Define the behavior to preserve and the evidence that would justify changing it. For a broad audit, rank candidates by confidence, maintenance burden and measured runtime or CI cost. Keep uncertain candidates visible with the missing evidence; do not turn an incomplete inventory into a claim that everything else is safe.
219
+
220
+ Use Fallow and source searches to find candidates, then trace their consumers. In this repository, include `src/index.ts` exports, command dispatch, registry-selected recipes, emitted source strings, generated package scripts, plugin/MCP entrypoints and source-only examples. An internal import search alone cannot establish that a published API or generated recipe is unused. Check aliases, wrappers, computed names and external consumers where relevant. Keep compatible entrypoints unless a breaking change is explicitly in scope.
221
+
222
+ For each proposed removal, capture the symbol or configuration, callsites, history, evidence links or commands, expected behavior and unresolved dependencies. Use authorized read-only provider configuration, CI history and telemetry when they can resolve uncertainty. Note environment, source revision and observation window. Zero observed traffic is supporting evidence, not proof that a recovery path is obsolete. If live access is unavailable, finish source analysis and mark that candidate unverified.
223
+
224
+ ### Preserve operational controls
225
+
226
+ Before retiring an experiment or constant flag, check its current authoritative value, targeting rules, dependent flags and all consuming services. Follow indirect references through schemas, aliases and dynamically constructed keys. Local overrides and SDK defaults do not establish production values. Preserve kill switches, emergency fallbacks, access boundaries, retry limits and recovery controls unless their retirement is explicitly justified and authorized. A permanent designation or conflicting evidence needs owner resolution before removal. A code cleanup does not imply permission to delete provider configuration or resources.
227
+
228
+ ### Prepare a bounded change and verify it
229
+
230
+ Group work by a single rationale and ownership boundary; separate unrelated candidates into small changes. Explain why behavior is preserved, including the dependency chain for flag removals. Add a meaningful regression for a code defect and exercise affected consumers. Recipe changes need generated-output checks; package/export changes need packed-consumer checks; provider behavior needs its relevant local contracts and separately scoped live evidence. Use the existing release gates when releasing. Report measured savings with the measurement method, and label estimates explicitly.
231
+
232
+ For flaky tests, inspect recent failed and successful CI runs at the same revision where possible. Distinguish product failures from timing, shared state, platform and infrastructure problems. Reproduce the failure or capture a concrete causal trace, fix that cause and rerun the affected case under the relevant conditions. Do not replace assertions with sleeps, increase retries to conceal failures, or disable required checks as a fix. When evidence is insufficient, report the suspected cause and next diagnostic step.
233
+
234
+ ### Improve agent context with evidence
235
+
236
+ Keep enduring instructions in the owning `AGENTS.md` or skill and detailed procedures in linked references. When an instruction appears to cause unnecessary work, use the original task and an isolated repository snapshot to compare the current instruction with one narrow correction. Hold model, effort, tools and inputs constant; compare correctness, tool calls, tokens, elapsed time and cost where available. Replays must avoid duplicate provider writes, messages or releases. If a replay cannot be run, call the edit a proposed improvement rather than a measured gain.
237
+
238
+ Use the configured model and effort for routine work. Consider a stronger reasoning setting for unresolved dependency chains or broad audits when cost and authorization permit; the article's benchmark is not an Anhedral quality or cost guarantee. Revisit corrective prompts when models change rather than accumulating permanent workarounds. Put accepted findings and verification gaps in `docs/verification.md`, and carry only durable, demonstrated lessons into shared instructions.
239
+
240
+ Expo remains pinned to SDK 57; current SDK 58 documentation is not an upgrade instruction. Static web cannot resolve arbitrary unknown dynamic paths at request time: provide build-time `generateStaticParams` for exported route IDs or deliberately select an implemented SPA/server profile. Experimental SSR is not the default. The reference app uses fixed health/account paths.
241
+
242
+ ## Cross-platform identity and optional billing
243
+
244
+ New Expo workspaces include Better Auth, Drizzle/D1 and private R2. Expo generates separate browser/native session clients, an exact trusted app scheme, SecureStore cookie transport and sign-in/account screens. Native calls the reachable `EXPO_PUBLIC_API_URL`; Hono derives the user from the session. Local browser/API checks and native exports are separate from development-build/device acceptance. Explicit Clerk retains its own adapter/setup requirements.
245
+
246
+ Select `--stripe`, `--revenuecat` or both explicitly. They add shared Hono billing, database schema, public contracts and selected Expo billing UI. Neither requires the other. Web uses server-created Stripe Checkout and Customer Portal; native RevenueCat provides purchase, restore and management flows. The verified auth `user.id` is the shared billing identity. Client purchase results and SDK `CustomerInfo` never grant server access.
247
+
248
+ | Hono route | Generated contract |
249
+ | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
250
+ | `GET /api/billing/identity` | Signed-in `appUserId`, selected providers and safe plan IDs/labels. |
251
+ | `GET /api/billing/entitlements` | Entitlement keys, `active`, nullable expiry, provider sources and `checkedAt`. |
252
+ | `POST /api/billing/refresh` | Strict empty JSON body; refreshes the signed-in account. |
253
+ | `POST /api/billing/checkout` | Strict `{ plan }`; UUID `Idempotency-Key`; server selects configured Stripe Price and returns URL. |
254
+ | `POST /api/billing/portal` | Strict empty JSON body; returns the signed-in customer's management URL. |
255
+ | `GET /api/billing/premium` | Example of the server entitlement guard; adapt the guarded business flow deliberately. |
256
+ | `POST /api/webhooks/stripe`, `/api/webhooks/revenuecat` | Provider-authenticated durable metadata inbox and canonical reconciliation. |
257
+
258
+ Hono independently projects Stripe and RevenueCat state and unions active entitlement grants. When both are enabled it excludes RevenueCat Stripe-origin grants, avoiding stale duplicate grants after Stripe revocation. Canonical refresh uses a fenced account lease; cached grants have a bounded 60-second freshness window and fail closed after expiry during provider outage. The durable inbox retries on a bounded five-minute scheduled handler; duplicate/reordered events do not directly overwrite grants. Stripe verifies raw-body signatures. RevenueCat requires configured webhook authorization and uses optional signing verification when configured. Account/environment/provider IDs are validated; configuration is not purchase proof.
259
+
260
+ Read generated `packages/billing/README.md` and `apps/api/.dev.vars.example`. Configure `BILLING_ORIGIN`, `BILLING_ENVIRONMENT`, `BILLING_PLANS_JSON`, `BILLING_ENTITLEMENTS_JSON` and `BILLING_PREMIUM_ENTITLEMENT`. Stripe needs its runtime/signing secrets. RevenueCat needs a scoped runtime key, webhook authorization, allowed app IDs and project ID, plus public iOS/Android SDK keys. Keep management keys separate. Generate/review/apply billing SQL explicitly; init and builds never migrate a configured database. Configure account products/Prices, native offerings and store credentials before acceptance.
261
+
262
+ Check logout/account-switch handling, late SDK callbacks, restore/transfer policy, provider outage, duplicate/reordered webhooks, invalid signatures, refunds/disputes and cross-user denial. Use actual iOS/Android development builds and Apple/Google sandboxes for purchase acceptance; Expo Go, exports and synthetic SDK/provider tests cannot establish real purchases. Existing billing-guidance/scaffold projects require a reviewed migration rather than silent replacement. Managed portal full-stack publishing remains separate implementation work.
263
+
264
+ References: [Better Auth Expo](https://better-auth.com/docs/integrations/expo), [Expo development builds](https://docs.expo.dev/develop/development-builds/introduction/), [RevenueCat Expo](https://www.revenuecat.com/docs/getting-started/installation/expo), [RevenueCat customer identity](https://www.revenuecat.com/docs/customers/identifying-customers), [RevenueCat webhooks](https://www.revenuecat.com/docs/integrations/webhooks), [Stripe subscription webhooks](https://docs.stripe.com/billing/subscriptions/webhooks).
265
+
209
266
  ## Provider configuration
210
267
 
211
268
  Anhedral scaffolds source, guides authentication, and provisions and configures the selected stack before deployment. The application and accounts belong to the developer or client. Feature development, design, custom integrations, and ongoing maintenance are Anhedral's services.
@@ -267,7 +324,7 @@ Replace example organization IDs with the intended account's actual identifiers.
267
324
 
268
325
  ### Delivery and retries
269
326
 
270
- For new supported Cloudflare workspaces, Void owns resource provisioning and deployment; Anhedral does not run its resource creator in parallel. Explicit resource declarations remain in `anhedral.cloudflare.json`, and Void records resolved identities in `void.lock.json`. Explicit OpenNext, queue/DLQ and Basin selections use Wrangler. Wrangler provisioning reconciles D1, private R2 buckets, KV, Queues, and private JSON Basin streams. Basin HTTP ingestion stays disabled; the Worker binding is enabled. Sinks and transformations require application-specific design. Durable Objects, schedules, Workflows, and Workers AI bindings are configured through Worker deployment. Hyperdrive configurations added by a developer still require an explicit provider workflow.
327
+ For new Expo workspaces, Wrangler owns API/gateway deployment. For other supported Cloudflare workspaces, Void owns resource provisioning and deployment; Anhedral does not run its resource creator in parallel. Explicit resource declarations remain in `anhedral.cloudflare.json`, and Void records resolved identities in `void.lock.json`. New Expo workspaces, explicit OpenNext, queue/DLQ and Basin selections use Wrangler. Wrangler provisioning reconciles D1, private R2 buckets, KV, Queues, and private JSON Basin streams. Basin HTTP ingestion stays disabled; the Worker binding is enabled. Sinks and transformations require application-specific design. Durable Objects, schedules, Workflows, and Workers AI bindings are configured through Worker deployment. Hyperdrive configurations added by a developer still require an explicit provider workflow.
271
328
 
272
329
  If Wrangler resource provisioning changes tracked binding IDs, `ship` returns `configuration-required` before deployment. Void may already activate targets before writing new resource identities to their locks. When only the expected `void.lock.json` files change, it retains the activation receipts and returns `configuration-required`; live product verification remains blocked. Review and commit the changed bindings or locks, then ship the clean configuration. It never commits code automatically. Pending Neon operations or unverified Resend DNS return `provider-configuration-required` and stop deployment. The configured integrations' remaining product setup appears in their results.
273
330
 
@@ -451,7 +508,7 @@ Open `http://127.0.0.1:4317/`. The preview binds only to loopback, validates Hos
451
508
 
452
509
  `src/project-inspector.ts` owns projection; `src/catalog-snapshot.ts` adds catalog identity. The browser only renders its validated schema. The MCP server exposes `open_projects`, `list_projects`, `get_project`, `get_project_services`, local metadata tools and model-only source/catalog context tools. They remain useful without UI rendering. Standard MCP Apps resources and bridge messages provide the optional panel, host themes and inline/fullscreen modes. Native host-specific draft support is a separate acceptance gate.
453
510
 
454
- The plugin and standalone CLI share one private catalog. List views read bounded summaries; only a selected project loads detailed inspection. The server does not scan for other projects. CLI initialization registers new apps using the persistent `identity.id` in `anhedral.json`; recreating a directory creates a separate app rather than silently retargeting an old catalog entry. A remote server cannot inspect these local directories without a separately reviewed architecture; never publish the local catalog through a tunnel.
511
+ The six focused skills (Init, Dev, Design, Auth, Billing and Hosting) share plugin-wide references in `plugins/codex/distribution/references`. The plugin and standalone CLI share one private catalog. List views read bounded summaries; only a selected project loads detailed inspection. The server does not scan for other projects. CLI initialization registers new apps using the persistent `identity.id` in `anhedral.json`; recreating a directory creates a separate app rather than silently retargeting an old catalog entry. A remote server cannot inspect these local directories without a separately reviewed architecture; never publish the local catalog through a tunnel.
455
512
 
456
513
  ### Recovery and release review
457
514
 
@@ -521,8 +578,10 @@ Keep application-facing guidance in the stack standard and this factory, with on
521
578
 
522
579
  Before release, review the entire diff, run `pnpm release:check` and `pnpm plugin:check`, and exercise affected generated profiles with `pnpm test:integration`. The full local release gate includes external advisory refresh, exact patch regressions, packed installation and package allowlisting. A restricted local environment can leave network, listener or browser checks blocked; record that boundary and require the corresponding hosted CI evidence. Do not disable required checks to make a release pass.
523
580
 
581
+ `README.md`, `CONTRIBUTING.md`, `.github/CONTRIBUTING.md`, `.github/PULL_REQUEST_TEMPLATE.md` and `docs/**/*.md` changes use lightweight CI: check the diff for whitespace errors and skip builds, browser tests, registry/generated-project matrices and release artifacts. All other paths, including plugin instructions, run full CI. The workflow still starts for every PR and push to main. Required matrix checks report a quick documentation-only success without installing dependencies; other expensive jobs are skipped. This preserves the existing branch-protection check names. Scope-detection failures also fail the existing Checks jobs. Merging documentation updates GitHub immediately and needs no version bump or npm publication. Packaged documentation updates with the next release. To deliberately release a documentation-only commit, manually run CI on main first; manual runs always execute the full matrix and produce the reviewed candidate.
582
+
524
583
  For a new version, update `package.json`, `src/version.ts` and the immutable marketplace `plugin-v<version>` reference in `.agents/plugins/marketplace.json`. Build regenerates plugin manifest and registry versions. Commit all source and generated references, open a focused PR and wait for its checks before merging. Keep the owner's local checkout on `main` and synchronize it with the merged source without discarding unrelated work.
525
584
 
526
- Publication uses `.github/workflows/release-on-main.yml` (Release Reviewed Candidate). It is dispatched explicitly against the exact current main commit, after its main-branch CI succeeds. Main CI builds and uploads the `release-candidate` artifact. Download it and review `metadata.json`, including its CLI `integrity` and matching `plugin.integrity`; dispatch with those exact values as `release_sha`, `cli_integrity` and `plugin_integrity`. The release workflow rebuilds, compares both immutable artifacts, runs the OS/Node portability matrix, publishes through npm trusted publishing and then creates the GitHub release and immutable plugin source tag. Do not manually publish a different tarball or move an existing release tag.
585
+ Publication uses `.github/workflows/release-on-main.yml` (Release Reviewed Candidate). It is dispatched explicitly against the exact current main commit, after its main-branch CI succeeds. Main CI builds and uploads the `release-candidate` artifact. Download it and review `metadata.json`, including its CLI `integrity` and matching `plugin.integrity`; dispatch with those exact values as `release_sha`, `cli_integrity` and `plugin_integrity`. The release workflow downloads that exact successful main CI candidate without rebuilding or reinstalling dependencies, verifies both reviewed integrities, runs the OS/Node portability matrix, publishes through npm trusted publishing and then creates the GitHub release and immutable plugin source tag. Do not manually publish a different tarball or move an existing release tag.
527
586
 
528
587
  Verify the workflow completed, npm exposes the intended version/integrity, the GitHub release has the CLI tarball and matching plugin ZIP/metadata, and `plugin-v<version>` resolves to the expected release source. Packaging or merging alone does not establish publication. An installed plugin remains at its installed version until updated through its host. Maintain the exact source, checks, artifact identities and unresolved acceptance gaps in the verification record.