Evidence record / paperclip

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-24-paperclip-beta-repairs-stop-recovery-and-finally-distinguishes-soft-budget-warnings

Beta repairs Stop recovery and finally distinguishes soft budget warnings. Native Stop can wake accounting reconciliation after a complete receipt, and only a later user message can promote queued input from before Stop into resumed work. The repair record distinguishes database regressions and bounded local API journeys from remaining Slack, warm/subscription, deployed-staging and remote-crash qualification. Separately, soft incidents become warnings rather than paused-work cards in beta. Stable v2026.1023.0 still renders the misleading wording.

Channel: preview-or-beta. Half: defect. Date: 2026-10-23.

Operator consequence: On stable, check the incident threshold and actual run before raising a cap or resuming. Trial the beta for the repaired stop/resume path with the exact provider and lifecycle you use; a passing local path is not evidence for all remote recoveries. Correct state labels can avoid unnecessary human intervention, while preserving pre-stop input and requiring a new human turn prevents a repair from silently reviving cancelled work.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-paperclip-beta-repairs-stop-recovery-and-finally-distinguishes-soft-budget-warnings

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact