glm-5.3-flash
069350bd51
Four corrections from discussion: - ALPN prefix: alknet/ -> alk/ swap happened in alkcall v0.1.1; docs must not perpetuate the old prefix (consumers would bake it in) - XY problem: except in the -D/dynamic composition case, params only identify a produced resource + substrate discriminator (tcp/udp/ extensible); the producer owns where the resource comes from (most likely a local port); UDP must be structurally supported even though TCP dominates expected use - self-contained JSON open-op object accepted as the params path (alktty NegotiateRequest precedent) - russh has no UDP channel support at all — no direct-udp prior art; noted in OQ-TN-02 and the survey list; SOCKS5 relevance scoped to the -D composition path Residue for OQ-TN-01: resource naming shape, discovery mechanism, exact JSON layout (Phase 1 ADR before first consumer).