Fleet::pause_task / resume_task / stop_task exist and are tested in stella-fleet, and nothing calls them. Verified on main: every hit in stella-cli (fleet_cmd.rs:23, :522, :667, command_deck.rs:23) is a doc comment describing the verbs, not an invocation.
So the supervisor seam is real, tested, and unreachable by a user. The fleet dashboard already owns a live grid keyed by task id, which is exactly the surface these verbs were built for.
Wiring was deferred as a new user-facing feature with no witness test for interactive rendering — both true. But tested-and-unreachable code is the worst of both states: it carries maintenance cost and delivers nothing, while the docs tell readers the capability exists.
Acceptance: a supervisor can pause, resume and stop a task from the dashboard — or the verbs are gone.
Triaged out of #621 as worth doing.
Fleet::pause_task/resume_task/stop_taskexist and are tested instella-fleet, and nothing calls them. Verified onmain: every hit instella-cli(fleet_cmd.rs:23,:522,:667,command_deck.rs:23) is a doc comment describing the verbs, not an invocation.So the supervisor seam is real, tested, and unreachable by a user. The fleet dashboard already owns a live grid keyed by task id, which is exactly the surface these verbs were built for.
Wiring was deferred as a new user-facing feature with no witness test for interactive rendering — both true. But tested-and-unreachable code is the worst of both states: it carries maintenance cost and delivers nothing, while the docs tell readers the capability exists.
Acceptance: a supervisor can pause, resume and stop a task from the dashboard — or the verbs are gone.
Triaged out of #621 as worth doing.