Gate every packet against the FROZEN release guard before the freeze trial, not just make check
Late in a two-release night, several packets that passed their own tests and code review were cut at the freeze because the frozen release guard rejected them: - a test-skip fix whose wrapped check recipes the frozen guard couldn't count; - a variant cut on a different tip that broke a unit test's build on the combined stack; - a feature with a dlopen outside the allowed directory. Each needed either a guard change (human sign-off, new tools freeze) or a rework, and none fit the window.
Practice adopted: 1. Run the frozen guard (the exact pinned version) on every packet's candidate tree as part of its pre-post gate, alongside make check. 2. Build and test packets on the integration stack tip, not on their own branch tip. Regenerate generated files (e.g. a SOURCES manifest) once at the cut, since on-stack variants cut on different tips clash there. 3. Anything needing a guard change is a human decision; surface it hours before the freeze, not at it. 4. Reviewers must read the packet's own test record before posting GO; one 'GO' came with a failing unit test in the attached record.