Idea
Opt-in AutoUpdate=true + QuietHours window, skip if traffic was forwarded in the last N minutes, per-major-version pinning so a 0→1 bump doesn't surprise people overnight.
Why parked
The existing surfaces are already enough for the current operator population:
- C5.1 - dashboard update banner
- C5.2 - one-click
/Update/apply
- Plan M -
trigger_update MCP tool
Together these give an operator (or an MCP-driven assistant) a "release is available, apply it" flow that takes seconds. A scheduled apply is a convenience for operators who don't watch the box at all, but those operators don't yet exist; today it's author + a small handful of friendly nodes.
Pickup signal
A real population whose nodes drift weeks behind because nobody clicks the button.
Out of scope
- Binary signing / signature verification - separate initiative (Sigstore? minisign?).
- Channels (stable / beta / dev) - YAGNI until we have releases that warrant the distinction.
- Cross-platform privileged-update (Windows service control / launchd) - Linux/systemd first.
Migrated from plan.md Phase C5.3 (parked).
Idea
Opt-in
AutoUpdate=true+QuietHourswindow, skip if traffic was forwarded in the last N minutes, per-major-version pinning so a 0→1 bump doesn't surprise people overnight.Why parked
The existing surfaces are already enough for the current operator population:
/Update/applytrigger_updateMCP toolTogether these give an operator (or an MCP-driven assistant) a "release is available, apply it" flow that takes seconds. A scheduled apply is a convenience for operators who don't watch the box at all, but those operators don't yet exist; today it's author + a small handful of friendly nodes.
Pickup signal
A real population whose nodes drift weeks behind because nobody clicks the button.
Out of scope
Migrated from
plan.mdPhase C5.3 (parked).