What

The Step 0 cleanup script for the F8 vendor-routing workstream, plus the design docs the open PRs reference.

Already executed against production: 32 tasks cancelled across 10 conversations and 8 users. Read-back clean, and a re-run is a no-op.

Why these tasks can never be cancelled by the system

listTasksTool.ts:272-273 scopes to eq(userTasks.conversationId, conversationId). The agent on the real deal cannot see the task; the agent on the vendor conversation cannot see the deal's stage. The one CRM-state-driven cancel path (external-crm-events.ts:489-503) misses on both predicates: it is scoped to the deal's own conversation and to taskType='crm-opportunity', and these are manual.

The safety test

Selection requires >= 5 inbound, >= 70% from a known vendor sender, and zero inbound from a real counterparty (an external sender that is neither the vendor nor one of the user's own domains).

That last predicate is what makes this safe to run. It excluded a "Melissa & Doug" conversation holding 4 PandaDoc notices and 1 email from the actual customer, which is a genuine deal whose tasks may be correctly placed.

It is deliberately conservative and under-selects. A few conversations were skipped because a second notifier not in the vendor list (Stripe, Superhuman, Slack) counted as a counterparty. Missing 3 tasks is a better failure than cancelling a legitimate one.

Not a behaviour change

This clears rows that already exist. The root cause is findOrCreateVendorConversation adopting a deal conversation, traced in docs/design/f8-vendor-conversation-routing.md §2.3, and fixed by Steps 2 to 4 of that plan.

Docs

f8-vendor-conversation-routing.md is referenced by #2694, where the link currently dangles. task-completion-write-path.md and refused-save-client-state.md are the two handoffs for Jesse. f8-agent-log.md records the workstream's scope corrections, including two fixes that were proven to be no-ops.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NVHnt2pEEjhVwSyhkcaxoC

Greptile Summary

This PR adds a one-off F8 cleanup utility and extensive design handoffs for vendor routing, stale tasks, refused document saves, and deferred task completion.

• Selects vendor-dominated, counterparty-free conversations and marks their open tasks agent_deleted.
• Adds an esbuild runner for executing the cleanup in dry-run or APPLY mode.
• Documents the vendor-routing workstream and several related production failure investigations.
• The cleanup’s domain predicates can misclassify genuine counterparties, and the documents expose identifiable production customer data.

Confidence Score: 2/5

This PR is not safe to merge until the cleanup’s false-positive domain matching, the production-data disclosure, and the explicit repository-rule violation are resolved.

The cleanup can cancel every open task on a genuine conversation whose counterparty domain merely contains a vendor token, and the new public documentation exposes identifiable customer operational data. The raw SQL double assertion also violates an explicit repository requirement.

Files Needing Attention: apps/server/scripts/cancel-vendor-bucket-tasks.ts; docs/design/refused-save-client-state.md; docs/design/stale-task-failure-modes.md; docs/design/task-completion-write-path.md; docs/