← Handoffs

Repository · handoffs

Handoff: Finish metadata repeat gates, then review and merge the cache prerequisite

View on GitHub ↗

id: hf-2026-10-04-settle-f80-and-ck1-ownership-then-finish-the-unchanged-endpoint-witness url: url://handoff/handoffs/hf-2026-10-04-settle-f80-and-ck1-ownership-then-finish-the-unchanged-endpoint-witness title: Finish metadata repeat gates, then review and merge the cache prerequisite summary: Finish fifteen more selected first-attempt passes and observe the supervisor replacement required check, then supervisor review and merge. Unchanged source4b818b25 has full79/79 and5/20 selected proof; two more retained passes are recovered. Publication and downstream sequence remain with the supervisor. created: 2026-10-04T04:07:29.395Z completed: null dependencies:

Handoff: Finish metadata repeat gates, then review and merge the cache prerequisite

Written: 2026-10-04 14:08 UTC

RE-VERIFY: This is a write-time snapshot. Re-fetch live PR state/head/checks, every listed branch and exact hosted artifact POM/JAR before acting. Current facts supersede prior conclusions. Source merges and a CLI coordinate alone do not prove an isolated worker’s selected runtime closure.

Mission and current state

The original owner asked that “shared caches must have fast, reliable locking internally so that serializing externally is never necessary; where that does not hold, we need concrete failure reproductions”. Restoring an unchanged endpoint witness exposed differently named Kotlin sources with identical bytes retrieving the wrong compiled class. The remedy requires filename identity at its upstream layers, normal artifact adoption and the same unchanged downstream witness.

The second-invocation ruling approved a real temporary-filesystem fixture for concurrentGetFileHashProducesConsistentResults. It explicitly stops this invocation after metadata PR readiness; the legacy source PR, manager release and endpoint witness remain unstarted until metadata 0.0.3 is published by the supervisor. Ownership between the previous lanes is settled. No merge, enqueue, publication, production deployment or handoff completion is delegated.

The corrected metadata PR is https://github.com/CodexCoder21Organization/FileMetadataCache/pull/24 at 4b818b25bc176a2d5776c67ff4909a5cf49b1ed6. The approved fixture retains four callers, ten contents, all 30 requests and every old operation/assertion, adds 30 exact expected-hash checks, joins its workers and deletes its unique FileSystem.SYSTEM directory on failure and success. The investigation ledger was removed after verifying its blob on the evidence branch. The resource rule/caller now use buildOldDirectoryMetadataFixtureResources. Directory/query source, README and five directory scenarios retain the supervisor-reviewed behavior.

Exact-head standalone remote run6cd45482 completed 79/79 tests,43/43 build records and 79/79 first attempts, with no test retries. It was archived after candidate commit11:17:51 (run start11:18:57). Selected runs 87e69da7, 7023934b and af96e861 each completed one passing first attempt: 3/20, zero failures. The required CI run e92aa412 has 79/79 passing first-attempt records but its GitHub check finished FAILURE. Its summary records a shard provisioning deadline and sibling provisioning shutdowns despite all tests passing. The provisioning cause and result-finalization behavior require upstream investigation; the failed check was not rerun. Gradle passed. This is CHECKPOINT, not PR readiness or whole-handoff completion.

