glm-5.2
1baa619ce9
The monolithic open-questions.md (1310 lines, 47 OQs) was large enough to be unmanageable, with high size variance (OQ-42 at 220 lines next to OQ-06 at 8). Decomposed into one file per OQ under docs/architecture/questions/ (NNN-slug.md, mirroring the ADR convention), with open-questions.md retained as the index: theme-grouped tables plus a cross-theme Deferred/Blocked section that surfaces the 6 deferred OQs with their Blocked-on conditions inline (the safe-exit visibility surface). Per-OQ content moved verbatim; all 62 inbound links stay valid (none used anchors). README's curated OQ summary dropped (now redundant with the index tables). Also seeds tasks/architecture/ with this task plus two follow-ups found during the decompose: OQ-09/10 missing structured Blocked-on fields, and the tasks/architecture/ blocker-task half of the Safe Exit protocol being unenforced.
1.1 KiB
1.1 KiB
OQ-44: Terminal Modes (TTY modes)
- Origin:
docs/research/alknet-tty/phase-0-findings.mdOQ-TTY-02; crates/tty/tty-backend.md (TerminalParams.modesfield). - Status: deferred(scope)
- Door type: Two-way
- Priority: low
- Blocked on: a concrete mode-control use case (a deployment that needs to set echo/raw/canonical/etc. modes on a PTY, beyond the backend's defaults).
- Resolution: Not yet decidable. SSH's
pty_requestcarries TTY modes (echo, raw, canonical, etc.) as a packed bitmask. The common case is "default terminal modes" — themodesfield inTerminalParamsisserde_json::Value(reserved as{}in v1) for when a concrete use case requires mode control. The backends (portable_pty, dockertty: true, russhpty_request) all have defaults that work for the common terminal case. Adding mode control is additive (extend themodesJSON shape) and does not break downstream; the decision is deferred until a use case forces it. - Cross-references: ADR-053, tty-backend.md, tty-wire.md