While monitoring UrlResolver PRs https://github.com/CodexCoder21Organization/UrlResolver/pull/771

Reported (UTC): 2026-07-13 23:09

While monitoring UrlResolver PRs https://github.com/CodexCoder21Organization/UrlResolver/pull/771 and https://github.com/CodexCoder21Organization/UrlResolver/pull/772, replacement kotlin.build runs 724729ee and 75f8770e both provisioned droplets and then survived two build-service restart/recovery cycles without advancing past 'Attaching to the runner event spool at line 1'. At 2026-07-13 23:07 UTC, retained forensics for both runs ended with the exact line 'Build cancelled by user', even though the sole orchestrating agent did not cancel either run. GitHub still reported both checks as pending afterward. test-events.jsonl contained only 1102 test_discovered events, so no selected test executed. Impact: repeated infrastructure failures prevent CI-green verification for two independently locally-verified flake fixes and can misleadingly attribute service-side cancellation to a user while leaving GitHub checks permanently pending. Durable fix: identify and log the actual cancellation actor/reason, make restart recovery resume the runner spool correctly, and reconcile terminal cancellation back to the GitHub check instead of leaving it pending.

Production verification — 2026-07-17

Status: STILL EXISTS. Live GitHub verification found 2 referenced tracker(s) still open: https://github.com/CodexCoder21Organization/UrlResolver/pull/771, https://github.com/CodexCoder21Organization/UrlResolver/pull/772. A live ProductionHealth connection also emitted repeated NothingToCompleteException gossip failures, while the stopped HardwareControlFabric daemon log ends with Netty ByteBuf leak reports.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.