# v77.2 — Scoped Pint Gate Repair

The v77.1 focused readiness tests and v61 readiness regression pass. The release then
stopped at `vendor/bin/pint --test` because the repository already contains hundreds of
historical Pint style violations across legacy and mature domain code.

That repository-wide style debt predates v77 and is unrelated to production readiness.
Auto-formatting all affected PHP files inside a production-hardening release would create
a very large unrelated diff and unacceptable regression risk.

v77.2 changes the release gate, not the application's formatting policy:

- Pint remains mandatory for PHP files introduced or modified by v77/v77.1.
- Repository-wide Pint cleanup is explicitly deferred to a dedicated formatting-only
  maintenance sprint.
- Full Laravel tests, optimization/cache compatibility, Web tests/build, Agent build/
  publish, scheduler/migration checks, diff checks, safe staging, and commit remain
  mandatory.

This keeps the release fail-closed for code touched by v77 while avoiding a 679-file
unrelated formatting rewrite.