docs: module dossier + install/quickstart sync for truthful cutover sprints
- API_CLI_REFERENCE.md, INSTALL_GUIDE.md, quickstart.md, architecture/integrations.md, dev/DEV_ENVIRONMENT_SETUP.md, integrations/LOCAL_SERVICES.md: reflect real-service wiring. - docs/modules/**: module dossier updates across the modules touched by SPRINT_20260415_001..007 + SPRINT_20260416_003..017 + SPRINT_20260417_018..024 + SPRINT_20260418_025 + SPRINT_20260419_026. - docs/features/checked/web/**: update feature notes where UI changed. - docs/qa/feature-checks/runs/web/evidence-presentation-ux/: QA evidence artifacts. - docs/setup/**, docs/technical/**: align with setup wizard contracts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -8,6 +8,14 @@ Task Runner now produces pack plans with explicit approval and policy-gate metad
|
||||
|
||||
Deliverables feed Sprint 37 tasks (`NOTIFY-SVC-37-00x`) and unblock Task Runner sprint 43 (`TASKRUN-43-001`).
|
||||
|
||||
## Implementation Status (2026-04-15)
|
||||
|
||||
- The current ingestion endpoint is `POST /api/v1/notify/pack-approvals` in `StellaOps.Notifier.WebService`.
|
||||
- Approval state now persists durably in `notify.pack_approvals`, with ingest/ack idempotency coordinated through durable `notify.locks`.
|
||||
- Pack-approval ingest writes through the shared Notify audit/repository path rather than host-local in-memory stores.
|
||||
- Restart-survival proof now exists in `StellaOps.Notifier.Tests.Integration.NotifierDurableRuntimeProofTests`: it boots real Postgres + Redis, submits a pack-approval event, restarts the web host, leases/processes the queued event through the live `NotifierEventProcessor`, and reads the durable delivery back through `/api/v2/notify/deliveries`.
|
||||
- The proof harness uncovered and closed a real persistence bug in `LockRepository` (`notify.locks` first-acquire semantics), which is now covered by `StellaOps.Notify.Persistence.Postgres.Tests.LockRepositoryTests`.
|
||||
|
||||
## Functional Requirements
|
||||
|
||||
### 1. Approval Event Contract
|
||||
|
||||
Reference in New Issue
Block a user