[FEATURE] Resize the primary PTY through its original session owner #4
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/ttyd#4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Native pagers need to observe changes to their original PTY dimensions. Ttyd already has typed resize requests and transactional PTY resize state, but its session-lifecycle IPC adapter does not dispatch that request.
Proposed behavior and scope
Accept
TtyResizeRequestV1only through the authenticated session owner's lifecycle endpoint. Resize that session's live primary PTY and return an empty typed success or retry reply. Identical dimensions remain a no-op; successive pending resize events retain the latest generation. Coordinate the original owner and physical-page fixture in Integration.Authority, security and reliability
The receiving endpoint selects the original generational session. Request bodies cannot name a session, PTY or capability. Inherited stdin/stdout endpoints remain unable to resize;
manretains state-read access and its exact manual-store READ only. Validate framing, dimensions, correlation and reply capacity before effects. Preserve event-queue backpressure, stale-session refusal and unwanted-receipt cleanup.Acceptance criteria
Alternatives and tradeoffs
Changing a host display does not prove guest PTY state changed. The existing lifecycle owner can issue the typed operation without delegating resize control to the reader or introducing another discovery route.
Tracking and rollout
Related terminal work: #1. The Integration fixture must retain actual owner calls, fresh state and physical screen rows before claiming resize acceptance.
Implemented in 77a106c. The original session owner can resize its primary PTY; inherited stream routes still refuse control. All 161 library tests passed in both default and runtime configurations, including the new resize and receipt-cleanup controls. Matching-image owner calls and physical screen observations remain open.
Wired in Integration 9c90cdf6 and Rootd 6d7e3ad2. Rootd retains the original lifecycle endpoint and coordinates the two resize checkpoints using sourced input events. The pager keeps state-read access and its exact manual-store READ; it receives no resize authority. Matching-image owner and screen acceptance remains open.