anhedral 0.11.2 → 0.12.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.
- package/README.md +107 -14
- package/dist/bin.js +48 -493
- package/dist/capabilities.d.ts +3 -3
- package/dist/capability-contract.js +4 -0
- package/dist/cli-arguments.d.ts +8 -0
- package/dist/cli-arguments.js +32 -0
- package/dist/cli-commands.d.ts +3 -0
- package/dist/cli-commands.js +114 -0
- package/dist/cli-delivery.d.ts +3 -0
- package/dist/cli-delivery.js +172 -0
- package/dist/cli-output.js +231 -205
- package/dist/delivery-evidence.d.ts +62 -0
- package/dist/delivery-evidence.js +186 -0
- package/dist/delivery.d.ts +3 -40
- package/dist/delivery.js +4 -181
- package/dist/dependencies.d.ts +1 -0
- package/dist/dependencies.js +2 -0
- package/dist/mobile-delivery.d.ts +21 -44
- package/dist/mobile-delivery.js +127 -80
- package/dist/provider-auth.js +3 -3
- package/dist/scaffold/documentation.js +1 -0
- package/dist/scaffold/stream.d.ts +2 -0
- package/dist/scaffold/stream.js +114 -0
- package/dist/service-readers.js +1 -1
- package/dist/services-command.js +8 -6
- package/dist/ship.d.ts +15 -15
- package/dist/stack-registry.d.ts +4 -2
- package/dist/stack-registry.js +16 -0
- package/dist/transaction-lock.d.ts +15 -0
- package/dist/transaction-lock.js +227 -0
- package/dist/transaction.js +2 -208
- package/dist/vercel-project.d.ts +101 -0
- package/dist/vercel-project.js +305 -0
- package/dist/vercel.d.ts +3 -36
- package/dist/vercel.js +3 -300
- package/dist/version.d.ts +1 -1
- package/dist/version.js +1 -1
- package/docs/software-factory.md +339 -3
- package/docs/stack-standard.md +138 -30
- package/docs/verification.md +444 -0
- package/package.json +2 -5
- package/docs/cli-design.md +0 -67
- package/docs/plugin-ui.md +0 -102
- package/docs/provider-configuration.md +0 -116
- package/docs/void-verification.md +0 -185
package/docs/stack-standard.md
CHANGED
|
@@ -4,42 +4,118 @@ This is the architecture standard for applications generated by Anhedral. Use it
|
|
|
4
4
|
|
|
5
5
|
The default web foundation is Vinext, React, TypeScript, Tailwind, shadcn/ui and Lucide on Cloudflare Workers. Every project uses pnpm workspaces and Turborepo. Add components for a concrete product requirement; the default does not include a database, identity provider or every available service.
|
|
6
6
|
|
|
7
|
+
## Defaults and foundations
|
|
8
|
+
|
|
9
|
+
| Area | Default behavior |
|
|
10
|
+
| ------------------------------- | ---------------------------------------------------------------------------------------------------- |
|
|
11
|
+
| Application | Vinext web app; Cloudflare hosting |
|
|
12
|
+
| Workspace | pnpm workspaces, Turborepo and one root lockfile, including single-app projects |
|
|
13
|
+
| Shared tooling | `packages/typescript-config` and `packages/eslint-config` |
|
|
14
|
+
| Web UI | Shared `packages/ui`, shadcn/ui conventions, React, Tailwind and Lucide |
|
|
15
|
+
| Cloudflare delivery | Void for supported selections; explicit OpenNext, Queues and Basin use Wrangler |
|
|
16
|
+
| Runtime | Node.js `24.21.0+` for Void; pnpm `10.34.5` |
|
|
17
|
+
| Configuration | One root `anhedral.json`; application tooling stays beside its app |
|
|
18
|
+
| Data, identity and integrations | Opt-in; no database, authentication, billing, email or analytics service is selected by plain `init` |
|
|
19
|
+
| Generation | Source and dependency setup; no cloud provisioning, deployment or automatic source commit |
|
|
20
|
+
|
|
21
|
+
The registry contains 28 selectable products and four foundation entries: `workspace`, `typescript`, `eslint` and `ui`. The first three accompany every project; `ui` accompanies web applications. Product flags select recipes; the resolver supplies required foundation dependencies.
|
|
22
|
+
|
|
7
23
|
## Select the applications
|
|
8
24
|
|
|
9
|
-
| Need | Selection |
|
|
10
|
-
| ------------------------------ | ----------------------------- |
|
|
11
|
-
| Web on Workers | Default, or `--vinext` | Vinext
|
|
12
|
-
| Native Next.js on Vercel | `--next` | Next.js
|
|
13
|
-
| Next.js on Workers | `--next --hosting=cloudflare` | OpenNext adapter and Wrangler delivery
|
|
14
|
-
| API shared by multiple clients | `--hono` | Hono Worker with OpenAPI contracts
|
|
15
|
-
| iOS and Android | `--expo` | Expo, React Native
|
|
16
|
-
| Desktop | `--electron` | Electron and
|
|
17
|
-
| Browser extension | `--wxt` | WXT
|
|
25
|
+
| Need | Selection | Destination and generated architecture |
|
|
26
|
+
| ------------------------------ | ----------------------------- | --------------------------------------------------------------------------------------------------- |
|
|
27
|
+
| Web on Workers | Default, or `--vinext` | `apps/web`; Vinext, Vite and React on Cloudflare |
|
|
28
|
+
| Native Next.js on Vercel | `--next` | `apps/web`; native Next.js and Vercel configuration |
|
|
29
|
+
| Next.js on Workers | `--next --hosting=cloudflare` | `apps/web`; OpenNext adapter and Wrangler delivery |
|
|
30
|
+
| API shared by multiple clients | `--hono` | `apps/api`; Hono Worker with OpenAPI/Zod contracts and health route |
|
|
31
|
+
| iOS and Android | `--expo` | `apps/mobile`; Expo, React Native, Expo Router, NativeWind and React Native Reusables configuration |
|
|
32
|
+
| Desktop | `--electron` | `apps/desktop`; Electron, React, Vite, isolated preload and platform packaging configuration |
|
|
33
|
+
| Browser extension | `--wxt` | `apps/extension`; WXT/React Chrome side panel with user-triggered active-page access |
|
|
18
34
|
|
|
19
|
-
For example, `--vinext --hono --expo --neon` selects web, an API, mobile and PostgreSQL. `--expo` alone selects mobile.
|
|
35
|
+
For example, `--vinext --hono --expo --neon` selects web, an API, mobile and PostgreSQL. Explicit application flags replace the default application selection: `--expo` alone selects mobile, and `--hono` alone selects the API. If only add-ons are requested, the resolver includes a default web app: `--neon` selects Neon and Vinext. Vinext and Next.js are alternatives. Native Next.js defaults to Vercel; Vinext uses Workers.
|
|
20
36
|
|
|
21
37
|
Use server routes inside the web app when it is the only consumer. Add Hono when mobile, desktop, extensions or independent clients need a shared API. Browser and device clients access server endpoints; they never import database factories or receive server credentials. Check actual Vinext behavior in its Worker runtime rather than assuming native Next.js parity.
|
|
22
38
|
|
|
23
|
-
## Select data
|
|
24
|
-
|
|
25
|
-
|
|
|
26
|
-
|
|
|
27
|
-
|
|
|
28
|
-
|
|
|
29
|
-
|
|
|
30
|
-
|
|
|
31
|
-
|
|
|
32
|
-
| WebSocket rooms | `--realtime` | Cloudflare Durable Objects; define identity and reconnect behavior |
|
|
33
|
-
| Live SQL results | `--neon-realtime` | Neon sealed-query server/client factories; see below |
|
|
34
|
-
| Background work | `--queues`, `--cron`, `--workflows` | Define idempotency, retry limits, concurrency and failure recovery |
|
|
35
|
-
| Inference | `--workers-ai`, `--openai`, `--ai-sdk` | Server-side calls with explicit model, cost and usage limits |
|
|
36
|
-
| Transactional email | `--resend` | Verified sending domain, templates and delivery handling |
|
|
37
|
-
| Billing | `--stripe`, `--revenuecat` | Application-specific products, entitlements and verified webhooks/purchases |
|
|
38
|
-
| Errors and analytics | `--sentry`, `--posthog`, `--basin` | Initialize SDKs/events and define privacy and operating ownership |
|
|
39
|
-
| Device-local data and shared styling | `--local-data`, `--styling` | Select for supported client requirements |
|
|
39
|
+
## Select data and identity
|
|
40
|
+
|
|
41
|
+
| Selection | Destination and generated scope | Required implementation/setup |
|
|
42
|
+
| --------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- |
|
|
43
|
+
| `--d1` | `packages/db`; Drizzle/D1 factory, schema and explicit migration tooling; `DB` Worker binding | Create/reconcile the database, define product tables and review SQL; one deployment migration owner |
|
|
44
|
+
| `--neon` | `packages/db`; Drizzle/Neon HTTP factory, schema and transactional migration tooling | Select project/role, configure runtime and separate direct migration connections, review SQL |
|
|
45
|
+
| `--better-auth` | `packages/auth` and database schema; auth routes on the selected server | Private secret, public auth origin, migrations, sign-up policy and resource authorization |
|
|
46
|
+
| `--clerk` | Web provider, sign-in/up pages and middleware when web is selected; `packages/auth` backend helper when Hono is selected | Configure keys, origins, protected routes and native client integration as needed |
|
|
47
|
+
| `--local-data` | `packages/local-data`; async read/write interface | Implement platform-specific SQLite/filesystem adapters, offline behavior and synchronization |
|
|
40
48
|
|
|
41
49
|
D1 is the standard choice when Worker-local SQL fits. Choose Neon when the application needs PostgreSQL semantics. Better Auth supplies application-controlled identity; Clerk supplies hosted identity. Hosting audience protection is a separate access layer from either choice.
|
|
42
50
|
|
|
51
|
+
## Select services
|
|
52
|
+
|
|
53
|
+
| Selection | Destination and generated scope | Required implementation/setup |
|
|
54
|
+
| ----------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
|
|
55
|
+
| `--r2` | Selected server's private `FILES` binding and `private-files.md` | Authorized upload/download/delete endpoints and file ownership checks; no public bucket or generic file API is generated |
|
|
56
|
+
| `--kv` | Selected server's `CONFIG` binding | Keys, TTLs and propagation handling; never use KV as transactional authority |
|
|
57
|
+
| `--realtime` | `apps/realtime`; SQLite-backed Durable Object rooms and WebSocket message forwarding | Authenticate connections, authorize membership, isolate rooms and handle reconnects; public entry returns 501 until implemented |
|
|
58
|
+
| `--neon-realtime` | `packages/neon-realtime`; separate sealing server/subscription client factories and Drizzle adapter | Manually activate the selected branch, configure origins and implement authorized queries, renewal and cleanup |
|
|
59
|
+
| `--stream` | `packages/stream`; server-only Cloudflare Stream live input factory for WHIP/WHEP broadcasts | Activate Stream manually; implement creator/player UI, input ownership, media negotiation, playback privacy and teardown |
|
|
60
|
+
| `--queues` | `apps/jobs`; queue producer/consumer, retry limits and dead-letter configuration; producer binding on a selected server | Transactional idempotency, processing and dead-letter recovery; the starter retries messages instead of acknowledging unimplemented work |
|
|
61
|
+
| `--cron` | `apps/scheduled`; scheduled Worker with an hourly starter trigger | Product schedule, task implementation, overlap policy, idempotency and failure visibility |
|
|
62
|
+
| `--workflows` | `apps/workflows`; durable workflow and a retryable validation step | Authorized invocation, product steps, retry/resume/cancel behavior and recovery |
|
|
63
|
+
| `--workers-ai` | Selected server's `AI` Worker binding | Model calls, authorization, input handling, usage and spending limits |
|
|
64
|
+
|
|
65
|
+
`--realtime` and `--neon-realtime` are independent and can coexist. The former supplies room-based messaging infrastructure; the latter supplies live SQL query integration. Neither generates a complete collaboration or subscription feature.
|
|
66
|
+
|
|
67
|
+
## Select SDKs and integrations
|
|
68
|
+
|
|
69
|
+
| Selection | Destination and generated scope | Required implementation/setup |
|
|
70
|
+
| -------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
|
|
71
|
+
| `--openai` | `packages/ai`; direct server-side OpenAI SDK factory | Models, routes, failure handling and usage limits |
|
|
72
|
+
| `--ai-sdk` | `packages/ai`; AI SDK `generateText`/`streamText` exports and OpenAI provider | Streaming, tools, cancellation and provider configuration; generated credentials default to OpenAI |
|
|
73
|
+
| `--resend` | `packages/email`; server SDK factory | Verified sending domain, templates, delivery/bounce handling and webhook verification |
|
|
74
|
+
| `--stripe` | `packages/billing`; server SDK factory | Products/prices, purchase/cancellation flows, signed webhooks, entitlements and idempotency |
|
|
75
|
+
| `--revenuecat` | `packages/billing/revenuecat.md`; cross-store integration guidance | Install platform SDKs and configure store products, offerings, purchase/restore flows and entitlement reconciliation |
|
|
76
|
+
| `--sentry` | `packages/observability`; integration boundary and redaction fields | Install/init platform SDKs, configure private source-map uploads and verify alerts |
|
|
77
|
+
| `--posthog` | `packages/analytics`; server analytics factory | Event schema, consent, privacy filtering and event delivery |
|
|
78
|
+
| `--basin` | `packages/analytics`, or `packages/basin` alongside PostHog; event helper and private `ANALYTICS` stream binding | Event schema, ingestion verification and application-specific sink/transformation design |
|
|
79
|
+
| `--styling` | `packages/styling`; light/dark tokens and Tailwind v3 preset used by Expo/WXT | Platform typography/components and adoption by other interfaces; automatically selected with Expo and WXT |
|
|
80
|
+
|
|
81
|
+
OpenAI and AI SDK are alternative recipes for `packages/ai`; Workers AI can accompany either. PostHog and Basin can coexist: the Basin recipe changes its package destination to avoid a collision. Electron starts with its own renderer styling; shared tokens do not imply one component library across every platform.
|
|
82
|
+
|
|
83
|
+
The provider adapters can configure selected Neon projects/connections, Clerk applications/keys, Resend domains/sending keys, Stripe account/webhook setup, RevenueCat projects/apps/keys, Sentry projects/DSNs, PostHog projects and OpenAI projects/service accounts. This automation is separate from the generated application integration. See [provider configuration](software-factory.md#provider-configuration) for fields, credentials, permissions and remaining owner steps. Neon Realtime activation is manual.
|
|
84
|
+
|
|
85
|
+
## Composition and compatibility
|
|
86
|
+
|
|
87
|
+
| Choice | Resolver behavior |
|
|
88
|
+
| ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
|
|
89
|
+
| No application flag | Adds Vinext, or Next.js when Vercel hosting is selected |
|
|
90
|
+
| `--next` without a hosting flag | Selects Vercel |
|
|
91
|
+
| Vinext with Vercel | Rejected; Vinext requires Cloudflare |
|
|
92
|
+
| Vinext and Next.js; D1 and Neon; Better Auth and Clerk; OpenAI and AI SDK | Each pair is mutually exclusive |
|
|
93
|
+
| Better Auth without a database | Adds D1; an explicit Neon selection uses PostgreSQL instead |
|
|
94
|
+
| Neon Realtime without a database | Adds Neon; an explicit D1 selection is rejected |
|
|
95
|
+
| Better Auth with Neon Realtime | Resolves to Neon regardless of flag order |
|
|
96
|
+
| RevenueCat without Stripe | Rejected; select `--stripe` explicitly |
|
|
97
|
+
| Expo or WXT | Includes the shared styling package |
|
|
98
|
+
| Database/auth or Neon Realtime without a server | Rejected; select a compatible web app or Hono |
|
|
99
|
+
| Native Next.js/Vercel with Worker-bound capabilities such as D1, R2, KV or Workers AI | Adds Hono for the Cloudflare runtime |
|
|
100
|
+
| OpenNext, Queues or Basin | Uses Wrangler for all Cloudflare targets in the workspace |
|
|
101
|
+
| Later addition that changes the engine or relocates existing runtime source | Rejected; `add` does not migrate delivery engines or runtime ownership |
|
|
102
|
+
|
|
103
|
+
When Hono is selected, it owns the shared database/auth runtime and server resource bindings. Other interfaces consume its endpoints. Worker services such as realtime, cron and workflows have their own deployable applications.
|
|
104
|
+
|
|
105
|
+
```sh
|
|
106
|
+
# Web with D1 and Better Auth (D1 is also the conditional auth default).
|
|
107
|
+
anhedral init my-app --better-auth
|
|
108
|
+
|
|
109
|
+
# Web, API and mobile with PostgreSQL.
|
|
110
|
+
anhedral init my-app --vinext --hono --expo --neon
|
|
111
|
+
|
|
112
|
+
# Vercel web with an automatically selected Hono backend for R2.
|
|
113
|
+
anhedral init my-app --next --r2
|
|
114
|
+
|
|
115
|
+
# Independent room messaging and live PostgreSQL queries.
|
|
116
|
+
anhedral init my-app --realtime --neon-realtime
|
|
117
|
+
```
|
|
118
|
+
|
|
43
119
|
The bundled registry is authoritative for exact dependencies, destinations and compatibility:
|
|
44
120
|
|
|
45
121
|
```sh
|
|
@@ -48,7 +124,7 @@ anhedral registry view better-auth --json
|
|
|
48
124
|
anhedral init my-app --vinext --hono --d1 --better-auth --r2 --dry-run --json
|
|
49
125
|
```
|
|
50
126
|
|
|
51
|
-
|
|
127
|
+
Append `--dry-run --json` to an initialization command to inspect its resolved products, destinations and setup requirements without writes or network requests. There is no `--all` or external registry support. Recipes create integration foundations; provider resources, credentials and finished features have their own setup and acceptance requirements.
|
|
52
128
|
|
|
53
129
|
## Organize the source
|
|
54
130
|
|
|
@@ -101,6 +177,23 @@ D1 manual migration defaults to local. `pnpm db:migrate -- --remote` explicitly
|
|
|
101
177
|
|
|
102
178
|
Neon runtime queries use server-supplied `DATABASE_URL` through the HTTP adapter. Interactive transactions require a reviewed WebSocket or PostgreSQL adapter. Migrations use a transactional WebSocket connection and direct `DATABASE_URL_UNPOOLED` from the environment or `packages/db/.env.local`/`.env`. Test migrations on the intended development branch before production. Runtime provisioning does not supply migration credentials automatically.
|
|
103
179
|
|
|
180
|
+
## Live video with Cloudflare Stream
|
|
181
|
+
|
|
182
|
+
Select `--stream` for one-to-many ultra-low latency live video: browser or supported encoder publishes with WHIP and viewers play with WHEP. [Stream Live WebRTC reached GA on October 15, 2026](https://developers.cloudflare.com/changelog/post/2026-10-15-stream-live-webrtc-ga/). It is the preferred broadcast service when a product needs live video. Add it only when needed; it can coexist with `--realtime` Durable Object messaging and `--neon-realtime` live SQL. Many-to-many calls require a separate Cloudflare Realtime design.
|
|
183
|
+
|
|
184
|
+
The recipe creates `packages/stream` with a server-only `@workspace/stream/server` export. `createStream({ accountId, apiToken })` exposes live input creation and retrieval. It requires a server, works with Vinext, native Next.js or Hono, and adds no Worker resource binding or SDK dependency. Follow the generated package README. Stream activation, live inputs and runtime credentials are configured explicitly; CLI provisioning and `ship` do not automate this integration.
|
|
185
|
+
|
|
186
|
+
Keep `STREAM_API_TOKEN` server-only and scope it to Stream Write in the customer account selected by `STREAM_ACCOUNT_ID`. Authorize creators, persist input ownership and enforce quotas before management calls. The returned `webRTC.url` is a publish credential: disclose it only to the authorized broadcaster, never to viewers, logs or static assets. Viewer responses contain only the approved WHEP endpoint or short-lived playback token. Choose `requireSignedURLs` explicitly when creating an input; implement and verify playback token issuance for private broadcasts. Hosting access protection does not protect Stream media endpoints.
|
|
187
|
+
|
|
188
|
+
Media goes directly between the browser and Stream. The application server owns identity, input ownership and endpoint/token issuance. Implement camera/microphone consent, HTTPS, ICE negotiation, user-facing errors, reconnect and session cleanup. Delete signaling sessions, close peer connections and stop capture tracks when a broadcast ends. No finished player, broadcaster or conferencing feature is generated.
|
|
189
|
+
|
|
190
|
+
As reviewed October 16, 2026, the [WebRTC documentation](https://developers.cloudflare.com/stream/webrtc-beta/) requires paired WHIP/WHEP and excludes recording, WHIP-to-HLS/DASH playback, RTMP/SRT-to-WHEP bridging, restreaming and live viewer counts. Usage is visible in Stream analytics/billing; broadcast and player-experience metrics remain unsupported. The URL retains `webrtc-beta` although the feature is GA. [Delivery billing](https://developers.cloudflare.com/stream/pricing/) began October 15 at standard Stream rates; budget viewer-minutes and check current account eligibility before activation. Verify creator/viewer access, private media denial, cross-tenant isolation, reconnect and teardown against the actual provider before claiming live acceptance.
|
|
191
|
+
|
|
192
|
+
```sh
|
|
193
|
+
anhedral init my-app --stream
|
|
194
|
+
anhedral add stream --dry-run --json
|
|
195
|
+
```
|
|
196
|
+
|
|
104
197
|
## Neon Realtime
|
|
105
198
|
|
|
106
199
|
`--neon-realtime` selects live PostgreSQL query foundations and adds Neon if no database was chosen. It requires a server and rejects an explicit conflicting database. It can coexist with `--realtime`, which means Durable Object WebSocket rooms.
|
|
@@ -123,7 +216,22 @@ Use pnpm `10.34.5`. The CLI's own supported Node range is broader than the gener
|
|
|
123
216
|
|
|
124
217
|
There is one Cloudflare engine per workspace. `add` refuses selections that would switch the engine or relocate existing runtime source. Anhedral owns composition, account/audience selection, shared packages and independent verification; Void owns its supported provisioning, deployment and code rollback mechanics. Native Void framework features are not implied by deploying Vinext through Void.
|
|
125
218
|
|
|
126
|
-
Void apps read one private app-root `.env`, copied from `env.example`. Avoid `.env.*` companions and `.dev.vars` in those apps. Wrangler and native Vercel use their generated runtime templates. Keep production secrets server-side; public `VITE_*`, `NEXT_PUBLIC_*` and `EXPO_PUBLIC_*` values are build inputs, not server secrets. Vinext maps `NEXT_PUBLIC_*` into client bundles. The [provider reference](provider-configuration
|
|
219
|
+
Void apps read one private app-root `.env`, copied from `env.example`. Avoid `.env.*` companions and `.dev.vars` in those apps. Wrangler and native Vercel use their generated runtime templates. Keep production secrets server-side; public `VITE_*`, `NEXT_PUBLIC_*` and `EXPO_PUBLIC_*` values are build inputs, not server secrets. Vinext maps `NEXT_PUBLIC_*` into client bundles. The [provider reference](software-factory.md#provider-configuration) describes credential transport and each integration's prerequisites.
|
|
220
|
+
|
|
221
|
+
### Delivery scope by target
|
|
222
|
+
|
|
223
|
+
| Target | Supported automation | Remaining delivery work |
|
|
224
|
+
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
|
|
225
|
+
| Cloudflare web/API/services | Selected resource setup, bindings/secrets, deployment, provider evidence, verification and recorded code rollback | Account/audience selection, product acceptance and data compatibility; rollback does not reverse SQL or restore data |
|
|
226
|
+
| Native Next.js/Vercel | Project connection, environment configuration, CLI delivery or adoption of connected Git deployments, provider evidence and recorded rollback | Eligible account plan, audience protection, repository/CI policy and product acceptance |
|
|
227
|
+
| Mixed Cloudflare/Vercel | Cloudflare first, then Vercel, with per-target receipts | Handle partial success; there is no atomic cross-provider release or rollback |
|
|
228
|
+
| Expo | Explicit platform/profile EAS build, project/source checks, queued-build resume and artifact receipt | Signing, device acceptance, store enrollment and submission; a simulator build is not a store artifact |
|
|
229
|
+
| Electron | Local build and packaging scripts | Platform signing, notarization, installers, updates and distribution |
|
|
230
|
+
| WXT | Local extension build and ZIP tooling | Installed-browser acceptance, store review and publication |
|
|
231
|
+
|
|
232
|
+
Hosting audience starts unconfigured and must be selected explicitly. Hosting protection, application authentication and resource authorization are separate decisions. Generated SDK factories and configured provider resources do not establish completed user flows.
|
|
233
|
+
|
|
234
|
+
The optional Codex inspector uses the same project and service domain logic as the CLI. Opening it reads local configuration and recorded evidence. Live status, analytics and bounded data reads require explicit service actions; supported deletion requires its separate confirmation flow. The inspector is development tooling, not a generated application dependency.
|
|
127
235
|
|
|
128
236
|
## Source ownership and dependency policy
|
|
129
237
|
|
|
@@ -139,4 +247,4 @@ Validate the resolved dependency graph for each application selection. A clean C
|
|
|
139
247
|
|
|
140
248
|
A completed application has server-side resource authorization, private file access, reviewed migrations, meaningful error/loading/empty states and tests for its actual user flows. Jobs and webhooks must tolerate duplicates; paid operations need limits and ownership. Verify the selected runtime and any native packaging, permissions and signing.
|
|
141
249
|
|
|
142
|
-
Use the [software factory](software-factory.md) for the implementation and acceptance process. Detailed delivery evidence and outstanding live acceptance gaps belong in the [Void verification reference](void-verification
|
|
250
|
+
Use the [software factory](software-factory.md) for the implementation and acceptance process. Detailed delivery evidence and outstanding live acceptance gaps belong in the [Void verification reference](verification.md#void-delivery-verification) and the application's own verification record, rather than in this architecture standard.
|