Nathan Flurry a171956298 feat(foundry): revert actions to queue/workflow pattern with direct sends ... Revert actor communication from direct action calls to queue/workflow-based patterns for better observability (workflow history in RivetKit inspector), replay/recovery semantics, and idiomatic RivetKit usage. - Add queue/workflow infrastructure to all actors: organization, task, user, github-data, sandbox, and audit-log - Mutations route through named queues processed by workflow command loops with ctx.step() wrapping for c.state/c.db access and observability - Remove command action wrappers (~460 lines) — callers use .send() directly to queue names with expectQueueResponse() for wait:true results - Keep sendPrompt and runProcess as direct sandbox actions (long-running / large responses that would block the workflow loop or exceed 128KB limit) - Fix workspace fire-and-forget calls (enqueueWorkspaceEnsureSession, enqueueWorkspaceRefresh) to self-send to task queue instead of calling directly outside workflow step context Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-16 18:46:53 -07:00
..
proposal-revert-actions-to-queues.md	feat(foundry): revert actions to queue/workflow pattern with direct sends	2026-03-16 18:46:53 -07:00
proposal-rivetkit-sandbox-resilience.md	feat(foundry): task owner git auth + manual owner change UI (#263)	2026-03-16 17:05:11 -07:00
proposal-task-owner-git-auth.md	feat(foundry): task owner git auth + manual owner change UI (#263)	2026-03-16 17:05:11 -07:00