test(evals): accept handleAuthkitProxy and app-owned AuthKitProvider modules

[nicknisi]

What

Two eval graders were rejecting valid integrations. Both false negatives came from the Opus 5.5 eval run in #261:

• Next.js: accept handleAuthkitProxy( as well as handleAuthkitHeaders(. In @workos-inc/authkit-nextjs 4.4.0, handleAuthkitHeaders is a @deprecated alias of handleAuthkitProxy.
• React: look for AuthKitProvider (and the env-based config next to it) anywhere in src/**/*.tsx, not only in src/{main,index}.tsx. Wrapping the provider in an app-owned provider module is valid, and the React skill doesn't require a specific file.

The companion skills change (workos/skills#53) updates the Next.js reference to recommend handleAuthkitProxy, so this grader change is needed before that lands.

Verification

• bunx vitest run tests/evals: 101 passed
• With the trimmed skills from fix: update skills for current SDKs and frontier models skills#53, the 34 JS scenarios pass 34/34 on both claude-opus-4-5-20251101 and claude-opus-5-5 (requires chore(deps): bump claude-agent-sdk to 0.3.295 for Opus 5.5 support #261 for the Opus 5.5 SDK).

[greptile-apps]

Confidence Score: 4/5

[Medium impact] Updates evaluation tests for authentication provider detection.

The PR still needs to check that the app actually renders the React provider before it appears safe to merge.

Findings

1.  Unused provider passes grading ▶

Fix with agent prompt

### Issue 1
tests/evals/graders/react.grader.ts:undefined-32
If `src/auth/Providers.tsx` imports and renders `AuthKitProvider` and reads the environment config, this search accepts it even when the entry file never mounts it. A component using `useAuth` and a successful build can satisfy the remaining checks, so an app without the provider can receive a passing grade. Check that the matched provider is connected to the entry file.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The PR accepts both Next.js helper names and allows React’s AuthKitProvider to live in an app-owned module.

• Next.js evals accept both AuthKit handler names.
• React evals recognize provider modules imported by app code.

_{Reviews (2) · Last reviewed commit: "test(evals): require mounted AuthKitProv..." · Reviewed by Greptile}

[greptile-apps]

Unused provider passes grading

If src/auth/Providers.tsx imports and renders AuthKitProvider and reads the environment config, this search accepts it even when the entry file never mounts it. A component using useAuth and a successful build can satisfy the remaining checks, so an app without the provider can receive a passing grade. Check that the matched provider is connected to the entry file.

Prompt To Fix With AI

This is a comment left during a code review.
Path: tests/evals/graders/react.grader.ts
Line: 32

Comment:
**Unused provider passes grading**

If `src/auth/Providers.tsx` imports and renders `AuthKitProvider` and reads the environment config, this search accepts it even when the entry file never mounts it. A component using `useAuth` and a successful build can satisfy the remaining checks, so an app without the provider can receive a passing grade. Check that the matched provider is connected to the entry file.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.