Tech Debt: Remove rawDelivery bypass once IDE supports wake/digest

Architectural Context

Currently, the Antigravity IDE host application's MCP notification listener expects un-coalesced, raw events to trigger its auto-wakeup sequence. In Phase 3, we transitioned the framework's native mcp-notifications transport to a coalesced wake/digest envelope structure (ADR 0002 §6.4.2) to prevent token-burn thundering herds.

Per human command, an explicit bypass flag (harnessTargetMetadata.rawDelivery: true) was introduced. This forces CoalescingEngineService to bypass batching and emit raw events (matching pre-Phase 3 behavior) to immediately restore IDE auto-wakeup functionality, as the current event volume does not strictly demand batching.

The Objective

This ticket serves as an audit hook to revisit and eventually deprecate the rawDelivery bypass.

Once the Antigravity IDE updates its internal notification listener to support parsing wake/digest payloads, or if event volume reaches a scale where raw streaming degrades the host performance, we must:

1. Remove the rawDelivery: true config from the harness bootstrapping.
2. Ensure the IDE properly wakes using the wake/digest payloads.
3. Remove the rawDelivery bypass logic from CoalescingEngineService.mjs to restore the strict canonical wire format.