Handoff: Reconcile F725 verification with the rewritten UrlProtocol callback branch

Written 2026-10-20 17:27 UTC. RE-VERIFY: all heads and state below are a write-time snapshot. Re-check https://github.com/CodexCoder21Organization/UrlProtocol/pull/725 with gh pr view 725 --repo CodexCoder21Organization/UrlProtocol --json state,headRefOid,isDraft, and branch heads with git ls-remote origin refs/heads/wip/F725-work refs/heads/wip/F725-evidence refs/heads/wip/closewait3-work. No CI state was inspected in this lane.

Mission summary

The user asked: "Close the first-sender insertion window in UrlProtocol pull request 725 so its three red proofs pass, and fix the readiness wait in the queued-work replacement fixture". The lane was explicitly pinned to starting head 4d3cef0e174fcec63085a9f200142a427ad222d2, with no rebase, merge, CI watching or additional verification rounds. The initial OPEN/head check matched exactly. F725 completed every local proof gate, but the final original-branch push was rejected because another effort force-rewrote that branch during the lane. Gate 4 (update original branch and append the PR section) remains incomplete and needs reconciliation by the manager. The earlier TinySite handoff is context, not a claim that this lane completed that broader effort: https://github.com/CodexCoder21Organization/PlanRepository/blob/main/handoffs/2026-10-19-containernursery-peerregistry-stall-tinysite-publish-timeouts.md .

What was found and done

1. OBSERVED: initial head OPEN at 4d3cef0e174fcec63085a9f200142a427ad222d2. Fresh clone in assigned F725 directory. No repository AGENTS.md. Read README, required testing/philosophy sections, PR opening, handoff and proof branch messages. The supplied source-path hint was wrong: guards were in PeerRegistry.kt at 1667/2082, not Libp2pHostFactory.kt.
2. OBSERVED mechanism: sender insertion checked the delivering root, then called caller clock/getter code while no lifetime had yet been installed. Close/removal could complete through the absent-lifetime return, after which insertion resumed and published. All three unchanged proofs failed their intended assertions on attempts 1/2/3, nine failures total.
3. F725 product: move clock and peer merge/index preparation outside admission locks; validate the captured peer and lifetime plus delivering root under the mutation stripe; serialize absent removal with that stripe; discard only a preparation's own unchanged provisional record while membership remains absent. Retain the first-store peer subtype. The broader existing capacity-ranking getter hold remains required by the network-thread isolation proof; that ownership is not redesigned here.
4. J2 fixture: testReview725QueuedWorkKeepsItsDeliveringRootAcrossLiveReplacement now negotiates/closes a real ping child on each exact root before inspecting server connection membership. Successful child negotiation proves server registration completed; the client connect future alone does not. All original assertions, bounds and iteration counts remain.
5. OBSERVED final tested head 45b0f11868b89c65eff65be1512d83dc61800c5b: three proofs each passed five separate invocations on attempt 1 (15/15 native records); J2 passed all five invocations on attempt 1 (5/5); all five XMLs have zero attempt-history elements. Product-only reversal restored only PeerRegistry.kt and PeerObservationLog.kt to the starting head, kept tests, and failed each proof on attempts 1/2/3 at its intended assertion (9/9). Restored product SHA256 values match and tree is clean. One requested family invocation selected all 42 matching files and passed 42/42 attempt 1, zero failed build rules and zero histories. Dedicated test and code review passes found no further issue in this edited commit path. No extra suite or CI run was launched.
6. OBSERVED final push: re-check returned OPEN/draft at 8df095387fb3b6671ee30c86e95366964d775668. Normal push rejected non-fast-forward. Fetch explicitly reported a forced branch update. The rewritten history includes separate insertion/observation fixes and new proofs (plus current-main TCP server changes), so the F725 branch must not replace it. Neither implementation was merged or rebased by this lane. The current PR head was not tested here, and F725 results must never be described as verification of that newer head.
7. PR body NOT patched. Proposed append-only fourth-round text is preserved with evidence, but it claims the F725 exact head and must not be applied unchanged to the rewritten PR. Evidence and logs are remote; no expensive work needs recreation.

Relevant PRs / refs

Evidence entry point: https://github.com/CodexCoder21Organization/UrlProtocol/tree/wip/F725-evidence/forensics/F725 . Both worktrees are clean, there are no stashes or local-only commits. Build outputs and dependency caches were intentionally omitted. Nothing was deployed, restarted, published or merged; the lane's command history contains only local testing, GitHub read/push operations and this handoff.

Next steps

1. Re-verify current PR/head state first. Ask the manager which concurrent effort owns the rewritten branch. Do not force-push F725 or automatically integrate two different fixes.
2. Compare the newer implementation with F725. J2's readiness addition is the isolated 11-line test diff against the starting head and is absent from the newer branch in the observed comparison. Preserve the newer branch's additional proofs and fixes.
3. Agree the verification scope for any reconciled head before editing. Existing F725 counts apply only to 45b0f11868b89c65eff65be1512d83dc61800c5b. The initial brief prohibited rebase and additional rounds; do not silently treat newer-head work as authorized by old gates.
4. Once the manager resolves the head, finish original gate 4: keep PR OPEN/draft, normal-push the intended head, append a section retaining every prior section via REST PATCH and read it back. Do not merge, enqueue, mark ready, publish, deploy or watch CI.

Reusable / operational knowledge

Run locally with scripts/test.bash --local --test <name> --log <native.xml>. Runner retries are separate sibling attempt-history elements: success is attempt 1 only when there is no history. family-files.txt is the exact 42-file register; run-green.py spells out the five separate invocations. Native XML and compressed logs preserve all attempts and full stacks. The literal proof names and restoration manifest are in the evidence directory. The verified body append is fourth-round-section.md, explicitly unapplied. Final local tree remains at the tested F725 head; origin/wip/closewait3-work points to the rewritten head. No rebase was performed.