Faryo 1.11.7

Faryo 1.11.7

Faryo 1.11.7 repairs App Server sessions that looked permanently busy after a
runtime interruption and makes Close semantics match Codex's writer lifecycle.

• Input sent during an active regular turn now uses the official turn/steer
  request with expectedTurnId and the existing idempotent browser message id.
• Authoritative hydration recomputes the active turn instead of preserving a
  stale inProgress id after reconnect or interrupt.
• Busy App Server cards offer an explicit Interrupt and close action. Owner
  waits for the interrupted turn to settle before unsubscribing and retains the
  Codex history.
• Codex keeps the writer for an unsubscribed loaded thread for up to 30 minutes.
  A TUI resume during that interval now uses Codex's official local --remote
  Unix endpoint, so it reuses the resident writer instead of failing with an
  active-writer conflict.
• Long action errors wrap inside the confirmation sheet and remain fully
  readable on phone and desktop instead of ending in a one-line ellipsis.

The release adds protocol, actor, runtime, Owner route and real-browser
regressions. It does not weaken authentication, expose the App Server socket,
delete conversation history, resize tmux, or add a second message store.