@augmenting-integrations/create-spoke 8.5.0 → 8.7.0

package/README.md

@@ -11,12 +11,16 @@ pnpm dlx @augmenting-integrations/create-spoke my-spoke --subdomain=foo --slug=b
 
 A Next.js 16 + Auth.js v5 app pre-wired for the augint tenant ecosystem:
 
+- `app.manifest.json` at the repo root (slug, subdomain, displayName,
+  navOrder, access policy, feature enablement, data plane)
 - `loadTenantConfig({ role: "spoke" })` in `src/lib/auth.ts` (single env-var read)
 - `<TenantBootScript>` + `<TenantProvider>` mounted in the root layout
 - Library-owned route handlers for `/api/auth/me`, `/api/billing/*`,
-  `/api/invitations/[token]`, and `/api/admin/users/[id]/impersonate` —
-  each is a 2-line re-export from `@augmenting-integrations/auth/server` or
-  `@augmenting-integrations/billing/server`
+  `/api/invitations/[token]`, `/api/admin/users/[id]/impersonate`, and
+  `/api/settings/*` — each is a 2-line re-export from
+  `@augmenting-integrations/auth/server` or `/billing/server`
+- `/api/apps` proxy to the tenant apex (the apex owns the canonical
+  roster; the spoke ships no roster file of its own)
 - Canonical Prisma fragments (`User`, `Invitation`, `PaymentMethod`,
   `CreditTransaction`, `ActivityLog`) in `prisma/schema.prisma` — your
   product models live below the marker comment
@@ -27,15 +31,16 @@ A Next.js 16 + Auth.js v5 app pre-wired for the augint tenant ecosystem:
 
 The generated app is portable; the AWS infra around it is per-tenant:
 
-- Provision your tenant's Cognito user pool, hosted zone, app registry
-  table, secrets, GitHub OIDC role (copy `template.yaml` from an existing
-  spoke in the same tenant — see `augint-example-leads-marketplace` for
-  the reference).
-- Register this spoke in the apex's DynamoDB app registry (slug, subdomain,
-  displayName, navOrder) so it shows up in every other spoke's AppShell.
+- Provision your tenant's Cognito user pool, hosted zone, secrets,
+  GitHub OIDC role (copy `template.yaml` from an existing spoke in the
+  same tenant — see `augint-example-leads-marketplace` for the reference).
+- Register this spoke in the tenant roster: add an entry to
+  `<tenant>-infra/config/apps.yaml` and the matching entry to the apex
+  repo's `config/apps.json`. `pnpm exec augint validate-app-roster`
+  enforces the two files agree. No DynamoDB; no Studio click.
 
 ## Bringing your product
 
-The kernel ships only auth/billing/admin route handlers. Product routes
-(`/api/leads`, `/api/quotes`, `/api/widgets`) are yours to design under
-`src/app/api/`.
+The kernel ships only auth/billing/settings/admin/invitations route
+handlers. Product routes (`/api/leads`, `/api/quotes`, `/api/widgets`)
+are yours to design under `src/app/api/`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@augmenting-integrations/create-spoke",
-  "version": "8.5.0",
+  "version": "8.7.0",
   "description": "Scaffold a new product subdomain (spoke) for an augint-* tenant. Generates a Next 16 + Auth.js v5 app with TenantConfig wired up, library-owned route handlers, a Prisma canonical schema fragment, and a deployable template.yaml + GitHub workflow. Single command: pnpm dlx @augmenting-integrations/create-spoke my-spoke.",
   "license": "MIT",
   "publishConfig": {

package/templates/src/app/api/apps/route.ts.tmpl

@@ -0,0 +1,14 @@
+// Auto-discovery endpoint consumed by @augmenting-integrations/ui's
+// AppShell. The browser fetches this same-origin; we proxy server-side
+// to the apex's /api/apps so the canonical tenant roster only lives in
+// one place (<tenant>-infra/config/apps.yaml, mirrored to the apex's
+// config/apps.json). Adding a new spoke does NOT require redeploying
+// every existing spoke.
+
+import { createAppsProxyRouteHandler } from "@augmenting-integrations/platform/server";
+import { tenant } from "@/lib/auth";
+
+export const runtime = "nodejs";
+export const dynamic = "force-dynamic";
+
+export const { GET } = createAppsProxyRouteHandler({ tenant });