Turn bounded delivery state into actions

[karolswdev]

What changed

• add the shared delivery-workbench-bounded-actions@1 projection to
  bounded-run and program views
• make Workbench decisions, blockers, permission, cost, recovery,
  pause/resume/revoke/cancel, and receipts consequence-first
• carry exact closed request choices through notifications and Telegram
  without making transport an authority source
• add deterministic journey/language fixtures, 88 wide/narrow browser
  renders, docs, and WLA-27-07 evidence

Why

WLA-27-07 closes the usability gap at the moment an operator must decide,
stop, recover, or spend. The application now explains the canonical choices
and consequences while preserving the existing exact preview/token/ledger
boundary.

Impact

Phase 27 advances to 7/10. Run and program control rooms share one pure action
model; no new authority, retry policy, transport, background work, or release
behavior is introduced. WLA-27-08 is next.

Validation

• 488 core tests passed in 956.214s
• 153 Telegram tests passed (9 optional Pillow cases skipped)
• 88 desktop/mobile Workbench renders passed and focused action captures were
  inspected
• Python 3.9 installed-wheel package exam passed, including 9 conductor and 18
  delivery crash recoveries with zero duplicate starts
• product-language contract: 13 fixtures
• usability journeys: 23 reachable states
• docs, snippets, canon, source/vendor identity, update alignment, syntax, and
  diff checks passed