Required remote remains red at 902a4856: discovery failed 3/3 while opening facade query streams in excluded UrlResolver. Memory/watchdog proofs are already pushed; 49 canonical passes include one SQLite setup failure before retry. L12 evidence is durable; orchestrator owns scope reassignment and final landing.
remaining work is in an excluded repository: UrlResolver
RE-VERIFY — 2026-10-04 11:40:50 UTC. This is a write-time snapshot. Recheck gh pr view https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 --json state,headRefOid,statusCheckRollup,mergedAt and git ls-remote before acting. The historical snapshots below are preserved for provenance, not current-state authority.
The user asked to drain the open handoff board. This lane owns only this handoff, with ContainerNursery in scope and BuildTest*, kompile*, UrlResolver and UrlProtocol excluded. The original memory/membership validation snapshot is stale: later repair lanes implemented and validated it, and pushed https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 to 902a48565f291c7fafc762f3484145b78d499fd1.
Verdict: BLOCKED on the excluded UrlResolver discovery gate; not obsolete. Current main dab37c7890cb8787c3ea767219ed0ad8bccb1ea5 is an ancestor of the PR head. Required kotlin.build (remote) is red at https://buildtest.kotlin.build/run?id=8e26e332 (667/668 canonical passes). No source repair is justified in ContainerNursery by the failed discovery evidence. An additional memory-test SQLite setup failure is explicitly unresolved below; do not call the validation clean or approve landing from informational green.
/root/buildtest-data/runs/8e26e332/. testUrlFacadeActiveQueryReturnsEveryMatchingProvider failed all three attempts: Results=[] then one standalone provider on each later attempt. All show resolver failure during facade query stream opening after successful registration. The test and facade implementation are unchanged versus main. Current UrlResolver source owns queryServices, its stream-opening wait, and PendingDialAdmissionController.Entry.closeChannel, which emits the recorded ADMISSION_RETIREMENT diagnostic. The exact reason those futures do not complete is not proven; the diagnostic itself does not prove retirement caused it. Current-source inspection is not a claim to have reproduced the pinned 0.0.1259 artifact mechanism.testMemoryPressure_sharedLimitingAncestorEscapedMount failed its first attempt at the unchanged 30000 ms default inside LocalFileSystemEventLog.<init> line 69 / NativeDB.step, before EventStore setup completed; later attempts passed at 7354 and 12783 ms. Cause unresolved, full stack/thread dump preserved. No limit or assertion was changed.| Repo | Branch/ref | Remote SHA | PR | Content and state |
|---|---|---|---|---|
| ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/main | dab37c7890cb8787c3ea767219ed0ad8bccb1ea5 | none | Main; exact ancestor of current product head |
| ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/fix/host-memory-from-proc-meminfo | 902a48565f291c7fafc762f3484145b78d499fd1 | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Product source, OPEN, required remote FAILURE; no new product push by L12 |
| ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/L262-memory-repair | 0540e048e0684d7436f30708bf8928a8992a9103 | evidence for same PR | Memory fail-first/corrected proofs under handoff-artifacts/L262; do not merge evidence branch |
| ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/L278-watchdog-identity-final | 3d19b667576e21de8e47edf0549fac052f9369b5 | evidence for same PR | Watchdog fail-first/corrected proofs under handoff-artifacts/L278; do not merge evidence branch |
| ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/L12-cn609-triage-evidence | 84a779bfb8de0abedbe1a1f1fc6c902222ae724f | no PR | Focused query and SQLite failure records, canonical scenario counts, live refs, incremental triage under handoff-artifacts/L12; evidence only, do not merge |
BuildTest WUI returned 503 while its cached test-results view had not materialized, and the initial run-page stream ended with a partial response. Documented fabric certificates were absent, so the provided cn_host_diag SSH key was used only to read saved run records as a last resort. No production state changed. The report-challenge CLI was not invoked because it automatically merges and this lane explicitly cannot merge; the orchestrator can record this friction centrally. A reports read also failed during handoff bytecode fetch, while get and RUNNING uploads succeeded.
No product work exists only locally, and no production deployment or Maven publication was performed by L12. Prior production notes below are historical claims and were not re-verified because this lane has no rollout authority. Focused evidence is pushed; unrelated whole-run journals, fetched dependency source and generated launchers are intentionally omitted from the evidence branch.
Remaining first: validate the memory repairs and membership edge cases on the cn609-fix WIP branch, resolve the shared-ancestor limitation, run the full suite, push the validated source to https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 and watch one required remote CI run. Delegate outcome is INCOMPLETE. No merge, queue, deploy, publishing, or handoff completion was performed.
| Lane | Branch / PR | Verified state |
|---|---|---|
| cn609-fix | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/cn609-fix-2026-10-02 | 3ded95ed871219e6e4a9379bab012aee66ad4126; local and ls-remote match; source repair commit 11651f0043778e12484806ee00e0edc5326e7e5b included; corrected runtime validation absent |
| cn609-fix PR | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | OPEN, code head 5d8eefb809d9cc404b023c41131170a85c88748a unchanged; description records WIP and unfinished review |
Observed: integrated review recipe repair and four probes, added a public same-cgroup adoption reproducer. Repaired real-process recipe passed 7 checks; reverting it selected 3 decoys and failed as expected. Local Kotlin baseline passed 10/14 and failed four precise public cases: host aggregate restart loses fields; a later pressure pass reuses old readings; zero host availability loses its known reading; same-group adopted child remains running. Gradle repair-only baseline passed MemoryScopeReportingTest 3/3 plus OomProtectionRecipeTest 1/1, no failures/errors/skips. Those main classes were compiled before the later four memory repairs; these counts do not validate the repaired head.
Four repairs are implemented and pushed: persist aggregate host total/sum/count/path; carry the newest snapshot across pressure passes; accept known zero available host RAM; compare adopted PID's current proc cgroup with the router's group, including descendants while excluding escaped namespace paths. Failed/empty proc reads are propagated with route/PID/path rather than turned into an assumed outside classification. No public interface shape changed.
Unfinished: corrected 14-selector run never acquired a compile slot and was stopped before execution at the exit window. Missing/unreadable membership, descendant and namespace-outside public API coverage remain; siblings sharing a finite capped ancestor require limit/mount/ancestor inspection beyond proc path comparison. Full suite, corrected Gradle validation, PR source push, CI watch and final independent review remain. This is an unfinished repair, not an approved limitation or CI-green PR.
Durable findings and complete baseline stack traces: https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/cn609-fix-2026-10-02/handoff-artifacts/cn609-fix . Findings RESULT is INCOMPLETE with per-selector counts. Shared waits: recipe acquired after 1503 s; Gradle after 1073 s; corrected verification remained queued. First WIP push was rejected generically; next normal push succeeded. gh pr edit hit classic Projects deprecation; REST updated the identical prepared body. One report bytecode fetch failed; the later RUNNING report succeeded. First handoff checkpoint update succeeded despite channel-close warnings. This is update attempt two of two.
The complete latest shared body follows, with its Mission, history, and every other lane's row preserved.
RE-VERIFY: 2026-10-02 18:30:39 UTC. Recheck GitHub heads/checks and remote branch refs before acting; this is a write-time snapshot.
Mission: integrate the review lane recipe repair into https://github.com/CodexCoder21Organization/ContainerNursery/pull/609, validate locally, settle same-group adoption, push the OPEN PR and watch one CI run. Supervisor alone reviews and merges; no merge, queue, deployment, publication or handoff completion by this lane.
Fresh clone of original PR head 5d8eefb809d9cc404b023c41131170a85c88748a; no unexplained newer commit/comment. Cherry-picked review repair b3f7939f and carried all four latest probes from review branch 349acc4a. Added a public-API same-group adoption test. Recipe fix binds matching to the jar basename and excludes the tmpdir marker. The first recipe test is waiting for a shared slot; no local runtime verdict yet. No ownership implementation was changed before red evidence.
Read-only membership probe created a child and read self/child proc records: both 0::/, reading the pair took 165375 ns in that sample. Adoption history cannot establish group membership. Proposed narrow fix is to inspect adopted PIDs at confined eviction decisions and treat proven same/descendant membership as LAUNCHED-bounded; missing membership and shared-ancestor limitations must be settled explicitly. This is source investigation, not a completed nursery test.
| Repo | Branch | Remote SHA | PR | Work | State |
|---|---|---|---|---|---|
| CodexCoder21Organization/ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/cn609-fix-2026-10-02 | ae5ea87005dcb0da27cd10f638479e03e63d600b | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Integrated repair, four probes, same-group public test, findings/recipe probe | Unvalidated checkpoint; PR remote unchanged |
Next: recipe green and reverted-red, candidate/original kts and Gradle reporting verdicts, fix only demonstrated bugs, rebase and validate, push existing OPEN PR, one watch. All earlier Mission/history/rows follow intact.
RE-VERIFY: 2026-10-02 18:05 UTC. Recheck GitHub and branch refs; all state is a write-time snapshot.
Mission: test-comprehensiveness then adversarial review of https://github.com/CodexCoder21Organization/ContainerNursery/pull/609. Review lane cannot merge, enqueue, deploy, publish or complete the handoff. Original PR remains OPEN at 5d8eefb809d9cc404b023c41131170a85c88748a; required remote check is IN_PROGRESS rather than green. No PR push or CI submission by this lane.
Confirmed finding: the widened manual OOM-score recipe selects a child JVM when its nursery tmpdir marker precedes an unrelated application jar. A real pgrep probe failed against the original recipe and passed after binding selection to the router jar argument basename. Doc and warning recipe repaired; score -500 and startup effect unchanged. Fixed/versioned, relative/absolute routers and three child/unrelated decoys are covered. The permanent Gradle recipe test remains unrun; the fix is preserved on WIP pending integration and required verification.
Source-review candidates remain unproved, with one public-API probe per condition: known host total with zero available RAM; loss of host total/sum/count/path when reopening a persisted aggregate; stale initial snapshot passed to the second eviction scope after launched shutdown frees host memory. Added proactive mixed-scope admission coverage. Memory implementation is unchanged pending red evidence. Same-cgroup adoption is an explicit unproved ownership question, not a confirmed defect.
Existing nine kompile scenarios passed 9/9 once, zero failed. No fix-reverted scenario or second/third positive batch was run. Gradle reporting run reached test compilation; candidate probes stayed queued. Owned unfinished runners were stopped for the lane budget, all confirmed absent; generated outputs removed. Final recipe counts: 3 expected baseline failures then 12 repaired passes, 0 failures. Final RUNNING progress report was accepted. No verdict is being inferred from compile completion. Full counts and final runner state are in incremental findings.
Test mapping and adversarial source pass are recorded in separate findings sections. Watchdog cases already cover v1/v2 small caps, a v2 ancestor, adequate and unlimited caps, root namespace, missing group information, refusal deduplication and refusal before termination. Exact boundary and broader ordering/ownership coverage remain explicitly listed. No deadline/iteration/assertion/test-enable change, reflection/mock, new swallowed exception/effect, artifact in PR diff, or OOM-score change found. PR description meets WHY, full URLs, handoff and footer requirements.
WIP work: https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/rev-cn609-2026-10-02 (current remote SHA is refreshed below before upload). It contains recipe repair, permanent Gradle test, four probes, real-process red evidence, test/compiler/transport logs and incremental findings under handoffs/artifacts/rev-cn609. PR branch remains unchanged remotely. All local source work is preserved there; nothing deployed or published.
Remaining work: finish candidate runtime proofs, repair only demonstrated mechanisms, run every changed test three times across both runners, verify claimed fail-first tests by relevant implementation reversions while retaining API shapes, locally validate final rebased head, push the OPEN PR and watch one required CI run. Supervisor alone decides final review and merge.
All earlier Mission, chain of findings and branch/PR rows follow intact.
| Repo | Branch | Verified remote SHA | PR | Work | State |
|---|---|---|---|---|---|
| CodexCoder21Organization/ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/rev-cn609-2026-10-02 | 5a0338ca1c9c00be1b63dfaa0fbfac94b801e44c | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Proved recipe repair, four probes, full findings/logs and closeout draft | REVIEW_BLOCKING; 9 kts passed once, remaining checks incomplete |
RE-VERIFY: 2026-10-02 17:05 UTC. Recheck GitHub state and remote branch refs before acting; all state is a write-time snapshot.
Mission: review tests and then code for https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 at 5d8eefb809d9cc404b023c41131170a85c88748a. This lane cannot merge, enqueue, deploy, publish or complete this handoff.
The lane brief's green-check premise was refuted: required kotlin.build (remote) was IN_PROGRESS at pickup; Gradle/release were SUCCESS and informational kompile NEUTRAL. Latest commit is accounted for by cn609's preceding lane and no newer comments were observed.
The public behavior/test map is preserved on the review WIP branch. Confirmed review finding: the new manual OOM-score pattern container-nursery.*\.jar also selects a child JVM carrying the nursery tmpdir marker before an unrelated application jar. Real pgrep against two owned process entries failed the exclusion assertion, selecting both child and router. A narrowed jar-argument/basename pattern passed the same probe three times locally; that source/doc repair and permanent Gradle recipe test are still local pending Kotlin runner validation, not yet pushed to the PR. OOM target -500 and startup effect behavior remain unchanged.
Two additional candidate public-API reproducers await execution: zero host availability must not be treated as unreadable data, and EventStore reopening must preserve all newly added host aggregate fields. The specific restart mechanism is omission of host total/sum/count/path from SystemMetricsAggregate.toJson/fromJson; existing cursor skips already-recorded events on restart. These are not yet counted as proved runtime failures. Candidate tests and the confirmed recipe reproducer are durable on the WIP branch.
| Repo | Branch | Remote head SHA | PR | What is on it | State |
|---|---|---|---|---|---|
| CodexCoder21Organization/ContainerNursery | https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/rev-cn609-2026-10-02 | cbce8ca0abf8e871461c28e6ced93522d0d0e079 | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Review artifacts, proved recipe failure, explicitly unrun host-zero/restart probes | Review in progress; no PR push by rev-cn609 |
Recover evidence at https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/rev-cn609-2026-10-02/handoffs/artifacts/rev-cn609. Nine existing kts selectors and the three-method Gradle reporting class were queued through the shared helper; kompile has acquired a slot, Gradle is waiting. No test verdict from those runners yet. No remote submission/rerequest by this lane. Next: runtime evidence, fail-first checks, three repetitions, fix confirmed defects, push PR only after local validation, and watch one CI run if pushed.
All earlier mission/history/branches/PR rows are carried forward below.
RE-VERIFY: 2026-10-02 16:54 UTC. Verify live GitHub state and branch SHAs before acting.
cn609 exit: owned local watcher PID 29330 stopped and confirmed absent; tracked exit 130. Last live GitHub snapshot was OPEN at 5d8eefb809d9cc404b023c41131170a85c88748a with required remote check IN_PROGRESS. Remote CI request preserved; delegate result INCOMPLETE. The final-body update succeeded; a subsequent compact refresh encountered bytecode-fetch failure and was retried against this latest body. All latest service content follows.
Finish required CI for https://github.com/CodexCoder21Organization/ContainerNursery/pull/609, then supervisor final review and merge decision. This lane's rebase and local verification are complete; the lane did not establish CI-green completion before its stop time.
The lane stops its local watcher on exit while preserving the remote CI request. Resume observation with coursier launch buildwatchman:build-watchman:0.0.21 -r https://kotlin.directory -- --repo CodexCoder21Organization/ContainerNursery --pr 609 --idle-timeout-minutes 60. The supervisor owns any CI-service repair and final review/merge decision. No merge, enqueue, deployment, production restart/route change, Maven publication, or handoff completion performed by this lane.
All earlier mission, findings and branch/PR rows are retained below.
The remaining lane gate is required remote CI for https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 at 5d8eefb809d9cc404b023c41131170a85c88748a. Gradle and bld-build-release CI are green. Required check https://github.com/CodexCoder21Organization/ContainerNursery/runs/110919728888 is IN_PROGRESS, still pointing at generic https://kotlin.build. Informational kompile check 110919864949 ended neutral after an upload-finalization error. Exactly one missing-dispatch rerequest was used; no second submission or rerequest.
Read-only fabric evidence: kotlin-build-ci PID 4165016 started 16:15:45.660Z, after the check was created. Its stdout resumes check 110919728888 for this exact head, downloads the source, submits CI build c7030a0f-2f3b-4e25-b112-897791c14f8b, observes PENDING, then records repeated failed getCiBuild reads: Cannot run CI operation 'getCiBuild' because the url://buildtest/ connection has not been established. A later snapshot still renews the request's lease at 755 seconds elapsed. No completed test verdict exists in these observations. The logs also mark the locally tracked required check completed in the event log during reconciliation, while GitHub still shows it in progress; preserve this discrepancy for the CI owner rather than treating it as a successful run.
This evidence identifies the affected service boundary, not the reason its connection was lost. No change to this PR's implementation or tests is justified by it. The lane continues its single watch until verdict or its 75-minute stop, then leaves CI observation and any service repair to the supervisor. All original mission/history/branch rows follow unchanged below. No merge, queue, publish, deployment, production restart/route change, or handoff completion performed.
The rebased PR https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 remains OPEN at 5d8eefb809d9cc404b023c41131170a85c88748a, with mergeStateStatus BLOCKED pending checks rather than the original conflicts. The required suite 100304232951 was independently verified through suite and check-runs endpoints as queued with zero runs at age 498.5 seconds. Three quick probes warmed the receiver. One rerequest at 16:06 UTC restored check creation; no live run was duplicated or deleted. Required check 110919728888 and informational check 110919864949 are IN_PROGRESS, currently with generic https://kotlin.build details links and no concrete run URL. bld-build-release is SUCCESS; Gradle CI remains IN_PROGRESS. One plain --pr watchman is running. Next: required CI verdict, then supervisor final review and merge decision. No merge, queue, publish, deployment, restart, route change, or handoff completion was performed.
RE-VERIFY before acting — 2026-10-02 16:00 UTC. This is a write-time snapshot. Re-check https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 with gh pr view 609 --repo CodexCoder21Organization/ContainerNursery --json state,headRefOid,mergeStateStatus,statusCheckRollup,mergedAt and verify branch SHAs with git ls-remote.
Mission for this lane: rebase https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 onto current main, preserve host /proc/meminfo memory decisions for adopted children and process/host limits for launched children, keep the watchdog safe across versioned artifacts, verify the affected tests, push, and watch one CI run. Supervisor alone owns final review, merge, enqueue, deployment and completion of this handoff.
Test did not complete during build execution. Exact build error begins Provisioning deadline exceeded for runId=1f99f96e: elapsedMs=600001 limitMs=600000, currentAttempt=18; lastFailure says Droplet 603262223 did not become active within 300 seconds (303s). The /api/test-results endpoint defaults to 100 rows and is not a full-run count. This differs from the earlier zero-test provisioning run recorded below. Do not rerequest the old head.All 1 peers for service 'handoff' failed bytecode fetch (direct and relay), incomplete response chunks); the second upload succeeded. Local compiler thread dumps showed real compilation and later classpath hashing; no locks were deleted. Shared-slot helper waits specifically on slot 1 after both are occupied; when Gradle released slot 2, canceled only this lane's unstarted wait and reacquired through the helper. Report-challenge's automatic enqueue/merge workflow was not invoked because this lane forbids all merge/enqueue actions; supervisor may record the transport issue separately.| Repo | Branch | Remote head SHA | PR | What is on it | State |
|---|---|---|---|---|---|
| CodexCoder21Organization/ContainerNursery | fix/host-memory-from-proc-meminfo | 5d8eefb809d9cc404b023c41131170a85c88748a | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Existing fix rebased to current main, no behavior changes from conflict resolution | Local 9/9 kts twice; 115/115 Gradle; required CI awaiting report |
| CodexCoder21Organization/ContainerNursery | wip/cn609-2026-10-02 | 5d8eefb809d9cc404b023c41131170a85c88748a | https://github.com/CodexCoder21Organization/ContainerNursery/pull/609 | Durable copy of rebased PR head | Same locally verified source |
Re-verify first, watch the single CI run, and act on its actual failure evidence if needed. A required provisioning/preparation failure with zero executed tests allows at most one evidence-backed rerequest. Once the required check is green, supervisor performs final review and decides merge. This lane never merges, enqueues, deploys, publishes, restarts production, or completes the handoff. No production changes or artifacts were published by cn609; historical deployment notes below remain snapshots requiring separate operator verification.
Local command: $S/withlock.sh scripts/test.bash --local with selectors testSystemMonitor_hostMemoryComesFromProcMeminfo, testEventStore_systemMetricsCarryHostFiguresAndCgroupPath, testMemoryPressure_launchedChildrenAreBoundedByTheNurseryCgroup, testMemoryPressure_confinedNurseryEvictsLaunchedChildrenNotAdoptedOnes, testWatchdogFindsVersionedContainerNurseryJar, testWatchdogRefusesToLaunchOnlyWhenItsCgroupCannotHoldTheRouter, testWatchdogReplacesUnhealthyRouterWithTheSameVersionedJar, testWatchdogRestartsARouterConfinedByAMemoryCappedCgroup, testWatchdogUsesLoopbackAndGracefulTermination.
Gradle command: ./gradlew test --tests 'org.example.MemoryScopeReportingTest' --tests 'org.example.SystemMonitor*' --tests 'org.example.EventStoreSystemMetrics*' --tests 'org.example.RollingFileLogCaptureTest' --no-daemon (also wrapped with $S/withlock.sh for shared-slot fairness).
Rescoped 2026-09-24 by sweep3-w6-20260924. Re-verify before acting.
3fdc4b60 on 2026-09-24; head is 703130dd9eb93bbe16c333405578b02269862b76.
pendingLogByteCapacity hunk that had been put on readIsBoundedByByteBudgetNotJustCount.kotlin.build (remote) first run, d434badf, failed before any test ran on a fleet-wide droplet provisioning failure (addSshKeyToDroplet timed out after 30s, 17 attempts). The one evidence-based rerequest produced run 0be44182, which was PENDING in the buildtest queue.RE-VERIFY before acting. This snapshot was taken 2026-09-13 12:58 UTC. Re-check the pull request states, heads, required checks, repository lock, and free disk space.
The per-droplet detail page is already delivered and live through https://github.com/CodexCoder21Organization/BuildTestWui/pull/283 and https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/959. Finish the three remaining BuildTestEmbedded hardening pull requests in order: runner-loss lifecycle PR 968, read consistency PR 964, and test hygiene PR 967. Get each to reviewed, locally verified, and green. Do not merge or enqueue; the campaign orchestrator owns that action.
https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/968 is OPEN and MERGEABLE at bd20e575df563a41582bec4af0b3e1a8dad09349. It is integrated linearly onto main ded69b6dad6b66ea325ec42f1a95b42cd2c1d1f6. The same commit is preserved on wip/968-current-main-merge; old checkpoint wip/968-latch-round remains at bf87565e1e9ae0139250d55099811643bc38e9d1.
The integration kept current main's snapshot refresh and fair append-persistence lock, the branch's grouped finalization publication, and both generations' test seams. testFinalizationGroupRecoveryEveryCrashPrefix and testLegacyJournalTrailingPartialLineRecovery passed 2/2 at parent 39ba4e8f6.
Exact-head source review then found a merge-resolution omission: drainPendingAppends ignored the physical framed byte count returned by appendCommittedLines and instead added unframed logical record bytes. With only unrelated disk-admission margins disabled in its fixture, testProjectionAppendFramingCountsTowardRawRetention failed before repair with A real append whose framing crosses the raw retention cap must publish a compaction. Commit bd20e575 captures the returned framed total, adds it once, removes the unframed per-record additions, and retains the fixture isolation.
Post-fix source compilation succeeded, but the paired tests did not execute: Coursier failed while materializing workspace-local artifacts because the shared 309 GB root filesystem had only 35 MB free. A separate remote attempt timed out in the build-service health RPC before submission. Do not count either as a test verdict. At this snapshot four fresh CI shards are in progress on bd20e575.
Next: obtain sufficient disk or a healthy remote builder and run testProjectionAppendFramingCountsTowardRawRetention plus testProjectionAppendFramingPreservesRecordByteBoundary first attempt. Then record exact-head independent test and code reviews and watch the existing CI run with build-watchman. Do not request a duplicate run.
https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/964 is OPEN and CONFLICTING at b9744482056bc23b3a0a9a7fea88de56fe1e3ed3. Its prior 62 targeted scenarios passed first attempt and its old CI was green, but it still needs rebase/conflict resolution, the saved R34 test review and R35 adversarial review rerun, their persisted-deletion restart probe, any resulting fix round, exact-head verification, and fresh CI. Reference artifacts remain on https://github.com/CodexCoder21Organization/PlanRepository/tree/wip/artifacts-2026-09-11-droplet-detail-landing/handoffs/artifacts/2026-09-11-droplet-detail-landing.
https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/967 is OPEN and MERGEABLE at 3b431db9be5dd74728db9f7d5788e329f9ba3be4; its old checks are green. It still needs R32/R33 rerun and one fix round for cleanup of runner JVMs after a parent hard timeout, archive relocation coverage, avoiding descendant-wide cleanup across concurrent tests, and the unbounded parser-cache process.waitFor(). Do not raise deadlines or reduce iterations. Reference artifacts are on the same PlanRepository branch.
workspace/BuildTestEmbedded-rank21, clean at bd20e575, no stashes, no local-only commits.wip/968-current-main-merge at bd20e575; wip/968-latch-round at bf87565e1.w4c/out/rank21-requeue-2026-09-13T1258Z.md.Use the campaign repository lock before editing BuildTestEmbedded. Rebase immediately before builds and before creating/updating pull request heads. Use targeted tests and build-watchman; never hand-roll CI polling and never merge or enqueue.
No status reports yet.
Moves it out of every priority list and into ArchiveArea.