Introduce PHPStan and PHPUnit infrastructure

[danijelgalic]

🪛 Generic / Task Pull Request

Related Issue

• Link the issue(s) this PR addresses:
  Closes PHPStan and PHPUnit infrastructure #3

Description

This PR introduces foundational development tooling into the FireHub Core repository by integrating PHPStan for static analysis and PHPUnit for automated testing.

The goal is to establish a strict quality assurance baseline that ensures type safety, architectural consistency, and regression protection across the Core layer.

What this introduces

• PHPStan configuration for static type analysis
• PHPUnit setup for unit testing support
  Base directory structure for tests
• Composer scripts for analysis and test execution (if applicable)
• Initial foundation for future CI quality gates

Purpose

This change introduces and formalizes the development-time quality infrastructure for the Core Standard repository using PHPStan.

It ensures that all Core components are validated before merge through a centralized static analysis setup, enforcing strict architectural and type-safety guarantees across the FireHub ecosystem.

This establishes a clear separation between:

• Core runtime logic (framework behavior)
• Development-time validation layer (static analysis via PHPStan)

Changes

Implementation

• Added phpstan.neon configuration file for project-level static analysis setup
• Introduced GitHub Actions workflow PHPStan.yml
  • Runs PHPStan on every pull_request
  • Enforces static analysis before merge
• Updated .gitattributes
  • Added /phpstan.neon export-ignore to exclude configuration from distribution artifacts
• Updated composer.json:
  • Added development dependencies:
    • phpstan/phpstan
    • the-firehub-project/phpstan-rules: dev-develop
  • Integrated FireHub shared PHPStan ruleset into Core Standard

Dependencies

• Added:

  • phpstan/phpstan:^2.0
  • the-firehub-project/phpstan-rules:dev-develop

• Updated:

  • Development tooling stack for Core Standard validation layer

Compatibility

• Backward compatibility:
  • Yes
  • No (explain below)

No runtime changes introduced. All changes are strictly development-time tooling and CI validation.

Testing

Verification

• Manual testing performed
• Changes verified locally
• No unintended side effects are observed

Automated Tests

• Unit / integration tests are added (if applicable)
• All CI checks pass

Documentation

• Documentation updated (if relevant)
• Changelog updated (if applicable)

Checklist

• Issue linked
• Task clearly described
• No unrelated changes are included
• Code follows FireHub standards

Risks / Impact

• Risk level:
  • None
  • Low
  • Medium
  • High

Potential Impact

• Existing codebase may surface hidden type-safety or architectural violations under PHPStan analysis
• CI may fail on previously untyped or loosely typed code paths
• Developers may need minor adjustments to satisfy strict analysis rules

Areas Requiring Attention

• Alignment between phpstan.neon and shared FireHub ruleset
• Stability of dev-develop branch dependency for phpstan-rules
• CI consistency across all Core repositories

Notes

Technical Notes

• PHPStan is now an enforced architectural validation layer, not just a development tool
• Configuration is intentionally separated from runtime logic
• .gitattributes ensures tooling config does not leak into distribution artifacts

Reviewer Notes

Focus on:

• correctness of CI enforcement model (PR-only execution)
• proper separation between runtime and development-time concerns
• stability of dependency on phpstan-rules (dev-develop)
• long-term maintainability of shared static analysis architecture