Evidence record / agent-flywheel
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-13-agent-flywheel-main-leaves-healthy-unchanged-agent-mail-running-during-routine-updates
Main leaves healthy unchanged Agent Mail running during routine updates. Routine updates previously restarted the shared Agent Mail server even when its binary and unit had not changed. The maintainer reports a midday interruption and more than 90 seconds of reload on large mailboxes. The untagged fix leaves an unchanged healthy service running and still restarts after binary/unit changes, failed readiness, inactivity or missing PID. No service or reload duration was measured here.
Channel: main-unreleased. Half: both. Date: 2026-10-13.
Operator consequence: Schedule stable updates around shared mail use rather than assuming no-op tool updates leave coordination untouched. Watch for a stable release containing conditional restart and verify service readiness after updates.
Receipt
Finding metadata
Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0
Finding ID: 2026-10-13-agent-flywheel-main-leaves-healthy-unchanged-agent-mail-running-during-routine-updates
Source links
Primary links, including exact changelog lines when available.
- commit2026-10-13-agent-flywheel-main-leaves-healthy-unchanged-agent-mail-running-during-routine-updatesgithub.com/Dicklesworthstone/agentic_coding_flywheel_setup/commit/ba279de19b300f3f153a6f063ca21aafc08a9f62tagged commit file2026-10-13-agent-flywheel-main-leaves-healthy-unchanged-agent-mail-running-during-routine-updatesDicklesworthstone/agentic_coding_flywheel_setup / scripts/lib/stack.sh#L1861-L1923
Versioned source: run artifact