Repository navigation
Keep Pathwise development and release validation framework independent - #25
Merged
Merged
Conversation
abmmhasan
marked this pull request as ready for review
October 10, 2026 03:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pathwise's development setup and release gates depended on an unavailable Foundation 3.0.1 pin. Remove that framework dependency and its unused packages. The comparison, HTTP load and lifecycle fixtures now call Pathwise directly; optional Runwire 2.1.1 context forwarding remains host-owned.
Preserve all existing performance/error/resource budgets, source-isolated comparisons, streamed small/large/range responses, concurrency profiles and request-isolation checks. Production-only CI exercises direct downloads with Foundation, Webrick and Runwire absent. PHP support fixtures, regression references and documentation now describe framework-neutral ownership. An owner with no Runwire binding returns before inspecting the current Fiber; bound-context checks remain active.
Final revision: 954aa9a. Exact-revision CI passed all 19 executed jobs, including Windows, lowest/stable dependency lanes, security/analyzers, adapters, production-only installation, optional Runwire forwarding, release stress and matched performance on both PHP versions.
Validation:
All hosted profiles met the unchanged 2% median RPM regression limit. Every HTTP phase had zero response errors and met latency/resource budgets. Both 30-second bound soaks had zero descriptor growth and less than 300 KiB RSS growth.
Local PHP 8.5.4 measurements initially exceeded the c64 limit by about 3%; the guard's targeted repeat met it, but large throughput variance prevents attributing that difference to the guard alone. The final independent hosted matrix supplies acceptance evidence for the defined fixture. These results do not guarantee throughput on other hardware, PHP patches or application workloads; no budget was relaxed.