phase 0: environment assessment + test baseline #2

New issue

Closed

opened 2026-02-20 01:40:46 +00:00 by Clotho · 0 comments

Clotho commented

2026-02-20 01:40:46 +00:00

Member

Context

You are a domain expert for core/php-framework - the foundation of the CorePHP modular monolith. All other core/php-* modules depend on this package.

Phase 0 Tasks

1. Environment Check

git checkout dev
composer install --no-interaction

If composer install fails, document the error and try to fix it.

2. Run Tests

vendor/bin/phpunit --testdox

Document: how many pass, how many fail, how many skip. Note any failures.

3. Run Lint

vendor/bin/pint --test

If lint issues found, fix them with vendor/bin/pint and commit.

4. Run Static Analysis

vendor/bin/phpstan analyse --memory-limit=512M

Document: level, number of errors, most common error types.

5. Coverage Assessment

Check which files in src/ have corresponding tests in tests/. List uncovered files.

6. Create TODO.md

Based on findings, create a TODO.md with phased tasks:

Phase 1: Fix failing tests
Phase 2: Increase coverage to 80%+
Phase 3: Fix all PHPStan errors
Phase 4: Security review

7. Create FINDINGS.md

Document all discoveries: architecture patterns found, test gaps, quality issues, dependency concerns.

8. Commit and Push

Commit TODO.md and FINDINGS.md to dev branch. Push.

Rules

Work on dev branch
UK English
Conventional commits: type(scope): description
Co-Author: Co-Authored-By: Clotho clotho@lthn.ai

## Context You are a domain expert for core/php-framework - the foundation of the CorePHP modular monolith. All other core/php-* modules depend on this package. ## Phase 0 Tasks ### 1. Environment Check ```bash git checkout dev composer install --no-interaction ``` If composer install fails, document the error and try to fix it. ### 2. Run Tests ```bash vendor/bin/phpunit --testdox ``` Document: how many pass, how many fail, how many skip. Note any failures. ### 3. Run Lint ```bash vendor/bin/pint --test ``` If lint issues found, fix them with `vendor/bin/pint` and commit. ### 4. Run Static Analysis ```bash vendor/bin/phpstan analyse --memory-limit=512M ``` Document: level, number of errors, most common error types. ### 5. Coverage Assessment Check which files in src/ have corresponding tests in tests/. List uncovered files. ### 6. Create TODO.md Based on findings, create a TODO.md with phased tasks: - Phase 1: Fix failing tests - Phase 2: Increase coverage to 80%+ - Phase 3: Fix all PHPStan errors - Phase 4: Security review ### 7. Create FINDINGS.md Document all discoveries: architecture patterns found, test gaps, quality issues, dependency concerns. ### 8. Commit and Push Commit TODO.md and FINDINGS.md to dev branch. Push. ## Rules - Work on dev branch - UK English - Conventional commits: type(scope): description - Co-Author: Co-Authored-By: Clotho <clotho@lthn.ai>