DL-265

Forge notifications ride the generic DispatchControl relay (SessionsResponse.deliver_control envelope wrapping AgentControl.forge_notification), NOT the bare SessionsResponse.forge_notification = 7 variant — that variant predates the generic relay (compass-notification-delivery/design.md:199-202) and is superseded: it stays reserved on the wire with a doc comment, and no Runner dispatch arm is built for it. Zero new Runner code on the relay path. Agent-side delivery idempotency is control-rail SEQ-based (acks.isApplied, packages/compass-agent/src/transport/control-source.ts:363-367); no content-tuple key exists on this lane, and duplicate content is within the at-least-once contract.

Status: Active (Matt, 2026-08-26)

Record: ../../server/compass-forge-agent-notification/design.md#the-pipeline-end-to-end