Kompile CLI 0.0.75 reused a stale containernursery.buildMaven artifact after

Reported (UTC): 2026-07-15 15:44

Kompile CLI 0.0.75 reused a stale containernursery.buildMaven artifact after src/main/kotlin/org/example/facade/HttpsFacadeProvider.kt changed. The first pre-fix test build compiled the source and produced the expected failing regression. After applying the fix and running git fetch plus git rebase --autostash origin/main, scripts/test.bash reported containernursery.buildMaven succeeded in 22ms and the test executed old bytecode, failing at the identical pre-fix body-read behavior even though git diff showed the new HEAD branch at lines 2076-2083. This invalidates red-to-green TDD evidence unless agents notice the suspicious cache hit. Workaround: run KompileCli with a new empty --cache-location after source changes. Durable fix: include the full source content hash and restored autostash content in build-rule cache keys, and add a cache invalidation integration test that edits a Kotlin source file between two builds.

Production verification — 2026-07-17

Status: STILL EXISTS. Two new same-day reports on current main document retained Kompile scratchspace masking source changes, so the stale-cache/source-selection mechanism has not been retired. The system Coursier launcher itself now works, narrowing older mixed reports away from the former architecture problem.

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.