Indexing the pinned CPython development root aborts the candidate18 runtime with SIGABRT before its first packet completes. The macOS crash report enters Rust’s stack-overflow handler through repeated codestory_indexer::walk_tree_nodes frames, called by native_declarators::callable_names. The report’s native UUID matches the packaged candidate18 binary.
The failure occurred on source f454c5e8559138bd75e421694e6f086338fe8573, tree e02e98ba8e97da792cdfe9a8cbc91fa3531b7416. Current walk_tree_nodes recursively visits the root and each named child. CPython source is pinned at 8f847875d60c81841e18a20510257a6e1b45b146. The original failure, native crash report and raw tool exchange are retained. Native process absence is verified separately; normal drain proof failed because the embedding-owner snapshot was never created.
Replace this traversal with a stack-safe implementation that preserves named-node preorder and subtree boundaries. Add a bounded deep-tree regression that reproduces the old failure in an isolated process and passes with the fix, plus traversal-order coverage. Avoid increasing worker stack sizes, excluding source files, changing parser coverage or embedding/retrieval policy.
Acceptance requires the focused regression, full indexer fidelity and language-coverage binaries, independent hostile review, and the same project-scoped CPython operation through the rebuilt candidate. Broader release proof remains deferred until the unified source converges. The remaining candidate18 batch is stopped.
Ownership: root coordinator; an isolated Cursor/Grok implementation lane and independent verifier. Base is the current integration head above. No main promotion or release is authorized by this issue.
Refs #2135, #2173
Current continuation — September 13
The traversal fixes remain merged. The subsequent Python dependency-eligibility repair was independently accepted at f5a6c4243e23197a6795eb39f46553335b14cd8d and merged through #2193 at 16578987a4131978b037da1ef88306b75758cafd with identical tree 398165ea912d475e7147bbb6b157e33462bb9975; #2192 is closed. The repaired first-question gate now prevents Q02 admission after an incomplete Q01.
Candidate21 was built and installed in isolated candidate-pinned fixture homes. Original CPython Q01 in batch006 stopped during core preparation at the frozen 3 GiB allocation cap: 3,366,633,472 charged bytes after 87.758 seconds, 15 preparing responses, zero complete packets, Q02 never admitted. The raw failure and failed normal drain remain preserved. A separate double native-absence scan and recorded-controller checks subsequently cleared the current slot. Batch006 is closed. Aggregate accounting cannot establish the peak product files or product-exclusive allocation. No cap increase or repeat of that closed attempt is authorized by this update.
Current ownership: Astra/root owns integration, controls, admission and native execution; Sol/high traces the existing core-writing sequence, Terra/high independently challenges the evidence, and Luna maintains coverage reconciliation. No competing implementation lane is open. The original installed packet remains the acceptance target; this issue stays open. Prepared Bazel and Terraform/EKS roots are separate bounded diagnostic work under #2173. Product convergence, complete adaptive investigations and independent unseen acceptance remain in scope before release qualification.
Indexing the pinned CPython development root aborts the candidate18 runtime with
SIGABRTbefore its first packet completes. The macOS crash report enters Rust’s stack-overflow handler through repeatedcodestory_indexer::walk_tree_nodesframes, called bynative_declarators::callable_names. The report’s native UUID matches the packaged candidate18 binary.The failure occurred on source
f454c5e8559138bd75e421694e6f086338fe8573, treee02e98ba8e97da792cdfe9a8cbc91fa3531b7416. Currentwalk_tree_nodesrecursively visits the root and each named child. CPython source is pinned at8f847875d60c81841e18a20510257a6e1b45b146. The original failure, native crash report and raw tool exchange are retained. Native process absence is verified separately; normal drain proof failed because the embedding-owner snapshot was never created.Replace this traversal with a stack-safe implementation that preserves named-node preorder and subtree boundaries. Add a bounded deep-tree regression that reproduces the old failure in an isolated process and passes with the fix, plus traversal-order coverage. Avoid increasing worker stack sizes, excluding source files, changing parser coverage or embedding/retrieval policy.
Acceptance requires the focused regression, full indexer fidelity and language-coverage binaries, independent hostile review, and the same project-scoped CPython operation through the rebuilt candidate. Broader release proof remains deferred until the unified source converges. The remaining candidate18 batch is stopped.
Ownership: root coordinator; an isolated Cursor/Grok implementation lane and independent verifier. Base is the current integration head above. No main promotion or release is authorized by this issue.
Refs #2135, #2173
Current continuation — September 13
The traversal fixes remain merged. The subsequent Python dependency-eligibility repair was independently accepted at
f5a6c4243e23197a6795eb39f46553335b14cd8dand merged through #2193 at16578987a4131978b037da1ef88306b75758cafdwith identical tree398165ea912d475e7147bbb6b157e33462bb9975; #2192 is closed. The repaired first-question gate now prevents Q02 admission after an incomplete Q01.Candidate21 was built and installed in isolated candidate-pinned fixture homes. Original CPython Q01 in batch006 stopped during core preparation at the frozen 3 GiB allocation cap: 3,366,633,472 charged bytes after 87.758 seconds, 15 preparing responses, zero complete packets, Q02 never admitted. The raw failure and failed normal drain remain preserved. A separate double native-absence scan and recorded-controller checks subsequently cleared the current slot. Batch006 is closed. Aggregate accounting cannot establish the peak product files or product-exclusive allocation. No cap increase or repeat of that closed attempt is authorized by this update.
Current ownership: Astra/root owns integration, controls, admission and native execution; Sol/high traces the existing core-writing sequence, Terra/high independently challenges the evidence, and Luna maintains coverage reconciliation. No competing implementation lane is open. The original installed packet remains the acceptance target; this issue stays open. Prepared Bazel and Terraform/EKS roots are separate bounded diagnostic work under #2173. Product convergence, complete adaptive investigations and independent unseen acceptance remain in scope before release qualification.