Save this content to: AGENTS.md

# Agent Notes

## Documentation

| Document | Path | Description |
|----------|------|-------------|
| README | `README.md` | Usage, migration, compatibility results and support boundaries |
| Changelog | `CHANGELOG.md` | Package changes by release |
| PBT consumer | `tests/Consumer/property-testing/README.md` | Optional consumer verification and shared trial state |

## PHPUnit removal (issue #12)

The repository no longer requires `phpunit/phpunit` in the root `composer.json`.
Runtime compatibility for Laravel framework assertions, `createStub()`, and
deferred Artisan assertions is provided by `src/Shim/PhpUnit/`.

### Test commands

Run the three suites that must pass without `phpunit/phpunit`:

```bash
vendor/bin/testo run --suite=Unit
vendor/bin/testo run --suite=Laravel
vendor/bin/testo run --suite=Rector
```

### Composer

- Do not re-add `phpunit/phpunit` to root `require` or `require-dev`.
- After changing `composer.json` autoload sections, run:
  `composer dump-autoload`
- `composer validate --no-check-publish` must pass.

### Rector source discovery without PHPUnit

Rector's static reflection needs explicit autoload paths when PHPUnit is
absent. The canonical list lives in
`ichinya/laratesto-rector`'s `src/Configuration/AutoloadPaths.php` and is used by:

- the package's `config/sets/laravel-phpunit-to-laratesto.php`
- `tests/Rector/Support/FrontierPipeline.php`
- `src/Overrides/Testo/Bridge/Rector/Testing/Internal/RectorRunner.php`

The `FrontierPipeline` builder merges these package paths with its own corpus
paths because `RectorConfig::configure()->withAutoloadPaths()` overwrites the
set's autoload configuration.

The migration package is maintained independently at
https://github.com/ichinya/laratesto-rector. Root development installs it
through Composer; keep its integration tests in `tests/Rector`. Do not recreate
a local `packages/rector` source copy.

### Testo Rector override

`src/Overrides/Testo/Bridge/Rector/Testing/Internal/RectorRunner.php` delegates
to `Laratesto\\Rector\\Testing\\RectorRunner` in the optional migration package.
The harness uses Rector 2.7's `findByContract()`, supports sets and reports system
errors. The delegate is registered via
`composer.json` `autoload.classmap` so it takes precedence over the vendor
class.

### JUnit fixtures

`tests/Fixture/issue10/junit/*.xml` are hand-curated compatibility fixtures for
migration integration tests. They record expected test/failure counts for the
migrated issue10 fixtures because those fixtures are now executed with Testo
instead of PHPUnit's JUnit reporter.

### Temporary files

Debug scripts named `test-*.php` in the repository root are not committed; the
Laravel/Rector suites create runtime files under `storage/framework/testing`.