anhedral 0.8.5 → 0.9.0

package/docs/delivery-workflow.md

@@ -0,0 +1,83 @@
+# Build and deliver an application
+
+Codex implements the product; the CLI supplies scaffolding, selected resource reconciliation and source/provider evidence. Customer-account delivery exists. Managed hosting has a local client foundation, not an operated service. Start with users, flows, audience, budget and observable acceptance criteria; preserve suitable existing apps.
+
+## Plan and implement
+
+1. Choose only needed components from the [stack standard](application-stack-standard.md). Record decisions, ownership, environment/cost assumptions and actual connections in the application's `docs/architecture.md`.
+2. Match installed plugin, registry `cliVersion` and executable versions. Check Node/pnpm, Git identity, toolchains and customer provider access. For unpublished development use `pnpm build` and `node dist/bin.js`; never silently substitute `@latest`.
+3. Inspect `new <unused-directory> <flags> --dry-run --json`, then generate with those choices. Review README, AGENTS, setup manifests and resolved lockfile. For initialized apps, preview `add <directory> <items...> --dry-run --json`; additions protect edited source and record registry provenance. Use `--registry <file|https-url>` for reviewed declarative registries. Older projects and runtime relocation require explicit migration. `doctor --providers --json` checks access without configuring infrastructure or certifying production.
+4. Implement screens, APIs, persistence, authorization and integration behavior. Replace placeholders with working flows. Configure real secrets, origins and reviewed migrations using provider tools; starters do not establish setup completion. Keep credentials out of source, logs and handoffs.
+
+## Source and release authority
+
+Use customer-owned accounts and a reviewed clean commit. Default to a private repository in the selected account; organizations require selection.
+
+```sh
+anhedral repository my-app --create --json
+```
+
+This verifies the app's Git root, owner, visibility, write access and exact remote commit. Reuse matching origins without `--create`; do not replace remotes, change visibility or force-push. Connected repository identity is retained and rechecked.
+
+Choose one release path per change: checked `ship`, or checks followed by an authorized Git push, active production confirmation and `adopt`. Git integration can deploy independently of CLI checks; configure required CI/branch/deployment policy explicitly. Do not routinely deploy the same commit twice.
+
+## Cloudflare delivery
+
+Vinext/Workers is the default web recipe. Explicit Next.js on Workers uses `--next --hosting=cloudflare`. Select persistence, identity and AI from the standard. Cloudflare manifests use `anhedral.project.json`; mixed apps append `--provider cloudflare` to lifecycle operations.
+
+```sh
+anhedral connect my-app --audience private --allow-email owner@example.com
+anhedral provision my-app --dry-run --json
+anhedral provision my-app --json
+anhedral ship my-app --dry-run --json
+anhedral ship my-app --json
+```
+
+Connect verifies the sole accessible or explicitly selected `--account` and preserves audience/account choices. Public access requires authorization. Private hosting needs Zero Trust and scoped Access/Workers permissions; verify routes, domains and previews before and after deployment. Whole-Worker Access does not cover WebSockets: design and verify private realtime separately.
+
+Provision reconciles D1, private R2, KV and Queues/dead-letter queues; it does not implement schemas or integrations. Configure reviewed migrations, direct Neon (or selected Hyperdrive), Basin and external providers separately. The Neon starter uses direct serverless HTTP with a server-side DATABASE_URL. Reconcile partial operations before retrying. Shipping requires clean source, checks account/bindings, runs application checks and confirms active versions/traffic. Multiple Workers are not an atomic release; web deploys last by default.
+
+## Native Next.js/Vercel delivery
+
+Select `--next`, authenticate the intended customer account and choose an eligible plan. Hobby is personal/non-commercial; commercial use requires an eligible existing plan.
+
+```sh
+anhedral connect my-app --scope customer-team --audience private --use personal --create --git
+pnpm --dir my-app run check
+anhedral repository my-app --json
+# Wait for the connected production Git deployment.
+anhedral adopt my-app --json
+anhedral verify my-app --json
+```
+
+Connect checks project/framework/root, repository link and audience. New private projects establish independently verified all-deployment Vercel Authentication before code or Git deployment. Hosting membership is separate from product identity; do not add members, seats or paid upgrades automatically. Existing protection changes need authorization. Mixed apps provision/ship Cloudflare services first, then verify the web-to-service flow.
+
+## Acceptance and operating limits
+
+Run relevant lint/types/Fallow, dependency audits, meaningful tests and actual runtime builds. Exercise browser flows, installed extension permissions, packaged desktop behavior and signed/native device flows where selected. Deployment or HTTP 200 alone does not establish product completion.
+
+Verify anonymous rejection at primary/deployment URLs, permitted-user login, denied-user and cross-tenant behavior. Verify selected private files, realtime reconnect/replay, duplicate jobs/webhooks, bounded AI, purchase/restore/refund, email/push and offline conflicts. Provider-authenticated requests do not prove visitor login or app authorization. Protected automation may use Vercel curl or authorized origin-scoped Trusted Sources; never weaken protection for testing.
+
+Record service quotas, maximum retries/concurrency/AI work, alert ownership and shutdown controls within the authorized budget. Test spikes, duplicate execution, partial deployment and backup restoration. Review migrations and compatibility before rollback; code rollback does not restore data.
+
+## Operations and handoff
+
+| Command | Boundary |
+| --- | --- |
+| `register` | Stable app identity; generated apps register automatically. |
+| `status --refresh` | Independently refresh provider state. |
+| `manage` / `manage --local` | Provider overview / explicitly historical local view. |
+| `adopt` | Verify active Vercel Git source/repository and record its checked release; no push/deploy. |
+| `recover` | Reconcile current provider state after cloning; no invented historical tests/releases. |
+| `verify` | Run meaningful root `test:live` with actual URL/release and source/provider checks. |
+| `rollback --release <id> --data-compatible` | Restore recorded code after compatibility review; no migration reversal/data restore. |
+
+Open the actual app URL or installable artifact and exercise acceptance. Maintain the application's existing `docs/verification.md`: exact versions, source/release, repository, provider identity, audience, configured versus tested integrations, reproducible results and remaining actions. Refresh after changes; acceptance becomes stale when production changes. After rollback, restore matching clean source before verifying.
+
+Committed manifests preserve identity. Ignored `.anhedral/` receipts are local history; back them up when needed. Before removing an interrupted shared lock, confirm no active process and inspect provider state. Maintain alerts, dependencies, costs and tested recovery. Recurring monitoring requires an authorized schedule. Release artifacts need exact contents, secret checks and integrity verification; never replace published version bytes.
+
+## Evidence and maintenance
+
+Local/mocked coverage is distinct from live GitHub/Vercel private setup, fresh-clone recovery, installed fresh-chat workflow and connected integrations. Retained HTTP/CRUD/redeploy/rollback runs prove only their tested profile. Sites' inventory, visitor connectors and managed sharing require separate platform implementation. No operated managed backend or issued app URL is established here; see the [managed contract](https://github.com/anhedral/anhedral-init/blob/main/docs/managed-hosting-architecture.md).
+
+Before release, check the exact candidate's runtime, current dependency advisories, remote CI, installed-plugin and selected provider/native acceptance. Unresolved high-severity production audit failures block shipping. Keep dated results with release/test artifacts. Update this guide when commands, lifecycle or acceptance requirements change, and regenerate its bundled plugin copy.

