← 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
{
"description": "Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure.",
"included_files": [],
"name": "debugging-mcp-delivery",
"skill_md_contents": "---\nname: debugging-mcp-delivery\ndescription: \"Use when an existing Noodle Seed MCP project has a concrete validation, runtime, connector, App, host, deployment, or production failure.\"\n---\n\n<!-- noodle-skill version:0.62.1 hash:aa715bae12041d7c -->\n\n# debugging-mcp-delivery\n\nRepair or isolate the first failing evidence layer while preserving everything already proven.\n\n## Use when\n\n- Diagnose this failing MCP project.\n- Inspect a hosted failure from logs or status.\n\n## Do not use when\n\n- Do not use for a greenfield build with no failure evidence.\n- Do not mutate hosted state during read-only inspection.\n\n## Required inputs\n\n- Exact failing command or symptom.\n- Current target and evidence level.\n- Most recent sanitized failure.\n\n## Workflow\n\nRead and follow the canonical playbook `references/verify-and-recover.md` at `../noodle-seed/references/verify-and-recover.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.\nLoad `references/troubleshooting.md` at `../noodle-seed/references/troubleshooting.md` only when the playbook or observed evidence names that concern.\nLoad `references/inspect-hosted.md` at `../noodle-seed/references/inspect-hosted.md` only when the playbook or observed evidence names that concern.\n\n## Verification evidence\n\nThe failed layer is rerun successfully, or the stable blocker and exact next action are reported.\n\n## Recovery paths\n\nAfter two attempts with the same signature, stop editing and preserve the repro and passing layers.\n\n## Stop conditions\n\nStop before hosted mutation unless the user separately requests deploying-mcp-services.\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 of public snapshot: 8384fb54dbcfc0c2c4a270031929812c7592782ce65c0062d3d01460a611e070