Skip action if response already sent by init hook

[loks0n]

Summary

• Init hooks (e.g. a cache layer) can call $response->send() to deliver a cached response directly to the client
• Without this guard, the framework still runs the route action immediately after — doing the full work pipeline before discovering the response was already sent and silently no-op'ing the second send()
• This adds a single isSent() check before dispatching the action; shutdown hooks still run so metrics, billing, and teardown logic are unaffected

Test plan

• Verify that a route whose init hook calls $response->send() no longer executes the action
• Verify that shutdown hooks still execute after a sent-in-init response (metrics, billing, etc.)
• Verify normal request flow (no init hook sends) is unchanged

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR adds a guard in execute() that skips the route action when an init hook has already called $response->send() (e.g., a cache layer), while keeping shutdown hooks running. A follow-up fix commit restores the Response parameter to execute(Route, Request, Response) — which had been dropped in 0.34.x compared to 0.33.x — so the $response->isSent() check is properly in scope. The DI-registered response and the parameter passed to execute() are the same object instance (set in runInternal()), so the isSent() flag propagates correctly between hook and guard.

Confidence Score: 5/5

Safe to merge — the critical undefined-variable bug from the first commit is fully resolved, and the guard logic is correct.

The only open concern (missing test for the isSent() guard) was already flagged in a prior review thread and is P2. No new P0/P1 issues remain: the $response parameter is properly in scope, the same object instance is shared between the DI container and the guard, and shutdown hooks are correctly unaffected.

No files require special attention.

Important Files Changed

Filename	Overview
src/Http/Http.php	Adds Response $response as a third parameter to execute() (restoring 0.33.x API) and guards the route action dispatch with if (!$response->isSent()); shutdown hooks are unaffected and correctly still run.
tests/HttpTest.php	All execute() call sites updated to pass new Response() as the third argument; no test added for the new isSent() guard behaviour (init-hook-sends-then-action-skipped scenario is untested).

_{Reviews (2): Last reviewed commit: "Fix: pass Response to execute() so isSen..." | Re-trigger Greptile}

[greptile-apps]

No unit test for the new guard

The PR description lists three test-plan items (all unchecked). There is no new test case in tests/HttpTest.php or the e2e suite that verifies an init hook calling $response->send() actually skips the route action while still executing shutdown hooks. Without a test, a future refactor could silently regress this behavior.