chore(changeset): consumer-facing summary for #412

Author: ScriptedAlchemy

.changeset/notice-delivery-adapter-surface.md

@@ -2,4 +2,4 @@
 "agent-bundle": patch
 ---
 
-Expose each host's #99 notice delivery advertisement through the adapter API and select cross-request notice routes from it when generating MCP entries. `TargetAdapter` gains `noticeDelivery` (a local `NoticeDeliveryAdvertisement` shape, structurally identical to the runtime's `AgentNoticeDeliveryAdvertisement` so public declarations never resolve through the optional `@agent-bundle/runtime` peer), `TargetRegistry` gains `noticeDelivery(target)`, and `adapters/capability-state` gains `noticeDeliveryAdvertisementFrom()` plus `intersectNoticeDeliveryAdvertisements()`. The built-in `claude`, `codex`, `cursor`, and `portable` adapters read the advertisement from their pinned capability tables and the unified `plugin` adapter advertises the three-host intersection; the registry re-validates JavaScript adapter declarations and fails closed on unknown route states or undated unavailability. `build` and `inspect --bundler` pass the target's advertisement to the generated route MCP entry and its Flight worker: the `agent-bundle://notices/inbox` resource is registered and mounted only where the host advertises `mcp-inbox`, and `resources/subscribe` plus `notifications/resources/updated` are wired only where the host additionally advertises `mcp-resource-updated` and the state is workspace-durable. A target with no advertisement wires no cross-request route; all built-in hosts advertise `mcp-inbox`, so their artifacts are unchanged.
+Gate the generated MCP server's notice routes on the target host's delivery advertisement. `TargetAdapter` gains the optional `noticeDelivery` field (typed by the new `NoticeDeliveryAdvertisement`, `NoticeDeliveryRoute`, and `NoticeDeliveryRouteState` exports, which resolve without the optional `@agent-bundle/runtime` peer), and `TargetRegistry` gains `noticeDelivery(target)`. The built-in `claude`, `codex`, `cursor`, and `portable` adapters advertise from their pinned capability tables and the `plugin` adapter advertises the three-host intersection; a JavaScript adapter declaring an unknown route state or an undated `unavailable` route is rejected at registration. `agent-bundle build` and `agent-bundle inspect --bundler` register the `agent-bundle://notices/inbox` resource only for hosts advertising `mcp-inbox`, and wire `resources/subscribe` plus `notifications/resources/updated` only where the host additionally advertises `mcp-resource-updated` and the state lifetime is workspace-durable. Built-in hosts all advertise `mcp-inbox`, so their artifacts are unchanged. (#412)