docs(review 007): mark R-01/R-02/R-03 resolved; record the two sketch deviations

Status → Resolved with the three unit commits; both deviations from
the review's sketches (typed-opaque ChannelPlan over Option<Value>;
(u64, u64) over io::Result) recorded up top with their rationale, as
the ADRs carry them.

docs/reviews/007-establishment-follow-ups-review.md

@@ -2,6 +2,20 @@
 
 ## Status
 
+Resolved — all three units landed in alkcall 0.6.0 (2026-09-07):
+Unit 1 `dc4ad2b` (R-01 + R-02's doc notes), Unit 2 `8f122b0` (R-02's
+telemetry), Unit 3 `9c6fec1` (R-03 + ADR-050). Two deviations from
+the sketches below, both recorded in the ADRs: (1) R-01's plan is
+**typed-opaque** (`ChannelPlan = Arc<dyn Any + Send + Sync>`), not
+`Option<Value>` — the sketch could not satisfy this review's own
+verification gate, because the payloads establishers hand off are
+live handles (dialed sockets, TTY handles) with no JSON
+representation; (2) R-03's helper returns `(u64, u64)`, not
+`io::Result<(u64, u64)>` — both pumps swallow copy errors by the
+ADR-078 contract (mid-stream error = abrupt close), so an `Err` state
+would be dead code. Original findings below, retained as filed
+(verified against tree `36e74cd`, 0.5.0).
+
 Open — findings filed from the alktunnels UDP POC pass
 (`alktunnels-udp-poc`, 2026-09-06; summary at
 `/workspace/@alkdev/alktunnels/docs/research/poc-summary.md`). This
@@ -15,6 +29,10 @@ working code against 0.5.0 and finding the shape insufficient.
 Findings continue the review numbering with prefix `R` (001–006 used
 P/C/R/A/B/C/D/F/G/E — each review numbers independently).
 
+> **Post-remediation note (2026-09-07):** the "Open —" paragraph
+> above is the original filing state, retained for the record. All
+> units landed; see Status above and ADR-049 amendment 2 + ADR-050.
+
 ## Scope
 
 The ADR-049 establishment surface (`OpenEstablisher`, `Establishment`,