@happyvertical/smrt-dev-mcp 0.45.0 → 0.45.2

package/AGENTS.md

@@ -55,7 +55,8 @@ An app that installs the published packages authors none of them, so workspace
 discovery alone sees nothing. Every installed `@happyvertical/smrt-*` package,
 plus the known SDK packages, is resolved from the project's and each workspace
 package's `node_modules/@happyvertical` scope directory and marked
-`isInstalledDependency`. This is an enumeration, not a walk: pnpm materializes
+`isInstalledDependency`. The filesystem enumeration and canonical doc reader are shared with CLI snapshots
+through `smrt-core/knowledge`; enrichment stays here. This is an enumeration, not a walk: pnpm materializes
 a store whose entries link back out to their siblings, so a descent reads the
 same package once per path that reaches it. Real paths deduplicate the result;
 each package is still read through its `node_modules` path, because a realpath
@@ -195,9 +196,13 @@ launcher or a small wrapper script with an absolute Node path.
     the canonical `smrt-projects` model and changed the facts.
 - **Budgets are enforced at the transport boundary**: `KnowledgePackage` carries
   the full `agentDoc` and domain manifest, so the MCP handlers project a compact
-  package record unless `detail: 'full'`. Library callers (the CLI) still receive
-  the full objects. Structural object facts render into prompt Markdown only in
-  full detail; summary mode remains names/counts/paths.
+  package record for `summary` (default) and `full`. `full` embeds package docs,
+  structural facts, and modules selected by changed paths, focus, or Modules-table
+  source mappings (including globs); other module paths remain discoverable.
+  `complete` preserves full package records and embeds every module. CLI context
+  JSON uses the same projection; `--complete` opts into full export. Library
+  builders retain full objects. Snapshot commands list module paths by default
+  and accept `--complete` to embed bodies.
 - **Private packages skip packaging checks**: the `files` allowlist governs npm
   publication, so `private: true` packages are exempt; authored docs are still
   required. A workspace root is exempt from both — but **only when member

package/README.md

@@ -144,7 +144,7 @@ drift. Reach it with `--scope installed`.
 ## Response Budgets
 
 Knowledge and introspection tools return a **summary** by default and accept
