natsukium/felis
Watch
1
Code Issues 27 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Add PTY-byte capture tooling for RefTest scenarios #114

New issue
Open
opened 2026-09-05 00:20:06 +09:00 by natsukium · 0 comments
natsukium commented 2026-09-05 00:20:06 +09:00
Owner
Copy link

Migrated from docs/backlog.md (Open / RefTest capture tooling).

The replay harness exists (crates/felis-grid/tests/ref_recordings.rs: recording.bin + size.json per tests/ref/<scenario>/ directory, screen pinned as an insta snapshot), but the two seed scenarios are hand-authored. A capture tool would let any two-minute demonstration become a fixture. A felis-client --record flag is the wrong tap for this architecture: the client never sees raw PTY bytes (the daemon parses), so the recorder must tap the daemon's PTY read loop (likely a debug flag or env var writing the verbatim byte stream per session) or wrap the capture in a standalone PTY tee. Decide the surface, then grow scenarios from the deferred esctest clusters.

Design choice: daemon PTY-read tap vs standalone PTY tee. Once decided, add the recorder and seed additional tests/ref/<scenario>/ fixtures.

Origin: docs/backlog.md RefTest capture tooling.

Migrated from `docs/backlog.md` (Open / RefTest capture tooling). > The replay harness exists (`crates/felis-grid/tests/ref_recordings.rs`: `recording.bin` + `size.json` per `tests/ref/<scenario>/` directory, screen pinned as an insta snapshot), but the two seed scenarios are hand-authored. A capture tool would let any two-minute demonstration become a fixture. A `felis-client --record` flag is the wrong tap for this architecture: the client never sees raw PTY bytes (the daemon parses), so the recorder must tap the daemon's PTY read loop (likely a debug flag or env var writing the verbatim byte stream per session) or wrap the capture in a standalone PTY tee. Decide the surface, then grow scenarios from the deferred esctest clusters. Design choice: daemon PTY-read tap vs standalone PTY tee. Once decided, add the recorder and seed additional `tests/ref/<scenario>/` fixtures. Origin: `docs/backlog.md` RefTest capture tooling.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/darwin-smoke
No results found.
Labels
Clear labels   
priority/P0
Must be resolved before the v0.1.0 tag

  
priority/P1
Must be settled before the first public contract freezes

  
priority/P2
Explicitly deferred until after v0.1.0

  
release/v0.1.0
Work tracked for the first tagged release

  
status/blocked
Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  
status/planned
Triaged with a source-grounded plan and a passed pi review; ready to implement

  
type/bug
Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  
type/design
An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  
type/test-gap
Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  
type/tracker
Parent issue that tracks child work

No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis#114
No description provided.