Handoff: Finish local and bld-build verification for build-kotlin-jvm CI

Written 2026-10-27 16:49 UTC. RE-VERIFY: this is a write-time snapshot. Recheck https://github.com/CodexCoder21Organization/build-kotlin-jvm/pull/75 with gh pr view <url> --json state,headRefOid,mergeStateStatus,statusCheckRollup,mergedAt, and inspect https://github.com/CodexCoder21Organization/build-kotlin-jvm/actions/runs/40539509539 before taking action. Fresh state overrides this document.

Design decisions in force

The lane brief, dated 2026-10-27, requires one separate PR based on main and says:

• “Do not merge or enqueue anything. Do not change repository settings or rulesets; the orchestrator does that after reviewing.”
• “Do not touch PR 74's branch.” The referenced PR is https://github.com/CodexCoder21Organization/build-kotlin-jvm/pull/74 .
• “No raised timeouts, no skipped or weakened tests, no --admin.”
• “If the bld-build check never starts after your push, record that and stop. Do not push empty commits to retrigger it.” That stop condition did not apply: bld-build started.
• “Every wait loop you start must have a hard deadline. Kill every process you start before you finish. Wall-clock limit: 90 minutes.”

The explicit brief selects https://my.externalbrain.wasmserver.com/doc/github-builders-racing-remote-ci.md over older contrary remote-only guidance. This lane must not change required-check settings even though the later rollout procedure describes doing so.

Latest verification

At 16:47:45 UTC the source PR and related fix PR were both open/unmerged at their recorded heads. The Actions run remained IN_PROGRESS, with Run tests active after successful build. Neither requested CI log line has been captured from a completed job. Both local full-suite attempts ended in preparation, passed/failed assertion counts unavailable. Evidence snapshot is 9444e8b034fd97f7b99572676751408d9df3ad3a, including final-state.json. The 90-minute lane window is ending; verification is incomplete and requires continuation under a new assigned window. No transitional mirror was confirmed; use this service record as authoritative.

Mission summary

The owner requested conversation IDs to be shown and searchable on https://aiclisupervisor.wasmserver.com/conversations, with the work merged and deployed. Search depends on the existing multi-release JAR fix at https://github.com/CodexCoder21Organization/build-kotlin-jvm/pull/74 . Its required remote check was in progress for hours while the brief reported BuildTest down. This lane only adds the GitHub runner CI alternative: pin both wrappers to 0.0.124, copy the ContainerNursery bld-build workflow, run local build/full tests, open a separate PR, and prove bld-build passes with its pinned-version fetch and ALL TESTS PASSED log lines. Merging, settings changes, publication and deployment are outside this lane.

What was found and done

1. Fresh clone was made under the assigned workspace. README and repository build scripts/workflows were read; no repository AGENTS.md exists. Main was https://github.com/CodexCoder21Organization/build-kotlin-jvm/commit/ff0f9ec2aaec66c18ad4fcd7e76ef11ce0dced55 . Effective requirements contained only kotlin.build (remote), no separate required test job. Both disabled workflows were left unchanged.

2. Source commit https://github.com/CodexCoder21Organization/build-kotlin-jvm/commit/4a19aaa169a89a36577f11aebe862397c407706c changes exactly .github/workflows/bld-build.yml, scripts/build.bash, and scripts/test.bash. The wrappers fetch 0.0.124 and preserve arguments; the test wrapper now also passes repository root with -w, as the procedure requires. No launcher existed initially; the generated ignored launcher was created at 0.0.124 for local verification.

3. Workflow is copied from https://github.com/CodexCoder21Organization/ContainerNursery/blob/main/.github/workflows/bld-build.yml with the actual build rule build.kotlin.jvm.internal_buildscript.buildMaven. It has the exact job context bld-build, all required triggers, runner/container/150-minute reference budget, disk cleanup/checks, curl installation, explicit --local-and-remote build/full test commands, and result upload. No test or production source was changed.

4. Independent static configuration and coverage review found no configuration defect. Shell syntax and git diff checks pass. The review recorded a documentation conflict: Testing Architecture says never remove the remote required check, whereas the owner-selected procedure replaces it. No settings were changed here. No new tests were added for copied configuration; actual build/full suite/Actions execution are the validation.

