Faryo 1.11.8

Faryo 1.11.8

Faryo 1.11.8 repairs conversation identity at both the message and session
layers, and makes the mobile conversation chrome adapt to real content rather
than fixed device offsets.

• Codex TUI rollout history now carries authoritative structured message
  blocks. Quoted banners, trust prompts and literal › lines remain inside the
  original user message instead of becoming false bubbles or activity rows.
• Question navigation, Markdown/TeX rendering and exact copy all consume those
  same server-owned message identities; terminal text parsing remains only a
  bounded fallback for genuinely unstructured captures.
• App Server and Codex TUI sessions now allocate faryoN names from one
  namespace under one lock. Every read, write and event route uses one resolver,
  and duplicate ownership returns a bounded 409 instead of silently opening
  or controlling the wrong thread.
• Startup migration moves a persisted App Server alias away from a live tmux
  alias without deleting conversation history or stopping either Codex writer.
• The verified Codex 0.149.1 command snapshot restores busy-task local controls
  such as /goal clear; unknown future versions still fail closed instead of
  inheriting stronger capabilities.
• The bottom status footprint is measured as part of layout, so release/status
  controls no longer cover the newest message.
• Narrow-screen status metadata can be swiped horizontally without widening the
  page. On multi-line phone input, attachment and send controls stack vertically
  to preserve textarea width, then return to the compact row at one line.

The release adds anonymous protocol, route, browser geometry, long-history and
namespace-race regressions. It adds no runtime dependency, does not resize tmux,
does not weaken authentication, and remains source-only.