Claude
eea746a635
5/5 sweep BUILD SUCCESSFUL post-merge of `origin/main` (5 `:quic`
commits: ALPN-list threading `2a4c07ae`, PTO STREAM retransmits
`d5c854be`, RFC 9001 §6 1-RTT key update `b622d0c9`, multiconnect
pacing `86a4727e`, qlog flush `31d19258`). Pre-merge baseline on
the same branch with the same TRACE capture: 3 fail / 5,
all in `late_join_listener_still_decodes_tail`. 55/55 tests pass.
Updated:
- routing-investigation: marked CLOSED, added Closure section with
pre-merge vs post-merge sweep counts + sample 1.6 ms-RTT
late-join trace.
- late-join investigation: marked closed.
- closure-roadmap: Priority 1 ✅; Priorities 2 and 3 unblocked.
Preserved a post-merge passing late-join relay trace under
`nestsClient/plans/artefacts/2026-05-07-routing-race-closed-by-merge/`
as the "what healthy looks like" baseline.
5.3 KiB
T16 closure roadmap — full coverage with correct behaviours
Goal state. Every spec'd cross-stack scenario green in suite-mode sweeps, asserting its full design intent (no soft-passes, no vacuous threshold loosening), with CI gating live and stable.
Where we are. The merged claude/cross-stack-interop-test-XAbYB
branch ships 22 of 23 spec'd scenarios; each passes individually.
Suite-mode runs hit a residual moq-relay 0.10.x routing race on a
specific subset (~40-60% flake rate). Five scenarios soft-pass the
listener side as a known-flake mitigation. CI is intentionally
unwired pending stability.
This roadmap takes the suite from "passes individually" to "passes in suite + CI" through three sequential plans. None should be parallelized — each unblocks the next.
Priority 1 — 2026-05-07-moq-relay-routing-investigation.md ✅ CLOSED
Closed 2026-05-07 by merging
origin/main(five:quiccommits:2a4c07ae,d5c854be,b622d0c9,86a4727e,31d19258). The flake was a:quicpacket-acceptance bug, not a moq-relay routing race. Step 1 trace capture in this branch first disproved the moq-relay-routing hypothesis (relay correctly forwards the upstream SUBSCRIBE); the QUIC team's separate work landed in main between the merge base and pickup and incidentally closed the speaker-side post-handshake bidi drop.
What landed.
- A 5-commit merge from
origin/maincarrying ALPN-list threading, PTO STREAM retransmits, RFC 9001 §6 1-RTT key update, multiconnect/multiplex pacing, and qlog flush. - Per-test moq-relay TRACE capture instrumentation
(commit
d7f87971) — kept in place; useful for follow-up regression triage. - Cross-stack trace artefacts preserved at
nestsClient/plans/artefacts/2026-05-07-routing-race-disproven/for post-mortem reference.
Acceptance bar met. 5/5 sweep BUILD SUCCESSFUL on HangInteropTest with their current soft-pass assertions intact. 55/55 tests pass.
Priority 2 — 2026-05-07-tighten-cross-stack-assertions.md
Why second. Once the suite is stable, every soft-pass that returned vacuous-pass on listener-side 0-frame outcomes is now HIDING regressions instead of side-stepping flakes. Replace each with a hard floor.
What lands.
- Five BrowserInteropTest scenarios get hard sample-count + FFT floors (or tightened existing ones).
- Gap matrix updated to reflect hard-pass coverage.
Acceptance bar. 5/5 sweep AGAIN, this time with hard assertions. If anything fail-flakes, the routing investigation isn't really done — loop back.
Priority 3 — 2026-05-07-cross-stack-interop-ci-gating.md
Why third. Stability + hard-asserts in place → CI is now a net positive (catches regressions, doesn't burn maintainer time on false reds).
What lands.
- Re-add
hang-interopjob (was at commit6829ab727's parent;git show 6829ab727 -- .github/workflows/build.ymlreverse gives the exact diff). - Re-add
browser-interopjob (same pattern, plus bun + Playwright caches). - Documentation update across the results plan + gap matrix.
Acceptance bar. 10/10 sweep before merge; ≥ 95% CI green rate over the first 2 weeks. If lower, the upstream race isn't fully closed — pull the jobs.
Independent track — 2026-05-07-framespergroup-production-rerun.md
This one doesn't block the closure roadmap. It can run any time after Priority 1 is done; it settles whether the test pin (5) and production default (50) can converge, or whether they must remain different. Either outcome is shippable.
What lands.
- Logcat data from a fresh two-phone field test against current
nostrnests production at multiple
framesPerGroupvalues. - A data-driven decision on whether to change the production default, the test pin, or neither.
Why it's parallelizable. Doesn't gate the test suite or CI;
it gates a one-line code change to NestMoqLiteBroadcaster's
default constant.
After all four close — what remains
Two open items, both genuinely upstream:
-
I7 post-reconnect listener cliff —
2026-05-07-i7-post-reconnect-cliff-investigation.md. The I7 reverse scenario passes its 2.5 s threshold but a regression test of "all post-reconnect data arrives" would require the moq-relay 0.10.x per-broadcast forward queue fix. Same upstream class as the routing race. -
I12 GOAWAY — only re-emerges if an IETF moq-transport target lands (currently moq-lite-03 only). Tracked in
2026-05-06-cross-stack-interop-test-results.md.
Beyond those: T16 reaches "full coverage with correct behaviours" when this roadmap closes.
Estimated wallclock
- Priority 1: 1–2 days (depends on whether upstream version bump fixes it, or we have to file + wait for upstream).
- Priority 2: 0.5 day (mechanical replacement of soft-passes with floors, plus rerun verification).
- Priority 3: 0.5 day (re-add CI jobs, run the 10× sweep, merge).
- Independent track (framesPerGroup): 0.5 day (needs prod-rig access).
Total: 2.5–3.5 days of focused work to take T16 from "infra shipped" to "fully closed".
Plan files
2026-05-07-moq-relay-routing-investigation.md2026-05-07-tighten-cross-stack-assertions.md2026-05-07-cross-stack-interop-ci-gating.md2026-05-07-framespergroup-production-rerun.md- (this file)
2026-05-07-t16-closure-roadmap.md