create-missing-tests-in-prlisted

**Constraint:** - Apply @rules/php/core-standards.mdc - Apply @rules/git/general.mdc - Apply @rules/code-testing/general.mdc - If the current project uses Laravel, also apply `@rules/laravel/laravel.mdc`, `@rules/laravel/architecture.mdc`, `@rules/laravel/filament.mdc`, and `@rules/laravel/livewire.mdc` - If you are not on the main git branch in the project, switch to it. - This task is based on the existing pull request review. - First read your existing code review for the current pull request and identify all testing recommendations related to current changes. - Never change the assignment scope. - Only add or modify tests when needed. - Production code may only be changed if it is strictly required by the existing create-test skill or test infrastructure, otherwise do not modify it — the only exception is the **Pre-existing issue handling** workflow below, which lands its production-code fixes in their own separate commits. - Use @skills/create-test/SKILL.md for all test-writing work. **Read, Map & Verify before writing tests (mandatory pre-flight):** Reading, mapping, and verifying come first; writing tests comes last. This pre-flight is **blocking** — do not add or modify a single line until all three steps pass, and never act on an assumption you have not confirmed by reading the code. 1. **Read** — open and read the actual changed code and the code it depends on (callers, called methods, related existing tests, configurati