feat: reuse triage priority in runbook actions

Author: Jacobinwwey

docs/brainstorms/2026-04-21-mainline-reconciliation-after-m8-50-priority-consumer-requirements.md

@@ -5,6 +5,8 @@ topic: mainline-reconciliation-after-m8-50-priority-consumer
 
 # Mainline Reconciliation After M8.50 Priority Consumer Requirements
 
+> Status note (2026-04-21): `M8.51` has now shipped on `main`. This document remains the pre-implementation narrowing pass and is superseded by [Mainline Reconciliation After M8.51 Primary Runbook Action Requirements](./2026-04-21-mainline-reconciliation-after-m8-51-primary-runbook-action-requirements.md).
+
 ## Problem Frame
 
 `M8.50` now ships on `main`.

docs/brainstorms/2026-04-21-mainline-reconciliation-after-m8-51-primary-runbook-action-requirements.md

@@ -0,0 +1,87 @@
+---
+date: 2026-04-21
+topic: mainline-reconciliation-after-m8-51-primary-runbook-action
+---
+
+# Mainline Reconciliation After M8.51 Primary Runbook Action Requirements
+
+## Problem Frame
+
+`M8.51` now ships on `main`.
+The bounded priority-consumer alignment step is closed:
+
+- runbook actions now reuse the already-shipped continuity-aware `triagePriority` surface,
+- `review-top-priority-replay-report` now emits whenever a bounded top-priority replay report exists,
+- severity stays explainable and bounded (`high -> critical`, `continuityBoosted -> warning`, otherwise `info`),
+- persistent managed-memory continuity inspection now records the current top-priority source context.
+
+That changes the next seam again.
+The active question is no longer whether any consumer should reuse `triagePriority`.
+The active question is whether pane/report consumers should keep inferring the primary operator recommendation from runbook-action array order alone.
+
+## Verified Mainline Reality (2026-04-21)
+
+- `/triage`, `/triage/history`, and `/triage/runbook` now stay aligned on the same bounded `runbookActions` set.
+- The first runbook consumer already reuses:
+  - `triagePriority`,
+  - `replayRiskLevel`,
+  - `replayRiskSignals`,
+  - `replayCandidateRate`,
+  - `managedConversationContinuitySummary`.
+- No new persistence model, route family, or broader dashboard shell was introduced.
+- Backend sufficiency remains green and dormant-by-default.
+
+## Critical Findings
+
+1. `M8.51` closed the first consumer-reuse seam.
+   Runbook guidance no longer has to recompute priority from raw replay-rate ordering.
+
+2. The next gap is now contract explicitness, not more ranking logic.
+   Consumers can currently read the intended primary recommendation only by trusting array position.
+
+3. Array-order semantics are too implicit for the next consumer.
+   If another pane/report surface needs the primary action, it should not have to assume `runbookActions[0]` is a stable API contract unless the API says so explicitly.
+
+4. Broader dashboard work is still not the sharpest next move.
+   The next bounded step is to expose primary-action semantics on top of the current runbook payload, not to widen the shell.
+
+## Requirements
+
+**Truth Refresh**
+- R1. This document becomes the new current source-of-truth item for post-`M8.51` direction.
+- R2. Current-facing docs must describe `M8.51` as shipped priority-aware runbook action reuse.
+
+**Next-Lane Narrowing**
+- R3. Current-facing docs must define `M8.52` as bounded primary runbook-action surfacing.
+- R4. `M8.52` must stay inside already-shipped fast-path payloads and their derived runbook output:
+  - `runbookActions`,
+  - `triagePriority`,
+  - `replayRiskLevel`,
+  - `replayRiskSignals`,
+  - `managedConversationContinuitySummary`.
+- R5. `M8.52` must prefer explicit primary-action semantics over array-position conventions.
+- R6. `M8.52` must not require new persistence, full-report joins, or a broader dashboard shell.
+
+**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.52` unless it compounds the same operator/study loop more directly.
+- R9. Do not jump to broader operator dashboards before primary runbook-action semantics land or are explicitly rejected.
+
+## Success Criteria
+
+- this document is listed first under `docs/brainstorms/index.md`,
+- EN/ZH current-facing docs describe `M8.51` as shipped,
+- EN/ZH current-facing docs describe `M8.52` as bounded primary runbook-action surfacing 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 broader dashboard work now ships.
+- This document does not require a new operator route family.
+
+## Next Steps
+
+-> `/ce:plan` for `post-M8.51 primary runbook-action surfacing`, keeping `M8.52` bounded to explicit primary recommendation semantics on the existing triage/runbook payloads.

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.51 Primary Runbook Action Requirements](2026-04-21-mainline-reconciliation-after-m8-51-primary-runbook-action-requirements.md)
 - [2026-04-21 Mainline Reconciliation After M8.50 Priority Consumer Requirements](2026-04-21-mainline-reconciliation-after-m8-50-priority-consumer-requirements.md)
 - [2026-04-21 Mainline Reconciliation After M8.49 Triage Prioritization Requirements](2026-04-21-mainline-reconciliation-after-m8-49-triage-prioritization-requirements.md)
 - [2026-04-21 Mainline Reconciliation After M8.48 Triage Policy Requirements](2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md)

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

@@ -484,15 +484,17 @@ It is conversation-product hardening on top of the shipped shell.
 `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.
+`M8.49` and `M8.50` now make severity and ordering continuity-aware, and `M8.51` now reuses that explainable priority inside runbook actions, so the next bounded seam is explicit primary-action surfacing rather than another consumer-specific ranking pass.
 
 Priority order:
 
-1. make `M8.51` about bounded priority-consumer alignment next, so any further operator action reuses the shipped explainable `triagePriority` surface instead of recomputing ranking,
-2. expand broader operator rollups only after that reuse step is in place,
-3. keep markdown-reader improvements secondary unless they clearly compound the same study/operator loop more than `M8.51`.
+1. make `M8.52` about bounded primary runbook-action surfacing next, so pane/report consumers can reuse the shipped priority-aware recommendation without scanning or re-sorting the full action list,
+2. expand broader operator rollups only after that explicit primary-action step is in place,
+3. keep markdown-reader improvements secondary unless they clearly compound the same study/operator loop more than `M8.52`.
 
 ## Related Pages
 
+- [Mainline Reconciliation After M8.51 Primary Runbook Action Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-51-primary-runbook-action-requirements.md)
 - [Mainline Reconciliation After M8.50 Priority Consumer Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-50-priority-consumer-requirements.md)
 - [Mainline Reconciliation After M8.49 Triage Prioritization Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-49-triage-prioritization-requirements.md)
 - [Mainline Reconciliation After M8.48 Triage Policy Requirements](../../../brainstorms/2026-04-21-mainline-reconciliation-after-m8-48-triage-policy-requirements.md)