[marcusrbrown]

Moves the harness base from OpenCode 1.19.0 to 1.19.4 and keeps all 15 carries. The @opencode-ai/sdk bump to 1.19.4 is in the same PR, so the server and the SDK move together.

Carries. None was merged upstream, and none has met its removal condition. I simulated merging the carries onto the v1.19.4 tag in config order, and the result matches the one at 1.19.0:

• Nine carries merge cleanly.
• Three have trivial conflicts, which resolve as the ledger describes: fix(opencode): bound SSE event backlogs and disconnect stalled consumers anomalyco/opencode#31922, fix(opencode): evict idle per-directory instances to bound serve memory anomalyco/opencode#33713 and fix(core): bound npm installs with a configurable timeout anomalyco/opencode#47430.
• Three need the resolver: fix(session): fire system.transform before messages.transform anomalyco/opencode#19961, fix(core): tolerate orphan part projection from cascade-delete race anomalyco/opencode#33134 and fix(core): retry transient SQLite lock-timeouts on durable event commits anomalyco/opencode#33159.

The conflicting files and hunk counts match the ledger. No carry head pulls extra commits onto the tag.

Upstream changes between 1.19.0 and 1.19.4 that matter here. Most of the code the Action, gateway and runtime use is unchanged: tool/task.ts, the session, permission, question and storage code, the /event handler (server.connected is still emitted first), the SDK's lazy SSE stream and its opencode serve spawn, the database migrations and instance dispose. Four things did change:

• Bun. Upstream's packageManager moved from bun@1.3.14 to bun@1.4.4. The harness build requires an exact match, so HARNESS_BUN_VERSION, the harness-release bun-version inputs and the Renovate Bun cap move to 1.4.4. The existing drift test keeps those three in step.
• Update check. It now reads npm for every install method and ignores build metadata, so <base>+harness.<sha> no longer counts as older than <base>. opencode serve still never runs the check. The harness README is corrected.
• Session sharing is discontinued upstream. We don't use it.
• reasoning_options is a new optional provider option. It is additive, and type checks stay clean.

script/build.ts adds --libc="*" to its native installs. The build-platform patch still applies, which I checked against the real v1.19.4 file.

Live checks against stock 1.19.4. These are the same as on 1.19.0:

• the event subscription is lazy, events aren't replayed, and server.connected is the first frame;
• /instance/dispose refreshes a stale file listing;
• the question tool isn't registered with OPENCODE_CLIENT=fro-bot-action;
• an early abort is honoured on a warm server.

On a cold server, meaning the first prompt the process handles, an early abort isn't honoured, and that is true on 1.19.0 as well. #1958 tracks it.

Other changes:

• The Renovate cap for anomalyco/opencode and @opencode-ai/sdk moves to <=1.19.4.
• The clonedeps manifest and the AGENTS.md source pins move to v1.19.4. So does the wiki's source pin, and the carry ledger's verified version and line references.
• The build-platform verification note and the provenance test expectation are updated.
• DEFAULT_OPENCODE_VERSION and the workspace image pin move when harness-release syncs them after publish.

[fro-bot]

Verdict: PASS

No actionable regression found in the 15-file diff. SDK manifests and lockfile agree on 1.19.4; release-job Bun pins match upstream's 1.4.4 declaration. The upstream target-selection block remains compatible with the harness patch.

Blocking issues

None

Non-blocking concerns

None

Missing tests

None identified for the changed pins. Existing provenance, pin-invariant, carry-ledger, and build-platform tests cover the relevant contracts. Tests were inspected, not executed.

Risk assessment (MED): likelihood of regression, security exposure, or blast radius

The upstream runtime and Bun compiler change has release-wide reach, though this diff introduces no new permissions or public API changes. Carry integration and platform binaries still depend on CI/release validation; the author's live probes were not independently reproduced.

---

Run Summary

Field	Value
Event	pull_request
Repository	fro-bot/agent
Run ID	40465701590
Cache	hit
Session	ses_e83c8f37bffew4aH0pOkFsU77E
Scope	All 15 changed files and relevant build/release/test context; checkout unchanged
Verification	Static review and upstream tagged-source inspection; no build, lint, type-check, or test suite executed
Focused probe	bun --version reported 1.3.14. bun install --help and bun install '--libc=*' --help inspected flag handling; bun install '--libc=*' --dry-run --ignore-scripts --no-save exited successfully, ruling out immediate argument rejection, not proving upstream build compatibility
Review tooling	Three read-only reviewer passes returned no findings; packaged synthesis validation was unavailable because reference access was denied, so their payloads were withheld from formal synthesis. Verdict is based on direct source inspection