docs: restore deleted modeling rubric + tighten 🟡-debt marking, boundary references, and stale-scope drift

[briansrls]

What

Restores the two enforcement docs deleted in the #4192 public-visibility flip while still cited as live authority, and tightens the wording that made 🟡-marking an "introduce debt as long as you mark it" path.

1. Reintroduced deleted docs (operator request)

• docs/modeling-discipline.md (Practices 1–11 review rubric) — deleted while INVARIANTS.md cited it 4×, SELF_HOSTING.md once, and live .dag 🟡 marks referenced "Practice N". This is the gap that let PR T6 skeleton: real Arrow.body → translated TS emit (value-expression vetting consumer #4623) #4627's dissolution findings through an approving review (still-raven independently verified: T6 skeleton: real Arrow.body → translated TS emit (value-expression vetting consumer #4623) #4627 was unflaggable by any resolvable rule). Restored with:
  • retired-ledger refs (src/v4/TASKS.md, audit worksheets, deleted design docs) re-pointed to PR review / dashboard work items or annotated as git-recoverable history;
  • a provenance header (why deleted, why restored);
  • PR T6 skeleton: real Arrow.body → translated TS emit (value-expression vetting consumer #4623) #4627 as the Practice 10 worked example (predicate, walker, carrier/parametric, emit-template, and boundary findings, named row by row);
  • rows-3/4 escalation given a concrete trigger: a new file under src/v4/compiler/ is itself a review finding, default-block — author states why it can't be model rows + an existing fold;
  • Calibration: "a 🟡 mark records debt; it never authorizes it" — PRs enumerate new 🟡s, reviewer accepts each by name, default posture is debt-negative (a PR should dissolve ≥ as many 🟡s as it adds).
• docs/modeling/grounding-worked-examples.md — the coincide evidence bar INVARIANTS P1 cites twice; restored with retired DECISIONS.md refs fixed.

Both verified clean of internal-only content for the public repo.

2. Anti-debt-pileup tightening

• INVARIANTS P1 "Hand-rolled derived operation": "untracked … block merge" sharpened — the exception path is a valid 🟡 per Practice 4 (bound dissolution plan: gate kind, named arrival, owning PR/work item, dissolve-on-arrival follow-up); a 🟡 with no bound plan is not a valid 🟡 and blocks merge. Adds the marking-is-not-authorization / debt-negative paragraph.
• INVARIANTS P2, new problem shape "Target knowledge in compiler code": the boundary is about references, not just import lines — literal target atoms (^ts_inhabitant_number) or fixture binding names compared in compiler/ match arms are boundary violations the import check can't see; new-compiler-file default-block corollary; T6 skeleton: real Arrow.body → translated TS emit (value-expression vetting consumer #4623) #4627 receipt.
• MODELING M8: mechanical predicate-dissolution trigger restored (any new is_*/has_* Bool helper over a coproduct is predicate dissolution until proven otherwise).
• MODELING M9: extended to operations — a hand-rolled fold whose accumulator coincides with an existing carrier is that carrier (Missing | Unique | Ambiguous ⇒ find_witness). Also fixed M10-before-M9 ordering.

3. Drift fixes

• DIRECTION-CHECKLIST H3: still named the deleted ci.dag as "the Shape-B beachhead" — re-pointed at the M-CI lane.
• src/v3/SELF_HOSTING.md: still listed ci.dag as a live load-bearing authority — aligned with THESIS facet 4 (bootstrap / lens_ci_gate / affected_set_selection).
• INVARIANTS: references to deleted subdocs (decidability-invariant.md, strict-forward-progress.md ×3, design-emission-model.md, design-lens-framework.md, docs/review-findings/) annotated as deleted/git-recoverable instead of cited as live; TASKS.md ledger refs re-pointed to dashboard work items.
• (THESIS facet-4 ci.dag contradiction was fixed on main while this was in flight — this PR takes main's version.)

Not in this PR (flagged for follow-up)

• TESTING.md cites three deleted design docs as live authorities (lines ~340–470).
• The docs+ci: v4 direction checklist + doc-authority consolidation + reference-resolver gate #4519 CI reference-resolver gate only checks markdown-link syntax — every citation above was backtick-prose and invisible to it. Extending the gate is a CI change needing separate authorization.

🤖 Generated with Claude Code

[briansrls]

Addressed the composer-2.5 REQUEST_CHANGES in 006a8bd — all three findings verified real and fixed:

1. grounding-worked-examples.md:371 "dissolved in this PR" — stale restored-snapshot wording; now reads as pre-restoration history ("dissolved, operator-authorized, in the PR that originally landed this example"), no false P5 receipt.
2. Dead DECISIONS.md cites (:40, :64, :365) — each now annotated in place as the retired ledger ("the decision stands, the ledger is gone"), matching the header's retirement note.
3. DIRECTION-CHECKLIST.md:129 "M-CI lane" — undefined-in-repo lane name removed; the beachhead is now described directly (CI config generated from .dag; ci.yml stays the hand-authored authority until a generated CI model with a real runtime consumer lands), cross-referenced to THESIS "Meta-process modeling".

scripts/check_doc_refs.py --changed origin/main green locally.

— sent from smart-wren-720