Files
alkssh/CHANGELOG.md
T
glm-5.3-flash 263f91fdb7 docs(architecture): review-pass cleanup — inconsistencies, stale refs, scaffolding refresh
- OQ-02: rewritten as a clean resolved statement; contradictory
  deferred-table row removed
- OQ-05: 'old-code anti-pattern' framing corrected — ephemeral-fleet
  accept-and-continue is a legitimate case-2 HostKeyPolicy; the crate
  rule is 'no hard-coded trust model', not 'accept-all forbidden';
  dangling 'expected ADR-007' pointer replaced with the real contract
  locations (auth.md, client.md)
- README: OQ counts corrected (6 resolved / 3 open / 4 deferred);
  sibling references normalized to real ADR IDs (alkcall 010 is alkhttp
  014's analog; 'ADR-016-analog' was a wrong number)
- client/auth: OQ-07 status corrected to resolved-at-adapter-level;
  TOFO typo; TOFU framing
- ADR-004: dangling 'ADR-008' -> serve-config defaults
- ADR-006: SOCKS5 typo
- mapping: alktty typo; '(OQ-… note below)' placeholder -> the real
  POC-3 note reference
- research: cross-repo numbers qualified (alktty OQ-44, alkvault
  ADR-021); reverse-runner lesson 5 reframed per correction
- scaffolding: Cargo.toml description/comments and src/lib.rs doc
  comment updated against ADR-002/003/006 (dynamic-forward retired,
  git exec-only, russh pin decided); CHANGELOG logs POC completion and
  ADRs 001-006

Verification: cargo test, cargo clippy --all-targets -- -D warnings,
cargo fmt --check, cargo check — all pass
2026-10-27 10:00:11 +00:00

36 lines
1.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Changelog
All notable changes to this crate are documented here. The format is
based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and
this crate adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
### Added
- Initialized: docs-only phase 0 base — SDD process (`docs/sdd_process.md`),
opencode agent definitions, rust crate manifest (lib only, no
dependencies yet), MIT OR Apache-2.0 licensing. The russh pin, the
capability feature graph, and the channel-type mapping table are
phase 0 research output (family ADR-003, OQ-08 remaining scope).
- Phase 0 research set under `docs/research/`: `vision.md` (scope
questions), `russh.md` (0.64.1-era inventory + pin considerations),
`auth-bridge.md` (fingerprint → identity server path; vault-backed
at-rest client key storage — the vault as secret store, not key
derivation), `mapping-table.md` (channel type/request → family seam
+ feature), `pocs.md` (POC-1..3 plan).
- Phase 0 completed — all three POCs passed against the current
published russh with vanilla tooling (121 checks total); findings
in `poc-1-auth-bridge.md` (31), `poc-2-vault-keys.md` (39),
`poc-3-mapping-bakeoff.md` (51, three mapping-table corrections
recorded), plus the reverse-runner client-direction extraction
(`reverse-runner.md`). POC source is disposable, never merged.
- Phase 1 architecture under `docs/architecture/`: the index +
open-questions tracker (OQ-01…13), the spec docs
(`overview.md`, `mapping.md`, `client.md`, `auth.md`), and ADRs
001–006 (Accepted) — the `alk/ssh` ALPN pin; the russh 0.65.0 pin
(aws-lc-rs, no compression, `rsa` off); the capability feature
graph (flat, two-direction, `dynamic-forward` retired); auth
dispositions; vault-key custody; and the mapping/dispatch
decisions (route-1 bridge, exec-only git, parse-only session
dispatch).