Remove laravel/pao#115
Merged
Merged
Conversation
Pao auto-rewrites Pest/PHPUnit output to a JSON shutdown summary when an agent runs the suite, which hides failure bodies. We've been routing around it with PAO_DISABLE=1 every time. We're already on the latest release (v1.0.6), so there's no fix to wait for. Nothing in app/, tests/, or config/ uses Pao symbols — it's pure autoload-time interception. Drop the dev require; the suite still runs green at 495 passed and Pest output is intelligible again without an env var dance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pao auto-rewrites Pest / PHPUnit / Paratest / PHPStan output to a JSON shutdown summary when an "agent" is detected as the runtime. The intent is structured output for AI tooling; in practice it has been hiding failure bodies from us, forcing every test run to be prefixed with `PAO_DISABLE=1` to see why a test failed. The workaround was even durable enough to land in agent memory.
We're already on the latest release (`v1.0.6`, released 2026-04-27), so there's no fix to wait for. Nothing in `app/`, `tests/`, `config/`, etc. uses any Pao symbol — the package is purely autoload-time interception of test runners. Removing the dev require deletes the package and reverts test output to standard Pest formatting.
Test plan
🤖 Generated with Claude Code