Wake agents from verified workflow mentions

[loganj]

🤖
I’m Larry.

Summary

Workflow-generated messages that explicitly mention an agent can now wake that agent automatically. The wake carries identifiers, not instructions: the harness retrieves the exact signed workflow revision and generated message, verifies their relationship to the run and recipient, then admits the message under the workflow author’s existing sender policy. The visible message cannot independently bypass that verification path.

• Persist the visible message, thread metadata, mentions, and recipient wakes in one transaction before fan-out. Committed wakes remain available for historical delivery after a connection or fan-out interruption.
• Restrict wake reads and delivery to the authenticated recipient with current relay and channel membership, including open channels. Client-authored wakes are rejected; wake records are excluded from full-text search.
• Retain a run’s captured revision across normal workflow replacement, while explicit deletion revokes it. Verification never substitutes the latest definition.
• Recover transient authority-read failures through paced retries and exact, recipient/channel-filtered replay. Storage outages, replay-guard outages, and interrupted response bodies remain fail-closed but retryable; proven denial and complete malformed authority remain terminal.
• Accept equivalent UUID spellings and valid templated channel targets without relaxing the executor’s bound-channel restriction.

Related issue

Stacked on #6960, which captures the exact signed workflow revision for new runs. This slice adds automatic mention waking only; manual owner-trigger behavior and legacy-run migration remain separate. Older runs without a captured signed revision continue sending messages but do not produce automatic wakes.

Migration and rollout

Migration 0042 excludes wake kind 44620 from the stored search vector while preserving the database’s existing policy for other kinds. It rewrites the events table and rebuilds its GIN index under an ACCESS EXCLUSIVE lock; account for this in the relay rollout window.

Migration 0043 records positively identified workflow supersession. Historical soft-deleted revisions with an unknown deletion reason are not backfilled as trusted authority and remain denied. This is not a general exactly-once execution guarantee.

Testing

At 24922e14458297c7fba340bf18be195882b98a23, Blox validation passed full ACP (850) and relay (1001 + 13) tests, all eight explicitly enabled PostgreSQL/Redis workflow lifecycle regressions, 11 workflow and 11 replaceable-event PostgreSQL tests, the full search suite (3 unit + 19 PostgreSQL), workspace clippy and formatting, just test-unit, Tauri clippy/tests, and the differential file-size gate.

Lifecycle coverage includes authenticated deletion after replacement; HTTP query/count, historical WebSocket REQ/COUNT, and live delivery before/after member removal; atomic rollback and post-commit historical recovery; and interrupted-authority recovery through the actual transport replay machinery. The recovery tests drive fetch/replay/verification directly rather than the complete outer agent dispatch loop.

[ryanshepps]

Need this!

[loganj]

🤖
I’m Larry. The restacked candidate 24922e14458297c7fba340bf18be195882b98a23 is ready for human review on foundation #6960 (bb7de1e37872746cec63a1c7b1feda4a242b32b9).

The integration preserves the reviewed wake, authority, atomic persistence, revocation, and recovery behavior. Database delivery follows the new store/ boundary with fixed-name datastore spans. Main’s push migration remains 0040; workflow revision capture is 0041, wake FTS 0042, and supersession authority 0043.

Exact-head Blox validation passed: ACP 850+9, DB 114+2, relay 1001+13, workflow 169; workflow PostgreSQL 11, wake lifecycle 8, replaceable PostgreSQL 11, search 3+19; workspace clippy/fmt, unit suites, Tauri clippy/full tests, and file-size checks. All 43 migrations applied to a fresh disposable database. Prior scoped reviews remain applicable to unchanged behavior; this structural restack did not restart a whole-PR review cycle.

GitHub reports 29 successful checks, four intentional skips, none pending/failing, with CLEAN / MERGEABLE. This candidate’s CI required no rerun.

• CI: https://github.com/block/buzz/actions/runs/33213704322
• Docker: https://github.com/block/buzz/actions/runs/33213704212
• Mesh: https://github.com/block/buzz/actions/runs/33213704296

The PR remains draft. Human GitHub approval is still outstanding. Recovery coverage exercises actual transport replay rather than the complete outer dispatch loop; migration 0042 requires an exclusive table rewrite/index rebuild during rollout.