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.2 KiB
1.2 KiB
OQ-46: Runner API Surface
- Origin:
docs/research/alknet-tty/phase-0-findings.mdOQ-TTY-05; crates/tty/tty-local.md (the runner pattern in pipe mode). - Status: deferred(scope)
- Door type: Two-way
- Priority: low
- Blocked on: a concrete runner-policy use case that forces the API surface (job management, log persistence, task graph integration).
- Resolution: Not yet decidable. The runner mechanism (pipe mode —
TtyParams.terminal = None→std::process::Commandwith piped stdio → framed byte stream + exit code) is in alknet-tty (ADR-054). The runner policy (job management, log persistence, task graph integration) is a downstream crate's job, not in scope for alknet-tty. This OQ tracks whether a runner-policy crate (e.g., analknet-runnercrate that builds on the pipe mode + the wire format to provide job management) is needed, and what its API surface would be. The decision is deferred until a concrete use case forces it; the mechanism is preserved regardless. See ADR-054 andtty-local.md§"The Runner Pattern". - Cross-references: ADR-054, tty-local.md