fimo 0.15.0-staging.3 → 0.15.0

package/assets/skills/fimo-cli/references/schedules.md

@@ -9,6 +9,7 @@ The command starts in that environment's sandbox. Commands can still target anot
 ```bash
 fimo schedules create <name> --cron "0 2 * * *" --do "fimo validate"
 fimo schedules create <name> --cron "0 2 * * *" --do "pnpm sync" --secret CMS_TOKEN --secret SEARCH_KEY
+fimo schedules create <name> --cron "0 2 * * *" --do "fimo validate" --paused
 fimo schedules list
 fimo schedules show <schedule>
 fimo schedules update <schedule> --cron "0 3 * * *" --secret CMS_TOKEN
@@ -33,7 +34,9 @@ Scheduled commands run in the project's environment runtime, not on the user's m
 
 Runs use at-least-once delivery. If Fimo loses a completion response, the same run may execute again. Side-effecting commands should use `FIMO_SCHEDULE_RUN_ID` as their idempotency key.
 
-Cron expressions use standard five-field syntax. Schedules must not run more often than every five minutes.
+Cron expressions use standard five-field syntax. The minimum cadence is owned by the organization's schedule plan and is shown by `fimo schedules list` and `fimo schedules show`. Use `--paused` to save a draft without consuming an active-schedule slot; it must satisfy the current cadence policy before it can be resumed.
+
+Schedules are subject to the current organization plan: capacity, cadence, compute, and concurrency limits can affect create, update, resume, and run. Treat the server response and the policy shown by `list`/`show` as the source of truth; the CLI explains whether to change the schedule, wait for a reset, or upgrade. Do not hardcode plan values in automation.
 
 ## Project secrets
 
@@ -60,7 +63,7 @@ Run detail includes status, timing, trigger, exit/error information, retained ou
 
 ## JSON
 
-All schedule commands support the CLI's global `--json` mode. List and run-history responses preserve the API page shape, including `items`, `nextCursor`, `usage`, and `policy`.
+All schedule commands support the CLI's global `--json` mode. List, detail, and run-history responses preserve the API shape, including the server-owned `plan` snapshot. The snapshot reports active slots, cadence, run-time and concurrency limits, compute usage, reset time, and policy state.
 
 ## Notes
 

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-17T13:37:37.289Z",
-  "cliVersion": "0.14.0",
+  "bundledAt": "2026-08-17T19:28:55.753Z",
+  "cliVersion": "0.15.0",
   "external": [
     "oxc-parser",
     "fsevents",