Chain of findings

  1. Endpoint diagnostics/input declarations are on main through https://github.com/CodexCoder21Organization/kompile-executionenvironment/pull/80 and https://github.com/CodexCoder21Organization/kompile-executionenvironment/commit/1cb38081a0f9db671ee69c4f117410cc48595857 . Its required remote and bld-all-tests checks are SUCCESS. The unchanged restored duplicate witness remains separate and worth salvaging.
  2. Modern definition-site basename/content identity and v2 namespace are on main through https://github.com/CodexCoder21Organization/kompile-core/pull/366 and https://github.com/CodexCoder21Organization/kompile-core/commit/8c63643a129694ea1a45dab0c0a8b8cf9c4ea999 . Six recorded checks are SUCCESS. Do not reimplement it. Main’s default manager version and hosted version are separate from actual worker adoption.
  3. Combined metadata source frames relative entry names/kinds/count/child hashes and recomputes current directory entries after reopening. Leaf hashes, empty-directory compatibility, parent exclusion and saved-record layout are preserved. The packaged index produced by published 0.0.1 verifies old-record upgrade. It also contains the exact bound-filesystem query/test content from https://github.com/CodexCoder21Organization/FileMetadataCache/pull/23 . After24 lands,23 becomes a content duplicate; supervisor should close it then.
  4. The inherited concurrency failure came from its shared FakeFileSystem fixture. The dependency-only public-API witness failed10/10 without FileMetadataCache on the classpath; it remains on wip/L5-cache-gate-evidence and is linked in the corrected test comment. The approved real-filesystem correction exercises the cache’s same four callers. This does not claim the upstream fake’s concurrency contract is fixed.
  5. Legacy CacheKeyBuilder still has baseline source on main. Preserved evidence has the exact candidate patch, eleven unchanged scenarios, baseline3/11 versus candidate11/11, and five real-compiler cases baseline1/5 versus candidate5/5. This is direct classpath evidence, not normal isolated-child adoption. The normal source PR/full gate follows metadata publication.
  6. Remaining selected requests are retained in admission; required CI has now finished red from provisioning errors despite 79 passing tests. The archived GitHub check summary is the next upstream investigation input, not proof of the underlying cause. No failed check was rerun. Earlier Fresh live coordinator logs show required CI queue14->10->9->5 through13:11; oldest selected queue32->26->19->17->12->8->7 through12:45. Reservation/fleet figures are recorded without an inferred cause. The stale HTTP membership/cached frontend and elapsed-time watcher warning do not prove an execution stall. Do not delete or requeue these runs merely because they are old.
  7. One zero-dispatch check suite was recovered after build-watchman named it and independent GitHub GET confirmed queued/zero runs. The recovered suite has two dispatched check runs and required rune92aa412. No failed CI check was rerun. gh pr edit’s deprecated Projects-classic query failed; a structured REST PATCH updated the why-first body instead.

Relevant PRs and refs

PR Live head State/checks
https://github.com/CodexCoder21Organization/FileMetadataCache/pull/24 4b818b25bc176a2d5776c67ff4909a5cf49b1ed6 OPEN; Gradle SUCCESS; supervisor replacement required remote IN_PROGRESS (bd7b7674); informational remote IN_PROGRESS. Historical e92aa412 failed provisioning despite 79 passing tests.
https://github.com/CodexCoder21Organization/FileMetadataCache/pull/23 1d379a32c218b7bcaaf119617c22c1a0db7f992d OPEN; threeSUCCESS; close as content duplicate only after24 lands.
https://github.com/CodexCoder21Organization/kompile-core/pull/366 d0a16d0b5b551b331c7f9f51ab4ab26b97256618 MERGED; sixSUCCESS.
https://github.com/CodexCoder21Organization/kompile-executionenvironment/pull/80 1e1e9db951f9057b01c634da206ab98478cc57af MERGED; required remote/bld-all-testsSUCCESS; informational remoteCANCELLED at closure.

Every remote branch and satellite

