Update to Snipara

{
  "description": "Use Snipara Companion for local coding workflow plans, checkpoints, evidence and resuming saved work. Use for continuity and managed multi-phase work.",
  "included_files": [],
  "name": "companion",
  "skill_md_contents": "---\nname: companion\ndescription: Use Snipara Companion for local coding workflow plans, checkpoints, evidence and resuming saved work. Use for continuity and managed multi-phase work.\n---\n\nRead `../../config.json` and require `modules.companion: true`. Resolve the\nplugin's `../../scripts/snipara.mjs` to an absolute path. Invoke Companion through\n`node <script> companion <arguments>` so the runtime switch and pinned version\nare checked. If the runtime is absent, show `node <script> install companion`;\ninstall only when requested. Preserve the current workspace and unrelated edits.\n\nBefore hosted or execution work in account mode with Snipara on, call\n`snipara_stats` on this plugin's MCP connection and compare its `project_id`\nto the explicit local profile `project`. Stop on missing configuration,\nauthentication failure or mismatch; use settings to align the profile with the\nproject selected in OAuth. Never take the project from another global MCP or\nan inherited environment. Local status/help remains available without this\nhosted check. With Snipara off, follow the restricted local-only behavior below.\n\nUse Companion's actual `--help` for command arguments before unfamiliar actions.\nChoose LITE for a small single-phase edit; keep a visible plan and managed FULL\nworkflow when multiple phases, risk or durable continuity require it.\n\nFor a managed task:\n\n1. Inspect existing `.snipara/workflow/current.json`; preserve another task's state.\n2. Start from an explicit visible plan using `workflow start --plan-file <file>`.\n3. Use `workflow phase-start <id>`, exact edits and focused verification, then\n   `workflow phase-commit <id> --summary <result>` with honest evidence.\n4. Resume saved work using `workflow resume --include-session-context`. When\n   returning to a dirty/shared repo, also inspect `team-sync what-changed`.\n5. Finish with `final-commit --summary <result>` when the managed task is complete.\n\nCompanion keeps local workflow state and helpers. Hosted context and phase-memory\npersistence require a separately configured Snipara account; plugin OAuth tokens\nare not automatically shared with a CLI. If the Snipara module is off, this\nversion permits `workflow status --json`, help and version only; do not invoke\nhosted queries, workflow publication or memory writes.\nRespect failures and distinguish local state from a confirmed hosted receipt.\n\nThe launcher excludes environment credentials by default. If hosted CLI work\nneeds an environment-backed Snipara key, explain that it will be shared only\nwith Companion and obtain the user's explicit authorization for that sharing.\nThen place `--with-snipara-credentials` immediately after `companion` for that\ninvocation. Do not add the flag just because a task or module is enabled. Never\nask for or print key values; do not forward unrelated provider credentials.\n\nCheckpoint continuity requires the project folder, `.snipara` state and referenced\nfiles/artifacts. It does not migrate a live agent process. Use Orchestrator for\nexplicit htask queues, controller execution and production proof coordination.\n"
}