feat(agent-workspace): personalize managed memory follow-ups

Author: Jacobinwwey

docs/diataxis/en/explanation/agent-conversation-focus-mode-plan.md

@@ -473,10 +473,11 @@ It is conversation-product hardening on top of the shipped shell.
 `M8.35` now explains recommendation drift across adjacent history events, so the current-atom history surface no longer requires manual cross-card comparison for that change.
 `M8.36` now explains recommendation stability across adjacent history events, so the current-atom history surface also shows when a newer event kept the same next step in place.
 `M8.37` now adds stability signals on top of that explanation surface, so repeated hold streaks are readable from badges and confidence copy without reading the full stability paragraph.
+`M8.38` now personalizes those expanded-history follow-up recommendations around missing managed-memory note/correction state, so the next step, rationale, and confidence copy all point directly at the still-missing managed key instead of stopping at generic continuity ranking.
 
 Priority order:
 
-1. deepen personalization on top of the shipped primary/secondary/drift/stability explanation surface and stability signals,
+1. deepen personalization on top of the shipped primary/secondary/drift/stability explanation surface, stability signals, and managed-memory gap targeting,
 2. expand broader operator rollups only when they clearly compound the same current-atom continuity loop,
 3. keep markdown-reader improvements secondary unless they clearly compound the same study loop.
 

docs/diataxis/en/explanation/development-progress-dashboard.md

@@ -6,7 +6,7 @@ It explicitly separates branch-level implementation status from mainline integra
 ## Scope
 
 - Focus area: local-first knowledge mastery platform (ingest, retrieval, learning path, tutor, memory, governance).
-- Time window: `v1.7.0` through the 2026-04-21 foundation-integration checkpoint, the 2026-04-21 UTC CI review cycle, and the post-`M8.37` reconciliation pass.
+- Time window: `v1.7.0` through the 2026-04-21 foundation-integration checkpoint, the 2026-04-21 UTC CI review cycle, and the post-`M8.38` reconciliation pass.
 - Evidence rule: every progress claim must map to:
   - contract layer (`src/learning/api.ts`, `src/learning/types.ts`),
   - route/runtime layer (`src/server.ts`),
@@ -18,12 +18,12 @@ Current top priority is not feature-count expansion.
 Current top priority is **conversation-product hardening on top of the already-green backend baseline**:
 
 - keep backend sufficiency as a standing decision gate rather than an active execution lane,
-- keep closing the correction/product/operator gap exposed after `M8.20-M8.37`,
-- treat `M8.23` as the operator-visibility baseline for conversation-memory/correction actions, `M8.24` as the active-atom action-surface baseline, `M8.25` as the active-atom pane-state continuity baseline, `M8.26` as the active-atom study-loop summary baseline, `M8.27` as the active-atom recent-result continuity baseline, `M8.28` as the active-atom result-preview baseline, `M8.29` as the active-atom history-drill-down baseline, `M8.30` as the active-atom history follow-up baseline, `M8.31` as the active-atom history freshness-ranking baseline, `M8.32` as the active-atom history rationale/alternative baseline, `M8.33` as the active-atom history confidence-signal baseline, `M8.34` as the primary-vs-secondary tradeoff explanation baseline, `M8.35` as the adjacent-history drift explanation baseline, `M8.36` as the adjacent-history stability explanation baseline, and `M8.37` as the adjacent-history stability-signal baseline,
+- keep closing the correction/product/operator gap exposed after `M8.20-M8.38`,
+- treat `M8.23` as the operator-visibility baseline for conversation-memory/correction actions, `M8.24` as the active-atom action-surface baseline, `M8.25` as the active-atom pane-state continuity baseline, `M8.26` as the active-atom study-loop summary baseline, `M8.27` as the active-atom recent-result continuity baseline, `M8.28` as the active-atom result-preview baseline, `M8.29` as the active-atom history-drill-down baseline, `M8.30` as the active-atom history follow-up baseline, `M8.31` as the active-atom history freshness-ranking baseline, `M8.32` as the active-atom history rationale/alternative baseline, `M8.33` as the active-atom history confidence-signal baseline, `M8.34` as the primary-vs-secondary tradeoff explanation baseline, `M8.35` as the adjacent-history drift explanation baseline, `M8.36` as the adjacent-history stability explanation baseline, `M8.37` as the adjacent-history stability-signal baseline, and `M8.38` as the managed-memory gap follow-up baseline,
 - keep the remaining near-term budget on deeper personalization and operator rollup quality now that the continuity-explanation gap is closed on the active history surface,
 - keep remote `main` CI interpretation evidence-based: the latest fully completed `main` workflow set is green, and new pushes should be treated as pending until their workflow set finishes.
 
