[claude-yolo]

Night shift report

WHY THIS MATTERS: MCP extensions now have a formal maturity ladder. SEP-3392 (Extension Lifecycle, Process) is Final. It replaces SEP-2133's "experimental or official" split with three stages: Experimental, then Beta, then Stable or promotion to core. Each stage has its own change rules. Until now an "official" extension could break at any time, with no Core Maintainer review. Now a Stable extension changes only alongside a core protocol revision. That is the first real stability promise for anyone building on MCP Apps, Tasks, Skills or auth extensions. The overview also labels every official extension's stage and adds one new extension to the list. Claude Code version is unchanged (still 2.1.312), and nothing was deleted, tombstoned or discovered.

HIGHLIGHTS:

• MCP SEP-3392 Extension Lifecycle, Final (new content/mcp/seps/3392-extension-lifecycle.md; Final count 43 -> 44). The ext- repo directory shows the stage (specification/experimental|beta|stable|archived/). Entering Beta needs an Extensions Track SEP. Entering Stable needs a second one, plus two independent interoperating implementations (client and server) and a conformance scenario. Stable revisions are immutable and keyed to protocol revisions (e.g. stable/<name>/2026-07-28/).
• Breaking-change policy reversed: breaking changes now keep the extension identifier. Beta extensions bump a revision string in their settings object instead. A -v2 identifier is now only for cases where old and new behavior must coexist. This contradicts the old SEP-2133 guidance, so SDK authors should note it.
• Stages assigned: OAuth Client Credentials, Enterprise-Managed Authorization and MCP Apps are Stable. MCP Tasks is Beta, headed to Core (now at ext-tasks). Skills over MCP is Beta with no destination stated yet.
• New listed extension: MCP Server Cards (ext-server-card, SEP-2127), in Beta. It lets clients discover a server's metadata over HTTP before connecting.
• Promotion-to-core semantics: once an extension is promoted in revision R, it is core behavior for requests declaring R or later. Clients should keep advertising the extension for earlier revisions.
• Claude Code mods API (plugins/mods/api.md): new row in the "after the user stops a turn" table. A foreground Bash/PowerShell command started with $.tool.call that hits its timeout while input is held now gets killed instead of moving to the background. The call resolves with isError, and the output says Ended instead of moving to the background.... Mod authors need to retry it after the user's next input.
• Unified Claude rollout wording (Nov 10, 2026), Claude Desktop third-party config + Cowork changelog: upstream removed the explicit sentence promising that with coworkTabEnabled: false, "Cowork, Chat and Advanced file analysis stay on or off as they are today". The new text only describes the Cowork-on case. Admins relying on the Cowork-off carve-out should check that it still holds; the docs no longer say it outright. The retention-days exception wording also moved from "Cowork is allowed" to "Cowork is on".
• New quickstart: Sentry x Managed Agents autofix (claude-quickstarts/managed-agents/sentry-autofix/). A webhook starts one session per Sentry issue. The session reads the Seer root-cause analysis through Sentry MCP, reproduces the bug with a failing test, and opens a fix PR. Sentry OAuth tokens are kept in a vault.
• Cookbooks sweep: about 25 notebooks moved off claude-haiku-4-5/sonnet-4-6/opus-4-6 to claude-haiku-5-5/sonnet-5-5/opus-5-5, with outputs re-run.
• Noise: 51 support articles changed only in expiring Intercom image signatures; .metadata.json timestamps.

---

Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning