fix(runtime): persist external tool effects

[AsperforMias]

Summary

• Persist MCP external-effect intent, attempt, result, and unknown-fence state in D1.
• Redeliver a durable MCP result after terminal-receipt loss without invoking the provider again.
• Require Driver protocol v2 and a durable effect ledger for MCP execution.

Why

• Closes fix(runtime): persist uncertainty for external tool effects #412: a Driver restart could otherwise replay a write-capable MCP call after an ambiguous terminal delivery.

Verification

• Commands: just db-reset-local; just check; just e2e deterministic session-log
• Manual/local fault injection: actual local D1 plus real Driver Dispatcher simulates provider success followed by lost terminal delivery, restarts the Dispatcher, and asserts exactly one provider call.
• Not run: live remote MCP or Cloudflare resources (not available).

Impact

• User/API/contract changes: Driver control protocol v2; an unknown effect fails closed with its durable effect ID.
• Generated files / GraphQL / DB / lockfile: additive 0005_external-tool-effects plus Drizzle snapshot/journal; no GraphQL or lockfile changes from this PR.
• Env or config changes: none.
• Risk and rollback: deploy API and Driver protocol v2 together. Migration is additive; old Driver versions are intentionally rejected to prevent unsafe execution.

Review

• Closest review areas: Driver RPC, API runtime persistence, D1 migrations, Agent Driver MCP dispatcher.
• Known trade-offs: generic MCP has no universal reconciliation/compensation protocol, so unknown effects never auto-replay. Follow-up feat(runtime): reconcile external tool effects for idempotency-capable MCP providers #446 tracks provider-specific reconciliation.
• Dependency: draft until fix(runtime): persist external tool effects mosoo-agent-driver#89 lands on fix/openai-app-server-init-stop-race, making the submodule gitlink available from its canonical upstream URL.

[AsperforMias]

这个要driver那边的#89先合 @Yevanchen