Update to Snipara

{
  "description": "Use Snipara Orchestrator for explicit controller plans, task coordination, execution receipts and proof gates. Invoke only when the user requests orchestration or an authorized task requires it.",
  "included_files": [],
  "name": "orchestrator",
  "skill_md_contents": "---\nname: orchestrator\ndescription: Use Snipara Orchestrator for explicit controller plans, task coordination, execution receipts and proof gates. Invoke only when the user requests orchestration or an authorized task requires it.\ndisable-model-invocation: true\n---\n\nRead `../../config.json` and require `modules.orchestrator: true`. Resolve the\nplugin's `../../scripts/snipara.mjs` to an absolute path. Use\n`node <script> orchestrator <arguments>` so the module gate and pinned runtime\nare enforced. If absent, show `node <script> install orchestrator`; install only\nwhen requested. Enabling this module never starts a controller or worker.\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\n1. Inspect `status --json` and the requested command's `--help` before work.\n2. Discover native hosts with `host discover --adapter all`; discovery is not\n   proof that a host can execute or that it is authorized for this task.\n3. Translate an explicit goal into a controller plan, acceptance conditions and\n   bounded budget. Start with observe autonomy unless execution is authorized.\n4. Preserve stored autonomy ceilings, proof floors, permissions and evidence.\n   Reconcile/preview before an explicit `--execute` action. Do not infer release,\n   deployment, publishing or worker-messaging authority from plugin activation.\n5. Capture execution receipts and review/proof evidence. Treat native execution,\n   independent acceptance and live customer-path proof as separate outcomes.\n\nHosted htask operations require account/project credentials and the hosted\nservice. Plugin OAuth does not provision CLI credentials. With Snipara off, do\nnot invoke hosted queues or context; this version permits `status --json`,\nhelp and version only.\nKeep htask coordination here, not on Companion. Report unavailable capabilities\nor missing proof without weakening an existing gate. Never fabricate credentials,\napproval, acceptance, runtime continuation or billing measurements.\n\nThe launcher excludes environment credentials by default. For a hosted command\nthat needs a Snipara key, explain sharing with Orchestrator and obtain explicit\nuser authorization before placing `--with-snipara-credentials` immediately after\n`orchestrator`. Permission to orchestrate alone does not authorize credential\nsharing. Never ask for or print keys or forward unrelated provider credentials.\n"
}