Complete the UrlProtocol-to-UrlResolver transport chain after publication

Written: 2026-07-30 23:10 UTC.

RE-VERIFY: This is a write-time snapshot. Re-check all three pull requests, their head SHAs and checks, the current foundation.url:protocol metadata, and the review-fix branch before changing anything.

Mission summary

After the supervisor merges and publishes the UrlProtocol transport change, move UrlResolver PR 901 and stacked PR 900 to that exact protocol release, apply the verified accounting review fix to PR 900, and drive both full check suites green without merging them.

What was found and done

• UrlProtocol PR 457 was evicted from the merge queue and remains open. The separate blocker handoff carries the queue evidence.
• The artifact repository reported protocol 0.0.429 as latest; 0.0.430 through 0.0.433 were free at the probe time. PR 457 declares 0.0.430. Re-probe before relying on this.
• UrlResolver PR 901 needs exactly eight replacements of foundation.url:protocol:0.0.429.
• Its current kotlin.build run is exactly 99 passed / 1 failed, with testConcurrentRelayBackedOneMiBStreamPullsFitConstrainedHeap returning OUTBOX_FULL.
• Its current GitHub Actions run actually has two failures: the same OUTBOX_FULL failure and testNetlabDiscoveryScenarios, where provider-ljnat did not report a connected relay within 180000 ms. This contradicts the earlier description of the whole pull request as 99/1; that description applies only to kotlin.build.
• UrlResolver PR 900 needs exactly 18 replacements of foundation.url:protocol:0.0.429. It remains stacked on PR 901 and has no GitHub Actions run.
• Review-fix commit 9f014311003829246afb109e8f7fa38e7fdd1b31 on origin/lane-w/pr900-review is a direct child of PR 900's current head. It adds non-list Collection and object Array traversal to cumulative sandbox-result accounting.
• The two real public sandbox tests in that commit passed together, 2/2, under -Xmx512m.
• Test-comprehensiveness and adversarial review passes found no additional gap in that checkpoint. Existing tests cover limit acceptance, nested containers, repeated references, ByteArray leaf accounting, connection reuse, array component types, nulls, wrappers, nesting, varargs, and cycle rejection.
• No version update or review fix has been applied to either pull-request branch because the required transport coordinate is not published.

Relevant pull requests and refs

• UrlProtocol PR 457, write-time head 4510849637941ae23cee8d41107bc8d8c21cf281.
• UrlResolver PR 901, write-time head 02fafa6c66e4afa5f14fcd7fd55fa7eba31fcb6f.
• UrlResolver PR 900, write-time head f8fb3c01a451cd69678f386e7cc7aab84c193406.
• Verified review-fix branch: https://github.com/CodexCoder21Organization/UrlResolver/tree/lane-w/pr900-review at 9f014311003829246afb109e8f7fa38e7fdd1b31.
• Full evidence: PlanRepository findings branch at 12fbea4d7b341945c3292b41a53faed732a972db.

Next steps

1. Wait for the supervisor to merge PR 457 and publish the final coordinate.
2. Re-probe that exact coordinate and confirm it resolves.
3. Check PR 901 is still open, fetch and rebase its branch on latest origin/main, apply exactly eight version replacements, run the required tests, push with --force-with-lease, and drive both checks green. Classify any failure by exact signature; the old NetLab failure is distinct from OUTBOX_FULL.
4. Wait for the supervisor to merge PR 901.
5. Check PR 900 is still open. Apply review commit 9f014311003829246afb109e8f7fa38e7fdd1b31 and exactly 18 version replacements, retarget the pull request to main, fetch and rebase on latest origin/main, run the required tests, push with --force-with-lease, and drive the newly dispatched full suite green.
6. Re-run the test-comprehensiveness and adversarial review passes against the final rebased diffs before declaring either pull request merge-ready.

Reusable operational knowledge

• PR 900's GitHub Actions workflow does not dispatch while its base is PR 901's feature branch; retarget it only after PR 901 merges.
• Use read-only build watching here. The --to-merged watch path can enqueue pull requests and is outside Lane X authority.
• One evidence-based rerun is allowed only after a failure is positively classified as infrastructure. Do not change payloads, iteration counts, caps, concurrency, or timeouts.