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

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).

docs/architecture/decisions/048-websocket-native-session-not-gateway.md

@@ -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)
 

docs/architecture/open-questions.md

@@ -99,10 +99,22 @@ with their resolutions; new alkhttp OQs start at OQ-01.
 - **Resolution**: (pending — v1 cut recorded 2026-08-29 in ADR-067 and
   ADR-048; the recently landed WS robustness work — idle-read timeout,
   session caps/eviction, pump consolidation — is the foundation the
-  deferred work builds on)
+  deferred work builds on. **2026-09-03**: the alkcall mechanisms this
+  wiring composes on landed — alkcall review 004 Units 1–3: the
+  per-session fork as dispatch registry (alkcall ADR-047 §4 amendment
+  #2), the opt-in connect-side serving loop
+  (`Dispatcher::serve_single_stream`), and the `op/register` bootstrap
+  op (alkcall ADR-022 amendment 2026-09-03). **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. What remains here is alkhttp-side wiring only — alkhttp review
+  003 Unit 2.)
 - **Cross-references**: [ADR-067](decisions/067-websocket-carries-channels.md),
   [ADR-048](decisions/048-websocket-native-session-not-gateway.md),
-  [websocket.md](websocket.md), tasks/websocket/review-001-ws-data-channel-decision.md
+  [websocket.md](websocket.md), tasks/websocket/review-001-ws-data-channel-decision.md,
+  alkcall reviews 004–005 (`alkcall/docs/reviews/004-per-connection-dispatch-and-client-serving-review.md`,
+  `alkcall/docs/reviews/005-serving-loop-concurrency-and-op-register-review.md`)
 
 ## Resolved (ported)