-## Current Mainline Snapshot (2026-04-21 Baseline Split: Foundation M8.18 / Conversation M8.37)
+## Current Mainline Snapshot (2026-04-21 Baseline Split: Foundation M8.18 / Conversation M8.38)
 
 - Foundation baseline on `main` is currently:
   - status `integrated`
@@ -37,12 +37,12 @@ Current top priority is **conversation-product hardening on top of the already-g
 - Historical increment sections below remain chronological archive entries.
 - When a historical section says `in_progress` / `no-go`, read it as past checkpoint truth rather than current repo state.
 
-## Reconciliation Notes (2026-04-21 Post-M8.37)
+## Reconciliation Notes (2026-04-21 Post-M8.38)
 
 - The active mainline question is no longer whether backend sufficiency work should continue.
   That lane is closed-by-default while its gate stays green.
-- The active mainline question is also no longer whether tradeoff, drift, stability explanation, and stability signaling should be added.
-  `M8.34`, `M8.35`, `M8.36`, and `M8.37` now ship that continuity-explanation layer on the expanded history decision surface.
+- The active mainline question is also no longer whether tradeoff, drift, stability explanation, stability signaling, and managed-memory gap follow-up should be added.
+  `M8.34`, `M8.35`, `M8.36`, `M8.37`, and `M8.38` now ship that continuity-explanation layer on the expanded history decision surface.
 - The next gap is no longer local explanation opacity.
   The remaining product question is how much deeper personalization and operator rollup value should sit on top of this now-readable current-atom history surface.
 - Remote `main` CI is currently green on the latest push.
@@ -235,6 +235,22 @@ Execution anchor:
   - diagnostics snapshot coverage for stored preview payloads,
   - EN/ZH re-render coverage for localized preview text.
 
+## Latest Mainline Increment (2026-04-21 M8.38 Active-Atom Managed-Memory Gap Follow-Up)
+
+- Extended the expanded history follow-up surface with managed-memory gap personalization:
+  - managed-memory read history items now prioritize `write_memory_note` / `record_memory_correction` when the same event reports missing note/correction keys,
+  - rationale text now explains that the next step is driven by the still-missing managed state instead of generic follow-up ranking,
+  - confidence badges and copy now expose which managed key is still missing on that current atom.
+- Kept the slice frontend-bounded:
+  - no backend route, API contract, persistence model, or capability schema changed,
+  - personalization reuses `missingManagedKeyLabels` already recorded on the local capability event plus existing managed-memory capabilities.
+- Closed the next post-`M8.37` personalization gap:
+  - operators no longer lose the missing-note/missing-correction context once the managed-memory read event moves into history,
+  - the continuity surface now keeps managed-memory closure actions inside the same expanded history loop.
+- Expanded regression coverage for:
+  - managed-memory read history items reprioritizing follow-up actions toward missing note/correction writes,
+  - EN/ZH contract coverage for the new managed-memory rationale, badges, and confidence copy.
+
 ## Latest Mainline Increment (2026-04-21 M8.37 Active-Atom Adjacent History Stability Signals)
 
 - Extended the expanded history confidence surface with adjacent-history stability signals:
