Obtain one successful local main-source UrlProtocol build with the existing 2 GiB heap and deadline, then return its artifact and provenance to the publication workstream. Two local compiles reached the deadline; measured CPU scheduling delay remains to resolve. Source and diagnostics are pushed.
Two local source builds exceeded the existing deadline; local compilation must succeed before publication.
Written 2026-10-20 16:48:03 UTC.
RE-VERIFY: This is a snapshot. Check current source, artifact publication and local build scheduling before acting. Evidence is preserved at https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/urlprotocol-publication-evidence/investigation/urlprotocol-publication .
The publication task explicitly requires a local --local build with -Xmx2g; no remote build, timeout increase, lowered iterations, weakened assertions, reflection, mocks, CI retries, merge/queue changes or production deployment. Use /home/u/bin/cs. These constraints remain in force for this prerequisite.
Unblock publication of the already-merged TCP stop fix https://github.com/CodexCoder21Organization/UrlProtocol/pull/741. The code checkpoint is https://github.com/CodexCoder21Organization/UrlProtocol/tree/release/protocol-0.0.1426-tcp-stop at aecaf7e8b9949f04bdf5ee912bd239174a8b966f; this is merged-main source plus the coordinate/history-comment change only. No version PR or publication exists from this effort. Candidate1426 still returned404 on the last direct POM probe.
Two local source builds exited1 at the unchanged builder deadline:1200197ms elapsed /1196324ms deadline, then1195862ms /1191392ms. Both children were terminated. These are compilation failures, not test failures. Raw errors and thread samples are remote in the evidence directory above, branch head6ad8b0dd30bd3b4cd8ba0f1973d25ba50f82591e.
Compiler work progressed rather than deadlocking. Early paging and later high CPU PSI were measured; at one sample host load was~64 on8 CPUs, container CPU PSI full avg60~56.7%, and main had29 CPU seconds in335 elapsed seconds. GC did not dominate. This is not a complete diagnosis of every compiler cost, and no request for larger hardware or relaxed limits is made.
Re-verify current state first. Diagnose the local compilation/scheduling delay enough to obtain one successful local main-source build inside the existing deadline, without restarting it repeatedly unchanged or using CI as a debugger. A supervisor-scheduled compile window may be needed; no other lane's processes were stopped by this effort. Keep the generated artifact and exact provenance for the dependent publication task, then complete this prerequisite handoff. All previous task-owned builds and probes have ended.
Nothing was deployed or published. The two remote branches named above preserve all useful partial work. No build outputs, dependency caches or credentials were pushed.
28a83ccc
2026-10-20 16:51:15 UTC — BLOCKED
The task is to publish the merged TcpServer.stop fix and bump ContainerNursery with unchanged-test before/after counts, full-suite evidence, a PR and bld-build verdict. Both local -Xmx2g builds hit the existing 20-minute build-rule deadline. No limit was changed, and no artifact was uploaded.
The old transport reproducer failed 10/10 batches: 370/1000 post-stop connections, including 289 exact Stream closed replies. No fixed-version transport run occurred. All evidence and the proposed patch are pushed. The upstream implementation fix is merged; this lane changed no implementation or assertion.
The independent test/code review finished without blocking findings; no subagent or build loop remains active. The publication artifact is the remaining gate, and all work possible before it is prepared. Owner direction is unchanged: no queue, merge, deployment or draft closure.
Next: resolve the local compilation prerequisite, then publish, validate the CN bump, open its PR and watch bld-build. The useful lesson here is to keep compilation failures separate from test verdicts.
Moves it out of every priority list and into ArchiveArea.