instar 0.24.14 → 0.24.15

package/.claude/skills/setup-wizard/skill.md

@@ -511,9 +511,9 @@ This handles directory creation, registry entry, port allocation, and gitignore
 
 Regardless of project or personal agent, **a messaging platform is how you talk to your agent**. This should be clear from the very first message. Don't present it as an optional add-on — it's the destination of this entire setup.
 
-The terminal session is the on-ramp. Messaging (Telegram, Slack, or WhatsApp) is where the agent experience lives.
+The terminal session is the on-ramp. Messaging (Telegram or WhatsApp) is where the agent experience lives.
 
-**Telegram is recommended** for its topic threads, bot API, and forum-style organization — but Slack and WhatsApp are fully supported alternatives for users who prefer them or already live there.
+**Telegram is recommended** for its topic threads, bot API, and forum-style organization — but WhatsApp is a fully supported alternative for users who prefer it or already live there.
 
 ## Phase 2: Identity Bootstrap — The Birth Conversation
 
@@ -788,8 +788,7 @@ Frame messaging as the core of the experience, then let the user choose their pl
 > This is how you'll actually talk to your agent day-to-day. Not the terminal — just messaging on your phone or desktop.
 >
 > 1. **Telegram** (recommended) — Topic threads for organized conversations, powerful bot API, forum-style groups. Best for power users who want structured channels.
-> 2. **Slack** — Your agent lives in Slack alongside your team. Channels, threads, reactions, Block Kit interactions. Great for professional workflows.
-> 3. **WhatsApp** — Talk to your agent from the messaging app you already use. Simple, familiar, works everywhere.
+> 2. **WhatsApp** — Talk to your agent from the messaging app you already use. Simple, familiar, works everywhere.
 >
 > Which do you prefer? (You can always add the other one later.)
 
@@ -797,16 +796,12 @@ Frame messaging as the core of the experience, then let the user choose their pl
 
 > "Without a messaging platform, you'll only be able to talk to [agent name] by opening a terminal and running `instar chat`. No mobile access, no proactive messages, no organized threads. Most of what makes an Instar agent useful requires messaging."
 >
-> "You can set it up later with `instar telegram setup`, `instar add slack`, or `instar whatsapp connect`."
+> "You can set it up later with `instar telegram setup` or `instar whatsapp connect`."
 
 ### If User Chooses Telegram
 
 Proceed with the Telegram setup flow below (Step 3b onward).
 
-### If User Chooses Slack
-
-Jump to **Phase 4h: Slack Setup**. Slack is a first-class option — treat it with the same energy and completeness as Telegram setup.
-
 ### If User Chooses WhatsApp
 
 Jump to **Phase 4g: WhatsApp Setup**. WhatsApp is a first-class option — treat it with the same energy and completeness as Telegram setup.
@@ -1525,278 +1520,7 @@ If both Telegram and WhatsApp are configured, mention:
 
 No additional config needed — CrossPlatformAlerts wires automatically in `server.ts` when both adapters are present.
 
