← Priority list

Resume UrlResolver race-fix landing campaign after PR 873 CI blocker

PR 873 is rebased and remote CI is green, but GitHub Actions twice failed on the linked persistent-RPC/NetLab stream-loss blocker; PRs 882, 866, and 827 remain untouched by strict ordering.

hf-2026-07-29-resume-urlresolver-race-fix-landing-campaign-after-pr-873-ci-blocker

Edit handoff

Title Summary Markdown body

**RE-VERIFY:** This is a snapshot from 2026-07-29 14:20 UTC. Re-check all linked pull requests and checks before continuing; GitHub and the Handoff dependency are authoritative.

## Mission summary

Resume the UrlResolver landing campaign in strict order: make https://github.com/CodexCoder21Organization/UrlResolver/pull/873 green, then PR 882, PR 866, the five-PR disposition analysis, and PR 827. Do not merge or deploy.

## What was found and done

PR 873 was rebased onto current main. Four branch commits replayed cleanly except for stale resolver-coordinate conflicts; current main's history was retained and the branch was allocated the live-free coordinate `foundation.url:resolver:0.0.712`. The branch was force-pushed with lease at `db8e5684645516e961ae205e5b776f38cd57fa11`.

Mechanism reviewed: pending-dial insertion and host close now share `admissionAccountingLock`. The decisive closed-host check, entry insertion, admission increment, and close snapshot use the same lock, so no entry can be inserted after the closed transition. Separate adversarial and test-comprehensiveness reviews found no branch defect or missing behavior case.

Local selected tests did not execute because the full source build failed first:

- kompile-cli 0.0.77 launched concurrent test compilers and was killed with exit 137 under shared-host memory pressure.
- kompile-cli 0.0.84 accepted the file selector but `foundation.url.resolver.buildMaven()` hit its fixed 20-minute build-script limit; XML recorded test duration 0.

Fresh remote CI run `d8ecf7aa` passed all 100 tests. GitHub Actions failed twice with 1,228/1,230 tests passing each time because of the linked shared persistent-RPC/NetLab blocker. No second rerun was requested after the repeated mechanism.

The detailed incremental report remains at:
`/tmp/claude-1000/-code/45c86b11-0eaa-43f0-b633-08f46bf17ae9/scratchpad/out/w8-report.md`

## Relevant PRs and refs

- Active PR: https://github.com/CodexCoder21Organization/UrlResolver/pull/873
- Remote branch: https://github.com/CodexCoder21Organization/UrlResolver/tree/fix/shutdown-dial-admission-flake
- Verified local and remote head: `db8e5684645516e961ae205e5b776f38cd57fa11`
- First failed Actions job: https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/30449647043/job/90568376677
- Rerun job: https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/30449647043/job/90584133603
- Next, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/882
- Then, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/866
- Last assigned fix, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/827
- Separately owned and untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/893 and https://github.com/CodexCoder21Organization/UrlResolver/pull/892

## Next steps

1. Resolve the linked persistent-RPC/NetLab blocker.
2. Re-run only PR 873's failed GitHub Actions job and re-arm build-watchman. Confirm both required checks are successful on head `db8e56846`.
3. Only after PR 873 is green, begin PR 882: inspect failed logs first, state mechanism and evidence, rebase, test, allocate a fresh coordinate immediately before push, review, push, and watch.
4. Repeat for PR 866.
5. Only after PR 866 is green, compare PRs 870, 863, 874, 737, and 804 for unique behavior/tests and write disposition recommendations without closing them.
6. Then handle PR 827, reusing the hermetic onboarding tests only where equivalent coverage is absent.
7. Do not merge, deploy, restart services, touch PR 885, or have more than one lane-owned UrlResolver CI run active.

## Reusable operational knowledge

Main was `0.0.701` at the final PR 873 push. PR 893 claimed `0.0.711`, so PR 873 used `0.0.712`. Coordinates move quickly and must be rescanned before every later push. The local checkout was clean with no stash or local-only commit; `git ls-remote` matched the local head exactly.

Add dependency

Complete this handoff

Moves it out of every priority list and into ArchiveArea.

Handoff document

Markdown

RE-VERIFY: This is a snapshot from 2026-07-29 14:20 UTC. Re-check all linked pull requests and checks before continuing; GitHub and the Handoff dependency are authoritative.

Mission summary

What was found and done

PR 873 was rebased onto current main. Four branch commits replayed cleanly except for stale resolver-coordinate conflicts; current main's history was retained and the branch was allocated the live-free coordinate foundation.url:resolver:0.0.712. The branch was force-pushed with lease at db8e5684645516e961ae205e5b776f38cd57fa11.

Mechanism reviewed: pending-dial insertion and host close now share admissionAccountingLock. The decisive closed-host check, entry insertion, admission increment, and close snapshot use the same lock, so no entry can be inserted after the closed transition. Separate adversarial and test-comprehensiveness reviews found no branch defect or missing behavior case.

Local selected tests did not execute because the full source build failed first:

kompile-cli 0.0.77 launched concurrent test compilers and was killed with exit 137 under shared-host memory pressure.
kompile-cli 0.0.84 accepted the file selector but foundation.url.resolver.buildMaven() hit its fixed 20-minute build-script limit; XML recorded test duration 0.

Fresh remote CI run d8ecf7aa passed all 100 tests. GitHub Actions failed twice with 1,228/1,230 tests passing each time because of the linked shared persistent-RPC/NetLab blocker. No second rerun was requested after the repeated mechanism.

The detailed incremental report remains at: /tmp/claude-1000/-code/45c86b11-0eaa-43f0-b633-08f46bf17ae9/scratchpad/out/w8-report.md

Relevant PRs and refs

Active PR: https://github.com/CodexCoder21Organization/UrlResolver/pull/873
Remote branch: https://github.com/CodexCoder21Organization/UrlResolver/tree/fix/shutdown-dial-admission-flake
Verified local and remote head: db8e5684645516e961ae205e5b776f38cd57fa11
First failed Actions job: https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/30449647043/job/90568376677
Rerun job: https://github.com/CodexCoder21Organization/UrlResolver/actions/runs/30449647043/job/90584133603
Next, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/882
Then, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/866
Last assigned fix, untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/827
Separately owned and untouched: https://github.com/CodexCoder21Organization/UrlResolver/pull/893 and https://github.com/CodexCoder21Organization/UrlResolver/pull/892

Next steps

Resolve the linked persistent-RPC/NetLab blocker.
Re-run only PR 873's failed GitHub Actions job and re-arm build-watchman. Confirm both required checks are successful on head db8e56846.
Only after PR 873 is green, begin PR 882: inspect failed logs first, state mechanism and evidence, rebase, test, allocate a fresh coordinate immediately before push, review, push, and watch.
Repeat for PR 866.
Only after PR 866 is green, compare PRs 870, 863, 874, 737, and 804 for unique behavior/tests and write disposition recommendations without closing them.
Then handle PR 827, reusing the hermetic onboarding tests only where equivalent coverage is absent.
Do not merge, deploy, restart services, touch PR 885, or have more than one lane-owned UrlResolver CI run active.

Reusable operational knowledge

Main was 0.0.701 at the final PR 873 push. PR 893 claimed 0.0.711, so PR 873 used 0.0.712. Coordinates move quickly and must be rescanned before every later push. The local checkout was clean with no stash or local-only commit; git ls-remote matched the local head exactly.