Run project validate in CI #1528

Activity

1. somethings (lasomethingsomething)

   added a parent issue on Sep 8, 2026

   • project dev makes validation and code health visible and first-class #1523
2. somethings (lasomethingsomething)

   added the

   Improvement

   issue type on Sep 8, 2026
3. lasomethingsomething commented on Sep 11, 2026

   

   somethings (lasomethingsomething)

   on Sep 11, 2026

   ContributorAuthor

   More actions

   One shape this could take, from hands-on testing of extension format: the CLI relays each tool's native stdout rather than presenting its own. A single run prints PHP-CS-Fixer's version banner, the loaded-config path, a "ask for help" URL, a progress bar, and Prettier's per-file lines — two tools' raw output side by side, no shared voice.

   A unified summary the tools report into would fix both the human and machine cases at once, e.g.:

   format: 2 files checked, 0 changed (php-cs-fixer, prettier)
   

   The underlying change is that each verifier tool currently owns its own stdout; normalizing means giving them one presentation layer to write structured results into, instead of printing past it.

   Three invocations:

   
4. somethings (lasomethingsomething)

   changed the title [-]Normalize human and machine output across verifier commands[/-] [+]Run `project validate` in CI[/+] on Sep 11, 2026