@nifrajs/cli 2.7.1 → 2.8.1

package/src/doctor.ts

@@ -9,6 +9,12 @@
  * declared by the package that imports it (for `tsc` and for that package to install on its own) even
  * when a monorepo would hoist it. Relative paths, runtime builtins (node core, `node:`/`bun:`, `bun`),
  * the package's own name, and tsconfig `paths` aliases are excluded - none of them are npm deps.
+ *
+ * The diff is against DECLARED dependency sets only; what happens to be installed on disk is never
+ * consulted. That is the point: a package pulled in transitively by some other dependency resolves fine
+ * locally while no manifest declares it, so resolvability is not evidence of declaration. The scan
+ * therefore also covers `*.test.ts`/`*.spec.ts`, which `nifra check` skips - `tsc` compiles them, so an
+ * undeclared import there fails a clean `bun install --frozen-lockfile` build just the same.
  */
 import type { Dirent } from "node:fs"
 import { readdir, realpath, stat } from "node:fs/promises"
@@ -679,12 +685,19 @@ export async function collectDoctorResult(cwd: string): Promise<DoctorResult> {
   const scopes = await doctorPackageScopes(cwd, pkg)
 
   const findings: DoctorFinding[] = []
-  await walkSource(cwd, (rel, content) => {
-    const scope = scopeForFile(scopes, rel)
-    for (const f of scanUndeclaredImports(rel, content, scope.declared, scope.isAlias)) {
-      findings.push({ file: f.file, line: f.line, package: f.snippet })
-    }
-  })
+  // `includeTests`: tests are part of the typechecked surface, so an import they declare nowhere is a
+  // real break. Excluding them is what let an undeclared `zod` in a `*.test.ts` pass doctor, pass a
+  // hoisted local `tsc`, and then fail CI on a clean install with `TS2307: Cannot find module 'zod'`.
+  await walkSource(
+    cwd,
+    (rel, content) => {
+      const scope = scopeForFile(scopes, rel)
+      for (const f of scanUndeclaredImports(rel, content, scope.declared, scope.isAlias)) {
+        findings.push({ file: f.file, line: f.line, package: f.snippet })
+      }
+    },
+    { includeTests: true },
+  )
   findings.sort((a, b) => a.file.localeCompare(b.file) || a.line - b.line)
   const duplicateInstalls = await collectDuplicateInstalls(cwd, pkg)
   const staleDists = await collectStaleWorkspaceDists(cwd, pkg)

package/src/mcp-app-tool.ts

@@ -1,5 +1,5 @@
 /**
- * The `nifra_examples_app` MCP tool: nifra's verified code examples as an MCP Apps widget. It returns the
+ * The `nifra_gallery` MCP tool: nifra's verified code examples as an MCP Apps widget. It returns the
  * examples as `structuredContent`, rendered by the {@link examplesWidget} `ui://` widget in MCP Apps hosts
  * (ChatGPT Apps, MCPJam, Goose); text-only hosts still get the example names as plain text. Part of the
  * public docs-MCP tool set (served by `handleMcpHttp`), so every self-host gets it from one definition.
@@ -50,10 +50,14 @@ export const examplesWidget = defineMcpWidget({
 /** The widget-backed tool. `loadExamples` is injected (disk on the CLI, cached fetch on the edge). */
 export function examplesAppTool(loadExamples: () => Promise<Example[] | undefined>): McpTool {
   return defineMcpTool({
-    name: "nifra_examples_app",
-    annotations: { title: "Browse nifra examples", readOnlyHint: true, openWorldHint: false },
+    name: "nifra_gallery",
+    annotations: {
+      title: "Browse the nifra example gallery",
+      readOnlyHint: true,
+      openWorldHint: false,
+    },
     description:
-      "Browse nifra's verified code examples as an interactive, filterable list (MCP Apps widget). Pass query to pre-filter; the widget also filters client-side.",
+      "Open an interactive, filterable gallery of ALL of nifra's verified code examples (MCP Apps widget) - for browsing and discovering what exists. NOT for fetching one snippet as text: use nifra_example for that. Pass query to pre-filter; the widget also filters client-side.",
     inputSchema: {
       type: "object",
       properties: { query: { type: "string", description: "Pre-filter examples by keyword." } },

package/src/mcp-docs-tools.ts

@@ -58,7 +58,7 @@ export function docsTools(
         openWorldHint: false,
       },
       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). Returns code as TEXT for direct use; to visually browse the whole example set instead, use nifra_gallery. Call with no query for the grouped index; pass query (e.g. "protected route", "upload", "isr revalidate") for matching snippets.',
       inputSchema: {
         type: "object",
         properties: {

package/src/mcp-http.ts

@@ -1,6 +1,6 @@
 /**
  * The PUBLIC nifra docs MCP - Streamable-HTTP transport exposing the project-INDEPENDENT tools
- * (`nifra_docs`, `nifra_example`, `nifra_types`, `nifra_learn` + the `nifra_examples_app` MCP Apps widget)
+ * (`nifra_docs`, `nifra_example`, `nifra_types`, `nifra_learn` + the `nifra_gallery` MCP Apps widget)
  * so any remote AI agent can learn nifra without a local checkout. They read the bundled corpus
  * (llms-full.txt / examples.json / types.json shipped in this package) and ignore `cwd`, so they reuse the
  * exact definitions from {@link projectTools} - one source, no drift.
@@ -29,7 +29,7 @@ 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.7.1"
+const VERSION = "2.8.1"
 const SERVER_INFO = { name: "nifra-docs", version: VERSION }
 // Derive the GET/health tool list from the tools actually served, so the line can never drift from them.
 const docsHealth = (tools: McpTool[]): string =>
@@ -38,7 +38,7 @@ const docsHealth = (tools: McpTool[]): string =>
     .join(", ")}.`
 
 /** The project-independent tools, reading the package's bundled corpus from disk (CLI use): the text
- * docs tools plus the `nifra_examples_app` MCP Apps widget tool. */
+ * docs tools plus the `nifra_gallery` MCP Apps widget tool. */
 export function publicDocsTools(): McpTool[] {
   return [
     ...docsTools(loadDocsCorpus, loadExamplesCorpus, loadTypesCorpus),
@@ -60,7 +60,7 @@ export function respondMcpHttp(
 }
 
 /** The CLI HTTP handler: serves the disk-backed corpus tools + registers the examples widget's `ui://`
- * resource so MCP Apps hosts can render `nifra_examples_app`. (`nifra docs-mcp` / `bun run` this file.) */
+ * resource so MCP Apps hosts can render `nifra_gallery`. (`nifra docs-mcp` / `bun run` this file.) */
 export function handleMcpHttp(request: Request): Promise<Response> {
   return respondMcpHttp(request, publicDocsTools(), {
     features: {