B16d checkpoint, 2026-10-21 03:55 UTC

RE-VERIFY: 2026-10-21 03:55 UTC. PR https://github.com/CodexCoder21Organization/UrlResolver/pull/1336 is OPEN and now at baf8dbcc20c56fe838a7adb3321a683cfb186da9 (lease-protected push over 89542f8dd), rebased on main 62495b692; PR body replaced. Source branch: https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/laneB16d-finish-1336. Evidence: https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/laneB16d-final-evidence/.laneB16d. Not merged, not enqueued, CI not watched or re-requested.

Remaining work

1. Orchestrator: independent reviews (test comprehensiveness, correctness) of head baf8dbcc2, CI on the pushed head, then the merge decision.
2. Main defect, separate lane: testActiveQueryRetainsConfiguredAddressAfterProviderRestart fails at line 126 on main too (3/16 first attempts on main 62495b692, 1/16 on the PR head, XML in .laneB16d/restart-classification). Likely the query client's independent relay registration dial (unverified).
3. Follow-up risk: temporary (gossip/peer exchange) and relay-host openers still give a replacement dial a discovery window; a peer resolver's RPC child reset there can still retire the peer's side under I1. Needs a distinguishable admission signal.

Done in B16d

• testSandboxedObjectReleasesResourcesAfterReconnect history explained: an independent relay registration pass dials its own connection to the scenario's target during the setup-error phase; the target resets that relay stream; per I1 a control stream never marks a connection, so nothing closes it and the close wait at line 189 times out. Fixture commit "Hold independent registration in the sandbox resource scenario" (8 lines, no assertion/count/bound/timeout change). Evidence: 100-cycle copies red 4 then 6/6 attempts, deterministic ordering copy red 6/6, held copies 6/6 clean (https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/laneB16d-release-observation/.b16d). Test alone 10/10 first attempts.
• Genuine reconnect interaction fixed at source: replacement dials for RPC openers that admit the peer's streams are no longer discovery-only (commit "Admit a peer's streams on a reconnect connection opened for an RPC child"); new scenario testReconnectConnectionAcceptsStreamsFromItsPeer red 3/3 attempts on f907e004f, 3/3 invocations clean after.
• Gate: 47-case set x5 = 235/235 first attempts. Complete suite on baf8dbcc2: 2265 cases, 2264 first-attempt passes, one history (the provider-restart case above, classified as reproducing on main).