Repository navigation
v2 self-host front-end gap lane (cont.): on fresh main (gaps 1-3 merged), run the full-manifest self-parse gate for the VERDICT (compiler_closure_scoped_ingest_parses TRUE = milestone, else located gap-4 Reject), checkpoint, then fix gap-4 and continue lex->parse->normalize->infer->emit - #5404
Closed
gunbai-bot[bot] wants to merge 45 commits into
Closed
gunbai-bot[bot] wants to merge 45 commits into
gunbai-bot[bot] wants to merge 45 commits into
Conversation
Use fold_list (not undefined fold) for witness_layer_roots carrier check. Rename closure_gunbc_claim_run to avoid transport fn collision; add corpus clean witness for compiler_closure_ingest_transport. Co-authored-by: Cursor <cursoragent@cursor.com>
Name dissolution target (ProcessExit host effects, no shell.Exec.Run) and concrete enroll trigger for bounded-slice gap-4 RED claims when locate lands. Co-authored-by: Cursor <cursoragent@cursor.com>
…64-test-claim-cleanup
…64-test-claim-cleanup
… rule Ephemeral gap-4 locate probes used `test fn` in src/v2/test/fixture/*.dag, tripping batch-2 discovery-corpus hygiene. Delete investigation-only fixtures and point the ignored Rust bisect harness at dag_comma_optional_list_test. Co-authored-by: Cursor <cursoragent@cursor.com>
…layer_roots text-scan) The N_v2 substrate Rust harness carried use std::process::Command (cargo shell-out) and a text-scan projection of dsl/gunbc/ci_layer_roots.dag (witness_layer_root_paths) — the §3 grep-not-lens anti-pattern the operator flagged. The gate is now a modeled ci_claim_gate test fn in compiler_closure_emit_from_ingest_test.dag, and the N_v2 cargo-check measurement is owned by the regen/measurement oracle lane — this forked Rust harness is redundant. Remove it + its mod registration in lib.rs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Replace removed emit-wrapper references with transport-aligned claim legs (layer_roots no-overlay, module_count + parses_holds with manifest). Carrier witness enrollment was already landed in compiler_closure_ingest_transport. Co-authored-by: Cursor <cursoragent@cursor.com>
Remote 2a796a0 deleted v2_compiler_closure_nv2_substrate_test.rs — the broken emit-wrapper references are gone with the harness. Keep lib.rs duplicate #[cfg(test)] cleanup. Co-authored-by: Cursor <cursoragent@cursor.com>
Track intentional narrowing vs deleted nv2 shell gate — emit acceptance stays on regen/measurement oracle lane until N_v2 emit milestone. Co-authored-by: Cursor <cursoragent@cursor.com>
…64-test-claim-cleanup
Malformed let missing `=` also surfaces parse_g0_tokens_remain, so the discriminating control falsely failed batch-2 discovery. Switch to unrecognized-char rejection (tokenize_lex_e1) like caret_lex witness. Co-authored-by: Cursor <cursoragent@cursor.com>
HEAD had a dangling match_arm_stmt_body production (missing expr fn, no choice arm) that broke grammar validation and floor witnesses. Wire stmt+repeat body expr, formal row, and expr|stmt_body choice; engine hook in 02_parse.dag unchanged. All six gap4_parse_tokens_remain witnesses green-by-execution locally. Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
marked this pull request as ready for review
June 20, 2026 18:12
6 tasks
Contributor
|
Closing as superseded by #5406. The lane goal — make the self-parse/ingest milestone pass — is ACHIEVED on main: source_root_ingest_gate is green (verified on #5413 CI) and main carries gap4_parse_tokens_remain_test.dag via #5406 (the merged gap-4 arm-body engine change). This branch is 45 commits behind / CONFLICTING / all-WIP and carries a scripts/*.sh (no-new-shell). Branch retained for salvage of its 3 unique files if a future increment wants them: gap4_ingest_reject_probe.dag, compiler_closure_emit_from_ingest_gate.dag, dag_parse_engine_hooks.dag. Next self-host increment should branch fresh off current main. |
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
1 participant
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.
Auto-opened by session-dashboard for session
snappy-stag-264.Pushing to
session/snappy-stag-264-test-claim-cleanupadvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan