feat: add notification-threshold supersession summary

Author: Jacobinwwey

docs/brainstorms/2026-04-16-mainline-ci-stabilization-and-m7-direction-requirements.md

@@ -969,7 +969,7 @@ Suggested verification slice:
 - Best next increment is not broader remediation or UI work.
   Best next increment is a narrow supersession summary surface over the existing history artifacts.
 
-### M7.27 (Next): Notification-Threshold Apply Outcome Supersession Summary (Lane Ops Bridge)
+### M7.27 (Now): Notification-Threshold Apply Outcome Supersession Summary (Lane Ops Bridge)
 
 Deliverables:
 
@@ -985,6 +985,60 @@ Suggested verification slice:
 - `npm run docs:diataxis:check`
 - `npm run docs:site:build`
 
+#### M7.27 Progress Note (2026-04-16)
+
+- [Done] expanded `src/server.ts` with compact supersession summary route:
+  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/summary?limit=...`.
+- [Done] added deterministic summary helper:
+  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeSupersessionSummary(...)`.
+- [Done] summary payload now layers compact operator handoff over the existing bounded history surface:
+  - `summary.scannedEntries`,
+  - `summary.counts.current`,
+  - `summary.counts.superseded`,
+  - `summary.counts.drifted`,
+  - `summary.latestCurrent`,
+  - `summary.latestSuperseded`,
+  - `summary.latestDrifted`.
+- [Done] summary semantics are now explicit:
+  - aligned latest entry is surfaced as `latestCurrent`,
+  - older covered entries are compacted under `latestSuperseded`,
+  - later-invalidated newest entry is surfaced as `latestDrifted`,
+  - all values remain bounded by the requested history scan limit.
+- [Done] expanded evidence coverage:
+  - `src/server.migration.test.ts` now validates pre-drift summary counts and latest snapshots, then validates drifted counts and latest drifted snapshot after a later override.
+  - `src/knowledge.api.contract.test.ts`, `src/agent_workspace.verification.contract.test.ts`, and `scripts/verify-agent-workspace-runtime.js` now fail fast on summary-route and summary-helper drift.
+- [Done] verification evidence:
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern "notification threshold apply outcome supersession summary stays deterministic"`
+  - `npm run test:agent-workspace:contracts`
+  - `npm run verify:agent-workspace:runtime`
+  - `npm run docs:diataxis:check`
+  - `npm run docs:site:build`
+
+### Post-M7.27 Architecture Judgment
+
+- L5 governance now covers preview, guarded apply, reconciliation, bounded history, and compact supersession summary for notification-threshold changes.
+- Current weak point shifts from operator scan effort to filterability:
+  - operators can now get a compact summary without scanning the whole list,
+  - operators still cannot request a targeted filtered slice such as drifted-only or superseded-only entries from the history surface.
+- Best next increment is not broader remediation or UI work.
+  Best next increment is a narrow filtered history surface over the existing bounded apply-outcome history.
+
+### M7.28 (Next): Notification-Threshold Filtered Outcome History Views (Lane Ops Bridge)
+
+Deliverables:
+
+- add read-only filtered history views for bounded apply-outcome history.
+- support compact filtering by reconciliation status so operators can request drifted-only, superseded-only, or current-only slices without client-side scanning.
+- keep scope limited to notification-threshold governance; do not reopen UI, unrelated remediation lanes, or retrieval/memory work.
+
+Suggested verification slice:
+
+- `npm test -- src/server.migration.test.ts --runInBand --testNamePattern "notification threshold filtered outcome history"`
+- `npm run test:agent-workspace:contracts`
+- `npm run verify:agent-workspace:runtime`
+- `npm run docs:diataxis:check`
+- `npm run docs:site:build`
+
 ## Success Criteria
 
 - CI failure mode that previously blocked the three agent-workspace suites is eliminated on mainline.
@@ -994,4 +1048,4 @@ Suggested verification slice:
 
 ## Next Step
 
-Proceed to `/prompts:ce-plan` using this document as the source for `M7.27` decomposition (notification-threshold apply outcome supersession summary), while preserving M7 lane boundary constraints.
+Proceed to `/prompts:ce-plan` using this document as the source for `M7.28` decomposition (notification-threshold filtered outcome history views), while preserving M7 lane boundary constraints.

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

@@ -599,34 +599,31 @@ Execution anchor:
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 
-## Latest Mainline Increment (2026-04-16 M7.26 Notification-Threshold Apply Outcome History Surface Lane)
-
-- Expanded `src/server.ts` with bounded history route:
-  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/history?limit=...`.
-- Added file-backed apply-outcome history persistence:
-  - `runtime_data/agent_workspace_diagnostics/triage_remediation_escalation_notification_threshold_apply_outcome_history.v1.json`.
-- Added deterministic history helper stack:
-  - `readAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`,
-  - `appendAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`,
-  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistorySurface(...)`.
-- Hardened operator handoff without widening scope:
-  - apply execution now writes both the latest single-record outcome and bounded newest-first history,
-  - history payload now exposes per-entry `reconciliation.isLatestOutcome`, `reconciliation.latestAuditMatchesEntry`, `reconciliation.activeThresholdsMatchEntry`, `reconciliation.status`, and `reconciliation.driftReasons`.
-- Added deterministic history semantics:
-  - aligned newest entry reports `current`,
-  - older entries superseded by later applies report `superseded`,
-  - newest entry later invalidated by follow-up overrides reports `drifted`.
+## Latest Mainline Increment (2026-04-16 M7.27 Notification-Threshold Apply Outcome Supersession Summary Lane)
+
+- Expanded `src/server.ts` with compact supersession summary route:
+  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/summary?limit=...`.
+- Added deterministic summary helper:
+  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeSupersessionSummary(...)`.
+- Hardened operator scan effort without widening scope:
+  - summary payload now exposes `summary.scannedEntries`, `summary.counts`, `summary.latestCurrent`, `summary.latestSuperseded`, and `summary.latestDrifted`,
+  - summary is computed over the existing bounded history surface rather than introducing a separate persistence model.
+- Added deterministic supersession summary semantics:
+  - aligned latest entry is surfaced as `latestCurrent`,
+  - older covered entries compact under `latestSuperseded`,
+  - later-invalidated newest entry is surfaced as `latestDrifted`,
+  - all values stay bounded by the requested scan limit.
 - Expanded executable evidence:
-  - `src/server.migration.test.ts` now validates newest-first history ordering, persisted history-file contents, superseded older entries, and later drift of the newest entry.
+  - `src/server.migration.test.ts` now validates pre-drift summary counts/latest snapshots and post-drift counts/latest drifted snapshot after a later override.
 - Hardened runtime verification gate:
-  - `src/knowledge.api.contract.test.ts`, `src/agent_workspace.verification.contract.test.ts`, and `scripts/verify-agent-workspace-runtime.js` now fail fast on notification-threshold history route and history-helper drift.
+  - `src/knowledge.api.contract.test.ts`, `src/agent_workspace.verification.contract.test.ts`, and `scripts/verify-agent-workspace-runtime.js` now fail fast on notification-threshold summary route and summary-helper drift.
 - Verification evidence:
-  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome history stays deterministic\"`
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome supersession summary stays deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 - Next direction judgment:
-  - current bottleneck shifts from history availability to compact operator summary,
-  - M7.27 should stay bounded to supersession summary, not broader remediation or UI expansion.
+  - current bottleneck shifts from summary compactness to filterability,
+  - M7.28 should stay bounded to filtered history views, not broader remediation or UI expansion.
 
 ## Mainline vs Working-Branch Snapshot (2026-04-14)
 
