Haiku Laravel Package

Product Decisions This Supports

• Build vs. buy for code-style enforcement: this package bundles opinionated style rules (separator conventions, import/exception-rule checks) into a single dev dependency, so the decision is "adopt a maintained ruleset" rather than writing and owning custom PHP_CodeSniffer/Pint configuration.
• Roadmap sizing for quality/tech-debt work: the cadence of small, rule-level releases (this one adds lint coverage for bad cosmetic and wrong domain separators, tightens exception-rule checks, and drops a fixer behavior) tells you the maintenance cost is low and the churn is incremental — safe to slot into an existing CI hardening story rather than a dedicated initiative.
• Feature scoping for internal tooling: the [lint] vs [fixer] split lets you decide whether to adopt the package as a gate (report only) or as an autofix step in pre-commit/CI. This release widens the first and narrows the second.
• Use cases to prioritize: greenfield Laravel services, monorepos wanting a consistent separator/import convention, and teams already on Pint who want extra opinionated checks layered on top — not legacy codebases where a mass autofix would generate unreviewable diffs.
• Upgrade planning: removing the removeUnnecessaryWildcard fixer means wildcard imports are no longer automatically cleaned. If a team relied on that autofix, the PM decision is either accept the manual lint burden or pin to v1.13.31.

When to Consider This Package

• You want an opinionated, low-config style gate for a Laravel/PHP codebase and are willing to accept someone else's conventions (separator style, exception rules) as-is.
• Your team already runs Pint/PHP_CodeSniffer and wants additional rules without authoring them.
• You need a lint-only signal in CI (non-blocking advisory first, then ratchet to blocking).
• You can absorb minor-version churn: this release is patch-level in version but changes fixer behavior, so pinning versions and reading changelogs is required hygiene.

Look elsewhere if:

• You need a configurable, widely adopted standard (PSR-12, Laravel Pint defaults, PHP-CS-Fixer) with a large ecosystem and stable autofix surface.
• Your codebase is large and legacy — behavior-changing fixer removals across patch releases are risky without a pinned lockfile and a staged rollout.
• You require long-term support guarantees or a formal deprecation policy; the changelog here is terse and semantic-versioning is loose (fix/feat mixed with behavioral removal in a 1.13.x bump).
• Autofixing imports is a core workflow — the wildcard-removal fixer is gone as of this release.

How to Pitch It (Stakeholders)

For executives: a small, actively maintained open-source package that enforces code style in our Laravel services, reducing review nitpicks and reviewer time at effectively zero licensing cost. Ongoing cost is a version bump per release; the risk to manage is behavioral changes landing in patch versions, which we mitigate by pinning and reading changelogs.

For engineering: v1.13.32 extends the linter (separator and exception-rule checks) and removes the removeUnnecessaryWildcard fixer. Net effect: more issues surfaced, one fewer auto-remedied. Recommend adopting as a lint-only CI step first, pinning the version in composer.json, and trialing autofix locally before enabling in pipelines. Validate against a representative branch before rolling out broadly, and confirm no team depends on the removed fixer.