Objective

Complete the transport chain after the UrlProtocol keystone merges and is published, then bring both dependent UrlResolver pull requests to green and report them merge-ready.

Current blocker

The keystone https://github.com/CodexCoder21Organization/UrlProtocol/pull/457 was evicted from its third merge-queue attempt. The supervisor owns enqueue, merge, and publication actions. No downstream edit is allowed until it merges and the supervisor confirms publication.

Dependent 1

• Pull request: https://github.com/CodexCoder21Organization/UrlResolver/pull/901
• Live head: 02fafa6c66e4afa5f14fcd7fd55fa7eba31fcb6f
• Base: main
• Required edit after publication: exactly 8 replacements of foundation.url:protocol:0.0.429 with the confirmed published coordinate.
• Before pushing: fetch and rebase on latest origin/main, run the complete suite with -Xmx512m and one test invocation at a time, then push with --force-with-lease.
• Prior failures:
  • The remote run's sole visible failure was testConcurrentRelayBackedOneMiBStreamPullsFitConstrainedHeap, where __stream_pull returned OUTBOX_FULL after the handler completed. This matches the keystone's transport defect.
  • GitHub Actions also had testNetlabDiscoveryScenarios, where provider-ljnat did not acquire a relay reservation within the existing 180000 ms budget and runner reporting emitted an InvalidClassException serialVersionUID mismatch. Classify this separately if it recurs.

Dependent 2

• Pull request: https://github.com/CodexCoder21Organization/UrlResolver/pull/900
• Live head: f8fb3c01a451cd69678f386e7cc7aab84c193406
• Current base: dependent 1 branch fix/sjvm-collection-return-jvmresult-exception
• Required edit after publication: exactly 18 replacements of foundation.url:protocol:0.0.429 with the confirmed published coordinate.
• Review fix to apply: remote commit 9f014311003829246afb109e8f7fa38e7fdd1b31, whose parent is exactly the current head.
• After dependent 1 merges: retarget this pull request to main, rebase, push, and run the full suite. Its GitHub Actions suite does not dispatch while the base is a feature branch.

Review findings already verified

Commit 9f014311003829246afb109e8f7fa38e7fdd1b31 adds cumulative preflight traversal for non-List Collection values and object arrays. Conversion already recursively handles Map, List, Collection, object Array, JSONObject, and JSONArray, with ByteArray as a leaf. The added tests use the public sandbox connection and cover the two missing container types.

Existing tests cover cumulative Map/List and JSONObject/JSONArray accounting, large ByteArray leaf accounting, repeated sibling references, default and configured limits, exact rejection text, rejection before sandbox allocation, and continued connection use after rejection. The object-array matrix covers heterogeneous Object arrays, declared String arrays, nulls, boxed primitives, varargs, nested arrays/lists, Collection.toArray, and cyclic-array rejection. No further gap was found in the preliminary test-comprehensiveness or adversarial review.

Work not performed

No version replacements were made, the review fix was not cherry-picked, no branch was pushed, no pull request was retargeted, and no publication coordinate was selected or probed. This preserves the required order after the keystone eviction.

Required order

1. Supervisor re-queues and merges the keystone.
2. Supervisor publishes a newly probed free coordinate and confirms publication.
3. Update, rebase, push, test, and review dependent 1 until green.
4. Supervisor merges dependent 1.
5. Apply the review fix and version replacements to dependent 2, retarget to main, rebase, push, test, and review until green.