@@ -676,7 +673,7 @@ This dashboard aligns against the following requirement chain:
 | L2 Retrieval | explainable hybrid/vector retrieval + governance | Expanded in branch-oriented plans | Mainline file-backed baseline only (`src/learning/store.ts`) | Re-enter lane after concrete module evidence lands on mainline |
 | L3 Learning | mastery diagnostics + path/session loop | Expanded in branch | Partially integrated | Contract and integration parity |
 | L4 Interaction | agent conversation + focus/path pane runtime | Implemented in branch | M1-M4 baseline integrated on mainline | Expand capability surface via typed contract only |
-| L5 Governance | runbook, diagnostics, replay/autonomy controls | Expanded in branch | Operator diagnostics persistence/triage/history/threshold governance + runbook automation/audit + adaptive simulation/remediation + remediation backtest/approval-gate + approval-policy hardening/regression-alarms + approval-policy drift/escalation + escalation acknowledgement lifecycle/audit + escalation SLA/reminder baseline + notification digest/suppression baseline + delivery-log observability + stale-cleanup health auditing + anomaly/retention governance + notification SLO governance + notification-threshold override/audit governance + rollback preview/drift-diff governance + rollback apply guardrails + latest apply-outcome reconciliation + bounded apply-outcome history integrated | M7.27: notification-threshold apply outcome supersession summary |
+| L5 Governance | runbook, diagnostics, replay/autonomy controls | Expanded in branch | Operator diagnostics persistence/triage/history/threshold governance + runbook automation/audit + adaptive simulation/remediation + remediation backtest/approval-gate + approval-policy hardening/regression-alarms + approval-policy drift/escalation + escalation acknowledgement lifecycle/audit + escalation SLA/reminder baseline + notification digest/suppression baseline + delivery-log observability + stale-cleanup health auditing + anomaly/retention governance + notification SLO governance + notification-threshold override/audit governance + rollback preview/drift-diff governance + rollback apply guardrails + latest apply-outcome reconciliation + bounded apply-outcome history + supersession summary integrated | M7.28: notification-threshold filtered outcome history views |
 
 ## Verification Baseline
 

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

