Update to Arez

{
  "name": "embedding-mcp-assistants",
  "description": "Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries.",
  "included_files": [],
  "skill_md_contents": "---\nname: embedding-mcp-assistants\ndescription: \"Use when embedding a Noodle assistant into an existing SaaS or web application with browser, identity, session, and credential boundaries.\"\n---\n\n<!-- noodle-skill version:0.62.1 hash:cc54a67f21c0ecdb -->\n\n# embedding-mcp-assistants\n\nDeliver the requested assistant embed with identity and credential separation proven at the tested level.\n\n## Use when\n\n- Embed the Noodle assistant in an existing web app.\n- Wire browser mounting and session exchange.\n\n## Do not use when\n\n- Do not use to build a standalone MCP App.\n- Do not use when the request is only server authoring or deployment.\n\n## Required inputs\n\n- Application origin and mounting point.\n- Desired built-in or custom browser experience.\n- Identity/session boundary.\n- Requested local or hosted evidence level.\n\n## Workflow\n\nRead and follow the canonical playbook `references/embedded-assistant.md` at `../noodle-seed/references/embedded-assistant.md`. It owns the workflow; do not recreate it here or load the command catalog speculatively.\nLoad `references/authoring-workflow.md` at `../noodle-seed/references/authoring-workflow.md` only when the playbook or observed evidence names that concern.\n\n## Verification evidence\n\nThe embed works at the requested boundary without forwarding inbound credentials to business backends.\n\n## Recovery paths\n\nLocalize failures to origin, session exchange, browser mount, MCP surface, or hosted configuration.\n\n## Stop conditions\n\nStop when unavailable identity, origin, or hosted authority blocks the next evidence layer.\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"
}