Record a real same-session app GIF for the README

[Snailflyer]

Faryo needs a short, real in-app same-session recording near the top of the README.

Current launch rule: do not use synthetic workflow art or generated diagrams as the primary visual. Until a real recording exists, the README should use the existing redacted app screenshots.

Acceptance criteria:

• Captured from real Faryo app operation, not a synthetic animation.
• Shows desktop tmux-backed AI session, phone or desktop Faryo workbench view, mobile approve or follow-up instruction, then the same session continuing on desktop.
• Redacted: no tokens, private paths, customer data, real hostnames, or private project content.
• GIF is under 8 MB, or the README uses a stable linked video plus the existing screenshots.
• README alt text explains same-session continuity without implying remote desktop or a second AI chat.

[Snailflyer]

The synthetic same-session demo assets have been retired. They were useful as an internal placeholder, but not good enough for launch-facing README placement.

Current direction for this issue:

• Use the existing redacted app screenshots near the top of the README.
• Do not add a GIF unless it is captured from real in-app operation.
• Keep the safety/maturity boundary close to the screenshots so Faryo is not mistaken for remote desktop or a hosted chat product.

[Snailflyer]

Update: the first real redacted same-session GIF is now available on the v1.0.7 release:

https://github.com/Snailflyer/faryo/releases/download/v1.0.7/faryo-public-redacted-same-session-handoff-walkthrough-20260528-0120.gif

This is not a synthetic mockup. It shows the Gateway workbench sending input/handoff content back into the same tmux-backed HP session. I am leaving this issue open until the README uses the asset cleanly instead of just linking it from the release.

[Snailflyer]

Ready README integration snippet. I am not closing this issue until the actual README carries it.

Suggested placement: immediately after the short product boundary (same tmux-backed session; not remote desktop, hosted IDE, browser terminal, or second AI chat) and before the two static screenshots.

<p>
  <a href="https://github.com/Snailflyer/faryo/releases/download/v1.0.7/faryo-public-redacted-same-session-handoff-walkthrough-20260528-0120.gif">
    <img
      src="https://github.com/Snailflyer/faryo/releases/download/v1.0.7/faryo-public-redacted-same-session-handoff-walkthrough-20260528-0120.gif"
      alt="Faryo same-session walkthrough: Gateway workbench sends short input, text handoff, and attachment handoff into the same live tmux-backed session"
      width="320">
  </a>
</p>

The walkthrough above is captured from the real Gateway workbench. It shows Faryo sending a short input, a text handoff package, and an attachment handoff back into the same live `tmux` session. The phone/browser is a compact control surface; the terminal process remains the source of truth.

Same README pass should also update the Quickstart and launch-guide links from v1.0.0 to v1.0.7, so the proof and install path do not point at different releases.