feat(eve): add Eve agent-framework MCP connection helper

[benfrank241]

What

Adds a first-party Eve integration: @vectorize-io/hindsight-eve, a thin helper that wraps Eve's defineMcpClientConnection so an Eve agent gains Hindsight long-term memory by dropping one file under agent/connections/:

// agent/connections/hindsight.ts
import { defineHindsightConnection } from "@vectorize-io/hindsight-eve";
export default defineHindsightConnection(); // reads HINDSIGHT_MCP_URL + HINDSIGHT_API_KEY

The helper pre-fills Hindsight's MCP endpoint, a model-facing description, and bearer auth, with env-var defaults (HINDSIGHT_MCP_URL, HINDSIGHT_API_KEY, HINDSIGHT_MCP_BANK_ID). Supports tool filters and human-in-the-loop approval passthrough. The model sees connection__hindsight__{recall,retain,reflect}; URL/token never reach it.

Why a draft / backup

The preferred home for this is Eve's own connection catalog — proposed upstream in vercel/eve#55. That hinges on a maintainer decision about non-Connect (bearer) auth. This in-repo integration ships value to Hindsight users regardless of that outcome, and remains a convenience wrapper even if the catalog entry lands. Keeping it draft until the upstream direction is settled.

Shape

Mirrors the ai-sdk integration exactly:

• src/index.ts — pure resolveHindsightConnection (env/option precedence + Cloud-needs-key validation) + buildHindsightConnectionDefinition + defineHindsightConnection.
• vitest (12 tests, incl. a real-eve smoke test) + tsup build, own package-lock.json.
• test-eve-integration CI job (Node 24, per Eve's engine requirement) wired into report-pr-status.
• Registered in release-integration.sh and generate_changelog.py.
• Docs gallery entry + docs-integrations/eve.md (passes check-integrations.mjs).

Checks

npm test / npm run build, check-integrations.mjs, check-integration-lockfiles.sh, and lint.sh all green locally.

Follow-up

• static/img/icons/eve.svg is a placeholder wordmark — swap for the official Eve mark before release.