spfn 0.3.0-beta.3 → 0.3.0-beta.4

package/README.md

@@ -2,7 +2,7 @@
 
 `spfn` takes a Next.js idea from prototype to production with a consistent full-stack
 architecture. It can scaffold either a core-only backend or a production baseline with
-authentication, internationalization, and an agent-facing MCP endpoint, then runs the
+authentication, internationalization, and a terminal operations surface, then runs the
 dev/build/start lifecycle, database tooling, RPC codegen, and environment validation.
 
 Consistent is the point rather than a nicety: what it scaffolds is one fixed shape per
@@ -31,7 +31,7 @@ is not supported — see [the root README](../../README.md#what-do-i-need-instal
 ## Usage
 
 ```bash
-# Prototype-to-Production baseline: core + auth + i18n + MCP
+# Prototype-to-Production baseline: core + auth + i18n + ops
 npx spfn@beta create my-app --mode full
 cd my-app
 docker compose up -d            # Postgres + Redis
@@ -71,7 +71,7 @@ pass `--mode full`.
 |--------|-------------|
 | `--pm <manager>` | Force package manager: `npm` \| `pnpm` \| `yarn` \| `bun` |
 | `--shadcn` | Also run `shadcn init` |
-| `--mode <mode>` | `bare` (core only) \| `full` (core, auth, i18n, MCP) |
+| `--mode <mode>` | `bare` (core only) \| `full` (core, auth, i18n, ops) |
 | `--skip-install` | Skip dependency install |
 | `--skip-git` | Skip `git init` |
 | `-y, --yes` | Skip prompts, use defaults |
@@ -86,7 +86,7 @@ already exists). See [Scaffold structure](#scaffold-structure) for what lands on
 
 | Option | Description |
 |--------|-------------|
-| `--mode <mode>` | `bare` (core only) \| `full` (core, auth, i18n, MCP) |
+| `--mode <mode>` | `bare` (core only) \| `full` (core, auth, i18n, ops) |
 | `-y, --yes` | Skip prompts, use defaults |
 
 Generated projects pin `drizzle-orm` and `drizzle-kit` to `1.0.0-rc.4`, matching
@@ -498,24 +498,30 @@ src/
   app/auth/callback/page.tsx         # OAuth session handoff
   i18n/catalogs.ts                   # application-owned en/ko starter messages
   i18n/server.ts                     # configured server-side i18n registry
-  server/mcp.ts                      # authenticated /mcp endpoint + starter app_status tool
-  server/router.ts                   # authRouter + mcpRouter + global authenticate
+  server/routes/ops.ts               # ops routes under /_ops + the manifest `spfn ops` reads
+  server/router.ts                   # authRouter + opsRouter + global authenticate
   server/server.config.ts            # createAuthLifecycle + i18n startup
 next.config.ts                       # /_auth/* callback rewrite
 .env.local                           # generated auth session secret (gitignored)
-.env.server                          # auth keyring + MCP operator key (gitignored)
+.env.server                          # auth keyring (gitignored)
 ```
 
 The full RPC proxy imports the auth interceptor and merges `authRouteMap`. Internal auth
-and MCP keys are generated with cryptographic randomness in ignored local env files;
+keys are generated with cryptographic randomness in ignored local env files;
 `.env.example` contains placeholders only. Add only the provider keys you use, then run
-`pnpm spfn db migrate`. The starter MCP endpoint accepts `SPFN_MCP_API_KEY` as a Bearer
-token for first-party operation; replace that validator with OAuth before third-party access.
+`pnpm spfn db migrate`.
+
+Operating the app is [`spfn ops`](#spfn-ops), not a dashboard: the starter
+`src/server/routes/ops.ts` exposes two read commands, and `spfn ops` discovers them from
+the running server's manifest. Issuing the first token signs in as an administrator, so
+uncomment `SPFN_AUTH_ADMIN_ACCOUNTS` in `.env.server` and restart before
+`spfn ops token issue`. The ops surface adds no dependency — the router comes from
+`@spfn/core/ops` and the tokens from `@spfn/auth`.
 
 `init` also patches `package.json` (scripts: `spfn:dev`, `spfn:server`, `spfn:next`,
 `spfn:build`, `spfn:start`, `codegen`; deps: `@spfn/core`, `spfn`, `drizzle-orm`,
 `@sinclair/typebox`, `concurrently`, etc.; full also adds `@spfn/auth`, `@spfn/i18n`,
-`@spfn/mcp`, auth's `@spfn/notification` peer, and a Node `>=20.0.0` engine when the
+auth's `@spfn/notification` peer, and a Node `>=20.0.0` engine when the
 existing range still permits older Node versions), excludes `src/server` from the root
 `tsconfig.json` (Vercel compat), and adds `.spfn/`, `.env.local`, `.env.server` to
 `.gitignore`.
@@ -621,8 +627,8 @@ type ships from `spfn` (`@type {import('spfn').SpfnConfig}`).
 something with an AI coding agent and now want a real backend under it, `init` is the one.
 
 **`bare` or `full`?**
-`full` is the recommended baseline: core, auth, i18n and MCP wired together, so you get a
-working authenticated app on day one. `bare` is core only — the architecture with nothing
+`full` is the recommended baseline: core, auth, i18n and the ops surface wired together, so
+you get a working authenticated app on day one, operable from the terminal. `bare` is core only — the architecture with nothing
 else decided. Automation should always pass `--mode` explicitly, because a `--yes` run
 without one still produces `bare` for backward compatibility.
 
@@ -637,7 +643,7 @@ pointing at your own PostgreSQL works too. PostgreSQL itself is not optional.
 
 **Which Node version do I need?**
 20 or later, in both modes. `@spfn/core` runs on `@hono/node-server` 2, which declares
-that floor, and full mode's MCP server needs the same.
+that floor, and full mode's `@spfn/auth` needs the same.
 
 **When do I have to run codegen by hand?**
 Whenever routes change outside `spfn dev`, which runs a codegen watcher for you. A stale or
@@ -685,5 +691,6 @@ committed.
 
 - [`@spfn/core`](../core/README.md) — server, route DSL, codegen, db, client runtime.
 - [`@spfn/auth`](../auth/README.md) — what `--mode full` wires in for accounts and roles.
-- [`@spfn/mcp`](../mcp/README.md) — what `--mode full` wires in for operating the app.
+- [`@spfn/mcp`](../mcp/README.md) — an agent-facing MCP endpoint, added on demand with
+  `spfn add @spfn/mcp`.
 - Project root README — framework overview and getting started.

package/dist/index.js

@@ -103,7 +103,7 @@ async function selectScaffoldMode(options) {
     choices: [
       {
         title: "full (recommended)",
-        description: "Core, auth, i18n, and MCP \u2014 ready for Prototype to Production",
+        description: "Core, auth, i18n, and ops CLI \u2014 ready for Prototype to Production",
         value: "full"
       },
       {
@@ -944,7 +944,7 @@ var init_deployment_config = __esm({
 
 // src/utils/version.ts
 function getCliVersion() {
-  return "0.3.0-beta.3";
+  return "0.3.0-beta.4";
 }
 function getTagFromVersion(version) {
   const match = version.match(/-([a-z]+)\./i);
@@ -988,7 +988,6 @@ async function setupPackageJson(cwd, packageJsonPath, packageJson, packageManage
   if (mode === "full") {
     packageJson.dependencies["@spfn/auth"] = spfnTag;
     packageJson.dependencies["@spfn/i18n"] = spfnTag;
-    packageJson.dependencies["@spfn/mcp"] = spfnTag;
     packageJson.dependencies["@spfn/notification"] = spfnTag;
   }
   packageJson.devDependencies["@types/node"] = "^20.11.0";
@@ -1187,9 +1186,12 @@ SPFN_AUTH_TOKEN_ENCRYPTION_KEYS=v1:${randomSecret("base64")}
 # SPFN_AUTH_NAVER_CLIENT_ID=your-naver-client-id
 # SPFN_AUTH_NAVER_CLIENT_SECRET=your-naver-client-secret
 
-# Full scaffold: MCP operator endpoint
-SPFN_MCP_URL=http://localhost:8790
-SPFN_MCP_API_KEY=${randomSecret("base64url")}
+# Full scaffold: ops CLI (spfn ops)
+# Ops commands need no variable of their own \u2014 they authenticate with a token
+# issued by \`spfn ops token issue\`, and issuing one signs in as an administrator.
+# Uncomment to seed that administrator on the next server start, then remove the
+# password once the account exists.
+# SPFN_AUTH_ADMIN_ACCOUNTS=[{"email":"admin@example.com","password":"replace-with-a-strong-password","role":"admin"}]
 `;
 }
 function randomSecret(encoding) {
@@ -1419,9 +1421,12 @@ SPFN_AUTH_TOKEN_ENCRYPTION_KEYS=v1:replace-with-a-base64-encoded-32-byte-key
 # SPFN_AUTH_NAVER_CLIENT_ID=your-naver-client-id
 # SPFN_AUTH_NAVER_CLIENT_SECRET=your-naver-client-secret
 
-# Full scaffold: MCP operator endpoint
-SPFN_MCP_URL=http://localhost:8790
-SPFN_MCP_API_KEY=replace-with-a-random-operator-key
+# Full scaffold: ops CLI (spfn ops)
+# Ops commands need no variable of their own \u2014 they authenticate with a token
+# issued by \`spfn ops token issue\`, and issuing one signs in as an administrator.
+# Uncomment to seed that administrator on the next server start, then remove the
+# password once the account exists.
+# SPFN_AUTH_ADMIN_ACCOUNTS=[{"email":"admin@example.com","password":"replace-with-a-strong-password","role":"admin"}]
 `;
   }
 });

package/dist/templates/README.md

@@ -71,13 +71,28 @@ Next.js interceptor, `/login` starter UI, OAuth callback, and route map are alre
 Edit `src/i18n/catalogs.ts` to add application-owned messages. Server components
 and handlers can import `getT` or `getClientMessages` from `@/i18n/server`.
 
-## Agent operations with MCP
+## Operations from the terminal
 
-The SPFN API serves MCP at `http://localhost:8790/mcp`. Connect with the Bearer
-token stored as `SPFN_MCP_API_KEY` in `.env.server`, then replace the starter
-`app_status` tool in `src/server/mcp.ts` with operations from your domain layer.
-Before third-party access, replace the generated operator-key validator with your
-OAuth access-token validator and scope each tool to the resolved operator.
+Operating this app needs no admin dashboard. Ops routes live in
+`src/server/routes/ops.ts`, are written like any other route, and the `spfn ops`
+CLI discovers them from the running server:
+
+```bash
+# 1. Seed an administrator: uncomment SPFN_AUTH_ADMIN_ACCOUNTS in .env.server,
+#    then restart the server so the account is created.
+
+# 2. Issue a token for this machine (stored in the OS keychain on macOS)
+{{pmExec}} spfn ops token issue --name laptop --scopes 'example:read'
+
+# 3. Run the app's own operations
+{{pmExec}} spfn ops list --app http://localhost:8790
+{{pmExec}} spfn ops call countExamples --app http://localhost:8790
+{{pmExec}} spfn ops call listRecentExamples --describe   # usage from the route's schema
+```
+
+Tokens are scoped and revocable (`spfn ops token list` / `revoke`). Add your own
+commands by exporting more `opsRoute` handlers and passing them to
+`createOpsRouter` — no CLI change is needed, the manifest carries them.
 <!-- {{/auth}} -->
 
 ## Deployment

package/dist/templates/modes/full/src/server/router.ts

@@ -2,12 +2,12 @@
  * Prototype-to-Production application router.
  *
  * Auth protects application routes by default. Public routes opt out with
- * `.skip(['auth'])`; the MCP router owns its Bearer-token boundary.
+ * `.skip(['auth'])`; the ops router owns its own ops-token boundary.
  */
 import { authRouter, authenticate } from '@spfn/auth/server';
 import { defineRouter } from '@spfn/core/route';
-import { mcpRouter } from './mcp';
 import { getRoot } from './routes/root';
+import { opsRouter } from './routes/ops';
 import {
     listExamples,
     getExample,
@@ -24,7 +24,7 @@ export const appRouter = defineRouter({
     updateExample,
     deleteExample,
 })
-    .packages([authRouter, mcpRouter])
+    .packages([authRouter, opsRouter])
     .use([authenticate]);
 
 export type AppRouter = typeof appRouter;

package/dist/templates/modes/full/src/server/routes/ops.ts

@@ -0,0 +1,52 @@
+/**
+ * Ops routes — operate this application from the terminal.
+ *
+ * Operations are written exactly like features: `opsRoute` puts them under the
+ * `/_ops` namespace, and `createOpsRouter` injects `opsTokenAuth` into every one
+ * of them plus serves `GET /_ops/_manifest`, which the `spfn ops` CLI reads to
+ * discover the commands this app owns.
+ *
+ * First run, against a running server:
+ *
+ *   spfn ops token issue --name laptop --scopes 'example:read'
+ *   spfn ops list --app http://localhost:8790
+ *   spfn ops call countExamples --app http://localhost:8790
+ *
+ * Issuing a token signs in as an administrator, so seed one first with
+ * `SPFN_AUTH_ADMIN_ACCOUNTS` in `.env.server`.
+ */
+import { createOpsRouter, opsRoute } from '@spfn/core/ops';
+import { opsTokenAuth, requireOpsScope } from '@spfn/auth/server';
+import { Type } from '@sinclair/typebox';
+import { ExampleRepository } from '../repositories/example.repository';
+
+const exampleRepo = new ExampleRepository();
+
+/**
+ * GET /_ops/examples/count — how many examples exist
+ */
+const countExamples = opsRoute.get('/examples/count')
+    .use([requireOpsScope('example:read')])
+    .handler(async () => ({ count: await exampleRepo.countAll() }));
+
+/**
+ * GET /_ops/examples — recent examples, ops view
+ */
+const listRecentExamples = opsRoute.get('/examples')
+    .use([requireOpsScope('example:read')])
+    .input({
+        query: Type.Object({
+            limit: Type.Optional(Type.Number({ minimum: 1, maximum: 100 })),
+        }),
+    })
+    .handler(async (c) =>
+    {
+        const { query } = await c.data();
+
+        return { items: await exampleRepo.findAll(query.limit ?? 10, 0) };
+    });
+
+export const opsRouter = createOpsRouter({
+    countExamples,
+    listRecentExamples,
+}, { auth: opsTokenAuth });

package/dist/templates/modes/full/src/server/routes/root.ts

@@ -10,6 +10,6 @@ export const getRoot = route.get('/')
             health: '/_core/health',
             examples: '/examples',
             auth: '/_auth',
-            mcp: '/mcp',
+            ops: '/_ops',
         },
     }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "spfn",
-  "version": "0.3.0-beta.3",
+  "version": "0.3.0-beta.4",
   "description": "Scaffold a full-stack TypeScript backend onto a Next.js app built with an AI coding agent: auth, database, typed routes and codegen, one fixed vertical slice per feature",
   "type": "module",
   "bin": {

package/dist/templates/modes/full/src/server/config/env.config.ts

@@ -1,23 +0,0 @@
-import {
-    createEnvRegistry,
-    defineEnvSchema,
-    envSecret,
-    envUrl,
-} from '@spfn/core/env';
-
-export const envSchema = defineEnvSchema({
-    SPFN_MCP_URL: envUrl({
-        description: 'Public base URL of the SPFN server that exposes /mcp',
-        default: 'http://localhost:8790',
-        required: false,
-    }),
-    SPFN_MCP_API_KEY: envSecret({
-        description: 'First-party Bearer token for the generated MCP operator endpoint',
-        required: true,
-        generate: 'base64url32',
-    }),
-});
-
-export const env = createEnvRegistry(envSchema).validate();
-
-export default env;

package/dist/templates/modes/full/src/server/mcp.ts

@@ -1,75 +0,0 @@
-/**
- * Remote MCP endpoint for operating this application with an agent.
- *
- * The generated operator key makes the endpoint usable immediately. Replace
- * `validateToken` with your OAuth access-token validator before granting access
- * to third-party clients, and expose only tools the resolved operator may use.
- */
-import { timingSafeEqual } from 'node:crypto';
-import type { McpAuth, McpTool } from '@spfn/mcp';
-import { createMcpRoute } from '@spfn/mcp/server';
-import env from './config/env.config';
-
-type OperatorAuth = McpAuth & {
-    operatorId: string;
-};
-
-type OperatorContext = {
-    operatorId: string;
-};
-
-const tools: McpTool<OperatorContext>[] = [
-    {
-        name: 'app_status',
-        title: 'Application status',
-        description: 'Check that the deployed application MCP endpoint is available.',
-        inputSchema: {
-            type: 'object',
-            properties: {},
-        },
-        annotations: {
-            readOnlyHint: true,
-            destructiveHint: false,
-        },
-        handler: async (_args, context) => ({
-            status: 'ok',
-            operatorId: context.operatorId,
-        }),
-    },
-];
-
-export const mcpRouter = createMcpRoute<OperatorAuth, OperatorContext>({
-    appUrl: env.SPFN_MCP_URL,
-    serverInfo: {
-        name: 'spfn-app',
-        version: '1.0.0',
-        description: 'Operate this SPFN application with an agent.',
-    },
-    validateToken: async (token) =>
-    {
-        // The registry validates this required secret at startup. Its public
-        // proxy type remains optional so schemas can also describe values that
-        // are not required in every environment.
-        if (!secretsMatch(token, env.SPFN_MCP_API_KEY!))
-        {
-            throw new Error('Invalid MCP access token');
-        }
-
-        return {
-            clientId: 'operator-agent',
-            operatorId: 'operator',
-            scopes: ['operate'],
-        };
-    },
-    resolveContext: async auth => ({ operatorId: auth.operatorId }),
-    listTools: () => tools,
-});
-
-function secretsMatch(actual: string, expected: string): boolean
-{
-    const actualBytes = Buffer.from(actual);
-    const expectedBytes = Buffer.from(expected);
-
-    return actualBytes.length === expectedBytes.length
-        && timingSafeEqual(actualBytes, expectedBytes);
-}