Repo Branch Verified remote head Recommendation / contents
FileMetadataCache wip/F80-file-metadata-2026-10-04 1d379a32c218b7bcaaf119617c22c1a0db7f992d Keep until combined PR lands, then retire API duplicate by content; open narrow PR green.
FileMetadataCache wip/F80-file-metadata-evidence-2026-10-04 51958a7a833da4c78aa846e35c1abd3e70f9be6e Keep evidence and patches; no new merge required from this report-only branch.
FileMetadataCache fix/CK1-persisted-directory-names 4b818b25bc176a2d5776c67ff4909a5cf49b1ed6 Keep: corrected combined source pushed to the open PR; full gate79/79 without retries, repeat proof incomplete (3/20); required check FAILURE from shard provisioning errors.
FileMetadataCache wip/CK1-directory-evidence-2026-10-04 c550b1140228314bc17ff8b720f978bd990fc672 Keep evidence and patches; no new merge required from this report-only branch.
CacheKeyBuilder wip/F80-named-files-2026-10-04 e786e2f2480d7fe72941c43c246145c30213771c Keep evidence and patches; no new merge required from this report-only branch.
CacheKeyBuilder fix/CK1-source-filenames 1f7f948fcfb8a1b6c0ce3b81c0c576736ae4f8fa Salvage into future main-target PR after metadata publication: eleven tests, production still baseline.
CacheKeyBuilder wip/CK1-legacy-evidence-2026-10-04 3cef9a62602bd1bdc1b9a295557c36703312e20b Keep evidence and patches; no new merge required from this report-only branch.
kompile-core wip/F80-definition-file-names-2026-10-04 6a7ce9b0611b0932c51d2c73d7cc7870baca9535 Source candidate superseded by merged core fix; retain fail-first/restart evidence, then old implementation branch may retire.
kompile-core fix/CK1-definition-source-filenames d0a16d0b5b551b331c7f9f51ab4ab26b97256618 Source merged; retain reference until source/release proof is recorded, then implementation branch may retire.
kompile-core wip/CK1-core-evidence-2026-10-04 8d50f13671520805178febe0eff575041ea0301c Keep evidence and patches; no new merge required from this report-only branch.
kompile-core wip/CK1-final-evidence-2026-10-04 53c7f1ba2c97e21830a891cbf9e5016feef86d95 Keep evidence and patches; no new merge required from this report-only branch.
kompile-executionenvironment wip/F80-2026-10-04 4e3906845ced521520dcf76ad1d5ccb80cf2bd5d Salvage unchanged restored duplicate witness into a fresh main branch after runtime adoption; old full candidate must not overwrite main.
kompile-executionenvironment wip/F80-evidence-2026-10-04 98eb3ae489b74cda3ddb7b8b6ebf17a0e918a6cb Keep evidence and patches; no new merge required from this report-only branch.
kompile-executionenvironment wip/F80b-2026-10-04 4716799f59c567fe9f5063f529242721ab8eed06 Merged endpoint lineage; retain requested review/input-fixture evidence. Source branch can retire after evidence is retained.
kompile-executionenvironment wip/F80c-2026-10-04 2cd9fecb127e0da5aebe2d993984ff0ce162542d Merged endpoint lineage; retain requested review/input-fixture evidence. Source branch can retire after evidence is retained.
BuildTestEmbedded wip/F80-worker-toolchain-facts-2026-10-04 45a17123edc91bb5e51898b7f6e217f4bb9379e6 Keep facts only: runner/override source does not prove deployed version or selection behavior.
FileMetadataCache wip/L5-cache-fixture-evidence 0248e682c0eb4eb6c896b710aad59abaf83dae41 Keep: approved fixture correction patch and separate test/code review passes; full remote gate 79/79, repeat 3/20, required CI provisioning-failure output, final cleanup and resume ledger.
FileMetadataCache wip/L5-cache-gate-evidence 808bff35df66402e10d995c5f5cfcd19397b35b8 Keep: fresh filesystem-only witness (10/10 failures), returned remote 79/79 log, live states and two review passes; evidence only.
CacheKeyBuilder wip/L5-legacy-filename-proof cb078e3eaedb3796d64f8f97e3b61e8de8023004 Keep: exact candidate, eleven unchanged test bodies, baseline 3/11 versus candidate 11/11, full logs and reproduction command; evidence only.

