- OQ-10 resolved: alkssh derives SSH exit-signal from the alktty exit
chunk's negative code (−N = signal N, pipe path) server-side; −1
(alktty's could-not-determine sentinel) → exit-status(255), never a
signal claim; core_dumped never asserted in v1; no alktty wire change
- new verified backend finding recorded: portable-pty 0.9 reduces
PTY-mode signal termination to a plain exit code 1 (signal number
unrecoverable through its trait surface) — faithful exit-signal on
the PTY row is an alktty/portable-pty upstream ask, not an alkssh one
- research docs (poc-3 §D.2, pocs.md, mapping-table rows) restated
accurately instead of carrying inline correction scaffolding
Verification: cargo doc --no-deps earlier this session (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
1a40bfb498