Child of #1058. The registry publishes operator agents (AP 3-way match, AR collections, bank reconciliation, cycle-count planner, reorder replenishment) but no dispatch path exists for the Operator nature: run_agent_now refuses them and the cron sweep silently advances the slot with no run row, activity or notification, while Configure still offers "Run automatically" and prints a next run date, and Apply still pushes their bundles (forcing restarts for zero function).
Expected: either an Approval-Board dispatch path for operators, or they are not offered for install.
Actual: a user installs, enables, schedules, and waits forever.
Suspected location: jarvis/chat/agents_api.py run_agent_now nature gate, jarvis/chat/agent_scheduler.py _sweep_one, jarvis/agents/registry.json.
Interim: the UX polish branch marks these listings Coming Soon so they stop being installable; this issue tracks the real dispatch path.
Child of #1058. The registry publishes operator agents (AP 3-way match, AR collections, bank reconciliation, cycle-count planner, reorder replenishment) but no dispatch path exists for the Operator nature:
run_agent_nowrefuses them and the cron sweep silently advances the slot with no run row, activity or notification, while Configure still offers "Run automatically" and prints a next run date, and Apply still pushes their bundles (forcing restarts for zero function).Expected: either an Approval-Board dispatch path for operators, or they are not offered for install.
Actual: a user installs, enables, schedules, and waits forever.
Suspected location:
jarvis/chat/agents_api.pyrun_agent_now nature gate,jarvis/chat/agent_scheduler.py_sweep_one,jarvis/agents/registry.json.Interim: the UX polish branch marks these listings Coming Soon so they stop being installable; this issue tracks the real dispatch path.