feat: add notification-threshold apply history

Author: Jacobinwwey

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

@@ -911,7 +911,7 @@ Suggested verification slice:
 - Best next increment is not broader remediation expansion.
   Best next increment is a narrow history surface for apply outcomes and their reconciliation statuses.
 
-### M7.26 (Next): Notification-Threshold Apply Outcome History Surface (Lane Ops Bridge)
+### M7.26 (Now): Notification-Threshold Apply Outcome History Surface (Lane Ops Bridge)
 
 Deliverables:
 
@@ -927,6 +927,64 @@ Suggested verification slice:
 - `npm run docs:diataxis:check`
 - `npm run docs:site:build`
 
+#### M7.26 Progress Note (2026-04-16)
+
+- [Done] expanded `src/server.ts` with bounded history route:
+  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation/history?limit=...`.
+- [Done] added file-backed apply-outcome history persistence:
+  - `runtime_data/agent_workspace_diagnostics/triage_remediation_escalation_notification_threshold_apply_outcome_history.v1.json`.
+- [Done] added deterministic history helper stack:
+  - `readAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`,
+  - `appendAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistory(...)`,
+  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeHistorySurface(...)`.
+- [Done] apply execution now writes both:
+  - latest single-record outcome file for fast reconciliation,
+  - bounded newest-first history for operator handoff across multiple applies.
+- [Done] history payload now exposes bounded per-entry reconciliation state:
+  - `reconciliation.isLatestOutcome`,
+  - `reconciliation.latestAuditMatchesEntry`,
+  - `reconciliation.activeThresholdsMatchEntry`,
+  - `reconciliation.status`,
+  - `reconciliation.driftReasons`.
+- [Done] history semantics are now explicit:
+  - latest aligned entry reports `current`,
+  - older entries superseded by later applies report `superseded`,
+  - latest entry later invalidated by follow-up overrides reports `drifted`.
+- [Done] expanded evidence coverage:
+  - `src/server.migration.test.ts` now validates newest-first history ordering, persisted history-file contents, superseded older apply entries, and later drift of the newest entry.
+  - `src/knowledge.api.contract.test.ts`, `src/agent_workspace.verification.contract.test.ts`, and `scripts/verify-agent-workspace-runtime.js` now fail fast on history-route and history-helper drift.
+- [Done] verification evidence:
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern "notification threshold apply outcome history 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.26 Architecture Judgment
+
+- L5 governance now covers preview, guarded apply, latest-outcome reconciliation, and bounded apply-outcome history for notification-threshold changes.
+- Current weak point shifts from handoff continuity to compact summary:
+  - operators can inspect recent apply history with per-entry status,
+  - operators still lack a concise aggregate view that says how many recent entries are current, superseded, or drifted without scanning the list.
+- 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)
+
+Deliverables:
+
+- add read-only summary surface over bounded apply-outcome history.
+- report concise counts and latest-entry snapshots for `current`, `superseded`, and `drifted` states so operator handoff does not require manual list 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 apply outcome supersession summary"`
+- `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.
@@ -936,4 +994,4 @@ Suggested verification slice:
 
 ## Next Step
 
-Proceed to `/prompts:ce-plan` using this document as the source for `M7.26` decomposition (notification-threshold apply outcome history surface), while preserving M7 lane boundary constraints.
+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.

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

@@ -599,34 +599,34 @@ Execution anchor:
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 
-## Latest Mainline Increment (2026-04-16 M7.25 Notification-Threshold Apply Outcome Reconciliation Lane)
-
-- Expanded `src/server.ts` with explicit reconciliation route:
-  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation`.
-- Added file-backed latest-apply outcome persistence:
-  - `runtime_data/agent_workspace_diagnostics/triage_remediation_escalation_notification_threshold_apply_outcome.v1.json`.
-- Added deterministic reconciliation helper stack:
-  - `readAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcome(...)`,
-  - `writeAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcome(...)`,
-  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeReconciliation(...)`.
-- Hardened operator readback without widening scope:
-  - apply execution now persists latest preview fingerprint, applied mode, audit id/changedAt, source/reason, and applied threshold snapshot,
-  - reconciliation payload now exposes `latestApplyOutcome`, `currentActiveThresholds`, `latestAuditEntry`, and bounded drift booleans/reasons.
-- Added deterministic reconciliation semantics:
-  - no apply outcome yields bounded `no-apply-outcome`,
-  - superseding audit entries mark the last apply outcome as drifted,
-  - active threshold divergence is reported independently from audit supersession.
+## 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`.
 - Expanded executable evidence:
