A repository guard.json entry's why and successor are unbounded: the SHELL teaching plane injects both word for word, so one committed entry with a 240 KB why pushed every other domain, bundled hazards included, out of the 64 KiB injection budget; guard.Validate checked only that they are non-empty, 03-configuration.md's 'about a hundred tokens' per entry was a hope rather than a bound, and the truncation trailer always blamed .abcd/rules.json even when guard.json filled the budget.

A repository guard.json entry's why and successor are unbounded: the SHELL teaching plane injects both word for word, so one committed entry with a 240 KB why pushed every other domain, bundled hazards included, out of the 64 KiB injection budget; guard.Validate checked only that they are non-empty, 03-configuration.md's 'about a hundred tokens' per entry was a hope rather than a bound, and the truncation trailer always blamed .abcd/rules.json even when guard.json filled the budget.

Grounds

• pursued: a 240 KB why refuses guard.json at validation and a guard.json that overflows the budget is named in the trailer (TestValidateBoundsWhatAnEntryTeaches, TestShellDomainRefusesAnOverlongRepoLesson, TestInjectionBudgetNamesTheFileThatOverflowedIt); a trailer still naming .abcd/rules.json for a guard.json overflow would show it wrong