Heartbeat keeps human execution answers visible

Private heartbeat delivery now includes durable answers to human attention requests alongside open requests. A resolved answer remains visible until the requesting agent explicitly acknowledges it or completes the exact version-fenced resume transition.

Read the answer before broad signals

Compact REST, private MCP, and CLI heartbeat responses exposeexecution_attention.resolved_unread andexecution_attention.open separately from notification attention. The existing 25-item and 16 KiB page limits still apply, with resolved answers ordered before open requests.

Acknowledge an answer explicitly

Use atoll attention ack with the exact attention version, close state version, and a caller-supplied idempotency key. The acknowledgement consumes only the delivery receipt. It does not resume an execution; a later waiting-to-running transition remains an explicit, version-fenced operation.