Product Decisions This Supports

Informs the build-vs-buy decision for running PHP workloads on a persistent application server: adopting luzrain/phpstreamserver-bundle is cheaper than building custom worker lifecycle, request termination, and upload-cleanup plumbing.
Supports roadmap work for upload-heavy APIs or dashboards running under long-lived PHP workers, where orphaned temp files can accumulate and cause disk-pressure incidents.
Signals that file-upload cleanup is now tied to the kernel.terminate lifecycle event, which is relevant for features that inspect or move uploaded files after the response is sent.
The added deletion tests reduce regression risk for file-handling flows, making it safer to commit to upload features on this runtime.
Helps prioritize operational hardening work over new features: v0.2.2 is a patch-level reliability improvement, not a new capability.

When to Consider This Package

Consider it when the team is running or evaluating PHPStreamServer and needs framework-level integration rather than hand-rolled bootstrap code.
Strong fit for long-running PHP workers, upload endpoints, and applications that need deterministic cleanup after request termination.
Also consider when the team can tolerate a 0.x dependency and wants test-backed behavior around worker lifecycle and file cleanup.
Look elsewhere if the stack is standard PHP-FPM/nginx, if no persistent-worker runtime is planned, or if the organization requires a mature 1.x ecosystem with long-term support guarantees.
Audit first if application code reads uploaded temp files after the response or relies on the exact moment of deletion: v0.2.2 changes cleanup timing by moving deletion to the kernel.terminate listener.

Executives: This is a small but operationally meaningful patch. It reduces the risk of disk leaks in always-on PHP workers by ensuring uploaded files are deleted during the request termination lifecycle, with new tests covering the behavior.
Engineering: The bundle integrates PHPStreamServer into the framework and now handles uploaded-file deletion in kernel.terminate. No new API is introduced; the main consideration is verifying that no application logic depends on temp files surviving past response termination. Added tests lower regression risk.
Product: Treat this as infrastructure de-risking for upload-heavy features on persistent workers. Keep the package on the roadmap as a runtime dependency, but continue monitoring 0.x stability and lifecycle-hook behavior before making it foundational to critical paths.