Define conventions so later work is consistent.
## Scope
- PHP coding standard (PSR-12) and the linter enforcing it
- Naming conventions for classes, DB tables, and columns
- Commit message format and branch naming
- How to run tests and linters locally
## Acceptance criteria
- [ ] CONTRIBUTING documented
- [ ] Linter config committed and runnable
---
Blocked by: #4
keith
added this to the M0 - Foundations & Decisions milestone 2026-10-10 22:17:12 +00:00
Implemented CONTRIBUTING, EditorConfig, PSR-12 PHPCS configuration, Composer scripts/lock and foundation checks. composer validate --strict, composer lint, composer test and composer audit pass. PHPCS 3.13.6 locked: installed global 3.13.0 was rejected by Composer security policy and was not used as the project dependency. Changes remain uncommitted; issue stays open pending commit/review.
Implemented CONTRIBUTING, EditorConfig, PSR-12 PHPCS configuration, Composer scripts/lock and foundation checks. composer validate --strict, composer lint, composer test and composer audit pass. PHPCS 3.13.6 locked: installed global 3.13.0 was rejected by Composer security policy and was not used as the project dependency. Changes remain uncommitted; issue stays open pending commit/review.
M0 work committed locally on main as c6cb3cec89 (chore: establish M0 project foundations). Verified composer validate --strict, composer lint, composer test, composer audit and git diff --cached --check before commit. Documentation explicitly defers runtime application/Compose to M1; tests cover repository foundations only. Closing following owner approval. Commit has not been pushed.
M0 work committed locally on main as c6cb3cec89b99634f255a93481363efe7ef19c33 (chore: establish M0 project foundations). Verified composer validate --strict, composer lint, composer test, composer audit and git diff --cached --check before commit. Documentation explicitly defers runtime application/Compose to M1; tests cover repository foundations only. Closing following owner approval. Commit has not been pushed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Define conventions so later work is consistent.
Scope
Acceptance criteria
Blocked by: #4
Implemented CONTRIBUTING, EditorConfig, PSR-12 PHPCS configuration, Composer scripts/lock and foundation checks. composer validate --strict, composer lint, composer test and composer audit pass. PHPCS 3.13.6 locked: installed global 3.13.0 was rejected by Composer security policy and was not used as the project dependency. Changes remain uncommitted; issue stays open pending commit/review.
M0 work committed locally on main as
c6cb3cec89(chore: establish M0 project foundations). Verified composer validate --strict, composer lint, composer test, composer audit and git diff --cached --check before commit. Documentation explicitly defers runtime application/Compose to M1; tests cover repository foundations only. Closing following owner approval. Commit has not been pushed.