Enhancement — raised during the teardown work.
Context
The operator controls added in #469 (ontology delete, tombstone flush, lane freeze) are synchronous request/response. Modeling them as jobs (on the existing queue + lane infra) would give progress, an audit trail, retry, and eventual consistency — and remove the "did it actually finish / is it really gone?" ambiguity that bit us during the delete/tombstone confusion.
To look into
- Which operator actions benefit from job-modeling vs. staying synchronous (small, instant ones may not).
- UX: how a job-backed delete/flush surfaces progress and completion in CLI + web.
- Reuse the lane manager / job queue rather than a parallel mechanism.
Enhancement — raised during the teardown work.
Context
The operator controls added in #469 (ontology delete, tombstone flush, lane freeze) are synchronous request/response. Modeling them as jobs (on the existing queue + lane infra) would give progress, an audit trail, retry, and eventual consistency — and remove the "did it actually finish / is it really gone?" ambiguity that bit us during the delete/tombstone confusion.
To look into