fix(tia): run the full suite when code the project loads from outside its root changes

[jfatr]

Builds on #1914. The first commit here is that pull request; review the second commit, fix(tia): run the full suite when code the project loads from outside its root changes.

What happens

A nested project can load PHP from outside its own root: a Composer path repository, a psr-4 mapping onto ../packages/shared/src, a PHPUnit bootstrap, <source> directory or <testsuite>, an --include-path, or a symlink that leaves the project. The dependency graph reaches no further than the project root, so a change to any of those files selects no test at all, and the suite replays from cache with results that the changed code no longer supports.

The fix

src/Plugins/Tia/ExternalSources.php reads the composer manifest of the project and the PHPUnit configuration that the run selects, and resolves the roots the project loads from outside itself.

• The configuration is the one PHPUnit opens: -c in its split, joined and attached forms, a directory as its value, --no-configuration, and the implicit file of the working directory in the order phpunit.xml, phpunit.dist.xml, phpunit.xml.dist. --bootstrap and --include-path on the command line count as declarations too, and so does the bootstrap attribute of each test suite.
• Each declaration resolves against the file that declares it, follows its symlinks when the target exists, keeps the segments before the first wildcard of a path repository or a source directory, and keeps a target that a commit deleted. A root matches the directory itself, so a submodule that git names by its gitlink alone matches.
• A committed change under one of those roots stops the replay and records a fresh graph when a coverage driver is available, or runs the full suite and keeps the recorded commit where it is when none is.
• An uncommitted change there runs the full suite and writes nothing, on every path that writes: a replay, a first run, --fresh, a rebuild after drift, and the result-only write of a --filter run. Git stops reporting such an edit the moment it is undone, so no snapshot of the run could stand behind a cached result.
• A declaration that leaves the repository, or that sits under a path the repository ignores, is reported and runs the full suite, because no run can observe a change there.
• The structural fingerprint carries the external roots and the identity of the selected configuration, so a graph recorded under one configuration does not replay under another, and a project that holds both phpunit.xml and phpunit.xml.dist tells -c phpunit.xml.dist apart from the default. A project that declares nothing outside its root and runs the file PHPUnit selects by default keeps the fingerprint it had.

This is the narrow form on purpose. Every change outside the project would make Tia worthless in a monorepo whose frontend moves daily; a project that declares nothing outside its root keeps the selection it had.

Tests

tests/Unit/Plugins/Tia/ExternalSources.php covers each declaration source, the configuration selection and the fingerprint. tests/Features/Tia/Monorepo.php runs a nested project against a changed sibling package, an autoload file, a bootstrap, a deleted package, an external test suite, a wildcard path repository, a symlink, a submodule, a configuration argument, a relative -c from the repository root, an uncommitted external edit on each write path, and a project that loads from outside its repository.

• pest --group=tia: 248 passed.
• rector, pint, phpstan and type coverage at 100 % pass.

🤖 Generated with Claude Code