← ArezCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Arez
Snapshot Sep 30, 2026 · 22:58 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "deploying-mcp-services",
"description": "Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write.",
"included_files": [],
"skill_md_contents": "---\nname: deploying-mcp-services\ndescription: \"Use when the user explicitly requests a Noodle Seed hosted link, configuration write, deployment, access change, rollback, or connection write.\"\n---\n\n<!-- noodle-skill version:0.62.1 hash:93e735b7ffb45df1 -->\n\n# deploying-mcp-services\n\nApply only the explicitly authorized hosted mutation to the explicit org, app, and environment.\n\n## Use when\n\n- Deploy this MCP service to an explicit environment.\n- Roll back or change hosted access.\n\n## Do not use when\n\n- Do not use for preparation, inspection, or local-only work.\n- Do not select or default a mutation target implicitly.\n\n## Required inputs\n\n- Explicit org, app, and environment.\n- Authorized mutation.\n- Pre-deploy verification evidence.\n\n## Workflow\n\nRead and follow the canonical playbook `references/deploy-and-ops.md` at `../noodle-seed/references/deploy-and-ops.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.\nLoad `references/cli-commands.md` at `../noodle-seed/references/cli-commands.md` only when the playbook or observed evidence names that concern.\n\n## Verification evidence\n\nThe requested hosted state is confirmed without claiming unperformed host or production checks.\n\n## Recovery paths\n\nPreserve local evidence and isolate authentication, target, build, rollout, health, or rollback failures.\n\n## Stop conditions\n\nStop and ask when target, authority, or effect is ambiguous.\n\n## Handoff contract\n\nPass the selected outcome, explicit target, changed files, commands run, passing evidence, first unproven evidence layer, sanitized failure, remaining authority, and exact next action. The receiving skill continues from that layer; do not restart discovery or discard prior proof.\n"
}SHA-256: 0e3d4ed115aead6cae08a0250eb6419e3961ce22d7c0125312dfec4ebc0d39ec