@@ -601,34 +601,31 @@
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 
-## 主线最新增量（2026-04-16 M7.26 通知阈值 apply outcome history surface 链路）
-
-- 已在 `src/server.ts` 增加有界 history 路由：
-  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/history?limit=...`。
-- 已增加 file-backed apply-outcome history 持久化：
-  - `runtime_data/agent_workspace_diagnostics/triage_remediation_escalation_notification_threshold_apply_outcome_history.v1.json`。
-- 已增加确定性 history helper 栈：
-  - `readAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`，
-  - `appendAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`，
-  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistorySurface(...)`。
-- 已在不扩 scope 前提下补足 operator handoff：
-  - apply 执行现在同时写入 latest 单记录 outcome 与有界 newest-first history，
-  - history 载荷现在输出逐条 `reconciliation.isLatestOutcome`、`reconciliation.latestAuditMatchesEntry`、`reconciliation.activeThresholdsMatchEntry`、`reconciliation.status` 与 `reconciliation.driftReasons`。
-- 已增加确定性 history 语义：
-  - 对齐的最新 entry 报告 `current`，
-  - 被后续 apply 覆盖的旧 entry 报告 `superseded`，
-  - 最新 entry 被后续 override 破坏时报告 `drifted`。
+## 主线最新增量（2026-04-16 M7.27 通知阈值 apply outcome supersession summary 链路）
+
+- 已在 `src/server.ts` 增加紧凑 supersession summary 路由：
+  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/summary?limit=...`。
+- 已增加确定性 summary helper：
+  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeSupersessionSummary(...)`。
+- 已在不扩 scope 前提下压缩 operator 扫描成本：
+  - summary 载荷现在输出 `summary.scannedEntries`、`summary.counts`、`summary.latestCurrent`、`summary.latestSuperseded` 与 `summary.latestDrifted`，
+  - summary 基于既有 bounded history surface 计算，不再引入新的持久化模型。
+- 已增加确定性 supersession summary 语义：
+  - 对齐的最新 entry 被汇总为 `latestCurrent`，
+  - 仍在扫描窗口内的旧 entry 被压缩到 `latestSuperseded`，
+  - 被后续 override 破坏的最新 entry 被汇总为 `latestDrifted`，
+  - 所有值都受请求扫描上限约束。
 - 已补可执行证据：
-  - `src/server.migration.test.ts` 现在覆盖 newest-first history 顺序、history 文件持久化内容、旧 entry 的 superseded 状态，以及最新 entry 的后续 drift。
+  - `src/server.migration.test.ts` 现在覆盖 drift 前 summary 计数/最新快照，以及后续 override 之后的 drifted summary 计数/最新快照。
 - 已加固 runtime 门禁：
-  - `src/knowledge.api.contract.test.ts`、`src/agent_workspace.verification.contract.test.ts` 与 `scripts/verify-agent-workspace-runtime.js` 现在对 notification-threshold history 路由与 history helper 做 fail-fast 断言。
+  - `src/knowledge.api.contract.test.ts`、`src/agent_workspace.verification.contract.test.ts` 与 `scripts/verify-agent-workspace-runtime.js` 现在对 notification-threshold summary 路由与 summary helper 做 fail-fast 断言。
 - 验证证据：
