create-snipara 1.3.52 → 1.3.53

package/dist/index.js

@@ -13,7 +13,7 @@ import { homedir } from "os";
 // package.json
 var package_default = {
   name: "create-snipara",
-  version: "1.3.52",
+  version: "1.3.53",
   description: "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   main: "dist/index.js",
   type: "module",
@@ -1476,7 +1476,8 @@ Use Snipara Hosted MCP before answering project-specific questions.
 - Start substantial work with \`snipara_recall\` and a targeted \`snipara_context_query\`.
 - Use \`snipara_context_query\` for source truth and \`snipara_get_chunk\` for exact cited sections.
 - When \`snipara_context_query\` returns \`answer_pack\`, use its facts, caveats, source map, and verification checklist before drafting claims.
-- Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for structural code questions.
+- Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for canonical structural code questions.
+- When local commits or a dirty working tree matter and \`snipara-companion\` is installed, use \`snipara-companion code callers/imports/neighbors/shortest-path/impact\`; it auto-selects hosted MCP or the local overlay and reports \`sourceSelection\`.
 - On paid Context plans, use \`snipara_code_symbol_card\` before editing important symbols and \`snipara_code_impact\` before risky multi-file changes or PR reviews.
 - Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings.
 - Use local file reads, \`rg\`, \`git status --short\`, and tests for exact edits/current working tree; use Snipara for architecture and indexed code graph context.
@@ -1506,7 +1507,8 @@ This workspace uses Snipara Hosted MCP for current project context, business/cli
 - Use \`snipara_context_query\` for docs, business context, current client/project truth, and narrative source material.
 - When \`snipara_context_query\` returns \`answer_pack\`, use its facts, caveats, source map, and verification checklist before drafting claims.
 - Use \`snipara_get_chunk\` before relying on exact cited wording from reference-based results.
-- Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for structural code questions.
+- Use \`snipara_code_callers\`, \`snipara_code_imports\`, \`snipara_code_neighbors\`, or \`snipara_code_shortest_path\` for canonical structural code questions.
+- When local commits or a dirty working tree matter and \`snipara-companion\` is installed, use \`snipara-companion code callers/imports/neighbors/shortest-path/impact\`; it auto-selects hosted MCP or the local overlay and reports \`sourceSelection\`.
 - On paid Context plans, use \`snipara_code_symbol_card\` before editing important symbols and \`snipara_code_impact\` before risky multi-file changes or PR reviews.
 - Check every \`snipara_code_*\` response for indexed commit SHA, indexing time, included files, coverage, and freshness warnings.
 - Use \`snipara_plan\` or \`snipara_decompose\` only for complex work and only when available.
@@ -2474,7 +2476,7 @@ async function createCompanionPack(answers) {
   fs.mkdirSync(packDir, { recursive: true });
   const readme = `# Snipara Companion Pack
 
-This project uses Snipara as a hosted-first context and memory layer with local companion workflow helpers.
+This project uses Snipara as a hosted-first project intelligence layer with source-backed context, reviewed memory, and local companion workflow helpers.
 
 ## Install Profile
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-snipara",
-  "version": "1.3.52",
+  "version": "1.3.53",
   "description": "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   "main": "dist/index.js",
   "type": "module",