Additional source checkpoint: https://github.com/CodexCoder21Organization/FileMetadataCache/tree/wip/L5-metadata-fixture at 4b818b25bc176a2d5776c67ff4909a5cf49b1ed6 contains the approved product candidate, after the exact-head full gate. It is not a separate product PR. The candidate is now pushed to the existing open PR, rebased and unchanged from the passing full gate; its why-first description marks repeated proof as pending.

No branch or PR has been discarded. Old endpoint candidates still contain the unchanged restored witness worth salvaging; modern old source candidates are superseded by content on main, but their fail-first/restart evidence is worth retaining. Evidence-only branches should not be merged into product source merely to preserve reports.

Immediate resume steps

  1. Claim this handoff and re-fetch this body/live state. The supervisor owns the required-check provisioning investigation and has requested replacement bd7b7674. This worker must only observe it, not re-request or investigate it. Archived check-runs-checkpoint.json records the historical all-79-tests-pass provisioning failure. Read investigation/L5-resume/findings.md, selected-run-ledger.json, first-attempt/full-gate JSON, separate review sections and after-publication-resume.md on the evidence branch. Do not redo the preserved diagnosis/inventory.
  2. Fetch the open metadata branch in a fresh clone, rebase on origin/main and verify whether head remains4b818b2. If it changes, run the complete remote suite again from the new exact head; the existing79/79 gate is valid only for unchanged4b818b2. Source is committed/pushed; no product edits remain requested.
  3. Recover retained queued requests before submitting replacements. Use current published CLI0.0.120 in an ignored local launcher and scripts/test.bash --remote --attach <runId> --log <absolute-log>. Ordinary completed result logs and live getTestAttemptResultsPaginated are required; exactly one PASSED first attempt counts each selected run. FILTERED_OUT rows are not failures or completed executions. Detached PENDING exit2 is no verdict and does not require resubmitting that ID. Cancelled zero-attempt requests do not count.
  4. Complete at least 20 selected independent remote passes (3 proved, 17 remain), recording attempts/failures/IDs. Review sections already cover unchanged4b818b2; append final validation evidence. Update the why-first PR body with actual counts after fetch/rebase/check OPEN, and watch required kotlin.build(remote) green in plain mode. Never --to-merged. Do not claim READY_FOR_MERGE until both gates finish; source/full suite alone is insufficient.
  5. Return READY_FOR_MERGE for this one PR to the supervisor, with metadata 0.0.3 publication and the subsequent sequence below. Only the supervisor reviews/merges/closes/publishes/adopts/completes.

Checkpoint run ledger: retain these twelve submitted selected requests: 0db53681, 3293f106, 51c386d9, 51ddb496, 55f61528, a8cc5d40, ab30d997, ae07736e, b49cb274, ce19f6c0, dbb9c79b, f8735be5. The earlier c2853e59 provisioning-recovery request needs separate inspection and is not counted. Five active client requests were cancelled during mandatory checkpoint cleanup: 455d2587, c18750a7, f6c91242, 67c434cc, 8fae0f98; none count as a passing test. Recover the twelve retained requests with scripts/test.bash --remote --attach <runId> --log <absolute-log> using the ignored current CLI launcher. If all twelve pass on their first attempt, five new independent selected runs still remain to reach twenty. Use scripts/test.bash --remote --test concurrentGetFileHashProducesConsistentResults --log <absolute-log> for genuinely new repetitions, after rebase and bounded memory admission. Do not resubmit retained IDs.

Publication-dependent resume sequence (do not execute in this invocation)

The supervisor owns every merge, enqueue, publication, runtime adoption and handoff-completion decision. Re-fetch live states and exact POMs first; recorded version numbers are candidates until rechecked. These steps are deliberately unstarted under the second-invocation ruling.

  1. Review and merge https://github.com/CodexCoder21Organization/FileMetadataCache/pull/24. Once its query implementation and identical query-test blobs are on main, close https://github.com/CodexCoder21Organization/FileMetadataCache/pull/23 as a content duplicate. Preserve evidence branches. Publish file.metadata.cache:file-metadata-cache:0.0.3 from merged main only, after rechecking both its literal and exact hosted POM/JAR absence. Build with scripts/build.bash --remote build.kotlin.util.filemetadatacache.buildMaven /absolute/artifacts/metadata-0.0.3. The supervisor's publisher command, after its publication decision, is:
