dhpk-composer-package-hygienelisted

# Composer package hygiene Use this skill for PHP packages installed by downstream projects. Treat every public symbol, `composer.json` entry, published artifact, tag, and registry release as one consumer-facing contract. ## Working sequence 1. Load `references/package-contracts.md` and select the branch that matches the task. 2. Inspect the package's declared PHP/dependency floors, public symbols, autoload maps, Laravel discovery metadata, and release files before choosing a change. 3. Classify compatibility from the contract rules, not from author intent or the current resolver result alone. 4. Run the branch-specific checks in the verification gate below and report any unavailable consumer or registry check as blocked rather than green. ## Contract branches - Semver or public API change → `package-contracts.md` §Semver and §Public API surface. - `composer.json`, autoload, or dependency change → §composer.json hygiene. - Laravel providers, aliases, or facade discovery → §Laravel package discovery. - Changelog, tag, or Packagist publication → §Release flow. ## When NOT to Use - Application code that is never published to downstream consumers. - Language-level idiom selection; use `skills/dhpk-php-modern-pro`. - Laravel service-provider, facade, publishing, or Testbench mechanics; use `dhpk-laravel-package-author` or `dhpk-laravel-testbench-matrix`. - A release workflow that does not publish a Composer package. ## Output Return one of: - a semver verdict