package/docs/managed-hosting-architecture.md

@@ -0,0 +1,87 @@
+# Anhedral Cloud: setup and deployment contract
+
+The CLI has `cloud register|stage|save|deploy|status` and a locally tested API client. There is no operated hosting backend, platform login, issued app hostname or managed provisioning service. Everything marked **planned** below is a design requirement, not an available command. Customer-account delivery remains independent; never silently substitute it for requested managed hosting.
+
+## Product boundaries
+
+Anhedral is the B2B managed software services business. Anhedral Cloud is its hosting/operations service and client workspace. Anhedral Init (`anhedral` on npm) is the open-source application foundation and CLI; customer-account deployments must work without an Anhedral subscription. Managed delivery is an optional provider adapter, not a dependency hidden in generated application code.
+
+Keep `anhedral-landing` as the public website and existing portal frontend initially; retain working Next.js/Vercel hosting while the Hono/Workers control plane is built. Both portal and CLI should consume that same API. One durable model should connect organizations, memberships/roles, engagements, applications, environments, resources, releases and usage. A services project can contain multiple applications; product users are distinct from portal members. The current portal's email-primary membership permits one team per person; expand membership deliberately before multi-organization operator/client access. Private file links need storage-side authorization, not just a private portal page.
+
+Use the portal for client progress, approvals, application access, operating status, invoices and exports; expose technical controls according to role. Keep hosted customer code on a separate origin/domain from staff/client sessions. Sell engineering and managed operations with explicit responsibilities and bounded infrastructure usage. Source/data export, recovery and the customer-account deployment path should remain usable when managed hosting ends.
+
+Sequence: align released CLI/docs; connect portal organizations to the control-plane registry; ship one independently recoverable private application; prove updates, isolation, backups and cost controls; then add operational/billing UI and selected distribution features. Begin as a managed service for invited clients; expand self-service only after those paths are repeatable.
+
+## Accounts and paid activation
+
+Managed users should need Anhedral sign-in only for ordinary hosted apps. Anhedral operates the infrastructure and bills its customers; customer-account hosting keeps providers and bills in the customer's account. Product login remains separate from platform/hosting access.
+
+| Owner | Account/service | When and gate |
+| --- | --- | --- |
+| Anhedral | [Cloudflare Workers for Platforms](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/pricing/), DNS zone and scoped deployment credentials | Required managed runtime. Published baseline is $25/month plus overages; purchase currently uses the dashboard. Verify account, subscription and permissions before provisioning. |
+| Anhedral | [Neon serverless driver](https://neon.com/docs/serverless/serverless-driver); optional [Hyperdrive](https://developers.cloudflare.com/hyperdrive/platform/pricing/) | Default direct HTTP Postgres; provision isolated app credentials/data boundaries. Add Hyperdrive only for measured needs, using the non-pooled Neon endpoint. D1 is the SQLite option. Free quotas are not production capacity guarantees. Hyperdrive is included in Workers plans; Neon has separate billing. |
+| Anhedral | [R2](https://developers.cloudflare.com/r2/pricing/), selected Cloudflare services | Source/build archives and app files; compute/storage/operations/AI/media have separate meters. Enable only selected services. |
+| Anhedral | Better Auth, verified sender and optional OAuth provider registrations | Platform identity, recovery and login mail. No customer Clerk account required; selected app identity providers can differ. |
+| Anhedral | Stripe merchant account | Anhedral subscriptions and usage billing. Customer app payments require the app owner's merchant account or deliberate Stripe Connect onboarding; never mix ledgers. |
+| App owner, when selected | RevenueCat, Apple/Google store products; external AI, mail or other providers | Own commercial identity and app integrations. Verification, terms, billing and OAuth consent may require a human; the CLI reports the exact remaining step. |
+| App owner, when distributed | [Apple](https://developer.apple.com/help/account/basics/about-your-developer-account), [Play](https://support.google.com/googleplay/android-developer/answer/6112435), [Chrome](https://developer.chrome.com/docs/webstore/register) publisher accounts | Paid enrollment/registration and identity checks. Native signing/builds and review remain platform-specific; cloud backend deployment does not publish clients. |
+| Optional | GitHub; custom domain/registrar | GitHub export/connection, not a prerequisite for managed source recovery. Platform subdomains use Anhedral DNS; [customer domains](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/) require ownership validation and hostname limits. |
+
+Prices/eligibility must be rechecked at activation. Current numeric baseline is a dated October 8, 2026 check, not an app quote. Paid activation requires authorized spending; an agent can prepare setup and resume after enrollment without recreating resources.
+
+## Platform architecture
+
+Use separate control-plane and dispatch Workers. Better Auth identifies platform users; Neon holds owners, apps, permissions, resource identities, versions, deployments and billing ledgers. R2 stores immutable source/build archives. Queues/Workflows execute resumable build/provision/deploy jobs. The dispatch Worker maps an authorized hostname to an isolated user Worker; it must not trust a caller-selected worker name.
+
+[Workers for Platforms bindings](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/bindings/) support app resources including D1/R2/KV, Durable Objects, Queues, Workflows and Hyperdrive. Attach only that app's resources; use separate credentials and migration/runtime roles for Postgres. Never give user code platform deployment, billing or shared-admin credentials. Build untrusted code in an isolated runner; export only reviewed executable artifacts. Resolve resources on the server from a declared capability manifest, not arbitrary account IDs from uploaded code.
+
+Private previews and production enforce platform audience at dispatch, including assets, APIs and WebSocket upgrades. In-app authorization is still the application's responsibility. Test the chosen framework in the actual dispatch runtime: [platform limits](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/limits/) include disabled `caches.default` and restricted `request.cf` in untrusted namespaces. Do not enable trusted mode for customer code to bypass compatibility failures. User Workers currently lack gradual deployments; use immutable versioned Worker names plus an authorized routing switch for previews/rollback, and verify WebSocket/stateful-version compatibility.
+
+## Agent workflow
+
+**Planned interface:** `cloud login` → `cloud plan --json` → implement/check/commit → `cloud ship --json --wait` → `cloud verify`. Login should use a browser/device authorization flow and OS-protected renewable credentials. CI uses revocable project-scoped credentials. JSON output should distinguish setup required, payment required, queued, failed, deployed and verified, with resumable operation IDs and non-secret next actions.
+
+`plan` must identify owner/environment, declared resources, provider access, compatibility, estimated cost and authorized limits without mutations. `ship` should check source/build provenance, resolve resources, stage/save, apply reviewed compatible migrations, deploy, poll to completion and return the independently confirmed URL. Neither command exists yet. `new --hosting anhedral` is also not supported; generation currently selects Cloudflare or Vercel.
+
+The current low-level sequence is executable only with an operated compatible backend and configured `ANHEDRAL_HOSTING_ORIGIN` / `ANHEDRAL_HOSTING_TOKEN`:
+
+```sh
+anhedral cloud register my-app --audience private --json
+# Review source/secrets and commit the managed manifest in the app's own Git repo.
+git -C my-app add <reviewed-paths>
+git -C my-app commit -m "Prepare application version"
+pnpm --dir my-app run check
+# Build a complete self-contained Worker bundle/assets into an ignored app directory.
+anhedral cloud stage my-app --artifact /absolute/path/my-app/build --json
+anhedral cloud save my-app --version <returned-stage-id> --json
+anhedral cloud deploy my-app --version <returned-stage-id> --json
+anhedral cloud status my-app --json
+```
+
+Current `deploy` requests deployment and checks once; it may return queued/building. It does not wait for completion, run product acceptance or implement managed rollback/export. `save` writes connected identity into the tracked manifest; review/commit that change before staging a subsequent version. A staged artifact is not proven to originate from its source merely because both were archived: the planned build receipt must bind source commit, lockfile, toolchain and artifact digest.
+
+## Source and API contract
+
+Local Git remains the working source of truth. Save the exact clean commit plus complete build tree; retain immutable version IDs, SHA-256 hashes and byte lengths. Current staging permits regular files only, at most 64 MiB per archive and 10,000 build files; it rejects symlinks/submodules and credential files. Restore/clone/export must preserve history and allow exit; optional [Artifacts](https://developers.cloudflare.com/artifacts/platform/pricing/) can add Git-compatible managed history but is Paid-plan-only and has separately published metering.
+
+Current API routes are under `/v1`. Authenticate every route, derive ownership from the session, preserve audience and validate project/version identity. Pin service origin and owner after connection; forbid redirects and credential-bearing origins.
+
+| Route | Contract |
+| --- | --- |
+| `GET /session` | Authenticated owner identity. |
+| `POST /projects`, `GET /projects/:id` | Idempotent registration/current owned project state. |
+| `POST /projects/:id/versions` | Immutable commit, hashes/lengths and version identity. |
+| `PUT /projects/:id/versions/:version/source` or `/artifact` | Independently verify uploaded hashes/lengths. |
+| `GET /projects/:id/versions/:version` | Saved only when both verified archives exist. |
+| `POST /projects/:id/deployments` | Idempotent deployment of exact saved version/audience. |
+| `GET /projects/:id/deployments/:deployment` | Independently confirmed state/source/artifact; HTTPS URL only when deployed. |
+
+Validate archives again server-side before extraction, including traversal, links, duplicate paths and decompression/size limits. Preserve incomplete upload/job evidence for safe retries. Saving source, deploying code and passing product tests remain separate states.
+
+## Limits and completion gates
+
+Enforce [dispatch CPU/subrequest limits](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/custom-limits/) plus application-owned request, storage, SQL, job, AI/media and outbound budgets. Provider alerts are not hard spend caps. Reserve costly work transactionally before execution; reconcile completion/failure idempotently. Rate-limit platform API jobs with bounded retry/backoff for provider throttling. Limit previews/builds, concurrent jobs and retention; define grace/suspension/export policies. Do not delete customer data merely because billing fails. Optional paid/beta/enterprise services need explicit eligibility checks and adapters; free analytics does not make the rest free.
+
+Build in this order: platform identity and account/subscription preflight; durable registry/archive API; isolated build/resource provisioning; dispatch/private routes; resumable deployment polling; logs/secrets/recovery/export; billing/quotas; signed client distribution where requested. First acceptance fixture: two owners, independent private apps, persistence, file upload, one bounded job and repeated update. Prove cross-tenant rejection, anonymous denial, interrupted-save/deploy retry, source restoration, quota rejection and code rollback/data compatibility before onboarding.
+
+Maintain this single contract as capabilities ship: replace planned claims with verified command/API behavior and update account/limit links. Keep dated test evidence in existing release/test artifacts, not new analysis documents. Deployment and publication remain unproven until the operated service and installed agent workflow pass acceptance.

package/docs/sponsorships.md

@@ -0,0 +1,25 @@
+# Support Anhedral Init
+
+## Help more people build applications they own
+
+Anhedral Init is free and open source. We build tools that help developers turn an idea into an application with source code, infrastructure, and data in their own accounts.
+
+If Anhedral Init helps you build, saves you time, or makes your work easier, consider supporting its continued development. Your support helps us improve the tools, maintain integrations, fix bugs, and write clearer documentation.
+
+## GitHub Sponsors — coming soon
+
+Support can be a thank-you for something useful today or an ongoing contribution to the project's future. Every contribution helps us spend more time improving Anhedral Init for the people who use it.
+
+We plan to offer donations and ongoing sponsorships through GitHub Sponsors. Our sponsorship profile is not available yet; we'll add the link here when it launches.
+
+In the meantime, [contact us at business@anhedral.com](mailto:business@anhedral.com?subject=Support%20Anhedral%20Init) if you'd like to support the project.
+
+## Company sponsorships
+
+Does your company use Anhedral Init or want to support its development? We'd love to hear from you. Get in touch to discuss a sponsorship and how we can recognize your support.
+
+**[Become a sponsor](mailto:business@anhedral.com?subject=Anhedral%20Init%20sponsorship)**
+
+Thank you for helping us keep Anhedral Init free, open source, and improving.
+
+[Back to Anhedral Init](../README.md)

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "anhedral",
-  "version": "0.8.5",
-  "description": "Initialize client-owned applications with shadcn, pnpm, Turborepo, and Cloudflare-first services.",
+  "version": "0.9.0",
+  "description": "Build and deliver applications with Cloudflare-first Vinext, selected services, optional Next.js on Vercel, and verified release evidence.",
   "type": "module",
   "exports": {
     ".": {
@@ -18,12 +18,16 @@
     "dist",
     "assets/anhedral-cli-init.svg",
     "assets/anhedral-cli-init-technical.svg",
-    "assets/images/svg/logo-white-subtract.svg",
+    "assets/anhedral-mark.svg",
     "LICENSE",
     "README.md",
     "assets/anhedral.svg",
     "assets/favicon.ico",
-    "docs/application-stack-standard.md"
+    "docs/application-stack-standard.md",
+    "docs/delivery-workflow.md",
+    "docs/sponsorships.md",
+    "docs/managed-hosting-architecture.md",
+    "assets/security"
   ],
   "homepage": "https://github.com/anhedral/anhedral-init#readme",
   "repository": {
@@ -43,14 +47,14 @@
   "scripts": {
     "scaffold": "node dist/bin.js init",
     "clean": "node scripts/clean.mjs",
-    "build": "pnpm clean && tsc && node scripts/prepare-cli.mjs && node scripts/build-control-panel.mjs",
+    "build": "pnpm clean && tsc && node scripts/prepare-cli.mjs",
     "prepare": "pnpm build",
-    "typecheck": "tsc --noEmit && tsc -p apps/control-panel/tsconfig.json",
+    "typecheck": "tsc --noEmit",
     "check:hygiene": "node scripts/check-source-hygiene.mjs",
     "check:security": "node scripts/check-security-policy.mjs",
     "check:release-policy": "node scripts/check-release-policy.mjs",
     "check:release-secrets": "node scripts/check-release-secrets.mjs",
-    "lint": "pnpm typecheck && pnpm check:hygiene && pnpm check:release-policy",
+    "lint": "pnpm typecheck && pnpm format:check && pnpm check:hygiene && pnpm check:release-policy",
     "audit:osv": "node scripts/audit-osv.mjs",
     "test": "pnpm test:unit",
     "pretest": "pnpm build",
@@ -71,7 +75,11 @@
     "test:standard": "pnpm build && node --test tests/test-standard.test.mjs",
     "test:unit": "node --test --test-concurrency=4 --test-reporter=spec tests/*.test.mjs",
     "test:integration": "pnpm build && node tests/test-generated-apps.mjs",
-    "dev:panel": "node .artifacts/control-panel/preview.js"
+    "test:live:delivery": "pnpm build && node tests/test-live-delivery.mjs",
+    "test:live:vercel": "pnpm build && node tests/test-live-vercel.mjs",
+    "test:live:vercel:git": "pnpm build && node tests/test-live-vercel-git.mjs",
+    "format": "prettier --write src scripts tests",
+    "format:check": "prettier --check src scripts tests"
   },
   "keywords": [
     "cli",
@@ -87,31 +95,18 @@
     "neon",
     "drizzle",
     "shadcn",
-    "turborepo"
+    "turborepo",
+    "vinext"
   ],
   "license": "Apache-2.0",
   "packageManager": "pnpm@10.34.5",
   "devDependencies": {
-    "@base-ui/react": "1.8.0",
-    "@modelcontextprotocol/ext-apps": "1.7.5",
-    "@modelcontextprotocol/sdk": "1.32.1",
-    "@openai/mcp-extensions": "0.1.0",
-    "@tailwindcss/node": "4.3.3",
-    "@tailwindcss/oxide": "4.3.3",
     "@types/node": "20.19.43",
-    "@types/react": "19.2.10",
-    "@types/react-dom": "19.2.3",
-    "class-variance-authority": "0.7.1",
-    "cn": "0.4.0",
-    "esbuild": "0.28.2",
-    "jsonc-parser": "3.3.1",
-    "lucide-react": "1.52.0",
-    "react": "19.3.0",
-    "react-dom": "19.3.0",
+    "prettier": "3.9.10",
     "simple-icons": "16.27.0",
-    "tailwindcss": "4.3.3",
-    "tw-animate-css": "1.4.0",
-    "typescript": "5.9.3",
-    "zod": "4.4.3"
+    "typescript": "5.9.3"
+  },
+  "dependencies": {
+    "jsonc-parser": "3.3.1"
   }
 }

package/dist/project.d.ts

@@ -1,4 +0,0 @@
-export interface ProjectOptions {
-    projectName: string;
-    displayName: string;
-}

package/dist/standard-products.d.ts

@@ -1,2 +0,0 @@
-export declare const STANDARD_PRODUCTS: readonly ["next", "expo", "electron", "wxt", "hono", "neon", "d1", "local-data", "clerk", "better-auth", "r2", "kv", "realtime", "queues", "cron", "workflows", "openai", "ai-sdk", "workers-ai", "resend", "stripe", "revenuecat", "sentry", "basin", "posthog", "styling"];
-export type StandardProduct = typeof STANDARD_PRODUCTS[number];

package/dist/standard-products.js

@@ -1,6 +0,0 @@
-export const STANDARD_PRODUCTS = [
-    'next', 'expo', 'electron', 'wxt', 'hono', 'neon', 'd1', 'local-data',
-    'clerk', 'better-auth', 'r2', 'kv', 'realtime', 'queues', 'cron', 'workflows',
-    'openai', 'ai-sdk', 'workers-ai', 'resend', 'stripe', 'revenuecat',
-    'sentry', 'basin', 'posthog', 'styling',
-];