export PATH=/code/ws/bin:$PATH
cs launch community.kotlin.maven.artifact.publishing:community-kotlin-maven-artifact-publishing:0.0.6 -r https://kotlin.directory -- --artifact-dir /absolute/artifacts/metadata-0.0.3 --api-url https://api.kotlin.directory/upload --force

The output path must contain the normal buildMaven directory/POM, not a fat JAR. Check the publisher's own exit code and GET the exact uploaded POM/JAR afterwards. This invocation published nothing.

  1. After metadata 0.0.3 resolves normally, make a fresh main-based CacheKeyBuilder source PR. Read its README/AGENTS. Retain the prior proof; do not redo its inventory or put investigation reports in product source. The saved patch already changes the metadata dependency to0.0.3 and candidate artifact version to0.0.7. Recheck current main/open PRs and version availability before applying it. Start with:
export PATH=/code/ws/bin:$PATH
mkdir -p workspace
git clone https://github.com/CodexCoder21Organization/CacheKeyBuilder.git workspace/CacheKeyBuilder
cd workspace/CacheKeyBuilder
git fetch origin
git rebase origin/main
git switch -c fix/legacy-file-name-identity
git fetch origin wip/L5-legacy-filename-proof wip/CK1-legacy-evidence-2026-10-04
git show origin/wip/L5-legacy-filename-proof:investigation/L5/legacy-proof/passing-legacy-candidate.patch > /tmp/legacy-file-name-candidate.patch
git apply --check /tmp/legacy-file-name-candidate.patch
git apply /tmp/legacy-file-name-candidate.patch

Restore these eleven unchanged test files from origin/wip/CK1-legacy-evidence-2026-10-04 with git restore --source=<ref> -- <paths>:

tests/nestedListOfFilesWithDifferentBasenamesProducesDifferentKeys.kts
tests/sameBasenameRelocatedParentProducesSameKey.kts
tests/sameBytesDifferentJavaFileBasenamesProduceDifferentKeys.kts
tests/sameBytesDifferentOkioPathBasenamesProduceDifferentKeys.kts
tests/sameBytesDifferentVirtualJavaFileBasenamesProduceDifferentKeys.kts
tests/sameDirectoryContentsRelocatedRootProduceSameKey.kts
tests/testCompilerCacheInvalidatesRegularFileRename.kts
tests/testCompilerCacheMissesLegacyContentOnlyKey.kts
tests/testCompilerCacheSeparatesSameByteBasenames.kts
tests/testCompilerCacheSharesRelocatedSameBasename.kts
tests/testCompilerCacheTracksDuplicateDirectoryFacadeNames.kts

