MARK-007 MED: past MARK_MAX_REFS=512 refdefs the collector silently stops — links misresolve, no warning

The refdef collector caps at MARK_MAX_REFS 512 (MARK.c:13/:104-118) and SILENTLY stops collecting past it; a reference to a dropped definition then falls back to the implicit form — probe with 600 refdefs: [R599] resolves to ./R599.html instead of its defined p599.html. A silent WRONG link, not even a refusal; ticket-board-scale pages (todo/README) can plausibly reach 512 definitions. From the 2026-07-07 mark/ diagnostic review, orchestrator-verified by probe. Method Issues.

Input

Context

Probe (2026-07-07): 600 refdefs, use of [R599] → href="./R599.html" (misresolve) on the fresh build; no diagnostic anywhere.
Silent truncation converts a capacity limit into a correctness bug — the reader cannot tell a bad link from a good one.

Goals

Either the cap goes (BASS-carved ref table sized to the page) or overflow refuses loudly (--strict fail + stderr warning otherwise); NEVER a silent misresolve.

Constraints

Repro-first (the 600-refdef page); ABC idioms for any dynamic table (a_carve, not heap ad-hoc); raw markref refs[512] stack array is MARK-010's scope — coordinate.

WIP

Design decisions

(pending)

TODOs

Repro: >512 refdefs → defined target wins or loud refusal.
Fix collector overflow policy; suite green.

Blockers and bummers

None known.

Outcome

(pending)