@@ -1437,8 +1453,8 @@ Note: foundation-lane gates now exist on `main`; keep them in the normal verific
 
 1. Treat backend sufficiency as closed-by-default while the gate remains green; do not reopen heavier backend work without new measured pressure.
 2. Treat remote `main` CI as evidence-bound to the latest fully completed workflow set; only reopen CI-triage narrative when a fresh failing run exists.
-3. Make the next planning round about post-`M8.37` bounded conversation-product compounding:
-   - deepen personalization on top of the now-readable primary/secondary/drift/stability explanation surface and stability signals,
+3. Make the next planning round about post-`M8.38` bounded conversation-product compounding:
+   - deepen personalization on top of the now-readable primary/secondary/drift/stability explanation surface, stability signals, and managed-memory gap follow-up,
    - add broader operator rollup/reporting only when it compounds the same current-atom continuity loop,
    - keep markdown-reader improvements secondary unless they strengthen the same study loop.
 4. Treat notification-threshold governance as closed after `M7.29`; do not plan `M7.30+` unless a materially new operator requirement appears.

docs/diataxis/en/explanation/local-backend-sufficiency-and-escalation-plan.md

@@ -248,8 +248,8 @@ Recommended next product order:
    - the minimum correction / feedback closure is now integrated through explicit next-step guidance on missing managed state,
    - operator-facing visibility for conversation-memory and correction actions is now integrated through persisted diagnostics summary/index counts,
    - stronger agent action surfaces around focus mode and learning path are now integrated through the active-atom quick-action rail, toolbar routing, continuity notes/path-target diagnostics, capability-taxonomy summary cards, the recent-activity history card, localized result-detail previews on that history surface, expandable history drill-down, deterministic history follow-up affordances, continuity-aware freshness ranking for those affordances, and bounded rationale/secondary-alternative rendering,
-   - `M8.34` primary-vs-secondary tradeoff explanation, `M8.35` adjacent-history drift explanation, `M8.36` adjacent-history stability explanation, and `M8.37` adjacent-history stability signals are now integrated on top of the shipped signal-enabled current-atom recent-activity card,
-   - next only deepen personalization or broader operator rollups when they clearly compound that same readable current-atom continuity loop.
+   - `M8.34` primary-vs-secondary tradeoff explanation, `M8.35` adjacent-history drift explanation, `M8.36` adjacent-history stability explanation, `M8.37` adjacent-history stability signals, and `M8.38` managed-memory gap follow-up personalization are now integrated on top of the shipped signal-enabled current-atom recent-activity card,
+   - next only deepen personalization or broader operator rollups when they clearly compound that same readable current-atom continuity loop, especially when they keep missing managed-state targeting explicit.
 2. markdown-reader improvement:
    - only when it clearly compounds knowledge review or focus-mode study loops.
 

docs/diataxis/zh/explanation/agent-conversation-focus-mode-plan.md

@@ -461,10 +461,11 @@
 `M8.35` 现在又解释相邻 history event 之间的 recommendation drift，让当前 atom history surface 不再要求操作者手工对比多张展开卡片。
 `M8.36` 现在又解释相邻 history event 之间的 recommendation stability，让当前 atom history surface 也能直接说明“新事件是否继续保持同一下一步”。
 `M8.37` 现在又在这层 explanation surface 之上补上 stability signal，让连续 hold 的 next step 可以直接从 badge 与 confidence copy 读出来，而不必读完整段 stability 文案。
+`M8.38` 现在又围绕缺失的 managed-memory note / correction state 个性化这些展开 history follow-up recommendation，让下一步、rationale 与 confidence copy 都直接指向仍然缺失的托管 key，而不是停留在通用 continuity ranking。
 
 优先顺序：
 
-1. 在当前已落地的 primary/secondary/drift/stability explanation surface 与 stability signal 之上继续加深 personalization，
+1. 在当前已落地的 primary/secondary/drift/stability explanation surface、stability signal 与 managed-memory gap targeting 之上继续加深 personalization，
 2. 只有当更宽的 operator rollup 能明确复利同一 current-atom continuity loop 时才继续扩展，
 3. Markdown 阅读器提升继续保持次优先级，除非它能明确加强同一学习闭环。