chore(drive): release 2.0.0 on the current V2 stack

[kitlangton]

Why

The published Drive 1.4.5 still uses Effect beta.101 and an older V2 client, while the compatibility migration in #67 is merged but unreleased. OpenCode has now published its coherent Effect rc.112 client/protocol/schema stack, so this release can align with current V2 without mixing exact Effect requirements.

What Changes

Dependency	Published 1.4.5	Main before this PR	Release 2.0.0
Effect / platform packages	4.0.0-beta.101	4.0.0-rc.111	4.0.0-rc.112
OpenCode client	0.0.0-next-17010	0.0.0-dev-18516	0.0.0-dev-18535
Effect contract	runtime dependency	exact peer rc.111	exact peer rc.112

• Align the exact Effect peer, platform/test pins, catalog workspace, and lockfile with the published client and its matching protocol/schema packages.
• Consume the existing major Changeset and other already-merged pending Changesets through release:version, producing 2.0.0 once.
• Ship the fix(drive): update Effect and OpenCode V2 compatibility #67 dynamic-tool migration: progress({ phase }) replaces progress({ structured: { phase } }), and context.id replaces context.callID. finish({ structured, content }) retains its contract.
• Add a reusable manual release probe for two server generations, fresh TUI name reuse, persisted sessions, queued replies, capture/PNG, and teardown.

Scope

This PR updates compatibility pins and versions the already-merged release contents; it does not change the LLM sequencing language or OpenCode/TUI product code. Publishing remains the existing tag-triggered OIDC bun run release workflow after a normal green-CI merge.

An additional existing-TUI reconnect probe on OpenCode V2 38bffc9db1b04010d0cfe317dabe802b2533270d found that the TUI observes a fresh title after server replacement but loses its agent/model footer and leaves the next prompt unadmitted. This reproduced before this PR's Drive changes and is tracked separately; fresh-TUI relaunch verification does not prove existing-TUI reconnect submission works.

Verification

# Drive repository root
bun run release:version
bun install
bun run release:validate

# apps/catalog
bun run check

# packages/drive; OPENCODE_DRIVE_DEV points to an isolated V2 checkout
bun run drive run test/manual/current-v2.ts
bun run drive check test/manual/current-v2-relaunch.ts
OPENCODE_DRIVE_DB=release-relaunch.sqlite bun run drive start \
  --name drive-rc112-relaunch --script test/manual/current-v2-relaunch.ts \
  --dev "$OPENCODE_DRIVE_DEV"
npm pack --dry-run --json
bun pm pack --destination ../../.tmp

# Clean consumer installed from the packed tarball
bun exports.ts
bun typecheck
./node_modules/.bin/opencode-drive --version

• Drive release validation: 244 Effect tests and 58 CLI integration tests passed; lint/typecheck/pack dry-run passed. The existing recording/marks.ts unsafe-assertion lint warning remains unchanged.
• Catalog: 40 tests, generated-data check, lint, types, and build passed.
• Current V2 simulation package: 42 tests and typecheck passed with isolated config/cache/data/state.
• Source and packed CLI: negotiated UI/backend handshake, queued replies, title routing, static/dynamic tool progress and context, capture/PNG, settlement, and checked fresh-TUI two-generation relaunch passed against V2 38bffc9d using simulated providers only.
• Packed artifact: 102 files; inspected executable bin, source exports, fonts, and docs; no tests, TSX transforms, temporary files, or credentials shipped.
• Clean consumer: all seven public exports imported, Bun typecheck passed, CLI reported 2.0.0, and Drive/platform/client/protocol/schema resolved one Effect rc.112 runtime without overrides.