docs(progress): refine m7.23 direction

Author: Jacobinwwey

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

@@ -707,6 +707,55 @@ Deliverables:
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
 
+### Post-M7.22 Architecture Judgment
+
+- L4 interaction lane remains stable enough for bounded operator-governance increments:
+  - current code reality still centers on `src/frontend/agent_workspace_runtime.js` + `src/server.ts` typed/runtime contract closure,
+  - no evidence yet justifies reopening broader pane/runtime architecture work inside this increment.
+- L5 governance lane now has a coherent progression instead of isolated helpers:
+  - triage thresholds,
+  - remediation approval gates,
+  - escalation lifecycle,
+  - notification delivery/anomaly/SLO governance,
+  - notification-threshold override/audit governance.
+- The main remaining gap is not another new route family.
+  The next high-leverage gap is operator safety around rollback preview and drift visibility before applying or resetting thresholds.
+
+### M7.23 (Next): Notification-Threshold Rollback Preview and Drift-Diff Governance (Lane Ops Bridge)
+
+Deliverables:
+
+- add bounded preview surface for comparing active notification thresholds against defaults before reset/apply.
+- expose structured drift diff so operators can see field-level deltas without reading raw audit history.
+- keep scope limited to notification-threshold governance; do not couple this increment to broader remediation-policy or pane-runtime work.
+
+Proposed boundaries:
+
+- In scope:
+  - read-only diff/preview route(s),
+  - default-vs-active threshold comparison payload,
+  - latest-audit-linked rollback preview semantics,
+  - executable tests and EN/ZH progress-doc updates.
+- Out of scope:
+  - UI wiring,
+  - cross-lane foundation retrieval work,
+  - markdown-reader changes,
+  - automatic rollback execution beyond explicit operator actions.
+
+Preferred implementation posture:
+
+- reuse the current file-backed governance style from `src/server.ts`,
+- avoid introducing a new generic config framework,
+- keep all new payloads deterministic and bounded by existing audit/retention constants.
+
+Suggested verification slice:
+
+- `npm test -- src/server.migration.test.ts --runInBand --testNamePattern "notification threshold rollback preview"`
+- `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.

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

@@ -624,6 +624,9 @@ Execution anchor:
   - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"escalation notification threshold overrides and audit-trail governance stay deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
+- Next direction judgment:
+  - current bottleneck is rollback visibility, not another broad governance subsystem,
+  - M7.23 should stay bounded to notification-threshold rollback preview and drift-diff governance on top of existing file-backed policy/audit artifacts.
 
 ## Mainline vs Working-Branch Snapshot (2026-04-14)
 

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

@@ -626,6 +626,9 @@
   - `npm test -- src/server.migration.test.ts --runInBand --testNamePattern \"escalation notification threshold overrides and audit-trail governance stay deterministic\"`
   - `npm run test:agent-workspace:contracts`
   - `npm run verify:agent-workspace:runtime`
+- 后续方向判断：
+  - 当前瓶颈是回滚可见性，不是继续扩一个更大的治理子系统，
+  - M7.23 应继续收敛在 notification-threshold rollback preview 与 drift-diff 治理，复用现有 file-backed policy/audit 产物。
 
 ## 主线 vs 工作分支快照（2026-04-14）