Run each scenario through the normal published dependency path (scripts/test.bash --remote --test <functionName> --log /absolute/logs/<functionName>.log); then scripts/test.bash --remote --test tests --log /absolute/logs/legacy-full.log from the exact rebased head. The saved candidate discovered100 tests; recheck rather than hardcode that count. Retain full first-attempt and final results. Complete separate test/code review passes, check for an equivalent open PR, and open a main-target why-first PR. Watch plain required checks with build-watchman --repo CodexCoder21Organization/CacheKeyBuilder --pr <new-pr> --check 'kotlin.build (remote)'. Supervisor reviews/merges and then builds/publishes cache.key.builder:cache-key-builder:0.0.7 with scripts/build.bash --remote cache.key.builder.buildMaven /absolute/artifacts/key-0.0.7 and the same artifact-dir publisher form.

  1. Modern definition-site basename identity is already on kompile-core main through https://github.com/CodexCoder21Organization/kompile-core/pull/366 and https://github.com/CodexCoder21Organization/kompile-core/commit/8c63643a129694ea1a45dab0c0a8b8cf9c4ea999 . Do not reimplement it. In a fresh main-based core branch, update ordinary metadata/key dependencies to0.0.3/0.0.7 and choose a new unused manager version. Main currently declares RELEASE_VERSION0.0.203; hosted0.0.204 predates the basename fix. Recheck0.0.205 before selecting it. Inspect with git grep -n -E 'RELEASE_VERSION|file-metadata-cache|cache-key-builder' -- build.kts. Run targeted filename/compiler witnesses and exact-head full remote suite, completing normal compiler fixture preparation on remote executors as README/CI requires. Do not run README’s local warm-up or a large local build on this shared6GiB client. The remote command is scripts/test.bash --remote --test tests --log /absolute/logs/core-full.log; verify/run the supported remote preparation profile before relying on its results. Open a main-target dependency/release PR after the two reviews and required checks. Supervisor merges/publishes its chosen manager using scripts/build.bash --remote tools.kompile.buildMaven /absolute/artifacts/manager-new and the artifact-dir publisher form.

  2. Prove ordinary isolated-child/worker adoption through its supported public execution path. Record the actually selected manager, metadata and key artifact closure. Locate normal consumer pins with git grep -n 'kompile:manager:' in fresh relevant consumer checkouts and prepare any required main-target pin PRs with normal gates. A CLI override, private classpath overlay, source merge or file presence alone is insufficient. Runtime deployment, if needed, is an explicit supervisor/operator decision; this lane must not perform it.

  3. With corrected published artifacts and selected worker closure established, restore the unchanged historical endpoint witness in a new kompile-executionenvironment main branch. Never update the merged endpoint branch. Read root README/AGENTS and fetch the evidence branch. Restore only:

git restore --source=origin/wip/F80-2026-10-04 -- tests/testReviewLoopbackBindErrorNamesEndpoint.kts tests/testReviewLoopbackBindErrorNamesEndpoint/ReviewLoopbackBindErrorNamesEndpointParent.kt tests/testReviewLoopbackBindErrorNamesEndpoint/resources/bind-errors/testReviewLoopbackBindErrorNamesEndpoint/denySocketOperations.py

Selectively restore buildReviewLoopbackBindErrorNamesEndpointParent(fixtureSource: File = File("tests/testReviewLoopbackBindErrorNamesEndpoint")) from that branch’s build.kts; preserve its declared default File input. Do not overwrite current build.kts or rename/change same-byte fixture source names/content. Run scripts/test.bash --remote --test testReviewLoopbackBindErrorNamesEndpoint --log /absolute/logs/endpoint-witness.log, its endpoint neighbors, then the current complete downstream suite from the exact head. Recorded main discovery was159 before this restored case; recheck live count. Open a why-first main-target PR after separate test/code reviews and watch required checks. Supervisor owns final merges/adoption and handoff completion.

Operational knowledge

  • Prepend /code/ws/bin to PATH in every shell. Its cs JVM launcher works; the host’s native coursier does not. This repo’s old scripts use ignored jars/coursier, so use a JVM shim there. No product toolchain pin was changed.
  • Current ignored local CLI launcher uses published 0.0.120, whose --attach recovers completed runs. Remote archive selection excludes ignored files, so launcher heap limits do not alter test/worker configuration. The selected test’s limit remains30000ms. Local clients use128MiB; no local full suite or large fat-JAR build was run.
  • Shared host6GiB: wait below4.5GiB before new client starts. Admission records capped6 ordinary local selected clients; two extras required below3.5GiB and capped the total8. This controls clients only, not the test’s four callers. All owned background processes were stopped at the checkpoint and their recorded PIDs verified absent. Every process/wait is bounded. No artificial load was added.
  • HTTP /api/runs has outOfDate/refreshFailing data and misses newer IDs. Live public RPC, normal --attach and attempt records provided authoritative results. Bound build-watchman process deadlines end; retain run IDs and investigate its PROBLEM lines rather than interpreting HTTP503/missing Last-Modified as a dead executor.
  • No default Fabric credentials were available. Nursery health CLI hit JSONObject[uptime_human] not found; its API answered. No SSH, restart or production mutation was used.
  • Evidence reports/patches/logs are on evidence branches, not product source. report-challenge auto-enqueues/merges and conflicts with this lane’s explicit prohibition; actionable tool/service friction is retained in findings for the supervisor.

