From 1fb9e068eef964f5188c404aeb395bce0eeb5556 Mon Sep 17 00:00:00 2001 From: damocles Date: Fri, 11 Sep 2026 23:20:31 +0200 Subject: [PATCH] docs: drop the operator-schedule-target aside from approvals.md --- docs/agent-lifecycle/approvals.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/docs/agent-lifecycle/approvals.md b/docs/agent-lifecycle/approvals.md index 7430ff2c..ffd3aa32 100644 --- a/docs/agent-lifecycle/approvals.md +++ b/docs/agent-lifecycle/approvals.md @@ -216,11 +216,6 @@ target drives `push_todo`'s own upsert-by-key dedup: a re-fire of the *same schedule* against a target that hasn't reviewed the last one collapses into that one todo instead of stacking up. -`operator` isn't a valid schedule target — she isn't a container with -a todo inbox to push a wake into, and this mechanism is for fanning a -prompt out to agents, not scheduling something at her. Rejected at -submit/edit time (`ScheduledPrompts::submit`/`update`). - ### Missing-target failure When a target name doesn't resolve to a known agent (container