instar 0.28.33 → 0.28.41

package/upgrades/0.28.33.md

@@ -1,22 +0,0 @@
-# Upgrade Guide — v0.28.33
-
-<!-- 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
-
-- **Built-in job gate/execute commands now self-heal on refresh.** Generalizes the v0.28.32 port-repair fix. `refreshJobs` now syncs the entire `gate` field and `execute.type`/`execute.value` fields of built-in jobs (matched by slug) to the current source-of-truth defaults from `getDefaultJobs(port)`. User-tunable fields (`enabled`, `schedule`, `priority`, `model`, `telegramNotify`, etc.) are left untouched. This closes a class of bugs where existing installs' `jobs.json` keeps old gate/execute logic after a source update, causing built-in jobs to silently skip forever. The motivating case: `degradation-digest` had an old gate that checked `.instar/state/degradation-events.json` (always empty), while the current source checks `.instar/degradations.json` (the real file) — leaving 11 unreported degradations undetected for ~2 weeks. Contract change: built-in `gate`/`execute` are implementation details that track the codebase. To customize, fork under a different slug.
-- Feedback cluster: `cluster-degradation-digest-gate-checks-wrong-file-job-never-runs`.
-
-## What to Tell Your User
-
-- **Background health checks self-heal after upgrades:** "A few of my background checks were quietly looking at outdated places after past upgrades and never running. They'll fix themselves automatically. One that was supposed to surface system warnings to you had been dark for about two weeks — it'll start working again."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Self-healing built-in job gate/execute | Automatic on refresh — built-in jobs whose gate or execute commands drifted from source defaults are resynced |

package/upgrades/0.28.5.md

@@ -1,17 +0,0 @@
-# Upgrade Guide — v0.28.5
-
-<!-- bump: patch -->
-
-## What Changed
-
-- **Topic cleanup no longer closes explicitly-configured topics**: The startup topic cleanup was closing forum topics for on-alert and silent jobs even when those topics were explicitly configured in jobs.json or shared with other active jobs. Now only dynamically-created topic mappings are cleaned up, and only if no other job references the same topic.
-
-## What to Tell Your User
-
-- **"Your Telegram forum topics should stay open now"**: If your user noticed that certain Telegram topics kept getting closed after server restarts, that should be resolved. The system was incorrectly treating explicitly-configured topics as stale.
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Safe topic cleanup | Automatic — explicitly-configured topics are preserved on restart |

package/upgrades/0.28.7.md

@@ -1,24 +0,0 @@
-# Upgrade Guide — v0.28.7
-
-<!-- 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
-
-Added `PATCH /config` endpoint that all FeatureDefinition enable/disable actions reference. Previously, toggling features from the dashboard (evolution, threadline, publishing, tunnel, etc.) returned 404 because the endpoint didn't exist. The new endpoint deep-merges the request body into config.json with an allowlist of safe config keys, and updates runtime config.
-
-Also includes CI test fixes from previous commits (trust wiring, quota tracking, config validation, job scheduler edge cases).
-
-## What to Tell Your User
-
-- **Dashboard feature toggles now work**: "You can now enable/disable features from the dashboard — the toggle buttons actually persist your choice."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Config patch API | `PATCH /config` with JSON body — dashboard uses this automatically |
-| Feature toggle persistence | Toggle features on/off from dashboard, changes persist to config.json |

package/upgrades/0.28.8.md

@@ -1,21 +0,0 @@
-# Upgrade Guide — v0.28.8
-
-<!-- bump: patch -->
-
-## What Changed
-
-Fixed a bug where `loadConfig()` silently dropped many optional config fields — including `safety`, `evolution`, `agentAutonomy`, `externalOperations`, `autonomyProfile`, `notifications`, `responseReview`, `inputGuard`, `dashboard`, and `moltbridge`. These fields were defined in `InstarConfig` and written to `config.json` by subsystems like `AutonomyProfileManager.applyProfileToConfig()`, but were never read back because `loadConfig()` constructed its return object with only explicitly listed properties.
-
-The fix spreads `fileConfig` as the base object before applying explicit overrides, so all config fields pass through while preserving existing defaults and transformations.
-
-**Impact**: If you had manually set `safety.level` in your config or changed autonomy profile settings, those overrides were being silently ignored — the system always fell back to profile defaults. After this update, your config file settings will be respected.
-
-## What to Tell Your User
-
-- **Config settings now fully respected**: "If you've customized safety levels, autonomy settings, or other advanced configuration, those settings are now properly loaded. Previously they could be silently ignored — that's fixed now."
-
-## Summary of New Capabilities
-
-| Capability | How to Use |
-|-----------|-----------|
-| Config passthrough fix | Automatic — all config.json fields now properly loaded |