At 2026-10-04 13:49 UTC, build.kts still declares file.metadata.cache:file-metadata-cache:0.0.3. Exact hosted POM and JAR GETs returned404 at13:25; recheck both before the supervisor publishes. No publication occurred. All owned background processes were stopped and their tracked PIDs were verified absent. The claim will be released because this lane ends at CHECKPOINT.

Third-invocation checkpoint — 2026-10-04 14:08 UTC

The narrowed supervisor brief requires only metadata prerequisite readiness in this invocation: keep source at 4b818b25bc176a2d5776c67ff4909a5cf49b1ed6, recover the twelve retained IDs, reach twenty independent first-attempt selected passes, and observe the supervisor replacement check. No other source or publication work is delegated. The exact-head 79/79 and three selected first passes were verified from saved public attempt records. Fresh source fetch/rebase is unchanged and both own review passes found no introduced defect.

All twelve retained requests were attached. None supplied an additional selected attempt at the snapshot. Six had provisioning failures with no attempts and six were pending; a later live list shows ab30d997/dbb9c79b also failed before tests. Retain pending 0db53681,3293f106,51ddb496,a8cc5d40 rather than replacing them. Complete failure outputs and empty attempt pages are retained on the evidence branch. Two independent requests356419d3/60699ca3 were admitted from unchanged source; no more than two selected clients run at once, each -Xmx256m and timeout5400, and each start checks memory below4.5GiB. Future submissions exclude unresolved retained requests from their count. A provisioning failure with zero attempts is neither a selected pass nor a selected failure.

The supervisor owns the shared provisioning defect and the replacement required check bd7b7674. Its watcher is plain report-only; never re-request, enqueue or merge. Source proof remains3/20; required check remains IN_PROGRESS. The READY_FOR_MERGE gate still requires both completion conditions. Separate test-comprehensiveness and adversarial-review sections are preserved in investigation/L5-third/findings.md.

Repo Branch Verified remote head PR Contents and state
FileMetadataCache wip/L5-cache-repeat-evidence 84cdc4e1b3c9c85a5fbde4b0b9569cd98b2097d7 no PR Third-invocation snapshots, all twelve attach/attempt records, separate review passes, inherited proof checks and new issued IDs; evidence only, keep.

Read investigation/L5-third/selected-run-ledger.json and new-issued-ledger.json along with the normal publication-dependent sequence at investigation/L5-resume/after-publication-resume.md on this evidence branch. The original publication coordinate remains file.metadata.cache:file-metadata-cache:0.0.3. No merge, enqueue, publish, deploy, PR closure, branch deletion or handoff completion occurred.

Recovered-pass milestone 2026-10-04 14:17 UTC

Public first-attempt pages now prove3293f106/51ddb496 passed once each (894ms/994ms), raising selected proof to5/20,0 selected failures. Authoritative consolidated record is investigation/L5-third/final-selected-ledger.json; ignore the earlier3/20 snapshot above. Updated evidence head is 84cdc4e1b3c9c85a5fbde4b0b9569cd98b2097d7. New356419d3/60699ca3 remain active. Required-check replacement remains supervisor-owned. Source4b818b25 and the79/79 full gate are unchanged.