Program Insert Errata Afteruse Mechanics

The mechanic treats printed errata as narrow state, not a reusable permission token. Entry requires a visible source errata row, program editor or explicit absence, printing context, cited scope, requested afteruse, harmed claimant or explicit absence, proof bridge, and a future reader attempting to consume the errata state.

Resolution branches certify the original scope, restrict the reader, attach the program-editor bridge, reopen a claimant, split print correction from custody authority, quarantine the afteruse, or let a false-clean default mutate later play. Every branch records counter deltas and a named future reader/route effect.