Faryo 1.11.10

Faryo 1.11.10

Faryo 1.11.10 hardens Codex writer ownership after App Server use.

• Resume now probes Codex's process-held per-thread writer lock before starting
  an independent App Server or TUI. A thread already open in another Codex
  client returns an explicit conflict instead of creating a failing tmux pane.
• The probe is advisory and non-mutating: Faryo never deletes or rewrites a
  Codex lock file, and the actual Codex resume remains authoritative for races.
• The production Owner routes bounded thread/read, thread/goal/get, and
  rate-limit reads through its existing supervised Unix-socket App Server. It
  no longer keeps a second stdio App Server and model-refresh worker alive.
• Closing the last Faryo App Server session restarts only the dedicated
  faryo-appserver.service after the turn has settled and the registry record
  is removed. This releases Codex's otherwise delayed writer immediately while
  preserving conversation history.
• If another Web session remains, the shared App Server stays alive; no active
  turn is recycled. Existing TUI sessions, tmux geometry, authentication and
  reliable-send semantics are unchanged.

The release remains source-only and adds no runtime dependency. The behavior is
covered by writer-lock, runtime, Owner-route and compatibility-channel tests.