Restore policy simulation history compatibility
This commit is contained in:
@@ -38,6 +38,17 @@ Non-goals: policy authoring UI (handled by Console), ingestion or advisory norma
|
||||
- Translation sources are layered deterministically: shared embedded `common` bundle -> Policy embedded bundle (`Translations/*.policy.json`) -> Platform runtime override bundle.
|
||||
- The rollout localizes selected request validation and readiness responses for `en-US` and `de-DE`.
|
||||
|
||||
### 1.2 · Simulation compatibility contract (Sprint 20260309_011)
|
||||
|
||||
- The Policy Gateway exposes a deterministic compatibility surface for the Console simulation history workflow while the deeper Policy Engine read models continue to evolve.
|
||||
- Compatibility endpoints under `/policy` include:
|
||||
- `GET /policy/simulations/history`
|
||||
- `GET /policy/simulations/compare`
|
||||
- `POST /policy/simulations/{simulationId}/verify`
|
||||
- `PATCH /policy/simulations/{simulationId}`
|
||||
- These endpoints return tenant-scoped history entries, comparison diffs, reproducibility checks, and pin state with stable field names that match the live Console contract (`resultHash`, `findingsBySeverity`, `pinned`, `matchPercentage`, `discrepancies`).
|
||||
- The compatibility layer is intentionally stateful per tenant so operators can exercise history actions end to end in the live shell without client-side mocks.
|
||||
|
||||
---
|
||||
|
||||
## 2 · High-Level Architecture
|
||||
|
||||
Reference in New Issue
Block a user