-`detail: "full"` for the complete payload.
+`detail: "complete"` for complete knowledge context payloads (`introspect-project` uses `full`).
 
 - `introspect-project` summary returns one compact record per object
   (`className`, `qualifiedName`, `extends`, `tableName`, `tenantScope`,
@@ -154,13 +154,18 @@ Knowledge and introspection tools return a **summary** by default and accept
   budget.
 - `smrt-architecture`, `smrt-review`, and the `build-*-context` tools list
   authored `AGENTS.md` and module docs **by path** rather than embedding them,
-  and return compact package records. With `detail: "full"`, their prompt
+  and return compact package records. With `detail: "full"`, they embed the package
+  AGENTS doc plus module docs matching changed files or request text. Source paths and globs
+  in the same Modules-table row as a doc link also select that module. Missing or
+  unmatched hints leave all module docs listed by path for on-demand reading.
+  `detail: "complete"` embeds every module and returns complete package records.
+  With `detail: "full"` or `"complete"`, prompt
   bundles also render high-signal object facts: tenant mode/field, `cti`/`sti`
   strategy, conflict columns, method signatures, and field
   defaults/constraints/readonly/transient flags.
 
 The `smrt dev:knowledge-*` CLI commands request `detail: "full"`, so they remain
-full-detail and unbudgeted.
+structurally detailed and unbudgeted. Add `--complete` to embed every module.
 
 ## Knowledge Boundary
 
@@ -356,7 +361,7 @@ then return a model-ready prompt bundle.
 | `changedFiles` | `string[]` | No | Files to route to package experts |
 | `focus` | `string` | No | Review focus or concern |
 | `documentation` | `string` | No | Additional docs or notes to include |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `build-domain-review-context`
 
@@ -370,7 +375,7 @@ Domain-scoped alias for `build-review-context`.
 | `documentation` | `string` | No | Additional docs or notes to include |
 | `scope` | `'project' \| 'local' \| 'package' \| 'sdk' \| 'installed'` | No | Knowledge source scope (default: `project`) |
 | `package` | `string` | No | Package name or short name to focus |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `smrt-review`
 
@@ -383,7 +388,7 @@ Return deterministic review findings, a prompt bundle, or both.
 | `focus` | `string` | No | Review focus or concern |
 | `documentation` | `string` | No | Additional docs or notes to include |
 | `mode` | `'findings' \| 'prompt-bundle' \| 'both'` | No | Response mode (default: `both`) |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `build-architecture-context`
 
@@ -396,7 +401,7 @@ then return a model-ready architecture prompt bundle.
 | `idea` | `string` | No | Product or implementation idea |
 | `documentation` | `string` | No | Existing docs or requirements |
 | `focus` | `string` | No | Architecture concern to prioritize |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `build-package-specialist-context`
 
@@ -422,7 +427,7 @@ Domain-scoped alias for `build-architecture-context`.
 | `focus` | `string` | No | Architecture concern to prioritize |
 | `scope` | `'project' \| 'local' \| 'package' \| 'sdk' \| 'installed'` | No | Knowledge source scope (default: `project`) |
 | `package` | `string` | No | Package name or short name to focus |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `smrt-architecture`
 
@@ -435,7 +440,7 @@ risks, questions, and the reusable architecture prompt bundle.
 | `idea` | `string` | No | Product or implementation idea |
 | `documentation` | `string` | No | Existing docs or requirements |
 | `focus` | `string` | No | Architecture concern to prioritize |
-| `detail` | `'summary' \| 'full'` | No | Default `summary`; `full` embeds authored docs and full package records |
+| `detail` | `'summary' \| 'full' \| 'complete'` | No | Default `summary`; `full` embeds package docs and matching modules; `complete` embeds all modules and full package records |
 
 ### `list-agent-skills`
 

package/dist/index.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { a as checkKnowledgeFreshness, c as packageDocPaths, d as smrtArchitecture, f as smrtReview, i as buildReviewContext, m as TOOLS, n as buildKnowledgeIndex, o as checkKnowledgeFreshnessFromIndex, p as REVIEW_SKILL_NAME, r as buildPackageSpecialistContext, t as buildArchitectureContext } from "./knowledge-D2k9xM3M.js";
+import { a as checkKnowledgeFreshness, f as smrtArchitecture, h as TOOLS, i as buildReviewContext, m as REVIEW_SKILL_NAME, n as buildKnowledgeIndex, o as checkKnowledgeFreshnessFromIndex, p as smrtReview, r as buildPackageSpecialistContext, s as compactContextResult, t as buildArchitectureContext } from "./knowledge-SqpqYA67.js";
 import { existsSync, readFileSync, realpathSync } from "node:fs";
 import { dirname, isAbsolute, join, relative, resolve, sep } from "node:path";
 import { fileURLToPath, pathToFileURL } from "node:url";
@@ -1518,47 +1518,6 @@ function sanitizeKnowledgeIndex(index) {
 		installedPackages: packages.filter((pkg) => pkg.isInstalledDependency)
 	};
 }
-/**
-* Compact projection of a context result for MCP callers (#2143).
-*
-* `selectedPackages` carries each package's whole authored `agentDoc`, its
-* module-doc contents, and its full domain manifest. A three-package downstream
-* product serialized to 329,003 characters that way, which is what made these
-* tools unusable as planning aids. `detail: "full"` returns the whole shape.
-*/
-function compactContextResult(result, detail) {
-	const source = result;
-	if (detail === "full") return source;
-	const compact = {
-		...source,
-		detail: "summary"
-	};
-	for (const key of ["selectedPackages", "selectedSdkPackages"]) {
-		const packages = source[key];
-		if (!Array.isArray(packages)) continue;
-		compact[key] = packages.map(compactKnowledgePackage);
-	}
-	return compact;
-}
-function compactKnowledgePackage(pkg) {
-	return {
-		name: pkg.name,
-		version: pkg.version,
-		kind: pkg.kind,
-		directory: pkg.relativeDirectory,
-		objectSource: pkg.objectSource,
-		...pkg.objectSourceReason ? { objectSourceReason: pkg.objectSourceReason } : {},
-		docs: packageDocPaths(pkg),
-		domainKnowledgePath: pkg.domainKnowledgePath,
-		relationshipFeatures: pkg.relationshipFeatures,
-		smrtDependencies: pkg.smrtDependencies,
-		sdkDependencies: pkg.sdkDependencies,
-		exportKeys: pkg.exportKeys,
-		objectCount: pkg.objects.length,
-		objects: pkg.objects.map((object) => object.tableName ? `${object.qualifiedName ?? object.className} (${object.tableName})` : object.qualifiedName ?? object.className),
-		mcpToolCount: pkg.mcpTools.length
-	};
-}
 function detailArg(args) {
 	const detail = args?.detail;
 	return typeof detail === "string" ? detail : void 0;