Pet: qualify the /pet habitat in a real terminal and accept the shared owner across TUI + desktop

[Hmbown]

0.9.13 ships /pet (#6154, from #6110 plus the prepared shared-owner/Kitty patch). What it ships on is test evidence and the prepared-archive receipts; these acceptance items were explicitly not done and stay open here (split out of #6109 so the umbrella can track the cross-surface owner work):

1. Real-terminal visual qualification of the Kitty pixel habitat: docked→full transitions, continuous motion, resize, Escape image cleanup, a fallback (braille) terminal, tmux/SSH behaviour, reduced motion. Measure delivered frame timing, CPU, RSS, bandwidth and input latency in the terminal; the only numbers today are the raster microbenchmark (17.09 ms mean / 19.55 ms p95, ~150 KB/frame, excludes transport) and a 30 Hz simulation. 60 fps is a target, not a measured result. Computer Use access to Ghostty/Terminal was denied in the preparing session; do not relabel browser or native screenshots as terminal proof.
2. Shared-owner acceptance: open the TUI habitat and the desktop/browser view on one live session, compare identity/tick/digest at a retained frame, interact from either side, close and reopen the TUI, confirm continued ownership, one producer, one audio lease, durable appearance. Exercise owner restart, a competing owner, source change, storage failure.
3. Engine metadata attachment beyond the TUI: only the TUI producer forwards accepted Engine metadata today; app-server does not (App-server: finish Runtime client conversion and acceptance #6139, Event projection for watch-only clients: broadcast/watch instead of a single-consumer event channel #6152).
4. Founder direction "Codewhale by default" for the appearance: not interpreted in 0.9.13 (the eight prepared presets are unchanged). Decide what the default look is and make it the default.
5. Completion outcome fidelity: the pet projection keeps only a derived failed; carry the typed completed|interrupted|failed terminal status and receipt identity through the metadata projection so a cancelled turn never gets a success gesture (see the animation packet in artifacts/pet-review-20260912/CORE-PET-GPUI-CONTRACT.md).

Contract and evidence: pet/SHARED.md, pet/QA.md, docs/design/DOT_WHALE_PET.md, artifacts/pet-review-20260912/{PREPARED-PET-HANDOFF,RUST-PET-MODE-TAKEOVER,CORE-PET-GPUI-CONTRACT}.md.

[Hmbown]

Status (v0.9.14 run): not reached in this slice — qualifying the /pet habitat needs a real Kitty terminal, which this environment cannot provide (a stop-and-ask condition recorded per the run brief).

[Hmbown]

Status from the 0.10.0 readiness pass (PR #6370): nothing on this list was executed, and nothing is claimed.

• The pass ran in a headless Linux container with no Kitty-protocol terminal, so item 1 (real-terminal qualification of the pixel habitat, frame timing, CPU/RSS, resize, image cleanup, tmux/SSH, reduced motion) could not be run. The only new pet evidence in 0.10.0 release readiness: green CI, #6362 stack fixes, water cadence, Extensions trust review, SIGPIPE-safe MCP startup #6370 is the agent-event handoff test from feat(runtime-api): terminal byte stream (#34), stream resume + idempotent submit (#76), pet agent-count pin (#12) #6361 that pins the ×N count.
• Items 2–5 (shared-owner acceptance, Engine metadata beyond the TUI, the default appearance decision, typed completion outcome in the projection) were not touched.

This stays open and needs a human with a native Kitty terminal before 0.10.0 ships with /pet as qualified.

---

Generated by Claude Code