fix: prioritize operator input while preserving API run obligations #142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/operator-foreground-integration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Prioritize channel/operator questions over queued background work and steer active background prompts without cancelling independent workers. Preserve separate API prompts, overrides, progress and terminal-delivery obligations. Retain current Activity and Cron finalization boundaries and internal cron-followup suppression.
Seven files, 454 insertions / 14 deletions. No runtime/config/deployment changes.
Exact reviewed candidate
c31034a3d71e87b2a45839ed9da9f9263e1c1cd4ec41310ca46fa3a1f8dab4187b4b562eaa664fe15ee0098fb5d7cca26b2eab75abce877c186fdda26a059556dc3d69813ae4acf499d2c918a041f9435aac2a81793ecb4b4bc198a2Independent final integration review
878041a2-2d6e-4ff2-8ed0-c43ad0538131: no concrete P0/P1, explicitly including Activity/Cron adaptation. P2 F2 runtime-finalization window and F3 multi-address channel steering remain documented nonblocking limitations; no optional edits.Verification
These are local test results, not a claim of green forge CI. Actual head checks and effective branch policy are inspected separately before normal merge. Source merge does not activate a running instance. Parent retains the full mandate and separate notification correction.