-  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome history stays deterministic\"`
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome supersession summary stays deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 - 后续方向判断：
-  - 当前瓶颈从 history 可用性转向紧凑 operator summary，
-  - M7.27 应继续收敛在 supersession summary，不要扩成更大的 remediation 或 UI 子系统。
+  - 当前瓶颈从 summary 紧凑性转向 filterability，
+  - M7.28 应继续收敛在 filtered history views，不要扩成更大的 remediation 或 UI 子系统。
 
 ## 主线 vs 工作分支快照（2026-04-14）
 
@@ -678,7 +675,7 @@
 | L2 检索层 | 可解释混合/向量检索 + 治理 | 分支规划增强中 | 主线当前为 file-backed 基线（`src/learning/store.ts`） | 待主线出现对应模块证据后再收敛 |
 | L3 学习层 | 掌握诊断 + 路径/会话闭环 | 分支增强中 | 主线部分集成 | 契约与集成一致性 |
 | L4 交互层 | agent 对话 + focus/path pane 运行时 | 分支已实现 | 主线 M1-M4 已落入基线 | 继续通过 typed contract 扩展动作面 |
-| L5 治理层 | runbook/诊断/回放与自动化 | 分支增强中 | 主线已集成运维诊断持久化/分级/趋势历史/阈值治理 + runbook 自动化/阈值审计 + 自适应模拟/自动修复 + 回测/批准门禁 + 批准策略硬化/回归告警 + 批准策略漂移/升级 + 升级确认生命周期/审计 + 升级 SLA/提醒基线 + 通知摘要/抑制基线 + 交付日志可观测性 + 陈旧通知健康审计 + 异常/retention 治理 + 通知 SLO 治理 + 通知阈值覆盖/审计治理 + 回滚预览/drift-diff 治理 + 回滚 apply guardrails + latest apply-outcome reconciliation + bounded apply-outcome history | M7.27：通知阈值 apply outcome supersession summary |
+| L5 治理层 | runbook/诊断/回放与自动化 | 分支增强中 | 主线已集成运维诊断持久化/分级/趋势历史/阈值治理 + runbook 自动化/阈值审计 + 自适应模拟/自动修复 + 回测/批准门禁 + 批准策略硬化/回归告警 + 批准策略漂移/升级 + 升级确认生命周期/审计 + 升级 SLA/提醒基线 + 通知摘要/抑制基线 + 交付日志可观测性 + 陈旧通知健康审计 + 异常/retention 治理 + 通知 SLO 治理 + 通知阈值覆盖/审计治理 + 回滚预览/drift-diff 治理 + 回滚 apply guardrails + latest apply-outcome reconciliation + bounded apply-outcome history + supersession summary | M7.28：通知阈值 filtered outcome history views |
 
 ## 验证基线
 

scripts/verify-agent-workspace-runtime.js

@@ -176,6 +176,10 @@ function verifyAgentWorkspaceRuntime(repoRoot = path.resolve(__dirname, '..')) {
     serverSource.includes('/api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/history'),
     'Missing diagnostics remediation escalation notification-threshold reconciliation history route in src/server.ts'
   );
+  assert(
+    serverSource.includes('/api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/summary'),
+    'Missing diagnostics remediation escalation notification-threshold reconciliation summary route in src/server.ts'
+  );
   assert(
     serverSource.includes('/api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/audit'),
     'Missing diagnostics remediation escalation notification-threshold audit route in src/server.ts'
@@ -392,6 +396,10 @@ function verifyAgentWorkspaceRuntime(repoRoot = path.resolve(__dirname, '..')) {
     serverSource.includes('buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistorySurface'),
     'Missing remediation escalation notification threshold history surface helper in src/server.ts'
   );
+  assert(
+    serverSource.includes('buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeSupersessionSummary'),
+    'Missing remediation escalation notification threshold supersession summary helper in src/server.ts'
+  );
   assert(
     serverSource.includes('buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationAnomalyReport'),
     'Missing remediation escalation notification anomaly report helper in src/server.ts'