fix(opencode): bump runtime for session schema compatibility

[snvtac]

Summary

• Bump the bundled OpenCode sidecar from v1.17.3 to v1.17.11.
• Bump all direct @opencode-ai/sdk consumers to ^1.17.11 and update the lockfile.

Why

• Closes [Bug]: Cannot create new session #2370.
• Users can hit SQLiteError: no such column: replacement_seq when OpenWork's pinned OpenCode runtime handles a session prompt against a DB schema where upstream OpenCode has already removed that column.
• Upstream OpenCode v1.17.11 contains the migration/schema compatibility fix path noted in ci(core): reject downgrade-incompatible database migrations anomalyco/opencode#33898.

Issue

• Closes [Bug]: Cannot create new session #2370

Scope

• OpenCode sidecar version pin in constants.json.
• Direct SDK dependency pins in app, desktop, server, orchestrator, and opencode-router packages.
• Minimal lockfile update for @opencode-ai/sdk@1.17.11.

Out of scope

• No OpenWork session UI or server route behavior changes.
• No OpenCode DB repair/migration code in OpenWork.

Testing

Ran

• pnpm install --frozen-lockfile --ignore-scripts --store-dir ../pnpm-store
• git diff --check
• pnpm --filter openwork-server typecheck
• pnpm --filter @openwork/app typecheck
• pnpm --filter @openwork/desktop typecheck:electron
• pnpm --filter opencode-router typecheck
• pnpm --filter openwork-orchestrator typecheck
• PATH=$PWD/../opencode-bin/extract:$PATH HOME=$PWD/../opencode-e2e-home XDG_DATA_HOME=$PWD/../opencode-e2e-data XDG_CONFIG_HOME=$PWD/../opencode-e2e-config OPENCODE_DISABLE_AUTOUPDATE=1 OPENCODE_CHANNEL=local OPENCODE_CLIENT=openwork-e2e node apps/app/scripts/e2e.mjs --dir "$PWD"
• sqlite3 ../opencode-e2e-data/opencode/opencode.db "pragma table_info('session_context_epoch');"

Result

• pass: frozen lockfile install reported lockfile up to date and supply-chain policy passed.
• pass: all five SDK consumers typechecked.
• pass: real OpenCode v1.17.11 smoke returned healthy: true, created a session, ran session.prompt noReply, and wrote 1 message.
• pass: the smoke DB's session_context_epoch columns were session_id, baseline, snapshot, baseline_seq; replacement_seq was absent while prompt write still succeeded.

CI status

• pass: not run remotely yet; local gates above passed.
• code-related failures: none observed.
• external/env/auth blockers: full AI model call skipped because the regression is in prompt/session DB setup and the local smoke intentionally used noReply to avoid requiring provider credentials.

Manual verification

1. Downloaded the v1.17.11 darwin-arm64 OpenCode release asset used by constants.json.
2. Started opencode serve from that binary with isolated HOME/XDG dirs.
3. Verified session.prompt noReply succeeds on a DB schema without replacement_seq.

Evidence

• Runtime smoke output: health.version = 1.17.11, session.prompt noReply status ok, message count 1.
• Schema check: session_context_epoch has no replacement_seq column.
• Video/screenshot: N/A; this is a backend/runtime DB compatibility path validated by scripted smoke output.

Risk

• Low-to-medium: this updates the embedded OpenCode runtime across OpenWork consumers. Typechecks passed and the release asset exists for supported sidecar platforms.

Rollback

• Revert this PR to restore OpenCode/SDK 1.17.3 pins.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-landing	Ready	Preview, Comment, Open in v0	Jun 26, 2026 8:54am

[vercel]

@snvtac is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

[cubic-dev-ai]

No issues found across 7 files

_{Re-trigger cubic}

[fussdeek-del]

LGTM, so far nothing unusual found.