create-snipara 1.3.55 → 1.3.56

package/dist/index.js

@@ -13,7 +13,7 @@ import { homedir } from "os";
 // package.json
 var package_default = {
   name: "create-snipara",
-  version: "1.3.55",
+  version: "1.3.56",
   description: "Onboard Snipara Hosted MCP Context + Memory with auth, companion workflows, and optional Snipara Sandbox",
   main: "dist/index.js",
   type: "module",
@@ -1431,8 +1431,8 @@ Agent task lifecycle:
    context and \`snipara-companion code impact\` before risky multi-file changes, PR
    reviews, routes, services, jobs, auth, billing, deployment, schema, migrations,
    or explicit "what is missing" assessments.
-8. Use \`snipara_plan\` or \`snipara_decompose\` only for FULL-mode work and only
-   when the hosted server exposes them.
+8. Use \`snipara_plan\` for complex work in any plan when exposed; reserve
+   \`snipara_decompose\` for FULL-mode work when the hosted server exposes it.
 9. When the LLM has produced a visible multi-phase plan and \`snipara-companion\`
    is installed, keep the machine plan in JSON and run
    \`snipara-companion workflow start --goal "<goal>" --plan-file <plan_json_file>\`.
@@ -1517,7 +1517,7 @@ This workspace uses Snipara Hosted MCP for current project context, business/cli
 - For code impact and structural code questions, use \`snipara-companion code callers/imports/neighbors/shortest-path/impact\` first when \`snipara-companion\` is installed; it auto-selects hosted MCP for clean indexed code or the local overlay for dirty/ahead worktrees and reports \`sourceSelection\`. Use hosted \`snipara_code_impact\` only when companion is unavailable or after push/reindex for canonical graph impact.
 - On paid Context plans, use \`snipara_code_symbol_card\` before editing important symbols.
 - 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.
+- Use \`snipara_plan\` for complex work when available; use \`snipara_decompose\` when deeper decomposition is needed and the hosted server exposes it.
 - Use local file reads, \`rg\`, \`git status --short\`, and tests for exact code edits and current working-tree state.
 - When \`snipara-companion\` is installed and the LLM has a visible multi-phase plan, keep the machine plan in JSON, use \`snipara-companion workflow start\`, \`phase-start\`, and \`phase-commit\` per phase, and after \`workflow resume\` rerun \`workflow phase-start\` before editing again.
 - Generated hooks can call \`snipara-companion pre-tool\`, \`post-tool\`, and \`stuck-guard status\` so Rescue Packs are runtime-triggered rather than relying only on instructions.

package/package.json

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