Update to Snipara

{
  "description": "Configure the Snipara plugin project and independently enable or disable Snipara, Companion and Orchestrator. Use only when the user requests setup or a settings change.",
  "included_files": [],
  "name": "settings",
  "skill_md_contents": "---\nname: settings\ndescription: Configure the Snipara plugin project and independently enable or disable Snipara, Companion and Orchestrator. Use only when the user requests setup or a settings change.\ndisable-model-invocation: true\n---\n\nLocate this plugin's `scripts/snipara.mjs` from the loaded skill directory: it is\n`../../scripts/snipara.mjs`. Resolve that to an absolute path before running it.\n\n1. Read `../../config.json`. Show the selected project and the three on/off values.\n2. For first setup, use the plugin's native MCP OAuth login. In account mode,\n   the user signs into Snipara and explicitly chooses one accessible project in\n   the consent screen. After login, call `snipara_stats` on this plugin's MCP\n   connection named `snipara-plugin` and read its returned `project_id`. Do not use another global\n   connection or infer the project from environment variables. If local runtime\n   setup is requested, show that project ID and build its profile with\n   `node <script> build --connection account --project <observed-project-id> --output <directory>`.\n   This keeps the account MCP URL and native OAuth audience unchanged. A\n   project-specific profile remains available with `--connection project` for\n   existing explicit-project integrations. Never request a secret in chat.\n3. To change an existing profile, use\n   `node <script> configure --output <marketplace-directory> --companion off`\n   (or `--snipara on|off`, `--orchestrator on|off`, `--project <slug>`). Preserve\n   options the user did not change. If the marketplace location is unknown, ask\n   for it; do not modify an installed cache or an unrelated repository directory.\n4. Explain that the client must refresh its installed local plugin and restart.\n   Until reload, its cached profile is still active. Show the resulting profile.\n   If first setup installs a project profile from a second marketplace, disable\n   the bootstrap copy before using the project profile. Avoid two active copies\n   of the same Snipara skills. Do not uninstall unrelated plugins or connections.\n5. Use the native client's MCP login for account access. Changing the selected\n   account project requires reconnecting and choosing it in consent, then\n   updating the local runtime profile to the newly observed project ID. OAuth credentials remain with the native client. If OAuth fails,\n   report the observed failure; do not silently copy API keys into a manifest.\n6. Local dependencies are separate from the plugin files. When the user requests\n   installation, run `node <script> install companion` or `install orchestrator`\n   for enabled modules. Never install dependencies or launch tasks at session start.\n\nAll three modules default to on. A disabled module's skill is omitted from the\ngenerated profile. Snipara off removes the plugin's MCP registration. Companion\nand Orchestrator off also reject the corresponding runtime and install commands.\nThese switches govern this plugin; existing global MCP connections, independently\ninstalled CLIs, and already running tasks have their own lifecycle.\n"
}