Handoff: Observe the remaining C22i required CI verdict

Written: 2026-10-22 00:40 UTC

RE-VERIFY: This is a write-time snapshot. Read current PR state and checks before acting with gh pr view https://github.com/CodexCoder21Organization/UrlProtocol/pull/807 --json state,headRefOid,statusCheckRollup.

Design requirements (2026-10-21)

• New separate PR off main; do not update https://github.com/CodexCoder21Organization/UrlProtocol/pull/759 . Rebase this lane's branch once that earlier PR lands.
• No merge, queue entry, publication, deployment, or production restart.
• No lane evidence in the product PR branch; evidence goes to wip/laneC22i-evidence.
• Never call accessors (cause, suppressed, message, stackTrace) on a caller-supplied Throwable; unchanged main tests remain the specification. Do not weaken or delete an existing assertion, increase a timeout, or reduce iterations.

Mission summary

The owner reported that https://droplets.wasmserver.com/ "is super unreliable, frequently rendering various errors/notices due to bugs in UrlResolver or UrlProtocol or something else" and asked for the underlying root cause to be fixed. Fresh review of the earlier PR found an unchanged atomic-write helper losing its earlier move IOException when deleting the temporary record then reports an Error. The requested small correction and permanent public reproducer are implemented and fully verified locally. Only the required CI test verdict and its final reporting remain.

Findings and completed work

1. The helper prepared a PeerPersistenceException after atomicMove reported an IOException, but caught only Exception around temporary-record cleanup. A cleanup Error left the helper before the earlier report was retained. The copied public saveAll reproducer was unsuccessful on attempt 1 and all three runner attempts on unchanged main.
2. Added three production lines: catch the cleanup Error, attach the prepared report with addSuppressed, and throw the same Error. No diagnostic accessor call was added in production. The supplied reviewer test is copied unchanged into tests/testPeerTemporaryRecordReportsKeepOriginals.kts. No existing test changed.
3. Ten separate fixed invocations passed on attempt 1. Removing just those three lines made three independent invocations unsuccessful on attempt 1, all nine runner attempts at the same assertion. Thirty neighboring storage scenarios passed on attempt 1. The repeated-run head is preserved in the historical source branch; PeerRegistry.kt and the reproducer are byte-identical to the rebased PR head.
4. The required locked local suite finished at the exact PR head: 3,031/3,031 first-attempt tests, zero histories, and 19/19 build rules. suite-counts.json and suite.xml.gz are on the evidence branch. XML SHA256 a506a931c4667f11937b767bf18e85045744f8aeffcd60995585cb0871e9cdfa.
5. Required bld-build CI is SUCCESS; bld-all-tests is IN_PROGRESS at the snapshot. Test workflow: https://github.com/CodexCoder21Organization/UrlProtocol/actions/runs/39695526661 . Build workflow: https://github.com/CodexCoder21Organization/UrlProtocol/actions/runs/39695526732 . PR head: https://github.com/CodexCoder21Organization/UrlProtocol/commit/e7b3f8b77a5d3f50f3b561110a42be13bf65d819 . The previous PR was still OPEN at the latest check, so its conditional rebase had not been triggered.

Relevant PRs and refs

Every source and evidence branch was verified against git ls-remote before writing. The evidence ref may advance with final reporting; use its live branch link for the latest notes.

No code was published, deployed, queued, or merged by this lane; no such command was performed. The local suite and output cleanup are complete. The only remaining long-running task before session cleanup is the plain CI watcher; it will be stopped before exit.

Next steps

1. Re-verify current state first. Check this PR's head and required checks, then check https://github.com/CodexCoder21Organization/UrlProtocol/pull/759 . If the earlier PR has merged, rebase this feature branch onto current main, run the public reproducer, verify this PR is still OPEN before pushing, and observe the new head's required CI. Do not update the earlier PR branch.
2. If required CI is still running, observe with coursier launch buildwatchman:build-watchman:0.0.21 -r https://kotlin.directory -- --repo CodexCoder21Organization/UrlProtocol --pr 807 . Never use a queue or merge mode. Do not repeat a job to obtain a green result. If CI is unsuccessful, obtain its XML and reproduce the named condition locally before changing code.
3. Once the required CI verdict is known, update the PR validation notes and rC22i-final.md on the evidence branch. The product branch must continue to contain only source and the permanent test. Stop after the requested evidence is complete; no extra test rounds are requested.

Operational notes

• All local verification used scripts/test.bash --local. The full suite used the required machine-wide out/suite-slot.sh wrapper; it finished successfully and released the slot.
• GitHub REST core quota reached 0/5,000 and resets at 2026-10-22 00:41:49 UTC. GraphQL still works, so gh pr view continues to provide CI status. The plain watcher remains valid but its REST observations can be unavailable until reset. Local complete-suite XML already satisfies the full-suite count requirement; CI XML is optional if that full local evidence is used.
• Installed gh pr edit queries the retired Projects classic field. The description was updated through a JSON-file PATCH request before the REST quota filled. GraphQL updatePullRequest can update the body while REST is unavailable; use the PR node id from gh pr view --json id and a structured JSON request.
• A separate non-required kotlin-build-ci-test app suite had no dispatched runs. No check was re-requested and no receiver was changed from that notice. Required Actions checks continued independently.
• Challenge records remain on the evidence branch because the report-challenge CLI queues and merges a reporting PR, which this lane explicitly prohibits.
• Read README persistence and clock contracts, architecture/TESTING.md TDD and Never Calibrate a Reproducer to a Machine, and relevant PHILOSOPHY.md testing/evidence sections. The current create-handoff skill uses the central service; the canonical format README's older merge procedure is superseded and is not allowed here.