-### 4h. Slack Setup
-
-Slack is a **first-class messaging option**. The user may arrive here either:
-- **As their primary choice** from Phase 3 (chose Slack over Telegram/WhatsApp)
-- **As an additional channel** after Telegram or WhatsApp is already configured
-
-**If arriving as primary choice from Phase 3**, skip the "want to add" prompt — they already chose this. Go straight to Step 4h-1.
-
-**If arriving after Telegram/WhatsApp setup**, present:
-
-> **Want to add Slack as an additional channel?**
->
-> Slack lets you talk to your agent from Slack — channels, threads, reactions, and interactive buttons. It works alongside your other messaging platforms.
->
-> 1. Yes, set up Slack
-> 2. Skip for now
->
-> Type a number.
-
-If they choose to skip, move to Phase 4i.
-
-#### Step 4h-1: Browser Automation for Slack
-
-**Use the same browser automation detection from Step 3a.** Playwright preferred, Chrome extension as fallback, manual as last resort.
-
-Tell the user:
-
-> I'm going to open a browser to set up Slack automatically. I'll create a workspace, configure an app, and set everything up.
->
-> You'll need to log into Slack in the browser window. Ready?
-
-Wait for confirmation before proceeding.
-
-#### Step 4h-2: Navigate to Slack and Handle Login
-
-Navigate to `https://slack.com/signin`. Take a snapshot.
-
-**If already logged in** (redirected to a workspace or shows user avatar): Skip to Step 4h-3.
-
-**If not logged in** (sign-in form visible):
-> "Please log into your Slack account in the browser window. You can use email, Google, or Apple sign-in. Let me know when you're logged in."
-
-Wait for user confirmation. Take a snapshot to verify.
-
-**If no Slack account:**
-> "You'll need a Slack account. Click 'Create an account' in the browser and follow the steps. Let me know when you're logged in."
-
-#### Step 4h-3: Workspace Setup
-
-Ask the user:
-
-> I recommend creating a dedicated workspace for your agent — it keeps things clean and avoids privacy concerns with colleagues. Would you like me to create a dedicated workspace, or install into an existing one?
-
-**If creating a new workspace:**
-
-1. Navigate to `https://slack.com/get-started#/createnew`
-2. Take snapshot, find email field
-3. Type user's email (from USER.md or ask)
-4. Click "Continue"
-5. **WAIT** — user must enter 6-digit email verification code from their inbox
-   > "Check your email for a 6-digit code from Slack and enter it in the browser."
-   Wait for user confirmation.
-6. Take snapshot — workspace name field
-7. Type workspace name: `{agent-name}-agent` (e.g., "echo-agent")
-8. Click "Next"
-9. Take snapshot — project/channel name field
-10. Type "general"
-11. Click "Next"
-12. Take snapshot — invite page
-13. Click "Skip" or skip link
-14. Wait for workspace to load
-
-**If using existing workspace:**
-1. Ask which workspace to use
-2. Navigate to the workspace URL
-3. Take snapshot to confirm workspace loaded
-
-#### Step 4h-4: Create Slack App via Manifest
-
-Build the app manifest JSON with minimal Phase 1 scopes:
-
-```json
-{
-  "display_information": {
-    "name": "{agent-name}",
-    "description": "Instar agent"
-  },
-  "features": {
-    "bot_user": {
-      "display_name": "{agent-name}",
-      "always_online": true
-    }
-  },
-  "oauth_config": {
-    "scopes": {
-      "bot": [
-        "channels:history", "channels:manage", "channels:read",
-        "chat:write", "im:history", "im:read", "im:write",
-        "pins:write", "reactions:read", "reactions:write", "users:read"
-      ]
-    }
-  },
-  "settings": {
-    "event_subscriptions": {
-      "bot_events": [
-        "message.channels", "message.groups", "message.im",
-        "file_shared", "reaction_added", "app_mention"
-      ]
-    },
-    "socket_mode_enabled": true,
-    "org_deploy_enabled": false
-  }
-}
-```
-
-1. URL-encode the manifest JSON
-2. Navigate to: `https://api.slack.com/apps?new_app=1&manifest_json={ENCODED_JSON}`
-3. Take snapshot — workspace picker dropdown
-4. Select the target workspace from dropdown
-5. Click "Next"
-6. Take snapshot — manifest review/summary page
-7. Click "Create" button
-8. Wait 2-3 seconds for app creation
-9. Take snapshot — should be on app's Basic Information page
-10. Extract App ID from the URL (`api.slack.com/apps/A{APP_ID}/...`)
-
-#### Step 4h-5: Install App to Workspace
-
-1. Navigate to: `https://api.slack.com/apps/{APP_ID}/install-on-team`
-2. Take snapshot — "Install to Workspace" button
-3. Click "Install to Workspace"
-4. Take snapshot — OAuth authorization page
-5. Click "Allow"
-6. Wait for redirect back to app settings
-7. Take snapshot — OAuth & Permissions page
-8. **CRITICAL: DO NOT take screenshots/snapshots on this page** — it shows the bot token
-9. Extract Bot User OAuth Token (`xoxb-...`) from the page using regex. Pattern: `xoxb-\d+-\d+-[A-Za-z0-9]+`
-10. Store token in memory — do NOT log it
-
-#### Step 4h-6: Enable Socket Mode & Generate App Token
-
-1. Navigate to: `https://api.slack.com/apps/{APP_ID}/socket-mode`
-2. Take snapshot — Socket Mode toggle
-3. If toggle is OFF, click to enable it
-4. Navigate to: `https://api.slack.com/apps/{APP_ID}/general`
-5. Scroll to "App-Level Tokens" section
-6. Take snapshot — find "Generate Token and Scopes" button
-7. Click "Generate Token and Scopes"
-8. Take snapshot — token creation dialog
-9. Type token name: "socket-mode" in the name field
-10. Click "Add Scope"
-11. Select "connections:write" scope
-12. Click "Generate"
-13. **CRITICAL: DO NOT take screenshots/snapshots** — token is displayed
-14. Extract app-level token (`xapp-...`) from the dialog. Pattern: `xapp-\d+-[A-Za-z0-9]+-\d+-[A-Za-z0-9]+`
-15. Click "Done"
-
-#### Step 4h-7: Validate Tokens
-
-Validate both tokens via API (NOT browser):
-
-```bash
-# Validate bot token and extract workspace info
-BOT_RESULT=$(curl -s -X POST https://slack.com/api/auth.test \
-  -H "Authorization: Bearer ${BOT_TOKEN}" \
-  -H "Content-Type: application/json")
-
-# Expected: {"ok": true, "team_id": "T...", "user_id": "U...", "team": "workspace-name"}
-
-# Validate app token
-APP_RESULT=$(curl -s -X POST https://slack.com/api/apps.connections.open \
-  -H "Authorization: Bearer ${APP_TOKEN}" \
-  -H "Content-Type: application/json")
-
-# Expected: {"ok": true, "url": "wss://..."}
-```
-
-If either fails, tell the user and offer to retry the extraction step.
-
-Extract from `BOT_RESULT`:
-- `team_id` → `workspaceId`
-- `team` → `workspaceName`
-- `user_id` → add to `authorizedUserIds` (this is the installing user)
-
-#### Step 4h-8: Create System Channels
-
-```bash
-# Create lifeline channel
-LIFELINE=$(curl -s -X POST https://slack.com/api/conversations.create \
-  -H "Authorization: Bearer ${BOT_TOKEN}" \
-  -H "Content-Type: application/json" \
-  -d '{"name": "{agent}-sys-lifeline"}')
-
-# Create dashboard channel
-DASHBOARD=$(curl -s -X POST https://slack.com/api/conversations.create \
-  -H "Authorization: Bearer ${BOT_TOKEN}" \
-  -H "Content-Type: application/json" \
-  -d '{"name": "{agent}-sys-dashboard"}')
-
-# Pin a welcome message in lifeline
-curl -s -X POST https://slack.com/api/chat.postMessage \
-  -H "Authorization: Bearer ${BOT_TOKEN}" \
-  -H "Content-Type: application/json" \
-  -d '{"channel": "LIFELINE_ID", "text": "Lifeline channel active. This is where I send critical system messages."}'
-```
-
-#### Step 4h-9: Write Configuration
-
-Write Slack config to `.instar/config.json`:
-
-```javascript
-node -e "
-const fs = require('fs');
-const p = '<project_dir>/.instar/config.json';
-const c = JSON.parse(fs.readFileSync(p, 'utf-8'));
-c.messaging = c.messaging || [];
-// Remove existing slack config if any
-c.messaging = c.messaging.filter(m => m.type !== 'slack');
-c.messaging.push({
-  type: 'slack',
-  enabled: true,
-  config: {
-    botToken: '${BOT_TOKEN}',
-    appToken: '${APP_TOKEN}',
-    workspaceId: '${WORKSPACE_ID}',
-    workspaceName: '${WORKSPACE_NAME}',
-    authorizedUserIds: ['${USER_ID}'],
-    stallTimeoutMinutes: 5,
-    logRetentionDays: 90,
-    lifelineChannelId: '${LIFELINE_CHANNEL_ID}',
-    dashboardChannelId: '${DASHBOARD_CHANNEL_ID}'
-  }
-});
-fs.writeFileSync(p, JSON.stringify(c, null, 2));
-fs.chmodSync(p, 0o600);
-"
-```
-
-#### Step 4h-10: Confirm Success and Close Browser
-
-Close the browser (Playwright: `browser_close()`).
-
-Tell the user:
-
-> Slack is set up! Your workspace '{workspaceName}' is ready.
-> I've created your system channels and configured everything.
->
-> Important: Your bot tokens provide full access to your Slack workspace — treat them like passwords. They don't expire, so if you suspect compromise, revoke them at api.slack.com/apps.
->
-> Would you like me to store your tokens in Bitwarden for extra security? (recommended)
-
-If they accept Bitwarden, trigger the `secret-setup` skill.
-
-#### Slack Manual Fallback
-
-**Only use this if NO browser automation tools are available.** If automation failed partway, tell the user exactly what succeeded.
-
-Walk the user through:
-
-1. Go to `https://slack.com/get-started#/createnew` and create a workspace (or use existing)
-2. Go to `https://api.slack.com/apps?new_app=1` → click "From a manifest"
-3. Select your workspace
-4. Paste this manifest: [provide the JSON from Step 4h-4]
-5. Click Create, then Install to Workspace, then Allow
-6. Go to Basic Information → App-Level Tokens → Generate Token and Scopes
-7. Name: "socket-mode", Scope: "connections:write", click Generate
-8. Copy both tokens (bot token from OAuth page, app token from Basic Info)
-9. Run: `instar add slack` and paste the tokens when prompted
-
-Even in manual mode, system channel creation (Step 4h-8) and config writing (Step 4h-9) are done by the wizard, not the user.
-
-### 4i. Agent Network
+### 4h. Agent Network
 
 Your agent can join a secure network to communicate with other AI agents. Present this as an optional but recommended step:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "0.24.14",
