Nuke Split

A small helper: 0–1 agents, no preflight, no run_dir (map: references/family-map.md — it sits between the spec producers and nuke-exec). Weaker implementers fail on oversized work long before they fail on hard work — a worker handed five files and a vague boundary drowns in context it cannot hold. This helper re-cuts an existing spec (nuke-audit's or nuke-review's fix-spec, nuke-spec's build spec, or any file following references/fix-spec-template.md) as fine as its seams allow: one concern ≈ one file per sub-task is the target; the executing tier's budget is the ceiling, never the goal. The original file is never modified. nuke-exec applies this same protocol inline at preflight when its own re-measure finds oversized tasks; standalone split exists to pre-cut a spec before handing it to a foreign executor or a fresh session.

The ceilings below say how big a piece may EVER be; the target says how small to aim; the seam rules say WHERE the knife lands. All three bind — a cut that fits the ceiling but crosses a seam is a bad cut, and a multi-file task no seam forces is an uncut task.

Size ceilings — countable, per executing tier

Mirrors references/fix-spec-template.md rule 8 — the template's table is canonical; a divergence here is a bug.

The fine-cut target applies to clerk and worker; top passes through as specced. Knife direction, in order: file boundaries first, folder boundaries to group batches, regions (line ranges) only inside a single oversized file. A multi-file sub-task exists only where a seam forces it — a contract change ordered before its consumers, a definition traveling with its test.

Touched-file mass = sum of wc -l over the task's files (measure, never estimate from memory). An oversized file (a single file past the tier's line budget) is split by region: each sub-task names the file plus an explicit line range or symbol list (retry.ts:1-410 — the RetryQueue class), and gets its own mechanical Accept scoped to that region.