glm-5.3-flash
cb553ea033
The ask ledger's two alktunnels items landed 2026-09-18/20 — superseded in shape, not implemented as posed. The graduation (alktunnels tunnels-graduation.md -> ADRs 007/008) adopted the ssh forwarded-tcpip-shaped alternative over the per-ask carriers. phase-0.md: - settled-foundations: establishment gains the reply-projection note (ADR-049 amendment 3); the relay/hub note records the in-tree ChannelRelay/HubLegTemplate (ADR-051); identity-seam note marked current at 0.8.0 - OQ-SK-01: Option A updated — the direct op (channels/tunnel/direct, ADR-007) is the dynamic-target channel; POC #5's scope-gate + ADR-007 rationale point the same way (separation lives at the ACL) - OQ-SK-03: composed egress's vehicle is open_direct + Substrate::Udp; the ~0.8 ms measurement carries over; the stale POC-candidate hunch paragraph updated - OQ-SK-08: the landed note — ask #1 dissolved (bind-first establisher; the real bound rides the open reply; POC #5's open-rides-the-accept workaround + the 10s-bound finding retire), ask #2 landed at the wire's native moment (forwarded op's {listen, substrate, peer} params), correlation token per ADR-008 Amendment 1 - convergence: egress seam composes against 0.2.0; the upstream-asks bullet records the landing per crate; the BIND hand-off bullet notes variant 2 is now fully vanilla-fidelity - checklist OQ-SK-08 item + POC #5 register entry point at the landed note poc-bind-findings.md: ledger statuses appended (superseded in shape; evidence stands as the alktunnels-0.1.0 record) AGENTS.md: alkcall pin 0.7.1 -> 0.8.0 (reply projection noted); architecture context: alktunnels v0.2.0 entry added, alkcall 0.8.0 surface listed Verified against the repos: alkcall 0.8.0 changelog (U-1/U-2/ADR-051), alktunnels 0.2.0 changelog + ADR-007/008 + exports (bindfirst_establisher producer.rs:641, register_tunnel_bindfirst_ openable :924), fast-socks5 still 1.0.0 with no net feature (the courtesy tail). Docs-only change; no build surface affected.