Completed 2026-10-27: https://github.com/CodexCoder21Organization/ContainerNursery/pull/758 merged as 89f3685f2; JAR readiness now requires the launched process tree to have accepted the nursery's own connection (kernel inode attribution), OSHI removed. Follow-ups tracked by PRs 766 (awaiting owner approval) and 767 (draft); production not yet redeployed.
RE-VERIFY: everything below is a write-time snapshot taken at 2026-10-27 17:00 UTC. Authoritative re-checks: git log origin/main in https://github.com/CodexCoder21Organization/ContainerNursery (merge commit https://github.com/CodexCoder21Organization/ContainerNursery/commit/89f3685f2587877ee266d5ff5e10996d52040020), and gh pr view <url> --json state,mergedAt for each pull request named here.
/proc/net/tcp (or /proc/net/tcp6 for an IPv6 probe, which then is a required table) has a nonzero inode, and that inode appears as a socket:[inode] link under /proc/<pid>/fd of a pid in the launched tree. Inode zero (queued in the backlog) is not ready. Accepted outside the tree is not ready; the probe is closed and the next poll opens a fresh connection. EOF, reset or a vanished row before attribution is inconclusive and retried inside the existing startupTimeoutSeconds budget. After attribution the row is re-checked ESTABLISHED. No bytes are written to the app. This proves accepting, not that the app answers requests; the url RPC transport keeps its separate framed-reply probe. Adoption and the Docker provider are unchanged. OSHI is removed from build.kts. Timeouts and polling cadence are unchanged.https://github.com/CodexCoder21Organization/ContainerNursery/pull/758 "Attribute JAR readiness to a connection accepted by the launched process tree" merged into main at 2026-10-27T16:54:47Z as commit https://github.com/CodexCoder21Organization/ContainerNursery/commit/89f3685f2587877ee266d5ff5e10996d52040020 (squash of branch head 54b4b69f3a51f43266788bc9100bec2f1d51d321, 30 commits). Verified on main after the merge: readJarProbeConnection present in src/main/kotlin/org/example/danger_jarfile/DangerJarFileBackedContainer.kt, zero OSHI references in build.kts, the two original reproducers (tests/testDangerJarFile_sharedInheritedListenerDoesNotConfirmForeignServer.kts, tests/testDangerJarFile_boundButNotAcceptingChildIsNotReady.kts) and the three missing-tcp6-table tests present. README.md and docs/ContainerProviders.md carry the accept-only contract, "ContainerNursery sends no bytes", and the IPv6-required-table sentence.
Evidence chain (all recorded in the status reports filed on this handoff): both reproducers red on main before the fix, green after, red again in a reverse control with the old readiness source restored; every adversarial and test-comprehensiveness review finding across heads bfc9b2426 → a044ee705 → 13f55c647 → 54b4b69f3 closed test-first with red and green runs; the final head's required bld-build check green with 1379 of 1379 tests, exactly one of which was retried by the runner (testInheritedHttpsStartupCleanupSettlesExitedApplication, a pre-existing timed window in an untouched fixture; see follow-ups). The optional kotlin.build (remote) check was red on the branch and on the queue ref with a pure infrastructure verdict (the remote build service reported RECOVERING_LOCAL_STATE and ran nothing); it is not a required check under the repository ruleset.
This effort deployed and published nothing: no jar was uploaded, no route was changed, no Maven artifact was published. The production ContainerNursery router on 198.199.106.165 was not redeployed and therefore still runs the pre-fix readiness code until someone deploys from main (the owner's explicit ask is required for a production deploy).
| Repo | Branch | Remote head SHA | PR | What is on it | State |
|---|---|---|---|---|---|
| CodexCoder21Organization/ContainerNursery | fix/jar-readiness-accept-attribution | 54b4b69f3a51f43266788bc9100bec2f1d51d321 | https://github.com/CodexCoder21Organization/ContainerNursery/pull/758 | the readiness fix, tests, docs | merged to main as 89f3685f2 (squash); branch safe to delete |
| CodexCoder21Organization/ContainerNursery | fix/jar-readiness-ci-fixtures | efea2bb0aa1829737ca20756717175b2fad5714c | no PR | 12 fixture repairs (bind-and-sleep / accept-and-close apps → accept-and-hold) | cherry-picked into 758; superseded, safe to delete |
| CodexCoder21Organization/ContainerNursery | fix/jar-readiness-ipv6-review-fixes | c18999347908eed0e59aa424787674ba8a327488 | no PR | absent-tcp6 diagnostic fix and IPv6 tests | integrated into 758 as 13f55c647; superseded, safe to delete |
| CodexCoder21Organization/ContainerNursery | fix/jar-readiness-tcp6-worker-timing | 13f55c6479108afc107f92783d075f13baafa75a | no PR | no commits beyond the PR branch (lane found no reproduction) | empty, safe to delete |
| CodexCoder21Organization/ContainerNursery | fix/l153-shutdown-settlement | ef6a3314880302c2e75b50def86c4126733f0072 | https://github.com/CodexCoder21Organization/ContainerNursery/pull/766 | L153 test awaits public settlement after bounded shutdown; new contract test | OPEN, bld-build green, marked "do not merge" pending owner approval of the test-expectation change (follow-up 1) |
| CodexCoder21Organization/ContainerNursery | fix/inherited-https-exited-status-wait | bc144dfa623bae260fbc4e2712ab6d2568768911 | https://github.com/CodexCoder21Organization/ContainerNursery/pull/767 | inherited-HTTPS scenario observes the adopted app's exit after the successor's startup failure completes; gated regression variant | OPEN draft, bld-build in progress; the authoring lane was still running at write time (follow-up 2) |
main at write time: 89f3685f2587877ee266d5ff5e10996d52040020.
testL153AdoptionClockCannotReplaceCurrentGeneration asserted an active count of zero immediately after a 100 ms-bounded shutdown(); README lines 330–337 document bounded shutdown with cleanup settling afterwards, two sibling L107 tests await settlement, and https://github.com/CodexCoder21Organization/ContainerNursery/pull/742 corrected 35 fixtures for the same assumption. A held-stop control fails the original assertion 3 of 3 times. Recommendation: approve.src/test/resources/InheritedHttpsListenerScenarios.java harness (the predecessor's first cold request around line 502 and the restored nursery's first request around line 544), kept out of scope with logs recorded in the lane's findings, and a sibling testInheritedHttpsReplacementWaitsForPersistentApplication failing 3 of 3 locally in its clone with the app stuck "waiting at startup gate" (not yet root-caused at write time; may be caused by the lane's own in-flight edit to InheritedTestSupport.java). Each needs its own small fix-first pull request.testDangerJarFile_tcp6MetadataFailureNamesTable, testDangerJarFile_missingTcp6TableFailsIpv6Readiness); they once hit their 30 s budget under a load average above 100 and did not reproduce in 18 honest attempts.testDangerJarFileBackedContainer_urlFacadePortConnectableAfterStart.kts:84, testDangerJarFileBackedContainer_urlFacadeWaitsForTcpReadiness.kts:87) still carry pre-existing timed waits./proc/net/tcp shows inode 0 while queued in the listen backlog; after accept() the inode is nonzero and the fd link exists only in the accepting process. This is a reliable, byte-free acceptance proof usable through an okio FileSystem seam.localhost on the CI runner can resolve to ::1; bind fixtures to InetAddress.getAllByName("localhost").first() and treat /proc/net/tcp6 as required only when the probe socket is Inet6Address.test_log_file.xml artifact's <attempt-history> elements. Audit it before enqueueing.gh pr edit fails on this repository; edit descriptions with gh api --method PATCH repos/CodexCoder21Organization/ContainerNursery/pulls/<n> -F body=@file.--to-merged enqueues through GraphQL and follows the queue ref; a failed non-required queue check does not evict by itself here (758 merged with kotlin.build (remote) red on the queue ref).Recorded agent work, including concurrent agents
23 h 4.2 min agent time · 683,472,029 tokens
15-minute columns · empty columns are idle gaps · UTC
| Series | Minutes | % minutes | Total tokens | % tokens | Output tokens | First active | Last active |
|---|---|---|---|---|---|---|---|
| fable-readiness-20261027 · claude-fable-5-1 | 176.6 | 12.8% | 130,183,892 | 19.0% | 394,913 | ||
| brief2-fix · gpt-6.1-sol (high) | 140.9 | 10.2% | 63,833,608 | 9.3% | 177,961 | ||
| brief6-adversarial-fixes · gpt-6.1-sol (high) | 107.9 | 7.8% | 45,079,881 | 6.6% | 151,200 | ||
| sol-r19-l153-settlement-fix · gpt-6.1-sol (high) | 89.0 | 6.4% | 42,987,932 | 6.3% | 83,371 | ||
| sol-r21-inherited-https-exited-status-wait · gpt-6.1-sol (high) | 88.7 | 6.4% | 44,562,296 | 6.5% | 134,120 | ||
| sol-r16-coverage-gap-fixes · gpt-6.1-sol (high) | 81.3 | 5.9% | 33,792,308 | 4.9% | 78,809 | ||
| brief7-ci-fixtures · gpt-6.1-sol (high) | 73.7 | 5.3% | 31,321,170 | 4.6% | 86,644 | ||
| brief1-red-tests · gpt-6.1-sol (high) | 73.1 | 5.3% | 25,806,748 | 3.8% | 91,559 | ||
| sol-r11-tuple-test-fix · gpt-6.1-sol (high) | 72.9 | 5.3% | 31,982,515 | 4.7% | 80,280 | ||
| sol-r17-tcp6-worker-timing · gpt-6.1-sol (high) | 65.7 | 4.7% | 32,106,326 | 4.7% | 68,138 | ||
| sol-r12-ipv6-review-fixes · gpt-6.1-sol (high) | 55.6 | 4.0% | 26,890,379 | 3.9% | 75,411 | ||
| brief5-pr-and-test-review-fixes · gpt-6.1-sol (high) | 55.5 | 4.0% | 27,267,378 | 4.0% | 68,581 | ||
| sol-r13-integrate-ipv6-fixes · gpt-6.1-sol (high) | 42.3 | 3.1% | 17,054,215 | 2.5% | 34,049 | ||
| sol-r14-review-adversarial-delta · gpt-6.1-sol (high) | 40.7 | 2.9% | 15,850,660 | 2.3% | 50,881 | ||
| brief4-adversarial-review · gpt-6.1-sol (high) | 36.7 | 2.7% | 19,694,477 | 2.9% | 49,355 | ||
| sol-r8-integrate-fixtures · gpt-6.1-sol (high) | 30.3 | 2.2% | 12,837,404 | 1.9% | 22,821 | ||
| sol-r10-review-adversarial-final · gpt-6.1-sol (high) | 29.7 | 2.1% | 14,963,469 | 2.2% | 48,288 | ||
| brief2-accept-attribution · claude-fable-5-1 | 28.5 | 2.1% | 12,551,768 | 1.8% | 79,997 | ||
| sol-r20-review-test-delta · gpt-6.1-sol (high) | 20.5 | 1.5% | 11,944,057 | 1.7% | 31,300 | ||
| sol-r9-review-tests-final · gpt-6.1-sol (high) | 18.5 | 1.3% | 11,354,222 | 1.7% | 27,580 | ||
| brief3-test-review · gpt-6.1-sol (high) | 18.0 | 1.3% | 10,265,728 | 1.5% | 26,578 | ||
| brief1-red-tests · claude-fable-5-1 | 14.8 | 1.1% | 4,909,065 | 0.7% | 40,357 | ||
| sol-r15-review-tests-final · gpt-6.1-sol (high) | 13.8 | 1.0% | 12,641,051 | 1.8% | 24,241 | ||
| sol-r18-l153-analysis · gpt-6.1-sol (high) | 9.4 | 0.7% | 3,591,480 | 0.5% | 16,833 |
Agent-minutes add across parallel agents. Tokens include input, cached input, cache writes and output. Percentages are rounded to one decimal place in text and may sum to slightly more or less than 100%.
No status reports yet.