3 Commits

Include renames

Author	SHA1	Message	Date
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
glm-5.3-flash	04f48ab9bc	docs(research): client host-key policy resolved to a two-case policy seam ... - OQ-05 resolved: known-beforehand hosts (assembly-minted/family runners) -> pinned, hard-decline on mismatch; unknown-beforehand hosts (rental fleets) -> assembly-provided HostKeyPolicy the crate calls — prompt- record, provider-metadata match, or learn-and-record. Crate default stays fail-closed reject-unknown; crate never decides trust; storage of learned pins is assembly detail - auth-bridge.md: refinement postscript — no-TOFU is a no-trust-decisions- -in-crate rule, not pin-everything; alkminer's accept-all was the fleet- churn collapse, and the real anchor for ephemeral fleets is hub-held key material, not host pins - reverse-runner.md §5 rewritten with the same nuance	2026-10-26 12:04:41 +00:00
glm-5.3-flash	31207057ff	docs(research): phase 0 closed — pocs.md refreshed, reverse-runner pattern extracted ... - pocs.md: marked complete; corrected the stale 0.5x-era accept-defaults hypothesis wording (0.64.1: only auth_publickey_offered defaults to accept), stage D recorded as ran-in-full, completion gate updated with per-question resolution status - added client-side scope section: no dedicated POC needed (client API exercised throughout POC-1/POC-3) + the acceptor-default fact (russh client accept-and-drop for unhandled forwarded opens is ours to fix) - new reverse-runner.md: alkminer pattern extraction (concepts only, never code) — hub-dials-runner surface inventory, both tunnel legs, the OAI-proxy secret-hygiene shape, and the client-direction lessons (keepalive defaults, reconnect-restore, acceptor disposition) - vision.md: scope-question resolution addendum + whitespace typo fix	2026-10-26 06:09:38 +00:00