Require audit-driven fixes with focused regression coverage

When addressing repository or PR issues, perform a thorough audit rather than a narrow edit, tracing findings through related runtime code, workflows, documentation, and tests. Treat correctness and safety findings as merge blockers until fixed and covered by focused regression tests, especially validation and failure paths. Preserve exact contracts, including formatting or trailing bytes where relevant; do not weaken validation merely to satisfy fixtures or permit unsafe fallbacks. Keep code, generated artifacts, and documentation aligned, remove unrelated churn, verify affected paths and the final diff, rerun full verification, and obtain a fresh read-only audit before declaring the work mergeable.