fix(eve): accept scoped package names in eval target check

[BlackishGreen33]

What

eve eval now uses the same package-name normalization as agent discovery when it checks the target identity.

For a scoped package like @acme/agent, eval expects the runtime agent id agent instead of the full package name @acme/agent.

This fixes valid scoped-package projects failing before evals start:

Expected eval target "@acme/agent" at http://127.0.0.1:4275, but "agent" is responding there.

Closes #112.

How

readExpectedAgentName() now strips the npm scope from package.json.name before passing the expected name into the eval target handshake.

The existing target mismatch guard stays in place. If the current app is @acme/agent and the server responds as other-agent, eve eval still fails the handshake.

Tests / changeset

• Added a scenario regression for a project named @acme/agent, asserting that eve eval --url ... checks for agent.
• Kept the existing unit coverage for target identity mismatch behavior.
• Added a patch changeset for eve.

Verification

• fnm exec --using v24.15.0 pnpm --filter eve exec vitest run --config vitest.scenario.config.ts test/scenarios/eval-command-environment.scenario.test.ts
• fnm exec --using v24.15.0 pnpm --filter eve exec vitest run --config vitest.unit.config.ts src/evals/target.test.ts
• fnm exec --using v24.15.0 pnpm --filter eve run typecheck
• fnm exec --using v24.15.0 pnpm exec oxfmt --check packages/eve/src/evals/cli/eval.ts packages/eve/test/scenarios/eval-command-environment.scenario.test.ts .changeset/scoped-eval-target.md
• git diff --check

[vercel]

@BlackishGreen33 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.