Ship Routines that stay off until someone turns them on

You can now ship a CompanyOS template with a Routine that waits for a person to switch it on. Set enabled=False on Agno's Routine, and the template's users see it in their list with no runs firing.

Routine(
    name="daily-review",
    executor_type="agent",
    executor_id="reviewer",
    instructions="Review documentation and propose useful improvements.",
    cron_expr="0 9 * * *",
    enabled=False,
)

We ran this declaration through AgentOS with FastAPI's TestClient on SQLite, with no model, on both releases. The test moved the Routine's next run into the past, so the scheduler's claim query had a due row to pick up. Real output:

Before: enabled: Extra inputs are not permitted [type=extra_forbidden, input_value=False, input_type=bool]
Now:    claim_due_schedule (disabled): None
        claim_due_schedule (resumed): documentation.daily-review

The flag defaults to True, and it works in Python and YAML declarations, POST /company/routines, POST /company/setup, CompanyManager, AsyncCompanyManager and CompanyTools. A repeated create request for the same name still returns 409 and leaves the Routine disabled.

Agno OS turns a Routine on through the existing resume endpoint, and AgentOS keeps that choice across restarts.

See the cookbook, and learn more about CompanyOS Routines in the documentation.