You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(laravel): detect quality tools, capture baselines, and verify after upgrade
Detect Pint, PHPStan, ESLint, Prettier, Cypress, and Playwright during recon.
Capture pass/fail baselines before the upgrade starts so the agent knows what
was already broken vs what it regressed. Run detected tools conditionally in
verify-fast (pint + phpstan) and verify-full (+ eslint) so CI-breaking
regressions are caught during the upgrade, not after the PR is opened.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
-**Upgrade everything to latest** — the goal is eliminating tech debt and security risks. If a major version upgrade requires code changes (namespace migrations, API changes, config updates), DO those changes. This is expected.
@@ -86,10 +91,25 @@ This phase is optional — if the current constraint already covers the containe
86
91
-`.upgrade/laravel-upgrade-guide.html` — the official Laravel upgrade guide for the target version (if available). **Read this during Phase 1** for breaking changes and required migration steps.
87
92
-`.upgrade/recon-report.md` — pre-analyzed repo overview: package usage, component counts, test suite shape
88
93
94
+
## Baseline Awareness
95
+
96
+
Before the upgrade started, quality tools were run and results saved to `.upgrade/baseline/`:
- If a tool was PASSING before the upgrade (`pass` in .status file), it MUST still pass after. Fix any regressions you introduce.
104
+
- If a tool was FAILING before the upgrade (`fail` in .status file), you are NOT required to fix pre-existing failures. But if you can fix them easily as part of the upgrade, do so.
105
+
- Pint runs automatically in auto-fix mode via verify-fast.sh after every change. Include any Pint-reformatted files in your phase commit.
106
+
- If PHPStan/Larastan is installed: run `./vendor/bin/phpstan analyse` and fix errors that you introduced. Ignore pre-existing errors (compare with baseline).
107
+
- Log any baseline comparison notes in `.upgrade/run-log.md`
0 commit comments