feat: add continuity-aware triage runbooks

Author: Jacobinwwey

docs/brainstorms/2026-04-21-mainline-reconciliation-after-m8-47-operator-consumer-requirements.md

@@ -5,6 +5,8 @@ topic: mainline-reconciliation-after-m8-47-operator-consumer
 
 # Mainline Reconciliation After M8.47 Operator Consumer Requirements
 
+> Status note (2026-04-21): `M8.48` has now shipped on `main`. This document remains the pre-implementation narrowing pass and is superseded by [Mainline Reconciliation After M8.48 Triage Policy Requirements](./2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md).
+
 ## Problem Frame
 
 `M8.47` is no longer a planned seam.
@@ -53,7 +55,7 @@ The active gap is "which operator consumer should use the newly normalized conti
 ## Requirements
 
 **Truth Refresh**
-- R1. This document becomes the new current source-of-truth item for post-`M8.47` direction.
+- R1. This document captured the current source-of-truth item for post-`M8.47` direction before `M8.48` landed.
 - R2. Current-facing docs must describe `M8.47` as shipped operator-summary promotion, not as pending work.
 
 **Next-Lane Narrowing**

docs/brainstorms/2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md

@@ -0,0 +1,89 @@
+---
+date: 2026-04-21
+topic: mainline-reconciliation-after-m8-48-triage-policy
+---
+
+# Mainline Reconciliation After M8.48 Triage Policy Requirements
+
+## Problem Frame
+
+`M8.48` is now shipped on `main`.
+The bounded continuity-aware operator-consumer step is closed:
+
+- runbook actions now consume the normalized continuity digest,
+- persistent managed-memory continuity now surfaces as an explicit operator action,
+- existing high-risk replay escalation is now annotated with continuity context,
+- replay-risk bucket calculation itself still remains replay/failure-only.
+
+That moves the next seam again.
+The active question is no longer "how does the operator see continuity context in runbook actions."
+The active question is "whether bounded continuity summary fields should start affecting triage severity policy itself."
+
+## Verified Mainline Reality (2026-04-21)
+
+- `AgentWorkspaceDiagnosticsSummary` already normalizes compact continuity digest fields.
+- `/triage`, `/triage/history`, and `/triage/runbook` now expose continuity-aware runbook guidance without full-report joins.
+- Current risk-level calculation still depends on:
+  - replay candidate rate,
+  - failure presence,
+  - threshold policy.
+- Current risk-level calculation does **not** yet depend on:
+  - persistent continuity counts,
+  - continuity breadth,
+  - latest-transition kind/freshness.
+
+## Critical Findings
+
+1. `M8.48` closed the first consumer-logic loop.
+   Continuity summary now affects operator guidance, not only transport.
+
+2. Another runbook-only slice would have low leverage.
+   The same continuity digest already reaches the operator action surface.
+
+3. The sharpest remaining seam is policy calibration.
+   Triage severity buckets still ignore persistent continuity even when runbook actions now call it out.
+
+4. Broader dashboards or personalization still remain secondary.
+   They would consume the same digest later, but they do not tighten the current triage decision loop as directly as bounded policy calibration.
+
+## Requirements
+
+**Truth Refresh**
+- R1. This document becomes the new current source-of-truth item for post-`M8.48` direction.
+- R2. Current-facing docs must describe `M8.48` as shipped continuity-aware triage/runbook consumption.
+
+**Next-Lane Narrowing**
+- R3. Current-facing docs must define `M8.49` as bounded continuity-aware triage policy calibration.
+- R4. `M8.49` must stay inside already-normalized summary fields:
+  - `atomCount`,
+  - `readCount`,
+  - `transitionCount`,
+  - `resolvedKeyCounts`,
+  - `persistentKeyCounts`,
+  - `latestTransition`.
+- R5. `M8.49` must not require full-report joins, a new persistence model, or a larger dashboard surface.
+- R6. `M8.49` must keep continuity-policy logic explainable in runbook/triage payloads rather than introducing opaque scoring.
+
+**Scope Control**
+- R7. Do not reopen backend-escalation or CI-repair narration unless fresh evidence appears.
+- R8. Do not move markdown-reader work ahead of `M8.49` unless it compounds the same operator/study loop more directly.
+- R9. Do not jump to broad operator dashboards before bounded continuity-aware triage policy lands or is explicitly rejected.
+
+## Success Criteria
+
+- this document is listed first under `docs/brainstorms/index.md`,
+- EN/ZH current-facing docs describe `M8.48` as shipped,
+- EN/ZH current-facing docs describe `M8.49` as bounded continuity-aware triage policy work,
+- docs verification passes,
+- `main` stays clean after verification.
+
+## Scope Boundaries
+
+- This document does not reopen backend sufficiency work.
+- This document does not add a new diagnostics persistence model.
+- This document does not claim that continuity-aware risk policy already ships.
+- This document does not require a new operator dashboard.
+
+## Next Steps
+
+-> `/ce:plan` for `post-M8.48 continuity-aware triage policy calibration`, keeping `M8.49` bounded to normalized continuity summary fields already present on operator fast paths.

