alkdev/alkhttp
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(review 003): land the Unit-1 re-point; extend it to alkcall review 005 + 0.3.0

Browse Source 
Commits the re-point edits left uncommitted in the working tree
(5b62307's follow-through; alkcall review 005 verified these lines at
that tree), updated to the post-review-005 state:

- ADR-048 reconciliation note gains the 2026-09-04 update: alkcall
  review 005 remediated the landed mechanisms (serving-loop
  concurrency G-01/G-02, op/register collision policy G-03, spec
  round-trip G-04, bootstrap-list alignment G-05) and alkcall 0.3.0
  shipped them; alkhttp now consumes 0.3. The ADR-022 collision
  sub-amendment binds here: a peer-announced op never shadows the
  serving side's own registrations — the WS session's op/register
  handler gates on the session fork.
- OQ-05 resolution gains the same dated update and extends the
  cross-references to alkcall reviews 004-005.

What remains here is still alkhttp-side wiring only (review 003
Unit 2).
This commit is contained in:
glm-5.3-flash
2026-09-04 14:55:23 +00:00
parent 3dee46aead
commit df86f89440
2 changed files with 35 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/decisions/048-websocket-native-session-not-gateway.md
+21
View File
@@ -15,6 +15,27 @@ Accepted
> its rationale are recorded in
> [OQ-05](../open-questions.md); the native-session contract below
> stands as what the deferred wiring must satisfy.
>
> **Re-point (2026-09-03):** the two alkcall mechanisms this wiring
> composes on now exist. alkcall review 004 Units 1–3 landed the
> per-session fork as the dispatch registry (alkcall ADR-047 §4
> amendment #2), the full-duplex serving loop
> (`Dispatcher::serve_single_stream`, opt-in via
> `ChannelClient::from_connection_with_serving`), and the
> `op/register` bootstrap op (alkcall ADR-022 amendment 2026-09-03 —
> the bootstrap-op set each side may serve). The browser
> bidirectionality promise is no longer standing on unmechanized
> commitments: the deferred WS wiring (OQ-05, alkhttp review 003
> Unit 2) composes on those alkcall ADRs.
>
> **Updated (2026-09-04):** alkcall review 005 remediated the landed
> mechanisms (serving-loop concurrency, `op/register` collision
> policy, spec round-trip completeness) and alkcall 0.3.0 shipped
> them; alkhttp now consumes 0.3. The ADR-022 collision policy
> (2026-09-04 sub-amendment) binds here too: a peer-announced op may
> replace other peer-announced ops but never the serving side's own
> registrations — the WS session's `op/register` handler gates on the
> session fork.
## Status amendment (alkhttp port)