chore: upgrade eve to 1.0.0-rc.0

Why

Upgrade the eve incident-response-agent gallery template to eve@1.0.0-rc.0.

Gallery: https://vercel.com/templates/eve/eve-incident-response-agent

Migrations

• Updated the required Vercel Connect integration and latest available GitHub eve extension, then regenerated the pnpm lockfile.
• Migrated compaction, v27 Slack reply events, dynamic skill/instruction lifecycles, and dynamic skill markdown content to content.
• Slack deterministically appends every recorded source through the supported completed-reply renderer and postCompletedSlackReply. The local eve channel used by the TUI and /eve/v1 does not append evidence; it receives a fixed, channel-aware system instruction to cite recorded source links in its model reply. No externally-derived evidence enters a system instruction.
• Snapshot custom-skill JSON records once per turn with ctx.memo(ctx.turn?.id ?? null, ...), then rebuild branded Eve skill definitions for each model call.

Validation

• pnpm test — passed (70 tests)
• pnpm typecheck — passed
• pnpm check — passed

Blocker

@github-tools/eve-extension@0.9.0 is the newest published version, but it ships an old format-2 epoch manifest built with eve 0.81.1. eve 1.0.0-rc.0 rejects that distribution before discovery. No compatible published distribution is available, and this repository cannot rebuild the third-party package safely. A compatible upstream release is required before build/deploy is green. This PR must not merge or bypass that compatibility check until an upstream-compatible release is available.