Atomically plan Workshop streaming finalization

[dcellison]

Summary

• add schema v13 execution contracts for durable delivery work and immutable send / edit fragment operations
• atomically persist a canonical assistant reply, its streaming-finalization delivery, and its complete operation plan
• resolve the canonical direct Telegram binding and optional confirmed preview internally from the inbound message identity
• preserve all preexisting delivery work as send_fragments / send during migration
• record the completed boundary and the next bounded adapter/worker milestone in the Workshop implementation map

Finalization contract

• a confirmed preview produces an explicit edit of that exact Telegram message followed by continuation sends
• no confirmed preview produces an all-send plan
• the terminal edit remains explicit even when the preview already contains the terminal snapshot
• message, delivery, and operation plan share one SQLite transaction and one prior-state decision
• changed content, changed plan semantics, routing disagreement, and either tested half-state fail closed
• retries across process restart or a later observation time return the same immutable state

Production safety

• no production handler calls the new atomic service
• the Workshop runtime remains unregistered
• the existing Telegram worker explicitly claims only the send_fragments execution contract
• the existing adapter rejects edit operations before any Bot API call
• claim and expired-lease recovery are execution-contract scoped
• qualification work and all current direct Telegram behavior remain unchanged

Verification

• make check
• make typecheck
• focused Workshop delivery/finalization suite: 82 passed
• full suite: 5,364 passed, 1 skipped