@nifrajs/cli 2.2.0 → 2.3.0

package/src/mcp-docs-tools.ts

@@ -1,5 +1,5 @@
 /**
- * The two project-INDEPENDENT MCP tools — `nifra_docs` + `nifra_example` — as a single factory shared
+ * The two project-INDEPENDENT MCP tools - `nifra_docs` + `nifra_example` - as a single factory shared
  * by every transport: the project stdio server ({@link projectTools}), the CLI HTTP server
  * (`nifra docs-mcp`), and the site's Cloudflare-Pages worker (`/mcp`). The corpus source is injected as
  * loaders, so the SAME tool definitions work whether the corpus comes from disk (`Bun.file`, on the
@@ -25,7 +25,7 @@ export function docsTools(
     {
       name: "nifra_docs",
       description:
-        "Search nifra's framework documentation and get back ONLY the matching sections — auth, uploads, ISR, WebSockets, loaders, deployment, anything. Call with no query for the cheap section index; pass query (e.g. \"isr revalidate\") for the top matching sections. Use this instead of reading llms-full.txt (~150 KB) whole. For the EXACT TypeScript of a type/interface/function, call nifra_types instead (don't read .d.ts files).",
+        "Search nifra's framework documentation and get back ONLY the matching sections - auth, uploads, ISR, WebSockets, loaders, deployment, anything. Call with no query for the cheap section index; pass query (e.g. \"isr revalidate\") for the top matching sections. Use this instead of reading llms-full.txt (~150 KB) whole. For the EXACT TypeScript of a type/interface/function, call nifra_types instead (don't read .d.ts files).",
       inputSchema: {
         type: "object",
         properties: {
@@ -40,7 +40,7 @@ export function docsTools(
       handler: async (args) => {
         const corpus = await loadDocs()
         if (corpus === undefined) {
-          return "docs corpus missing — run `bun run gen:llms` in the nifra repo (published builds ship it)."
+          return "docs corpus missing - run `bun run gen:llms` in the nifra repo (published builds ship it)."
         }
         const { query, limit } = args as { query?: string; limit?: number }
         return renderDocsResult(corpus, query, clamp(limit, 1, 5, 3))
@@ -49,7 +49,7 @@ export function docsTools(
     {
       name: "nifra_example",
       description:
-        'Get a VERIFIED, copy-pasteable nifra code example for a task — auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, etc. Every snippet is typechecked against the installed nifra version, so it compiles as-is. PREFER THIS over writing nifra code from memory (training data drifts). Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.',
+        'Get a VERIFIED, copy-pasteable nifra code example for a task - auth route, file upload, ISR page, loader/action, typed client, SSE, deployment, etc. Every snippet is typechecked against the installed nifra version, so it compiles as-is. PREFER THIS over writing nifra code from memory (training data drifts). Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.',
       inputSchema: {
         type: "object",
         properties: {
@@ -64,7 +64,7 @@ export function docsTools(
       handler: async (args) => {
         const corpus = await loadExamples()
         if (corpus === undefined) {
-          return "examples corpus missing — run `bun run gen:llms` in the nifra repo (published builds ship it)."
+          return "examples corpus missing - run `bun run gen:llms` in the nifra repo (published builds ship it)."
         }
         const { query, limit } = args as { query?: string; limit?: number }
         return renderExamplesResult(corpus, query, clamp(limit, 1, 5, 3))
@@ -73,14 +73,14 @@ export function docsTools(
     {
       name: "nifra_types",
       description:
-        'Get the EXACT TypeScript declaration of any exported @nifrajs/* symbol — interface, type, class, function, const. Each signature is generated from the package\'s built .d.ts, so it is the LITERAL declaration: complete, authoritative, never prose and never truncated. THIS IS THE SOURCE OF TRUTH for nifra\'s types — do NOT read node_modules/@nifrajs/**/*.d.ts; call this instead. Pass `name` for an exact symbol (e.g. "RateLimitStore", "RouteSchema", "Context", "rateLimit"); pass `query` to search by keyword; omit both for the per-package index of names. A `name` lookup is always the complete declaration; a `query` returns a one-line summary plus the signature, collapsing an oversized body — pass `full: true` to override.',
+        'Get the EXACT TypeScript declaration of any exported @nifrajs/* symbol - interface, type, class, function, const. Each signature is generated from the package\'s built .d.ts, so it is the LITERAL declaration: complete, authoritative, never prose and never truncated. THIS IS THE SOURCE OF TRUTH for nifra\'s types - do NOT read node_modules/@nifrajs/**/*.d.ts; call this instead. Pass `name` for an exact symbol (e.g. "RateLimitStore", "RouteSchema", "Context", "rateLimit"); pass `query` to search by keyword; omit both for the per-package index of names. A `name` lookup is always the complete declaration; a `query` returns a one-line summary plus the signature, collapsing an oversized body - pass `full: true` to override.',
       inputSchema: {
         type: "object",
         properties: {
           name: {
             type: "string",
             description:
-              "Exact symbol name — returns its literal declaration (e.g. RateLimitStore).",
+              "Exact symbol name - returns its literal declaration (e.g. RateLimitStore).",
           },
           query: {
             type: "string",
@@ -94,7 +94,7 @@ export function docsTools(
           full: {
             type: "boolean",
             description:
-              "Query mode only: return whole declarations instead of collapsed ones. Off by default — a search is for picking a symbol, and one match can be tens of thousands of characters.",
+              "Query mode only: return whole declarations instead of collapsed ones. Off by default - a search is for picking a symbol, and one match can be tens of thousands of characters.",
           },
         },
         additionalProperties: false,
@@ -102,7 +102,7 @@ export function docsTools(
       handler: async (args) => {
         const corpus = await loadTypes()
         if (corpus === undefined) {
-          return "types corpus missing — run `bun run build && bun run gen:llms` in the nifra repo (published builds ship it)."
+          return "types corpus missing - run `bun run build && bun run gen:llms` in the nifra repo (published builds ship it)."
         }
         const { name, query, limit, full } = args as {
           name?: string

package/src/mcp-http.ts

@@ -1,13 +1,13 @@
 /**
- * The PUBLIC nifra docs MCP — Streamable-HTTP transport exposing the project-INDEPENDENT tools
+ * The PUBLIC nifra docs MCP - Streamable-HTTP transport exposing the project-INDEPENDENT tools
  * (`nifra_docs` + `nifra_example`) so any remote AI agent can learn nifra without a local checkout.
  * Both tools read the bundled corpus (llms-full.txt / examples.json shipped in this package) and ignore
- * `cwd`, so they reuse the exact definitions from {@link projectTools} — one source, no drift.
+ * `cwd`, so they reuse the exact definitions from {@link projectTools} - one source, no drift.
  *
  * The transport itself (body cap, CORS, JSON-RPC dispatch) lives in `@nifrajs/mcp/http`; this module is
  * the docs-specific layer over it: it supplies the bundled corpus tools and the `nifra-docs` server info.
- * {@link handleMcpHttp} self-hosts ANYWHERE Bun runs — the simplest path is `nifra docs-mcp` on a VPS; the
- * same handler runs on Cloudflare/Vercel edge (there inline the corpus as string imports — a Worker has no
+ * {@link handleMcpHttp} self-hosts ANYWHERE Bun runs - the simplest path is `nifra docs-mcp` on a VPS; the
+ * same handler runs on Cloudflare/Vercel edge (there inline the corpus as string imports - a Worker has no
  * filesystem). `export default { port, fetch }` also lets `bun run mcp-http.ts` serve it directly.
  */
 
@@ -26,10 +26,10 @@ export { docsTools } from "./mcp-docs-tools.ts"
 export type { TypeEntry } from "./types-search.ts"
 
 // Kept in lockstep with packages/cli/package.json by check:publish's version-consistency gate.
-const VERSION = "2.2.0"
+const VERSION = "2.3.0"
 const SERVER_INFO = { name: "nifra-docs", version: VERSION }
 const DOCS_HEALTH =
-  "nifra docs MCP — POST JSON-RPC 2.0 here (methods: initialize, tools/list, tools/call). Tools: nifra_docs, nifra_example."
+  "nifra docs MCP - POST JSON-RPC 2.0 here (methods: initialize, tools/list, tools/call). Tools: nifra_docs, nifra_example."
 
 /** The two project-independent tools, reading the package's bundled corpus from disk (CLI use). */
 export function publicDocsTools(): McpTool[] {
@@ -57,7 +57,7 @@ export function handleMcpHttp(request: Request): Promise<Response> {
 /**
  * Worker/edge + local entry. `export default { fetch }` is the universal server shape: Cloudflare /
  * Vercel edge / Deno deploy use `fetch` (and ignore `port`); `bun run mcp-http.ts` auto-serves it on
- * `port` (PORT env, default 8787) — Bun serves a module's default-exported server, so NO manual
+ * `port` (PORT env, default 8787) - Bun serves a module's default-exported server, so NO manual
  * `Bun.serve` here (that would double-bind the port).
  */
 export default {

package/src/mcp-protocol.ts

@@ -1,7 +1,7 @@
 /**
  * The MCP JSON-RPC dispatch now lives in `@nifrajs/mcp` (shared with nifra apps that expose their own
- * MCP server / MCP Apps widgets). This module is a thin re-export so the CLI's existing imports — and
- * the `@nifrajs/cli/mcp` self-host surface — keep resolving here unchanged.
+ * MCP server / MCP Apps widgets). This module is a thin re-export so the CLI's existing imports - and
+ * the `@nifrajs/cli/mcp` self-host surface - keep resolving here unchanged.
  */
 
 export * from "@nifrajs/mcp/protocol"

package/src/mcp-render.ts

@@ -1,12 +1,12 @@
 /**
- * The `nifra_render` engine + its child-process entry — the page half of `nifra_run`. Where `nifra_run`
+ * The `nifra_render` engine + its child-process entry - the page half of `nifra_run`. Where `nifra_run`
  * runs requests through the BACKEND, this SSRs page routes through the WEB app (`createWebApp`), so an
  * agent can verify a page renders and its loader ran after an edit. Spawned fresh per call (`bun
  * mcp-render.ts <cwd>`) so the project's CURRENT route/loader code is loaded.
  *
- * No build required: a placeholder `clientEntry` is injected (the SSR HTML renders regardless — the
+ * No build required: a placeholder `clientEntry` is injected (the SSR HTML renders regardless - the
  * client bundle only matters for hydration in the browser, not for "did this page render server-side").
- * {@link renderPages} never throws — every failure (no config, a loader error, a render throw) becomes
+ * {@link renderPages} never throws - every failure (no config, a loader error, a render throw) becomes
  * `{ error }` so the agent gets the actionable message.
  */
 
@@ -19,7 +19,7 @@ import { loadApp, resolvePlugins } from "./load.ts"
 const errString = (err: unknown): string =>
   err instanceof Error ? `${err.name}: ${err.message}` : String(err)
 
-/** Load the project, register its SSR plugins, and build the SSR `createWebApp` once — the cost the warm
+/** Load the project, register its SSR plugins, and build the SSR `createWebApp` once - the cost the warm
  * worker amortizes across calls. Never throws (every failure → `{ error }`). Factored out of
  * {@link renderPages} so the cold path (fresh process per call) and the warm worker share one builder. */
 async function buildWebApp(cwd: string): Promise<{ app: AppLike } | { error: string }> {
@@ -92,7 +92,7 @@ function redirectConsoleToStderr(): void {
 /**
  * Warm-worker loop (`--worker`): build the web app ONCE, then SSR each `{ id, input: { requests } }` line
  * against that hot app and reply `{ id, output }`. The parent (`mcp.ts`'s warm-render handler) spawns this,
- * fingerprints the source tree, and restarts the worker when a file changes — so warm reuse never serves a
+ * fingerprints the source tree, and restarts the worker when a file changes - so warm reuse never serves a
  * stale render. Mirrors `mcp-run.ts`'s worker (single backend entry → no per-call entry key needed here).
  */
 async function runWorker(cwd: string): Promise<void> {
@@ -148,7 +148,7 @@ if (import.meta.main) {
   // The parent (mcp.ts) spawns `bun mcp-render.ts <cwd>` WITHOUT setting the subprocess `cwd` option, so
   // this process inherits the MCP server's working dir, not the app's. SSR resolves `react-dom/server`
   // from `process.cwd()` to share ONE React core with the app's route components (the dual-React fix in
-  // @nifrajs/web-react) — so we must chdir to the app root before any render. Best-effort: a bad path
+  // @nifrajs/web-react) - so we must chdir to the app root before any render. Best-effort: a bad path
   // surfaces later as a load error rather than crashing the child here.
   if (cwd !== process.cwd()) {
     try {

package/src/mcp-run.ts

@@ -1,6 +1,6 @@
 /**
  * The `nifra_run` engine + its child-process entry. The MCP server spawns this file fresh on every
- * `nifra_run` call (`bun mcp-run.ts <cwd>`) so the project's CURRENT backend code is loaded — picking
+ * `nifra_run` call (`bun mcp-run.ts <cwd>`) so the project's CURRENT backend code is loaded - picking
  * up the agent's latest edits. {@link runBackend} is the pure-ish core (resolve entry → import → run),
  * exported so it's unit-testable in-process; the entry below wires it to stdin/stdout.
  */
@@ -48,7 +48,7 @@ export async function loadBackend(
 
 /**
  * Resolve the backend entry under `cwd`, import it, and run `requests` through its exported app. Never
- * throws — every failure (missing/invalid entry, import/compile/runtime error) becomes `{ error }`, so
+ * throws - every failure (missing/invalid entry, import/compile/runtime error) becomes `{ error }`, so
  * the caller (and the agent) always gets actionable output. An import error here IS the failure the
  * agent needs to see and fix.
  */

package/src/mcp.ts

@@ -1,27 +1,27 @@
 /**
- * `nifra mcp` — a Model Context Protocol server (stdio) that lets a coding agent (Claude, Cursor, …)
+ * `nifra mcp` - a Model Context Protocol server (stdio) that lets a coding agent (Claude, Cursor, …)
  * act on a nifra project, not just read about it:
  *
- *   - `nifra_context` — this project's API routes + page routes + conventions (see {@link describeProject}).
- *   - `nifra_run`     — run HTTP requests through the project's backend and return structured results
+ *   - `nifra_context` - this project's API routes + page routes + conventions (see {@link describeProject}).
+ *   - `nifra_run`     - run HTTP requests through the project's backend and return structured results
  *     (status, body, errors). The write → run → see-the-failure → fix loop, powered by `@nifrajs/runner`.
  *     Each call runs the backend in a FRESH subprocess, so it reflects the agent's latest edits.
- *   - `nifra_render`  — SSR a page route through the project's web app; returns the rendered HTML (the
+ *   - `nifra_render`  - SSR a page route through the project's web app; returns the rendered HTML (the
  *     page half of `nifra_run`). Fresh subprocess per call; no build needed.
- *   - `nifra_ws`      — verify a WebSocket route with a real Bun WebSocket round-trip.
- *   - `nifra_docs`    — keyword-search the framework docs; returns only the matching sections.
- *   - `nifra_example` — a verified, copy-pasteable snippet for a task (typechecked against the live API,
+ *   - `nifra_ws`      - verify a WebSocket route with a real Bun WebSocket round-trip.
+ *   - `nifra_docs`    - keyword-search the framework docs; returns only the matching sections.
+ *   - `nifra_example` - a verified, copy-pasteable snippet for a task (typechecked against the live API,
  *     so it can't hallucinate a drifted nifra API).
- *   - `nifra_scaffold`— map a URL path to the correct `routes/` file + a contract-correct page stub.
- *   - `nifra_check`   — the drift gate (typecheck + lints, each with a structured fix), for an agent to fix against.
- *   - `nifra_assure`  — route classification + enforcement-evidence gate.
+ *   - `nifra_scaffold`- map a URL path to the correct `routes/` file + a contract-correct page stub.
+ *   - `nifra_check`   - the drift gate (typecheck + lints, each with a structured fix), for an agent to fix against.
+ *   - `nifra_assure`  - route classification + enforcement-evidence gate.
  *   - `nifra_levels`  - the cumulative verification ladder (L0 contract → L4 invariants): what the
  *     project actually proves, and why each level it misses does not hold.
- *   - `nifra_doctor`  — package.json dependency drift detector, with safe local-version auto-fix.
+ *   - `nifra_doctor`  - package.json dependency drift detector, with safe local-version auto-fix.
  *
  * Wire it into a client (e.g. Claude Desktop / Cursor) as: command `nifra`, args `["mcp"]`, run in the
  * project root. The protocol is hand-rolled (newline-delimited JSON-RPC 2.0 over stdio), including
- * standard MCP progress notifications and request cancellation — no SDK dependency, the same
+ * standard MCP progress notifications and request cancellation - no SDK dependency, the same
  * minimal-surface choice as the rest of nifra. The pure dispatch lives in `./mcp-protocol.ts`; this
  * module is the I/O shell (stdin loop, tool wiring, the run subprocess).
  */
@@ -159,7 +159,7 @@ type PipeSubprocess = ReturnType<typeof Bun.spawn> & {
 
 /** A persistent `mcp-run`/`mcp-render` `--worker` subprocess: the backend/web app is loaded ONCE and
  * reused across newline-delimited `{ id, input }` requests, replying `{ id, output }`. The same machinery
- * powers both `nifra_run warm` and `nifra_render warm` — `child` selects which engine, `label` shapes the
+ * powers both `nifra_run warm` and `nifra_render warm` - `child` selects which engine, `label` shapes the
  * cancellation message. The owning handler ({@link createWarmHandler}) fingerprints the source tree and
  * replaces the worker when a file changes, so warm reuse never serves a stale result. Exported for the
  * concurrency test that proves a single per-request cancel doesn't tear down the shared worker. */
@@ -217,7 +217,7 @@ export class WarmWorker {
         // Per-request cancel: drop just THIS id and resolve its cancellation. The worker is shared
         // across concurrent requests (`pending` is id-keyed for exactly this reason), so killing the
         // process here would reject every OTHER in-flight request via the `exited` handler and force a
-        // cold rebuild. Leave it hot — `createWarmHandler` already replaces it on file change.
+        // cold rebuild. Leave it hot - `createWarmHandler` already replaces it on file change.
         this.pending.delete(id)
         clearTimeout(timer)
         const reason = typeof signal?.reason === "string" ? `: ${signal.reason}` : ""
@@ -297,7 +297,7 @@ export class WarmWorker {
 
 /** A warm handler that reuses a hot {@link WarmWorker} across calls and falls back to a one-shot fresh
  * subprocess on any worker failure. Shared by `nifra_run` (`child: "mcp-run"`, `label: "run"`) and
- * `nifra_render` (`child: "mcp-render"`, `label: "render"`) — the only differences are the engine and the
+ * `nifra_render` (`child: "mcp-render"`, `label: "render"`) - the only differences are the engine and the
  * message label, so there's a single source for the reuse + auto-restart-on-file-change logic. */
 function createWarmHandler(
   child: "mcp-run" | "mcp-render",
@@ -616,7 +616,7 @@ export function projectFeatures(
 }
 
 /**
- * Resolve an optional `dir` tool argument — a subdirectory of the project root the caller wants to scope a
+ * Resolve an optional `dir` tool argument - a subdirectory of the project root the caller wants to scope a
  * check/test to (e.g. `nifra check` on `app/` when the MCP server's root is a monorepo). Returns the
  * absolute target, or `null` if `dir` escapes the root (a path-traversal guard: no `..` out, no absolute
  * path elsewhere). `undefined`/empty → the root itself.
@@ -630,7 +630,7 @@ export function resolveProjectDir(root: string, dir: string | undefined): string
 /** Consistent error string for a `dir` that escapes the project root. */
 function dirError(dir: string | undefined): string {
   return JSON.stringify(
-    { ok: false, error: `dir must be a subdirectory of the project root — "${dir}" escapes it.` },
+    { ok: false, error: `dir must be a subdirectory of the project root - "${dir}" escapes it.` },
     null,
     2,
   )
@@ -647,7 +647,7 @@ export function projectTools(
     {
       name: "nifra_context",
       description:
-        "Get this nifra project's surface. Call it once UNFILTERED for a tight INDEX: the route list (API routes as `METHOD path`, page routes as `pattern → file`) + framework conventions + a pointer — cheap even on a big app, no per-route schema dump. Then pass `path` (a route prefix like /api/orders) and/or `kind` (api|pages) to fetch the FULL contract for that slice (body/query/response TS shapes + the exact typed-client call form).",
+        "Get this nifra project's surface. Call it once UNFILTERED for a tight INDEX: the route list (API routes as `METHOD path`, page routes as `pattern → file`) + framework conventions + a pointer - cheap even on a big app, no per-route schema dump. Then pass `path` (a route prefix like /api/orders) and/or `kind` (api|pages) to fetch the FULL contract for that slice (body/query/response TS shapes + the exact typed-client call form).",
       inputSchema: {
         type: "object",
         properties: {
@@ -671,7 +671,7 @@ export function projectTools(
     {
       name: "nifra_routes",
       description:
-        "List this project's API routes as STRUCTURED JSON — each `{ method, path, call, body?, query?, response? }`, where `call` is the exact typed-client call form and the shapes are compact TS-typed contracts. For programmatic use (list_routes / get_route_schema) instead of parsing the nifra_context Markdown. No args = every route; pass `path` (a path or prefix like /api/orders) to narrow to those routes.",
+        "List this project's API routes as STRUCTURED JSON - each `{ method, path, call, body?, query?, response? }`, where `call` is the exact typed-client call form and the shapes are compact TS-typed contracts. For programmatic use (list_routes / get_route_schema) instead of parsing the nifra_context Markdown. No args = every route; pass `path` (a path or prefix like /api/orders) to narrow to those routes.",
       inputSchema: {
         type: "object",
         properties: {
@@ -851,7 +851,7 @@ export function projectTools(
     {
       name: "nifra_scaffold",
       description:
-        'Map a URL path to the CORRECT routes/ file and get a contract-correct page stub. Agents routinely place file routes wrong — this applies the convention for you: ":id"/"[id]" → [id], "*rest" → [...rest], "/" → index. Pass path (e.g. "/users/:id"). Returns the file to create + the route-module contract (loader/action/meta/default) + a stub (ready-to-write for react/preact/solid; path+contract for vue/svelte/vanilla — use nifra_example for those bodies).',
+        'Map a URL path to the CORRECT routes/ file and get a contract-correct page stub. Agents routinely place file routes wrong - this applies the convention for you: ":id"/"[id]" → [id], "*rest" → [...rest], "/" → index. Pass path (e.g. "/users/:id"). Returns the file to create + the route-module contract (loader/action/meta/default) + a stub (ready-to-write for react/preact/solid; path+contract for vue/svelte/vanilla - use nifra_example for those bodies).',
       inputSchema: {
         type: "object",
         properties: {
@@ -887,7 +887,7 @@ export function projectTools(
     {
       name: "nifra_check",
       description:
-        'Run the project\'s drift gate and return a structured result { ok, typecheck, diagnostics[] }: typecheck (the frontend↔backend contract), plus lints for hand-rolled fetch() to your own API, untyped client("…") calls missing <typeof app>, and server-only imports in routes/. Pass lintsOnly:true for a near-instant lint pass while iterating; run the full gate (default) to confirm the work is done — fix every diagnostic before finishing.',
+        'Run the project\'s drift gate and return a structured result { ok, typecheck, diagnostics[] }: typecheck (the frontend↔backend contract), plus lints for hand-rolled fetch() to your own API, untyped client("…") calls missing <typeof app>, and server-only imports in routes/. Pass lintsOnly:true for a near-instant lint pass while iterating; run the full gate (default) to confirm the work is done - fix every diagnostic before finishing.',
       inputSchema: {
         type: "object",
         properties: {
@@ -1086,7 +1086,7 @@ export function projectTools(
     {
       name: "nifra_doctor",
       description:
-        "Check this project for packages imported in source but NOT declared in package.json — the Bun-workspace trap where an import resolves at runtime (hoisting/workspace) so tests pass and `bun install` says no changes, yet tsc fails and a fresh/standalone install can't resolve it. Returns { ok, ran, findings[], fixed?, skippedFixes? }. Pass autoFix:true to update package.json only when the dependency version can be inferred locally from an ancestor package.json or installed package metadata; otherwise the tool returns the exact bun add command to run.",
+        "Check this project for packages imported in source but NOT declared in package.json - the Bun-workspace trap where an import resolves at runtime (hoisting/workspace) so tests pass and `bun install` says no changes, yet tsc fails and a fresh/standalone install can't resolve it. Returns { ok, ran, findings[], fixed?, skippedFixes? }. Pass autoFix:true to update package.json only when the dependency version can be inferred locally from an ancestor package.json or installed package metadata; otherwise the tool returns the exact bun add command to run.",
       inputSchema: {
         type: "object",
         properties: {
@@ -1259,6 +1259,54 @@ function namespaceForApp(
   }
 }
 
+/**
+ * Merge the backend-derived resources/prompts into `base` - and keep a project that cannot be loaded
+ * from deciding whether the server starts at all.
+ *
+ * Resources and prompts are OPTIONAL capabilities extracted from the app's backend, so this load is a
+ * best-effort enrichment. It was awaited unguarded, which made it a hard boot requirement: `loadApp`
+ * needs a web config (`adapter` + `clientModule`) and a `routes/` directory, and a backend-only
+ * project - the shape `create-nifra`'s DEFAULT template produces - has neither. On those projects the
+ * throw escaped before the JSON-RPC loop began, so the server wrote nothing and exited. `nifra
+ * init-agents` would happily register an `.mcp.json` pointing at a server that could never start, and
+ * every tool went with it, including the twelve that never touch the app (docs, examples, types,
+ * check, doctor, levels, test).
+ *
+ * Degrading costs only the backend resources/prompts. Tools that genuinely need the app still fail,
+ * but per call, with their own message - which is a diagnosis instead of a silence.
+ */
+async function backendFeatures(
+  loader: () => Promise<LoadedApp>,
+  base: McpServerFeatures,
+): Promise<McpServerFeatures> {
+  const resources = [...(base.resources ?? [])]
+  const prompts = [...(base.prompts ?? [])]
+  try {
+    const app = await loader()
+    resources.push(...extractBackendResources(app.backend))
+    prompts.push(...extractBackendPrompts(app.backend))
+  } catch {
+    // Not loadable here (no web config, or the config itself throws). The server still serves.
+  }
+  return { resources, prompts }
+}
+
+/**
+ * The MCP tools the app itself declares via `app.tool(...)`, or none when the app cannot be loaded.
+ *
+ * Same reasoning as {@link backendFeatures}, on the hotter path: this ran on EVERY JSON-RPC message,
+ * so an unloadable project failed `initialize` itself with a `-32603` and the session never opened.
+ * An app's own tools are an extension of the built-in set, so their absence must not withdraw the
+ * built-ins - a backend-only project still gets docs, examples, types, check, doctor, levels and test.
+ */
+async function appDeclaredTools(loader: () => Promise<LoadedApp>): Promise<McpTool[]> {
+  try {
+    return extractBackendTools((await loader()).backend)
+  } catch {
+    return []
+  }
+}
+
 /** Run the stdio MCP server: read newline-delimited JSON-RPC from stdin, write responses to stdout. */
 export async function runMcpServer(cwd: string, version: string): Promise<void> {
   let features: McpServerFeatures
@@ -1270,24 +1318,18 @@ export async function runMcpServer(cwd: string, version: string): Promise<void>
     const allPrompts: McpPrompt[] = []
     for (const { name, cwd: appCwd } of appEntries) {
       const loader = createCachedAppLoader(appCwd)
-      const app = await loader()
-      const base = projectFeatures(appCwd, loader)
-      const ns = namespaceForApp(name, [], {
-        resources: [...(base.resources ?? []), ...extractBackendResources(app.backend)],
-        prompts: [...(base.prompts ?? []), ...extractBackendPrompts(app.backend)],
-      })
+      const ns = namespaceForApp(
+        name,
+        [],
+        await backendFeatures(loader, projectFeatures(appCwd, loader)),
+      )
       allResources.push(...(ns.features.resources ?? []))
       allPrompts.push(...(ns.features.prompts ?? []))
     }
     features = { resources: allResources, prompts: allPrompts }
   } else {
     const loadAppCached = createCachedAppLoader(cwd)
-    const base = projectFeatures(cwd, loadAppCached)
-    const app = await loadAppCached()
-    features = {
-      resources: [...(base.resources ?? []), ...extractBackendResources(app.backend)],
-      prompts: [...(base.prompts ?? []), ...extractBackendPrompts(app.backend)],
-    }
+    features = await backendFeatures(loadAppCached, projectFeatures(cwd, loadAppCached))
   }
   const loadAppCached = createCachedAppLoader(cwd)
   const serverInfo = { name: "nifra", version }
@@ -1302,21 +1344,16 @@ export async function runMcpServer(cwd: string, version: string): Promise<void>
       const allTools: McpTool[] = []
       for (const { name, cwd: appCwd } of appEntries) {
         const loader = createCachedAppLoader(appCwd)
-        const app = await loader()
-        const baseTools = projectTools(appCwd, loader)
-        const backendTools = extractBackendTools(app.backend)
-        const ns = namespaceForApp(name, [...baseTools, ...backendTools], {
-          resources: [],
-          prompts: [],
-        })
+        const tools = [...projectTools(appCwd, loader), ...(await appDeclaredTools(loader))]
+        const ns = namespaceForApp(name, tools, { resources: [], prompts: [] })
         allTools.push(...ns.tools)
       }
       activeTools = [...docsTools(loadDocsCorpus, loadExamplesCorpus, loadTypesCorpus), ...allTools]
     } else {
-      const app = await loadAppCached()
-      const baseTools = projectTools(cwd, loadAppCached)
-      const backendTools = extractBackendTools(app.backend)
-      activeTools = [...baseTools, ...backendTools]
+      activeTools = [
+        ...projectTools(cwd, loadAppCached),
+        ...(await appDeclaredTools(loadAppCached)),
+      ]
     }
 
     const response = await handleRpc(message, activeTools, serverInfo, features, {

package/src/openapi-tool.ts

@@ -45,7 +45,7 @@ function toYaml(value: unknown, depth = 0): string {
  * Render a project's backend as OpenAPI 3.1. Frontend-only apps get a valid empty document, which is
  * easier for agents and API tooling to handle than a tool error.
  *
- * `pathPrefix` narrows the document to operations whose (OpenAPI-templated) path starts with the prefix —
+ * `pathPrefix` narrows the document to operations whose (OpenAPI-templated) path starts with the prefix -
  * mirroring `nifra_routes`'s `path` filter so a large backend needn't return the whole document. The keys
  * are templated (`/users/{id}`), so a prefix up to the first param (`/api/orders`) matches `/api/orders`
  * and `/api/orders/{id}` alike. `components.schemas` is left intact: it's keyed by schema name (not path),
@@ -57,7 +57,7 @@ export function renderOpenApi(app: LoadedApp, format: OpenApiFormat, pathPrefix?
   const input = hasRoutesMethod(app.backend) ? app.backend : {}
   const generated = toOpenAPI(input, { title, version: "1.0.0" })
   // Narrow to operations under the prefix, rebuilding the doc (its `paths` is readonly). `components`
-  // stays — see the doc comment for why the schema set isn't recomputed.
+  // stays - see the doc comment for why the schema set isn't recomputed.
   const document =
     pathPrefix !== undefined && pathPrefix !== ""
       ? {

package/src/pipeline-guard.ts

@@ -1,5 +1,5 @@
 /**
- * Pipeline separation guard — one bundler owns a phase, never two.
+ * Pipeline separation guard - one bundler owns a phase, never two.
  *
  * nifra supports both Vite and Bun, and the config keeps them in separate slots: `vitePlugins` for
  * the Vite pipeline, `clientPlugins`/`serverPlugins` for the Bun one. Nothing enforces the split, so