V2: remove V1 event surface after cutover (tracking) #35054

Tracking issue so the V1 event surface is removed deliberately, in one sweep, after V2 cutover. Collected while working #35021 (event audit), which intentionally deletes nothing V1.

Inventory to remove

Legacy definitions and manifests

• packages/schema/src/v1/* legacy event definitions
• Compatibility entrypoints that remain outside that subtree:
  • packages/schema/src/session-v1.ts
  • packages/schema/src/filesystem-v1.ts
  • packages/schema/src/legacy-event.ts
  • packages/schema/src/permission-v1.ts
  • packages/schema/src/question-v1.ts
• Core compatibility facades:
  • packages/core/src/v1/session.ts
  • packages/core/src/v1/permission.ts
• Standalone V1-only event modules:
  • packages/schema/src/ide-event.ts (ide.installed), dead remnant of the old automatic IDE-extension install/toast flow
  • packages/schema/src/session-compaction-event.ts (session.compacted), superseded by current compaction lifecycle events
  • packages/schema/src/project.ts (project.updated legacy event definition)
  • packages/schema/src/lsp-event.ts (lsp.updated)
  • packages/schema/src/mcp-event.ts (mcp.browser.open.failed), already excluded from the current MCP inventory but still published by V1
• packages/schema/src/session-status-event.ts, V1-only and not in ServerDefinitions; still published by packages/opencode/src/session/status.ts. Its retry status union (attempt/message/action/next/isRetryable) is condemned vocabulary.
• EventManifest session V1 splits (sessionV1Durable/sessionV1Live) and compatibility-only entries in the full Definitions map (packages/schema/src/event-manifest.ts)

Active compatibility bridges

• EventV2Bridge (packages/opencode/src/event-v2-bridge.ts)
• Current Core's remaining V1 durable bridge:
  • packages/core/src/session.ts publishes session.created through SessionV1.Event.Created
  • packages/core/src/session/projector.ts projects session.created, session.updated, session.deleted, message.updated, message.removed, message.part.updated, and message.part.removed
• V1 publishers for the standalone events above, including packages/opencode/src/session/compaction.ts, project/project.ts, lsp/lsp.ts, and mcp/index.ts

Consumers to migrate or remove

• packages/app V1 event consumers:
  • src/context/global-sync/event-reducer.ts
  • src/context/server-session.ts
  • src/context/permission.tsx
  • src/context/notification.tsx
  • src/pages/layout.tsx
  • pages/session/usage-exceeded-dialogs.tsx
• Current TUI transitional V1 subscribers:
  • packages/tui/src/app.tsx
  • packages/tui/src/feature-plugins/system/notifications.ts
• V1 CLI run stream consumers once the V2 CLI replaces opencode run:
  • packages/opencode/src/cli/cmd/run/noninteractive.ts
  • packages/opencode/src/cli/cmd/run/stream-v2.transport.ts
  • packages/opencode/src/cli/cmd/run/stream-v2.subagent.ts
  • packages/opencode/src/cli/cmd/run/session-data.ts
  • associated tests
• V1 retry implementation once V2 runner retry matures (V2: port V1 LLM retry policy into opencode #35002):
  • packages/opencode/src/session/retry.ts
  • packages/opencode/src/session/status.ts
  • retry paths in packages/opencode/src/session/processor.ts

Generated surfaces and tests

• Regenerate or retire legacy event unions in:
  • packages/sdk/openapi.json
  • packages/sdk/js/src/v2/gen/types.gen.ts
  • packages/sdk/js/src/gen/types.gen.ts
  • packages/codemode/test/fixtures/opencode-v2-openapi.json
• Legacy contract tests:
  • packages/schema/test/legacy-event.test.ts
  • packages/schema/test/v1-isolation.test.ts
  • packages/core/test/legacy-event-schema.test.ts
  • V1 assertions in packages/opencode/test/event-manifest.test.ts

Keep out of this sweep

• mcp.tools.changed is an active internal V2 Core event.
• server.connected is actively synthesized and consumed by current clients.
• vcs.branch.updated, installation.updated, and installation.update-available are current public events.
• Workspace/worktree lifecycle events and global.disposed need separate product decisions; they are not automatically obsolete just because their current implementation crosses legacy paths.

Notes

• specs/v2/schema-changelog.md stays historical; never rewrite old entries.
• Blocked on V2 CLI replacing opencode run and packages/app migrating to the V2 stream.