docs: correct v0.23.0 nudge-redesign framing; add dashboard v0.5.4 notes

Co-authored-by: Alfonso [Magic Context] <288211368+alfonso-magic-context@users.noreply.github.com>

Author: ualtinok

.alfonso/release-notes/dashboard-v0.5.4.md

@@ -0,0 +1,12 @@
+# Dashboard v0.5.4
+
+Companion release for plugin v0.23.0 — keeps the config editor in sync with the new context-reduction system.
+
+## Changes
+
+- **Config editor updated for v0.23.0.** The removed context-reduction keys (`auto_drop_tool_age`, `drop_tool_structure`, `nudge_interval_tokens`, `iteration_nudge_threshold`) are gone from the editor, so editing a config from the dashboard can no longer re-introduce keys the plugin removed. The schema parity guard now covers the new surface.
+- **Dependency updates**: `tar` and `openssl` bumped in the Tauri backend (dependabot security updates).
+
+## Compatibility
+
+Works with plugin v0.23.0 databases (schema v32). If you edit configs from the dashboard, update both around the same time.

.alfonso/release-notes/v0.23.0.md

@@ -6,7 +6,7 @@ A minor release with three themes: the context-reduction system was rebuilt arou
 
 **The agent maintains its own memories now.** `ctx_memory` grew `update`, `archive` (including batch archive in one call), and `merge` for the memories the agent already sees in its context — previously these were reserved for the background dreamer, so a wrong or outdated memory stayed wrong until the next maintenance run. Cross-project access stays locked down: an agent can only touch its own project's memories. Memory categories are now schema-enforced (the 5-category taxonomy), so invalid categories fail at validation instead of being silently rejected.
 
-**Context nudges are quieter and cache-safe.** The old chat-visible reminder messages are gone. In their place: a compact `<system-reminder>` appended to tool outputs when reclaimable context piles up (Channel 1), and a single one-shot escalation near the threshold (Channel 2) that's delivered mid-turn — between tool calls, while the pile is still growing — and only when a fresh measurement confirms it's still warranted, never on stale data. Channel 1 paces itself: the re-fire interval scales with the history budget, repeat reminders in the same severity band are suppressed, and the cycle resets once the pile actually shrinks — so a long turn sees a handful of escalating reminders instead of one per tool call. Subagents get the same self-management machinery now: they see §N§ tags and `ctx_reduce`, with a minimal guidance block, so long-running subagent sessions no longer balloon.
+**Context nudges are quieter and structurally simpler.** The agent-facing context-reduction reminders (never shown in chat) used to be injected into the message stream and replayed byte-for-byte on every pass — which worked, but needed careful replay machinery to stay cache-stable. The redesign removes that machinery instead of maintaining it: a compact `<system-reminder>` appended to tool outputs when reclaimable context piles up (Channel 1) persists naturally in the session database with nothing to replay, and a single one-shot escalation near the threshold (Channel 2) is delivered mid-turn — between tool calls, while the pile is still growing — and only when a fresh measurement confirms it's still warranted, never on stale data. Channel 1 paces itself: the re-fire interval scales with the history budget, repeat reminders in the same severity band are suppressed, and the cycle resets once the pile actually shrinks — so a long turn sees a handful of escalating reminders instead of one per tool call. Subagents get the same self-management machinery now: they see §N§ tags and `ctx_reduce`, with a minimal guidance block, so long-running subagent sessions no longer balloon.
 
 **Emergency context recovery actually hits its target.** At ≥85% pressure the tiered emergency drop (T3 misc → T2 edit/search → T1 navigation tools, newest 20% of each tier reserved) replaces the old need-blind age-based drops — and its reclaim target is now computed from the full live tail, fixing a systematic under-eviction the audits caught. The routine `auto_drop_tool_age` / `drop_tool_structure` config knobs are removed (doctor cleans them up); reduction is the agent's job via `ctx_reduce`, with the tiered drop as the safety net.