Repository navigation
fix(qualification): recover from vanished Claude scratch children - #938
Merged
Merged
Conversation
antropos17
marked this pull request as ready for review
October 15, 2026 10:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A temporary child file or directory can disappear between the fixed Claude task's enumeration and stat/read, causing a false scratch-limit refusal even when the scratch root is empty. Retry that one ENOENT with one immediate fresh whole-tree traversal. Missing roots, access errors, persistent disappearance and all original 16-MiB/256-entry/depth-eight excesses still refuse. Preserve bounded reason/count/error and retry/recovery diagnostics through the strict bootstrap reader, without paths, names, contents or exception text.
Validation: eighteen observer cases pass, including real file/directory deletion between enumeration and query, persistent unknown states, missing root/access errors and a quota excess after retry. Forty-four strict parser controls pass. Earlier diagnostic/retry failures and the controlled actual-filesystem baseline are retained.
All five required CI contexts passed on exact source53bcaca7 in run38718867955. Full Windows11 run38718867924 attempt1 passed on that source: actual Claude read/edit/test, cancellation, stdio, owner lifetime, host/guest installed corpora, private registration/upgrade counts1/1, 55 mutation denials and eleven native image controls. All44 installed-owner, 43 image-control and five Claude source inputs were verified against the freeze, retaining raw line-ending differences. VM Off/removal and all four finite file removals were confirmed, failure/cleanupFailure=null. Raw receipt900813 bytes, SHA256 5d9af8808d9963e586720720a4409778a4da85a5684697ea5671fe6555639de0.
The guest's final observation was17 entries/880 bytes/depth5, with zero retries/recoveries. Thus this successful compatibility run does not itself exercise or explain the original intermittent refusal; the recovery behavior is established by the real-filesystem regressions. Original run38651247611 lacked the reason/counters and its exact cause remains unknown. Separately retained diagnostic source0c9a16ea/run38717901854 passed Claude, then failed stdio case2 before helper identity capture. VM Off/removal and four file removals were confirmed, cleanupFailure=null. Its raw607393-byte receipt has SHA25684aa4973340a3e5d60d3fa525ebb9b880935371080db5dead7fad7ce8d5b401d. That older stdio failure does not replace the corrected source's full PASS.
Both review passes were by current Codex. Overall acceptance stays30/60; A1-A4 remain unreviewed and launch stays closed. This fixed-lab pass does not qualify full E1-E11, real-provider credentials or production deployment.