+  "version": "0.24.15",
   "description": "Persistent autonomy infrastructure for AI agents",
   "type": "module",
   "main": "dist/index.js",

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-03-28T04:58:11.477Z",
-  "instarVersion": "0.24.14",
+  "generatedAt": "2026-03-28T05:35:45.493Z",
+  "instarVersion": "0.24.15",
   "entryCount": 178,
   "entries": {
     "hook:session-start": {
@@ -352,7 +352,7 @@
       "type": "skill",
       "domain": "skills",
       "sourcePath": ".claude/skills/setup-wizard/skill.md",
-      "contentHash": "e00d5df3ad76876be8c96e4f170aaf2510b0f180fd2a8ced9a218d6f7a5bd295",
+      "contentHash": "84839d6c1acbb51049cade14b000d64c943a20580b4676f3c14b2ef33cc5874a",
       "since": "2025-01-01"
     },
     "route-group:health": {

package/upgrades/0.24.15.md

@@ -0,0 +1,49 @@
+# Upgrade Guide — vNEXT
+
+<!-- bump: minor -->
+
+## What Changed
+
+### Slack Messaging Adapter
+
+Instar now includes a full Slack messaging adapter (`SlackAdapter`), enabling agents to send and receive messages via Slack workspaces. The adapter supports:
+
+- Sending messages to channels and threads
+- Token validation and secure credential handling
+- Atomic write operations for message persistence
+- CLI tooling for Slack interaction (`slack-cli`)
+- Server-side routes for Slack webhook integration
+
+The adapter follows the same pattern as existing messaging adapters (Telegram, WhatsApp) and plugs into the unified channel routing system.
+
+### Server-Side Process Review Dashboard
+
+A new Systems tab on the dashboard provides real-time visibility into server processes. This includes:
+
+- Process telemetry collection and display
+- Health status monitoring for running services
+- Integration with the existing dashboard infrastructure
+
+### Architecture Documentation
+
+A new "Under the Hood" page on the documentation site explains Instar's internal architecture, giving developers and agents a clearer picture of how the system is structured.
+
+### CI Stability Improvements
+
+Several CI fixes improve reliability: resolved flaky test exclusions, fixed WhatsApp string test, added `skipStallClear` option to prevent stall-clear interference during topic sends, and fixed test failures blocking the push gate.
+
+## What to Tell Your User
+
+- **Slack support is here**: Your agent can now send and receive messages through Slack. If your team uses Slack, you can connect it as a messaging channel alongside Telegram and other platforms. Ask your agent to set it up for you.
+
+- **Better visibility into what is running**: There is a new Systems tab on your dashboard that shows what server processes are active and their health status. Useful for troubleshooting if something feels off.
+
+- **More reliable updates**: Several under-the-hood fixes make the CI pipeline more stable, which means smoother and more frequent releases going forward.
+
+## Summary of New Capabilities
+
+| Capability | How to Use |
+|-----------|-----------|
+| Slack messaging | Configure Slack token via CLI, then messages route automatically |
+| Process review dashboard | Visit the Systems tab on your Instar dashboard |
+| Architecture docs | Check the "Under the Hood" page on the docs site |

package/upgrades/0.24.11.md

@@ -1,23 +0,0 @@
-# Upgrade Guide — v0.24.11
-
-<!-- bump: patch -->
-
-## What Changed
-
-- **Health endpoint no longer blocks on stale sessions**: The health check previously called synchronous tmux operations for every tracked session, blocking the event loop. With many stale sessions (common after restart loops), this caused health check timeouts, which triggered MORE restarts — a death spiral. Now uses a cached session count updated asynchronously by the monitor tick.
-
-- **Startup session purge**: Before monitoring starts, the server now does a fast one-pass purge of all session records whose tmux sessions no longer exist. Uses a 1-second timeout per session to fail fast. This prevents the startup overload where the server spent all its boot time polling dead sessions.
-
-- **CoherenceMonitor suppresses known-pending updates**: When the AutoUpdater has already applied a version and a restart is pending (deferred for active sessions), the CoherenceMonitor no longer flags the version mismatch as a failure. This eliminates the race condition where both systems fought over restart decisions.
-
-## What to Tell Your User
-
-- **Stability improvement**: "The server should be much more resilient to restart loops now. Even if many sessions build up, the health check stays fast and the server won't get stuck in a crash-restart cycle. Stale sessions are cleaned up instantly on boot instead of dragging things down."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Non-blocking health endpoint | Automatic — no action needed |
-| Startup session purge | Automatic — runs on every server boot |
-| CoherenceMonitor update suppression | Automatic — no action needed |

package/upgrades/0.24.14.md

@@ -1,26 +0,0 @@
-# Upgrade Guide — v0.24.14
-
-## What Changed
-
-### Server Supervisor Self-Healing
-
-The ServerSupervisor now runs preflight diagnostics before every server spawn attempt. Previously, if the shadow install was missing or the node symlink was broken, the server would crash immediately on startup — and restarting via `/lifeline restart` would just repeat the same failure.
-
-Now, before each spawn, the supervisor checks and auto-repairs:
-
-- **Missing shadow install** — reinstalls via npm automatically
-- **Broken node symlink** — recreates it from available node binaries
-- **Stale lifeline locks** — removes locks older than 10 minutes
-
-This means `/lifeline restart` now actually fixes the problem instead of blindly retrying a broken state. Agents on remote machines can self-recover from common post-update failures without manual SSH intervention.
-
-## What to Tell Your User
-
-Your agent's server is now more resilient. If the server goes down due to a missing or corrupted install, the system will automatically detect and fix the issue before restarting. The /lifeline restart command in Telegram now does real recovery, not just a blind retry.
-
-## Summary of New Capabilities
-
-- **Preflight self-healing**: Server supervisor diagnoses and fixes common startup failures before each spawn
-- **Shadow install auto-repair**: Missing shadow installs are reinstalled automatically
-- **Node symlink recovery**: Broken node symlinks are recreated from available binaries
-- **Stale lock cleanup**: Old lifeline locks are removed to prevent restart deadlocks

package/upgrades/0.24.6.md

@@ -1,20 +0,0 @@
-# Upgrade Guide — v0.24.6
-
-<!-- bump: patch -->
-<!-- Valid values: patch, minor, major -->
-<!-- patch = bug fixes, refactors, test additions, doc updates -->
-<!-- minor = new features, new APIs, new capabilities (backwards-compatible) -->
-<!-- major = breaking changes to existing APIs or behavior -->
-
-## What Changed
-
-- **PermissionRequest auto-approve hook**: Subagents spawned via the Agent tool don't inherit `--dangerously-skip-permissions` from the parent session. This caused permission prompts that blocked autonomous work. A new catch-all `PermissionRequest` hook (`auto-approve-permissions.js`) unconditionally approves all permission requests. Real safety remains in PreToolUse hooks.
-- The hook is automatically added to `settings.json` during init and on upgrade via PostUpdateMigrator.
-
-## What to Tell Your User
-
-No user-facing changes. This fix ensures autonomous sessions and subagents run without interruption.
-
-## Summary of New Capabilities
-
-- Auto-approve permissions for subagent sessions (prevents blocking on tool use prompts)

package/upgrades/0.24.7.md

@@ -1,24 +0,0 @@
-# Upgrade Guide — v0.24.7
-
-<!-- bump: patch -->
-
-## What Changed
-
-- **Tunnel reconnect storm fix**: Added a start mutex to TunnelManager so concurrent `start()` calls coalesce instead of racing. Sleep/wake handler now disables auto-reconnect before force-stopping the tunnel, preventing exit handlers from spawning competing reconnection chains. Previously, sleep/wake cycles could trigger dozens of concurrent tunnel reconnection attempts.
-
-- **Non-fatal crash prevention**: The uncaught exception handler no longer crashes the server for "Cannot set headers after they are sent to the client" and similar HTTP lifecycle errors. These are expected during tunnel transitions and don't affect server stability. Previously, a single double-response event would kill the entire server process.
-
-- **Lifeline startup grace period fix**: During the 3-minute startup grace period, the Lifeline now probes health optimistically. Previously, health checks were completely skipped during boot, causing incoming Telegram messages to be queued with "Server is temporarily down" even when the server was fully responsive (typically within ~10 seconds of restart).
-
-- **Queue delivery confirmation**: When queued messages are replayed after server recovery, the Lifeline now sends a per-topic confirmation ("Server recovered — your queued message has been delivered") so users know their message actually reached the session.
-
-## What to Tell Your User
-
-Server stability improvements. The server is much less likely to restart unexpectedly, and when it does restart, your messages should flow through almost immediately instead of being queued for up to 3 minutes. You'll also get a confirmation when any queued messages are delivered.
-
-## Summary of New Capabilities
-
-- Tunnel reconnection is now atomic — no more reconnect storms after sleep/wake
-- Non-fatal HTTP errors are logged as warnings instead of crashing the server
-- Messages reach sessions within seconds of a restart instead of waiting 3 minutes
-- Queued message delivery is confirmed via Telegram

package/upgrades/0.24.8.md

@@ -1,19 +0,0 @@
-# Upgrade Guide — v0.24.8
-
-<!-- bump: patch -->
-
-## What Changed
-
-- **Lifeline auto-restart after update**: When the server recovers from a planned update restart, the supervisor now emits an `updateApplied` event. The lifeline listens for this and self-exits after a 5-second flush delay. launchd KeepAlive respawns it with the updated shadow install binary. This ensures both the server AND lifeline always run the same version after an update.
-
-- Both restart detection paths are covered: when the supervisor reads the restart request directly, and when the ForegroundRestartWatcher consumes it first (via the planned-exit marker).
-
-## What to Tell Your User
-
-- **Seamless updates**: "Updates now apply to the entire system automatically — both the server and the Telegram connection. Previously, part of the system could run stale code after an update until the machine rebooted. Now everything picks up new code within seconds."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Lifeline auto-restart on update | Automatic — no action needed |

package/upgrades/0.24.9.md

@@ -1,19 +0,0 @@
-# Upgrade Guide — v0.24.9
-
-<!-- bump: patch -->
-
-## What Changed
-
-- **Restart window**: New config option to control when update restarts happen. When set, automatic restarts are deferred until the configured time window. Updates are still downloaded and applied to the shadow install immediately — only the process restart is held. Manual triggers via the API or conversational commands bypass the window.
-
-- Configurable in the agent's config at the path "updates.restartWindow" with start and end times in 24-hour local time format. Supports windows that wrap midnight (e.g., 23:00-05:00).
-
-## What to Tell Your User
-
-- **Restart window**: "I can now schedule update restarts for off-hours so they don't disrupt your workflow. Updates still download instantly, but the actual server restart waits for the quiet window. If you ever need an immediate update, just ask — manual triggers always work regardless of the window."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Restart window | Set "updates.restartWindow" in config with start/end times (e.g., "02:00"-"05:00") |

package/upgrades/NEXT.md

@@ -1,35 +0,0 @@
-# Upgrade Guide — vNEXT
-
-<!-- bump: patch -->
-<!-- Valid values: patch, minor, major -->
-<!-- patch = bug fixes, refactors, test additions, doc updates -->
-<!-- minor = new features, new APIs, new capabilities (backwards-compatible) -->
-<!-- major = breaking changes to existing APIs or behavior -->
-
-## What Changed
-
-<!-- Describe what changed technically. What new features, APIs, behavioral changes? -->
-<!-- Write this for the AGENT — they need to understand the system deeply. -->
-
-## What to Tell Your User
-
-<!-- Write talking points the agent should relay to their user. -->
-<!-- This should be warm, conversational, user-facing — not a changelog. -->
-<!-- Focus on what THEY can now do, not internal plumbing. -->
-<!--                                                                    -->
-<!-- PROHIBITED in this section (will fail validation):                 -->
-<!--   camelCase config keys: silentReject, maxRetries, telegramNotify -->
-<!--   Inline code backtick references like silentReject: false        -->
-<!--   Fenced code blocks                                              -->
-<!--   Instructions to edit files or run commands                      -->
-<!--                                                                    -->
-<!-- CORRECT style: "I can turn that on for you" not "set X to false"  -->
-<!-- The agent relays this to their user — keep it human.              -->
-
-- **[Feature name]**: "[Brief, friendly description of what this means for the user]"
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| [Capability] | [Endpoint, command, or "automatic"] |