- OQ-10's seed overstated alktty's exit-chunk design as a 'signal-identity
gap': the negative code is the documented signal encoding (alktty ADR-004,
ported from alknet ADR-055; src/local/pipe.rs::exit_code_from — Unix
ExitStatus::signal() → -sig), a tty/pty-grounded convention
- 'alktty widens the chunk' demoted from co-equal candidate to gated
exception: it would widen ControlMessage::Exit's one-way parsed shape,
the backend-wide exit_code API, and the alknet ADR-055 lineage — requires
an alktty ADR with explicit tty/pty-grounded justification, never an
alkssh convenience ask
- OQ-10 re-scoped to the real remaining detail: −1 (wait failure vs SIGHUP)
collision, core-dumped disposition, non-Unix semantics, name derivation
- correction notes added in place: poc-3 §D.2, pocs.md, mapping-table.md
(both rows); mapping.md exit_signal row updated
Verification: cargo doc --no-deps (docs-only change)
Phase 1 (architecture) — in progress. Phase 0 is closed: all three
POCs passed (121 checks; docs/research/poc-{1,2,3}-*.md) and the
research docs record their corrections. The ADR set (001–006) is
Accepted — including the post-review amendments (ADR-002's
ed25519-only revert; ADR-003/006's dynamic-forward retirement) — and
the four spec docs (overview/mapping/client/auth) are drafted; the
architecture review pass is next, after which specs go to reviewed.
Tracked in open-questions.md — OQ-01 … OQ-13,
seeded from the phase 0 POC findings and research docs. Six resolved
(OQ-02/03/05/06/07/12), three open (OQ-08/10/11 — mapping-detail
decisions in the current review pass), four deferred with named
blockers (OQ-01/04/09/13).
Document Lifecycle
Status
Meaning
Transitions
draft
Under active development; may change significantly
→ reviewed when its open questions are resolved
reviewed
Final; implementation may begin; changes require review
→ stable when implementation is complete and verified
stable
Locked; changes require review and may warrant an ADR
glm-5.3-flash
9217a8b3cf