Test runs record every outward delivery instead of sending it #295
Notifications
Due Date
No due date set.
Blocks
Depends on
Reference: sam/archie#295
Reference in new issue
Block a user
A test run (Task.IsTestRun) today only wraps the forge client and worktree pushes (workflow.SuppressForgeWrites, forgerpc/worktreerpc refusals). Every other destination (channel posts, webhooks/HTTP, write-capable MCP tools, commands with network) acts for real. A forge is just one output destination (AGENTS.md), so the rule must not name it.
Wanted: a test run reads anything its caller could; every delivery to any destination is recorded as 'would ...' and not performed. The forge is one case.
Done when: a test run of a workflow that delivers through a non-forge destination records what it would have done and performs none of it; forge-specific names (SuppressForgeWrites, KindForgeSuppressed, 'forge writes are suppressed', the Test tooltip) give way to the generic rule.
Notes
Implementation: recorder on TaskContext delivery capability (deletes SuppressForgeWrites/KindForgeSuppressed/forge-specific wording) plus record-and-short-circuit in egress.Proxy for Kit runs. Native (non-Kit) containers have direct network and no proxy seam; that gap belongs to archie-core-n8d3, not here.
Close reason
Test runs record every delivery through one seam: TaskContext.Deliveries plus a recording egress session; no forge-specific naming remains.
Imported from beads
archie-core-ijmpz· GitHub #1793 · type feature · priority P1 · created 2026-10-18 · closed 2026-10-25