5. scripts/build.bash --local build.kotlin.jvm.internal_buildscript.buildMaven passed with exit 0 in 472897 ms. Its log proves Fetching kompile.cli:kompile-cli:0.0.124 from https://kotlin.directory/.... It emitted nonfatal duplicate Scala-class warnings. The build.kts internal nested CLI pin remains 0.0.91, deliberately outside the explicit wrapper-pin request.

6. First full local command scripts/test.bash --local --test . --log /tmp/l53-local-tests.xml reached its 45-minute outer validation deadline, exit 124, still in WorkspaceKt.prepareTests. No assertions executed, no XML, no passed/failed counts. Stack samples show workers executing local dependency builds and child compilers doing Kotlin bytecode generation. This does not prove a specific test failure or a pin regression; the cause of the long preparation is not established.

7. Source branch was fetched/rebased again, main unchanged, and PR https://github.com/CodexCoder21Organization/build-kotlin-jvm/pull/75 opened. Description carries the original reason, the incomplete local validation, and the exact required Claude Code footer. Remote head was verified. No merge/queue action.

8. bld-build started on the PR. GitHub setup, container, disk cleanup, checkout, build and post-build disk check passed; Run tests was in progress at the latest snapshot. A second local full-suite attempt using retained build outputs was started on the unchanged head with a smaller 20-minute outer deadline to complete missing validation. This is not a retry of a failing assertion. Its snapshot/result is recorded in the accompanying findings and final report.

9. Second local attempt also reached its 20-minute outer deadline (exit 124) without assertion counts/XML. Last successful sample was prepareTests. All tracked local test processes exited. PR description now states both incomplete attempts and that Actions build passed but tests were still running at 16:40 UTC. The cause of the preparation duration is unknown.

Relevant PRs and refs

The pre-existing https://github.com/CodexCoder21Organization/build-kotlin-jvm/pull/74 was observed open at https://github.com/CodexCoder21Organization/build-kotlin-jvm/commit/d145bc28c15a2fcd0e6bfd290681fcbc908222bf . This lane did not touch that branch. Recheck before relying on its state.

Deployed or published but unmerged: none. This lane ran local build/test commands and created branches/one PR; no deploy or Maven upload command was invoked. Build outputs and ignored launchers/caches are intentionally excluded from the evidence branch. The assigned fresh clone was removed at 16:45 UTC after clean-tree/no-stash/no-unpushed-commit audits. All tracked local build/test/watch processes ended, including the Actions watcher at its hard deadline. No monitoring shell remains.

Next steps

1. Re-verify current state first. Read the evidence findings and latest final report, then inspect the Actions run above: it may have finished since this snapshot. Do not create a duplicate PR or push an empty trigger commit.
2. Complete full local-suite verification from the exact source PR head under a new assigned time window if still missing; use scripts/test.bash --local --test . --log <outside-repo-path> after fetch/rebase and uptime check. Keep every existing test/timeout/iteration. First determine whether the existing cache can be reused; its availability is not guaranteed. Never infer passing counts from an empty/incomplete log.
3. Verify bld-build passes and capture both Fetching kompile.cli:kompile-cli:0.0.124 and ALL TESTS PASSED from its completed log. Full logs can be downloaded with gh run view 40539509539 --repo CodexCoder21Organization/build-kotlin-jvm --log once available. Record exact counts and any full failure traces. A failed assertion must be reproduced locally before fixing; do not blindly requeue CI or loosen tests.
4. Update the existing PR description with final validation and provide results to the orchestrator for review. Do not merge, enqueue, change settings, touch the related fix branch, publish or deploy under this brief.

Operational notes

• gh here is 2.23.0; gh run watch supports --interval 60 --exit-status, not --compact. Job logs API returned 404 while the job was unfinished.
• build-watchman 0.0.21 --check adds a context to existing required checks. It cannot gate only bld-build while excluding still-required kotlin.build (remote), so one read-only assessment plus the bounded Actions-specific watcher was used.
• The first local full-suite main thread was still in prepareTests just before its outer deadline. Preserve that distinction from any future actual test failure. No reliable bug mechanism was established and no speculative fix was made.
• The evidence branch is separate from the source PR. Do not merge its diagnostic files into product code. Read the owner procedure and reference workflow before altering configuration; older kotlin-ci-setup guidance conflicts with this task.