docs/brainstorms/index.md

@@ -4,6 +4,7 @@ This page tracks active and archived brainstorming outputs used before implement
 
 ## Current
 
+- [2026-04-21 Mainline Reconciliation After M8.48 Triage Policy Requirements](2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md)
 - [2026-04-21 Mainline Reconciliation After M8.47 Operator Consumer Requirements](2026-04-21-mainline-reconciliation-after-m8-47-operator-consumer-requirements.md)
 - [2026-04-21 Mainline Reconciliation After M8.46 Operator Continuity Summary Requirements](2026-04-21-mainline-reconciliation-after-m8-46-operator-continuity-summary-requirements.md)
 - [2026-04-21 Mainline Progress Reconciliation After M8.33 Requirements](2026-04-21-mainline-progress-reconciliation-after-m8-33-requirements.md)

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

@@ -483,15 +483,17 @@ It is conversation-product hardening on top of the shipped shell.
 `M8.45` now preserves the same continuity rollup block on `managedConversationIndex`, so operator-facing reports can consume the current-atom continuity story without snapshot-only coupling.
 `M8.46` now preserves continuity breadth (`atomIds` / `atomCount`) and latest-transition freshness (`newerAt` / `olderAt`) on that same summary surface, so future pane/report actions can stay on bounded continuity payloads instead of rejoining raw capability events.
 `M8.47` now promotes that compact continuity digest into server-readable diagnostics metadata plus triage/history fast paths, so operator consumers no longer need snapshot-only coupling or full-report joins to read continuity breadth, totals, and latest-transition context.
+`M8.48` now lets runbook guidance consume that same normalized continuity digest, so persistent managed-memory gaps surface as explicit operator actions before any broader dashboard work.
 
 Priority order:
 
-1. make `M8.48` about continuity-aware triage/runbook consumption first, so the newly normalized summary affects operator decisions before any broader dashboard work,
-2. expand broader operator rollups only after that consumer-logic step is in place,
+1. make `M8.49` about continuity-aware triage policy calibration first, so the same normalized summary affects severity policy before any broader dashboard work,
+2. expand broader operator rollups only after that policy step is in place,
 3. keep markdown-reader improvements secondary unless they clearly compound the same study loop.
 
 ## Related Pages
 
+- [Mainline Reconciliation After M8.48 Triage Policy Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md)
 - [Mainline Reconciliation After M8.47 Operator Consumer Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-47-operator-consumer-requirements.md)
 - [Mainline Reconciliation After M8.46 Operator Continuity Summary Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-46-operator-continuity-summary-requirements.md)
 - [Mainline Progress Reconciliation After M8.33 Requirements](../../../brainstorms/2026-04-21-mainline-progress-reconciliation-after-m8-33-requirements.md)