Skip to content

Namespace PR-5d: corpus import strip src/v2/test/** (~4319 import lines; delete import lines; disjoint from 5a/5b/5c; regen; dag_compile_clean_gate) - #6607

Closed
gunbai-bot[bot] wants to merge 5 commits into
mainfrom
session/fierce-ram-489
Closed

gunbai-bot[bot] wants to merge 5 commits into
mainfrom
session/fierce-ram-489

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Jul 14, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Namespace PR-5d: strip import statements from src/v2/test/** (576 .dag files, 4319 import lines deleted, single- and multi-line). Under namespace-only resolution (default policy NamespaceOnlyY on main), an import list is a second encoding of a module's usage (Rule-1 dual-representation); the body references are the sole authority and resolve via containment position, so the imports are deleted. Disjoint from 5a/5b/5c/5e by directory. Fixture .txt files (frozen source samples) are intentionally left untouched.

The strip itself is proven correct: a full 3-root compile (gunbc compile --source-root dag --source-root src/v2 --source-root src/v1 --target dag) with the strip applied produces zero undefined-variable / unresolved-type diagnostics across all 576 stripped files — every bare reference resolves under namespace-only.

Blocked on two upstream issues (neither caused by this strip)

CI is currently red, but on pre-existing / cross-lane issues that hit all strip PRs (5a–5e), not on the strip:

  1. inert-lens hygiene (fails ~44s): the reach BFS inert_lens_modules in src/v1/stage0/src/cli_run.rs builds its graph from extract_import_paths = parsed import statements. Stripping imports empties those edges, so 20 v2.lens.* modules read inert. Fix = repoint the import-graph consumers to the reference-derived module-graph edges (Namespace scaffold: reference-derived module-graph edge producer (flagged; no grammar delete; module_graph.dag only) #6593) — the "deps via container.member" prerequisite. Load-bearing Rust seed; namespace-lane scope, reported to parent nimble-boar-198.
  2. compile-clean (Blocker 2): non-exhaustive match in dag/gunbc/fleet_converge_cli.dag converge_cli_applied_knob_count — the 12 Srv3*/DurableApproval* HostEffect variants from shell→dag Shell→dag P5a: the 7 MECHANICAL srv3 tail files → typed observe/effect rows on host_effect_apply (their dissolution triggers already name this destination; receipt echoes → typed receipts); do NOT delete gunbc.shell_bash_runner.shell_exec_via_bash yet (P5b owns that deletion once no caller remains); #6586 are unhandled. Reproduces on origin/main with imports restored (merge-skew, independent of this PR).

The modeling-coherence per-head check reports "unavailable" because the diff exceeds 300 files — inherent to a mechanical corpus strip, fail-closed on the tooling side, not a modeling defect.

Test plan

  • gunbc compile --source-root dag --source-root src/v2 --source-root src/v1 --dependency-pool-index primary-precedence --output-dir <tmp> --target dag: with strip → 1 diagnostic (the pre-existing Blocker-2 Srv3 match); with imports restored → the same 1 diagnostic. Delta from the strip = 0 errors.

@gunbai-bot

gunbai-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Draft is intentional — this PR is held for the namespace strip Wave-1, not abandoned.

PR-5d (strip ~4319 import lines from src/v2/test/**) is correct in isolation — a full 3-root compile with the strip applied produces zero name-resolution errors under the namespace-only resolver. But it cannot merge yet: the corpus import strip depends on import-graph consumers being repointed to reference-derived edges first (the "deps via container.member" prerequisite). That work is staged:

  1. Blocker-1 part-1 (Namespace Blocker-1 (part 1): reference-derived module-edge producer + inert-lens reach repoint #6615) — reference-derived module-edge producer + inert-lens reach repoint. Approved (2/2), merge-ready, waiting on main compile-clean.
  2. Blocker-1 part-2 — module-graph loader + lens-hygiene disposition parser repoint (parked until the homonym-qualification lanes land).
  3. PR-4d (Namespace PR-4d: v1 global-unique bare fallback in lookup_binding_by_name — unblocks src/v1 import strip; witnesses + regen #6595, global-unique-bare) and the homonym-qualification lane (c).
  4. Blocker-2 (srv3 receipt-emit fold: quadratic concat → balanced join (bare-minimum-cost ruling) #6606) — pre-existing main compile-clean red (unrelated to strip).

This draft stays open as the tracked 5d deliverable and will be marked ready at Wave-1 once the above unblocks. Please do not merge or close it before then.

— sent from fierce-ram-489

@gunbai-bot

gunbai-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

MODELING-COHERENCE UNAVAILABLE here is a diff-size tooling limit, not a modeling defect.

The failure reason is explicit: gh pr diff 6607 returns HTTP 406: the diff exceeded the maximum number of files (300). This is the per-head coherence checker fail-closing because it cannot fetch the unified diff — PR-5d strips import lines from 576 files under src/v2/test/**, well over the 300-file API cap. Nothing in the .dag modeling changed (the strip only deletes import statements; deps are carried by reference resolution), so there is no modeling issue to fix and no push that would clear this — the diff is inherently large by the nature of a corpus-wide strip.

This is structural to every strip PR in the wave (all are >300 files). The PR remains a held draft for Wave-1 and gates nothing until then.

— sent from fierce-ram-489

@gunbai-bot

gunbai-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

CI red here is the expected Blocker-1 inert-lens breakage — fixed by #6615, not by anything in this PR.

The ci check fails at the pre-plan witness naming-hygiene walk:

inert-lens hygiene (DESIGN.md §6): 20 lens module(s) under v2.lens.* are authored but unreached by any discovered floor witness

This is the exact strip-triggered design gap: the inert-lens reach graph is built from parsed import statements, so stripping imports empties those edges and 20 v2.lens.* modules read as unreached. The fix is #6615 (Blocker-1 part-1): a reference-derived reach producer that carries the reach without imports (import ∪ reference-strict). It is approved (2/2) and merging into main; once it lands, this branch rebases on it at Wave-1 and the inert-lens gate goes green.

Nothing in this strip PR causes or can fix this red — the strip is correct in isolation (a full 3-root compile with it applied produces zero name-resolution errors). Held draft for Wave-1; do not merge.

— sent from fierce-ram-489

# Conflicts:
#	src/v2/test/claim/affected_set_universe_test.dag
#	src/v2/test/claim/ci_floor_plan_witness_test.dag
#	src/v2/test/claim/ci_spec_witness_test.dag
# Conflicts:
#	src/v2/test/claim/ci_floor_plan_witness_test.dag
#	src/v2/test/manual/forensics_6280_synth_consumer.dag
#	src/v2/test/manual/forensics_6280_synth_producer.dag
#	src/v2/test/manual/forensics_6280_tokenize_reject_locus.dag
@briansrls
briansrls marked this pull request as ready for review July 14, 2026 22:11
@gunbai-bot

gunbai-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by integration collapse PR #6640 (session/still-owl-689, work item adhoc-2ace4fe2-aad). Strip diff folded into single Wave-1 landing branch; individual lane PR closed per coordinator ruling.

@gunbai-bot

gunbai-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by integration PR #6640 (session/still-owl-689). Strip content collapsed into atomic Wave-1 landing target; hold draft until G1+(c). — still-owl-689

briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
#6612 #6613 #6622 after remote branch was reset to main. Includes G1
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls added a commit that referenced this pull request Jul 15, 2026
…nt main.

Re-apply atomic strip from collapsed PRs #6603 #6600 #6607 #6610 #6611
symbol_index resolve, global_bare census expansion, and stage0 bootstrap
sync. CI floor expected-red until Wave-0 (c) homonym qualify lands.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant