ahmido
f13a4ce409
Implements Spec 110 Ops‑UX Enforcement and applies the repo‑wide “enterprise” standard for operation start + dedup surfaces. Key points - Start surfaces: only ephemeral queued toast (no DB notifications for started/queued/running). - Dedup paths: canonical “already queued” toast. - Progress refresh: dispatch run-enqueued browser event so the global widget updates immediately. - Completion: exactly-once terminal DB notification on completion (per Ops‑UX contract). Tests & formatting - Full suite: 1738 passed, 8 skipped (8477 assertions). - Pint: `vendor/bin/sail bin pint --dirty --format agent` (pass). Notable change - Removed legacy `RunStatusChangedNotification` (replaced by the terminal-only completion notification policy). Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #134
10 lines
419 B
Markdown
10 lines
419 B
Markdown
# Contracts: No API Changes
|
|
|
|
This feature introduces **no new HTTP endpoints**, no new API resources, and no changes to existing request/response contracts.
|
|
|
|
Scope is limited to internal operation flow behavior:
|
|
|
|
- OperationRun status/outcome transitions must go through `OperationRunService`.
|
|
- Queued/running DB notifications are banned.
|
|
- Terminal completion notification is initiator-only and emitted exactly once.
|