-  - `src/server.migration.test.ts` now validates immediate post-apply reconciliation, persisted apply-outcome file contents, and drift detection after a later override.
+  - `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.
 - 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 reconciliation route and apply-outcome 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 history route and history-helper drift.
 - Verification evidence:
-  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome reconciliation stays deterministic\"`
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome history stays deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 - Next direction judgment:
-  - current bottleneck shifts from latest-outcome readback to bounded operator handoff/history,
-  - M7.26 should stay bounded to apply-outcome history, not broader remediation or UI expansion.
+  - current bottleneck shifts from history availability to compact operator summary,
+  - M7.27 should stay bounded to supersession summary, not broader remediation or UI expansion.
 
 ## Mainline vs Working-Branch Snapshot (2026-04-14)
 
@@ -676,7 +676,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 integrated | M7.26: notification-threshold apply outcome history surface |
+| 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 |
 
 ## Verification Baseline
 

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

@@ -601,34 +601,34 @@
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 
-## 主线最新增量（2026-04-16 M7.25 通知阈值 apply 结果对账链路）
-
-- 已在 `src/server.ts` 增加显式 reconciliation 路由：
-  - `GET /api/knowledge/operator/agent-workspace-diagnostics/triage/remediation/escalation/notification-thresholds/reconciliation`。
-- 已增加 file-backed latest-apply outcome 持久化：
-  - `runtime_data/agent_workspace_diagnostics/triage_remediation_escalation_notification_threshold_apply_outcome.v1.json`。
-- 已增加确定性 reconciliation helper 栈：
-  - `readAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcome(...)`，
-  - `writeAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcome(...)`，
-  - `buildAgentWorkspaceDiagnosticsRemediationEscalationNotificationThresholdApplyOutcomeReconciliation(...)`。
-- 已在不扩 scope 前提下补足 operator readback：
-  - apply 执行现在持久化 latest preview fingerprint、applied mode、audit id/changedAt、source/reason 与 applied threshold snapshot，
-  - reconciliation 载荷现在输出 `latestApplyOutcome`、`currentActiveThresholds`、`latestAuditEntry` 与有界 drift 布尔量/原因。
-- 已增加确定性 reconciliation 语义：
-  - 没有 apply outcome 时返回有界 `no-apply-outcome`，
-  - 后续 superseding audit 会把上一条 apply outcome 标记为 drifted，
-  - active threshold divergence 会独立于 audit supersession 单独报告。
+## 主线最新增量（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`。
 - 已补可执行证据：
-  - `src/server.migration.test.ts` 现在覆盖 apply 后即时 reconciliation、apply-outcome 文件持久化内容，以及后续 override 触发的 drift 检测。
+  - `src/server.migration.test.ts` 现在覆盖 newest-first history 顺序、history 文件持久化内容、旧 entry 的 superseded 状态，以及最新 entry 的后续 drift。
 - 已加固 runtime 门禁：
-  - `src/knowledge.api.contract.test.ts`、`src/agent_workspace.verification.contract.test.ts` 与 `scripts/verify-agent-workspace-runtime.js` 现在对 notification-threshold reconciliation 路由与 apply-outcome helper 做 fail-fast 断言。
+  - `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 断言。
 - 验证证据：
-  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome reconciliation stays deterministic\"`
+  - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"notification threshold apply outcome history stays deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 - 后续方向判断：
-  - 当前瓶颈从 latest-outcome readback 转向有界 operator handoff/history，
-  - M7.26 应继续收敛在 apply outcome history，不要扩成更大的 remediation 或 UI 子系统。
+  - 当前瓶颈从 history 可用性转向紧凑 operator summary，
+  - M7.27 应继续收敛在 supersession summary，不要扩成更大的 remediation 或 UI 子系统。
 
 ## 主线 vs 工作分支快照（2026-04-14）
 
@@ -678,7 +678,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 | M7.26：通知阈值 apply outcome history surface |
+| L5 治理层 | runbook/诊断/回放与自动化 | 分支增强中 | 主线已集成运维诊断持久化/分级/趋势历史/阈值治理 + runbook 自动化/阈值审计 + 自适应模拟/自动修复 + 回测/批准门禁 + 批准策略硬化/回归告警 + 批准策略漂移/升级 + 升级确认生命周期/审计 + 升级 SLA/提醒基线 + 通知摘要/抑制基线 + 交付日志可观测性 + 陈旧通知健康审计 + 异常/retention 治理 + 通知 SLO 治理 + 通知阈值覆盖/审计治理 + 回滚预览/drift-diff 治理 + 回滚 apply guardrails + latest apply-outcome reconciliation + bounded apply-outcome history | M7.27：通知阈值 apply outcome supersession summary |
 
 ## 验证基线