Repository navigation
FOLD into 5-regen-verify (one class-kill, not a sibling): floor-gate src/v1/*.dag PARSE via shape-(b) — a non-#[ignore] parse-only witness over every src/v1/*.dag (cheap half of full_dsl_compiles, no heavy dsl/ compile). Closes 'src/v1 §7 authority gated only OUTSIDE the floor': src/v1 not in witnes - #5693
briansrls wants to merge 2 commits into
Conversation
…ify) - dsl/tools/host_prelude.dag: ensure_v2_whole_tree_parse_scan_built helper - dsl/tools/v1_dag_parse_transport.dag: shell transport — green (scan src/v1, --exclude-subpath stage0) + perturb red receipt (malformed file, expects non-zero exit) - dsl/test/claim/v1_dag_parse_witness_test.dag: test fn auto-enrolled by CI floor; closes the gap where src/v1/*.dag were outside witness_layer_roots Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Closing — auto-reopened duplicate. Branch session/still-badger-517 (now archived) re-spawned this PR after I closed #5690; it is the same duplicate scope as quick-carp-124's established #5666 (which additionally carries the Rust v1_src_dag_parse bin and is execution-proven + approved). Consolidating on #5666 and deleting this branch to stop the auto-reopen. |
|
Thanks for the review — no action needed here. This PR is CLOSED as an auto-reopened duplicate: branch session/still-badger-517 (now archived, branch deleted) re-spawned it after I closed the earlier #5690. The exact same parse-only v1_dag_parse floor-witness work is carried by the established #5666 (quick-carp-124), which additionally includes the Rust v1_src_dag_parse bin this PR lacked and is execution-proven (37 files parse-clean, exit 0, red-on-injection). Your APPROVE validates the approach, which is identical on #5666 — so the substance stands, just on the canonical PR. Consolidating there; nothing to merge or fix on #5693. — sent from crisp-carp-603 |
1 participant
Auto-opened by session-dashboard for session
still-badger-517.Pushing to
session/still-badger-517advances 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