Development record

The post-stamp byte-cap guard sits in stampScopeConditions, before two further growth steps on the draft face of Plan (kind and spec_id rewrites), so a draft within a few bytes of the read cap is written past it and every intent verb then refuses the whole corpus until the file is hand-trimmed; the planned face holds the cap. Cap the final bytes at every intent write through one helper covering the kind, spec_id, stamp and Link writes. Also informational: the stamp write error wraps a PathError that re-introduces the absolute temp path into stderr (a pre-existing pattern), and a degenerate comment or an inline-code opener above the section masks the real heading so the gate reports no section rather than naming the unclosed comment.