Nat census follow-up: discharge BLOCKED+LAST, regen defork audit

[briansrls]

Follow-up to merged #7537. The census measurements landed on main; this PR repairs the stale BLOCKED + LAST status the operator ruled must go after prerequisites discharged (#6341 merged; generic-alias coproduct keystone green).

What changed

1. Removed BLOCKED + LAST from dag/gunbc/plans/dag_v2_defork_audit.dag (authority) and regenerated docs/plans/dag-v2-defork-audit.md via main_wet — not hand-edited.
2. Replaced status with DESIGN READY · IMPLEMENTATION LARGE/ATOMIC · SEQUENCED WITH integer+float repoint (not last).
3. Clarified 138: floor import-closure count where both nat authorities are reachable — a risk and closure-population measure, not 138 migration tasks.
4. Recorded atomic wave file ownership in the defork audit grounding cluster (one push: dag/std/nat.dag, delete semiring alias, v2.std.nat thin reimport, integer/float repoint, all importer repoints).
5. Synced cross-refs: docs/plans/nat-grounding-unification-design.md, docs/plans/algebra-grounding-unification-design.md, dag/std/integer.dag, src/v1/stage0/src/std_integer.rs.

Does not start the unification wave. Sequence remains: #7511 merged → bounded P3b PR2 overflow on std.integer → atomic nat/integer/float wave (one writer through the numeric authority).

Census conclusions (execution, 2026-08-01)

The fork is representational, not nominal: std.nat.Nat = CommutativeSemiring<Magnitude> (no constructors) vs v2.std.nat.Nat = Zero | Succ (Peano coproduct + catamorphism). Exactly one homonym exists across the two modules: nat_compare — already producing §13 ambiguity in mixed closures.

Metric	Value
Floor *_test.dag entries scanned	946 (was 351 in 2026-06 audit)
Closures with both std.nat + v2.std.nat	138 floor closures (was 4)
LIVE fail-open pair	{algebra (75), nat (138)}
dag/ std.nat importers	61
src/v2/ v2.std.nat importers	37
Direct std.nat inside src/v2/	5 modules

Census-phase gates (§7.6 — unsafe facts, not a co-occurrence ratchet): no new unqualified nat_compare in mixed closures; no silent Nat authority choice; no new cross-tree std.nat bypass beyond the 5 known src/v2/ importers; mixed closures must refuse until the fork is dissolved.

Exclusion rule (why 61, not 63)

Importer counts use authored top-level ^import lines only. Loose grep finds 63 dag/ files mentioning std.nat; two additional files match only inside embedded fixture strings (not real imports) and are excluded. This rule is why the census is trustworthy.

Commands run

# Importer census (authored ^import lines)
rg '^import.*std\.nat' dag/ --glob '*.dag' | wc -l   # 61
rg '^import.*v2\.std\.nat' src/v2/ --glob '*.dag' | wc -l   # 37

# Regenerate generated plan md from .dag authority
cargo build -p v1-compiler --release   # workspace target/release/gunbc
./target/release/gunbc run --entry dag/tools/generated_artifact_gate.dag \
  --function main_wet --source-root dag --source-root src/v2

# Drift gate (green)
./target/release/gunbc run --entry dag/tools/generated_artifact_gate.dag \
  --function run_generated_artifact_drift_gate --source-root dag --source-root src/v2

Worker attestation

• Census measurements re-verified on this branch
• BLOCKED + LAST removed repo-wide (grep clean)
• Generated dag-v2-defork-audit.md regen from .dag authority (not hand-edited)
• 138 semantics documented as risk measure, not task estimate
• Atomic wave + file-ownership sequence recorded
• No co-occurrence count ratchet; §7.6 unsafe-fact gates documented
• Unification implementation not started (census/status/docs only)
• PR body is the real handback (not auto-opened TODO)

Test plan

• run_generated_artifact_drift_gate green locally
• CI floor on ready (draft skipped auto-gates)

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[gunbai-bot]

review 45923 — fixed in 7a4174a5c

Verified: the §3b grounding-cluster decision-input table (dag/gunbc/plans/dag_v2_defork_audit.dag nat entanglement cell + generated docs/plans/dag-v2-defork-audit.md §3b row) still carried Escalated (smart-ant-466) while §2A and §3 sequencing already said DESIGN READY — a real §3 single-authority inconsistency.

Fix: updated the §3b nat entanglement cell to census complete (2026-08-01), DESIGN READY, link to nat-grounding-unification-design.md, prerequisites discharged (#6341 merged; coproduct keystone green), IMPLEMENTATION LARGE/ATOMIC sequenced with integer+float repoint. Retired the smart-ant-466 escalation label (archived worker; prerequisites now discharged). Authority .dag edit + main_wet regen; drift gate green locally.

— sent from eager-swift-71