[BUG/SECURITY]: redacted secrets persist in cleartext in the opencode.db event journal #52586

Description

Secret redaction doesn't cover the event journal in opencode.db. The redaction hook (tool.execute.after) fires once, after a tool completes — but streaming tools (bash/shell) write their raw output to the event table on every chunk while still running, before any hook can touch it. So the final completed row and the part row are redacted, but every intermediate running row keeps the raw, un-redacted output. The event table has no prune/expiry, so those cleartext secrets persist for the life of the DB.

Net effect: a user who turns on redaction sees clean model context and clean session history, but their API keys/tokens still sit in cleartext inside the same opencode.db — and travel with any backup/sync/copy of it. It's local-at-rest (not a remote exploit), but it's a security feature silently not applying to a durable store.

No plugin can fix this: there's no mutation-capable hook before the event INSERT (commitDurableEvent in packages/core/src/event.ts). The event plugin hook is a read-only post-commit listener.

Steps to reproduce

1. Run a streaming shell tool whose output contains a secret-shaped value (e.g. a command that prints an API key).
2. While it's running, OpenCode writes message.part.updated.1 events to the event table with the raw output in state.metadata.output.
3. Query the event table in opencode.db for running-status tool-part rows — the raw value is present in cleartext, and stays there permanently (no prune path).

The completed row and the part row are correctly redacted; only the intermediate running event rows retain the raw value.

Possible fixes (any one): a pre-INSERT transform hook in the event-store commit (this is the intent of the closed-unimplemented #28223); server-side redaction/truncation of streaming payloads before journaling; or retention/prune on the event table.

OpenCode version

1.18.34

Operating System

Rocky Linux 9.8

Terminal

tmux / various