Add a redacted handoff package walkthrough

[Snailflyer]

Create a short walkthrough that shows how a prompt, note, screenshot, or file becomes a Faryo handoff package and is injected into a selected live session.

Current launch rule: use real app screenshots or real in-app operation recordings. Do not use synthetic marketing diagrams as launch-facing proof.

Acceptance criteria:

• 6 to 10 steps.
• Starts from an existing Owner tmux session and ends with the same session continuing after the handoff.
• Uses redacted app screenshots or real in-app captures only.
• No private paths, real project content, tokens, hostnames, customer data, or live private terminal output.
• Explains why the handoff lands in the existing tmux-backed session instead of creating a new chat history.

[Snailflyer]

A same-session walkthrough structure was prepared, but the synthetic demo assets have been retired and should not be used as launch-facing visuals.

If this issue continues, the direction is:

1. Start a tmux session on the Owner machine.
2. Leave the terminal process running.
3. Open the Faryo Gateway workbench from phone or desktop.
4. Select the Owner endpoint and target session.
5. Review compact output.
6. Send a short instruction or approve an action from the phone.
7. Attach a note, screenshot, or file as a handoff package.
8. Return to the desktop and continue the same session.

Remaining work:

• Use only real app screenshots or actual in-app operation recordings.
• Explain why the handoff lands in the existing tmux-backed session instead of creating a new chat history.
• Avoid private paths, real hostnames, tokens, customer data, or live terminal output.

[Snailflyer]

Update: a real redacted same-session walkthrough GIF is now attached to 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

It is captured from the real Gateway workbench at 393x917. The flow shows the same HP tmux-backed session receiving a short phone/workbench input, then a text handoff package, then an attachment handoff. Host/path/git details are redacted.

Remaining work for this issue: turn this into the final README/issue walkthrough text and keep the upstream version-label fix from regressing on reinstall.

[Snailflyer]

Final issue walkthrough text is now ready; this issue should still stay open until README/docs carry it and the version-label fix is in source/package.

Same-session handoff walkthrough

1. Start from an existing Owner machine tmux session that is already running Codex, Claude Code, or a shell.
2. Open the Faryo Gateway workbench from a phone or desktop browser.
3. Select the route and the target live session. The browser talks to Gateway; Gateway proxies to Owner; Owner controls the selected tmux pane.
4. Review compact output from the target session. Use raw output only when exact terminal evidence is needed.
5. Send one short instruction from the workbench composer. The instruction appears in the same live tmux session.
6. Create a text handoff package from the Gateway workbench and inject it into the same target session. The session receives a # Faryo Handoff Package block.
7. Create an attachment handoff. Gateway uploads the file to the Owner inbox and injects the attachment path into the same target session.
8. Return to the desktop terminal and continue from that original session. No second chat history or remote desktop session is created.

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

The GIF is captured from the real Gateway workbench at a 393x917 mobile viewport. It shows short input, text handoff, and attachment handoff all landing in the same HP tmux-backed session. Hostnames, paths, git details, and private content are redacted.

README/docs follow-up: place this after the product boundary explanation, and keep the install path aligned with v1.0.7 rather than the older v1.0.0 links.