test(e2e): cover authorized approval responses

[benpankow]

Summary

Adds fixture-owned e2e coverage for the responder-authorized HITL lifecycle introduced by this stack.

The deterministic fixture authenticates the eval driver as a fixed user and defines a tool with explicit request and response policies:

approval: {
  request: always(),
  response: ({ response, responder }) =>
    response.decision === "approve" && responder.principalId === "e2e-approval-responder"
      ? { status: "allowed" }
      : { status: "rejected", safeReason: "Unexpected eval responder." },
}

The eval asserts:

input.requested
→ approval.candidate pending
→ approval.settled approved
→ action.result completed

It uses no external OAuth provider or injected credential, so the result is deterministic and self-contained.

This also adds compiler/runtime normalization coverage for the explicit { request, response } approval object; previously only the function shorthand was accepted by runtime normalization even though the public type allowed the object form.

Depends on #1374.

Validation

• pnpm --filter agent-tools-hitl typecheck
• pnpm --filter eve typecheck
• pnpm guard:invariants
• focused authored-definition unit tests

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
eve-docs	Error		Aug 8, 2026 1:16am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
eve-docs-4759	Skipped		Aug 8, 2026 1:16am

[vercel]

t.respond(...) is called with a bare input-response object instead of an array, so the HITL approval is posted as a malformed inputResponses body and the server rejects the turn with 400.

[vercel]

The OAuth eval passes an absolute authorization URL to t.target.fetch, which treats it as a route path and produces a mangled 404 URL, causing the eval to fail.