Finish exact-head verification of the UrlResolver rebase

Written: 2026-10-22 13:57:03 UTC.

RE-VERIFY: All state is a snapshot. Check https://github.com/CodexCoder21Organization/UrlResolver/pull/1163 and the two exact Actions run links below before acting. S102 is independently making follow-on source fixes from the rebased head; never overwrite its work with the old rebase branch.

Design decisions in force

S99's 2026-10-22 brief says: "No source/test changes beyond the rebase. Do not merge or enqueue. Time box 1.5 h." It also requires dropping copied commits from the merged dependency PR, preserving this PR's own patches, checking UrlProtocol pins, and exact-head full-suite verification through bld-build.

Mission and remaining work

The rebase itself is complete and pushed. Its exact-head Actions run has not supplied a full-suite result yet. Observe that existing run and attribute every failed first attempt; report its result separately from other same-name checks attached to the same commit. Preserve S102's follow-on work and coordinate with its owner before requesting any additional run.

What was found and done

Live main at the rebase was e3ae7694aa622f24393b5067da5f185aa09816d6, the squash merge of https://github.com/CodexCoder21Organization/UrlResolver/pull/1424. The original PR head was b9eb0112622e0fca94881ea3191c83604820116b. Dropped exactly four copied commits (4a53dafe248dbf1aa09fe2c5bd2e0420f6684c63, 805ab7f53fe7df201a13ad16e259562e87ceefe1, c46a3d890d9212ad7da7a351b3ae75f7703fbd34, 2c334bb18294d23926cbe15ae6db53a89b4289cb) with git rebase --onto origin/main 2c334bb18294d23926cbe15ae6db53a89b4289cb. All 124 own commits replayed without conflicts. Range-diff has 124 '=' rows and no changed, missing, or extra own commit. Both tracked file trees have ID e80f8aa5e47b46d03aa88f66f542714390f8fd5e. The two named relay fixtures match main exactly. Rebase head: 7410411995f6f18a87bc142da12234e1e791944f. Confirmed OPEN before explicit force-with-lease push and verified remote SHA.

The version audit found 57 active old test declarations introduced by the PR's own patches: 52 at 0.0.551, three at 0.0.1428, one at 0.0.1429, one at 0.0.1421. The production build and 2264 inherited/current test declarations use 0.0.1431. Historical comments and a scout outside tests also mention old coordinates. Updating the 57 declarations would change own patches and violate rebase-only scope; no such edits were made. User was asked about that scope conflict, without a reply. Findings list every active stale declaration.

Only bld-build is required by the branch rules. The workflow builds with --local-and-remote and runs the full suite with scripts/test.bash --local-and-remote --test . --log test_log_file.xml, uploading test-attempt-records. No local build/test was launched by S99.

Original exact-head run: https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/39780336730, branch wip/urlfix3-handoff-2026-10-02b, created 12:40:50 UTC. Its Build with kompile step started 12:41:08 UTC. Last observed state is recorded in the final lane findings. The PR later advanced under S102; this historical run cannot certify its newer head.

A later run on the same commit, https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/39782450851, belongs to wip/s102-failfirst, not the original branch run. It failed before compilation: java.net.SocketException (Connection reset) fetching https://kotlin.directory/kompile/cli/kompile-cli/0.0.124/kompile-cli-0.0.124.pom, followed by missing kompile.cli.CliKt. No test ran. build-watchman 0.0.21 plain PR mode selected this later bld-build and exited RED; that is the commit-level check outcome and must not be reported as the original run's test result. The original run was then watched directly with bounded gh run watch --exit-status --interval 60. No run was rerun or cancelled by S99.

Prior comparison run https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/39768421406 passed 2523/2523 tests on the identical original tree. Its losing remote race failed provisioning after createDropletAsync transport EOF, while the runner side passed. This is comparison evidence only and does not replace exact-new-head verification. Most recent main run https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/39772730200 succeeded before the later download failure; no claim is made that main reproduced that later failure.

The broad handoff referenced by common.md, url://handoff/handoffs/hf-2026-10-14-land-the-urlresolver-extreme-condition-bug-fixes-fix-the-two-merge-queue-flakes-then-merge-the-reviewed-prs-and-finish-the-rest, was already completed at 2026-10-21T06:53:03.522Z. Initial reads failed on transport; a later read succeeded and the full body was read. Status-report writes were rejected because it is archived. It was not reopened.

Process error: report-challenge auto-merged two PlanRepository reporting PRs despite the no-merge rule: https://github.com/CodexCoder21Organization/PlanRepository/pull/11161 and https://github.com/CodexCoder21Organization/PlanRepository/pull/11168. Disclosed to the user and recorded in findings; do not repeat the mutating reporter command under this brief. No UrlResolver merge or queue operation occurred.

Remote refs and unmerged work

Nothing from S99 was deployed or published. No source/test edit beyond the rebase. Existing test edits: none.

Next steps

1. Re-verify the live PR head and S102's work. Do not push the old rebase over a later head.
2. Observe the existing original Actions run; use an exact-run tracked watcher because another branch on the same commit can contribute a later bld-build. Bound the watch and end it on every terminal outcome.
3. When complete, fetch its full logs and test-attempt-records. Report tests passed/failed and attribute failed first attempts. If no tests ran, say so; do not treat a toolchain download failure as a regression test.
4. Keep the 57 old declarations explicit in the audit. Changing them requires scope clarification and coordination with the follow-on owner.
5. Report exact head, 124 unchanged patches / zero conflicts / four copied commits dropped, full-suite outcome and attribution. Do not merge, enqueue, publish, deploy, raise timeouts, weaken tests, or run mutating challenge-report automation.

Follow-on snapshot discovered during S99 verification

At 13:37 UTC the PR was OPEN at ca1c690ba9aee2be9a71412940e7232dc86121ce. S102 rebased onto newer main 8c1e8742355075bb3ec3c726ccab32fcd6c76488 and added eleven commits. A second range-diff confirms all 124 patches from S99 remain unchanged, with zero changed/dropped patches. This later head has 65 active older test declarations: the original 57, six added by newer main, and two added by S102. Current-head source/CI is owned by S102; S99 has not overwritten it.

Original pre-rebase history is also preserved at https://github.com/CodexCoder21Organization/UrlResolver/tree/wip/s99-original-1163-b9eb011262 (head b9eb0112622e0fca94881ea3191c83604820116b). Rebase-only head 7410411995f6f18a87bc142da12234e1e791944f is an ancestor of the dedicated evidence branch, so both complete ranges remain recoverable.

Final lane snapshot

Observed 2026-10-22 13:57:03 UTC: original run 39780336730 status=in_progress, conclusion=(none). Its full-suite step has not started; bld-build is still in Build with kompile. S99 cannot report a passing full suite or attribute an original-run test failure when none has been published. The later source head is ca1c690ba9aee2be9a71412940e7232dc86121ce. Older test declarations remain unresolved under the strict rebase-only scope (57 on S99 head, 65 on the later snapshot). No replacement run was requested.