Routines: ops-grade list and full detail page at /routines/<id>

[TheGreatAxios]

Closes https://linear.app/abklabs/issue/CL-6418

Routines become operable: the roster is an ops table and every routine gets its own page, replacing the placeholder CL-6412 routed there. This is surfacing work — the schedule and health telemetry (nextFireAt, consecutiveFailures, deadLetteredAt, and the per-fire routine_run history) was already recorded and simply never shown. No new storage, no new migration.

Addressing: /routines/<id> is canonical, a name resolves onto it

Corrected from the first revision of this PR, which had it backwards. DESIGN.md permits a slug in a route only where it is "immutable and tenant-unique, enforced as a hard database constraint — never a soft convention a migration can violate," and prescribes the opaque-ID route as the fallback where that can't be guaranteed. A routine has no slug column, so a name-derived slug is exactly the soft convention that rule forbids — it breaks on rename and collides across benches.

So the id is the address and renders the page directly, with no redirect hop. A name-shaped segment still resolves, as a convenience for links people typed or shared, by redirecting to the id path — so what lands in the address bar, a bookmark, and a shared link is always the durable address. A name two routines answer to resolves to neither and offers both by id link. An unknown segment says the routine is gone, rather than silently showing the roster under a URL that no longer means anything. resolveRoutineSegment is the whole rule in one pure function, and every branch is tested.

A real slug column for routines is ticketed separately and deliberately not built here.

Cron → English: cronstrue, and the old renderer is gone

cronstrue 3.24.0 — MIT, zero runtime dependencies, browser-safe — as a dependency of @corbits/routines. It had to be a real parser rather than a switch over the shapes cronExpressionForTrigger emits: the cron escape hatch, and now the detail page's editable expression field, accept any 5-field expression cron.ts validates.

Also corrected from the first revision, which claimed the Copy rule now held everywhere while routineCadenceLabel/routineCadenceSummary still shipped alongside — still emitting Cron: 0 9 * * 1-5 into the schedule editor's live summary (routine-schedule.tsx), the canvas panel's trigger rows (shell/routine-panel.tsx), and the in-workbench "routine created" notice (routes.ts). Both functions are deleted, every call site is cut over to routineScheduleSentence, and apps/web/src/routine-trigger.ts — whose remaining exports had no callers left — is deleted with them. One renderer, no parallel path.

Two rules keep the sentences honest: an interval keeps the schedule editor's own words ("Every 15 minutes", not cron's "On the hour, every 6 hours"), and the timezone is named only when the schedule has a wall clock to read in it — "Every 15 minutes (UTC)" says nothing.

Deploy skew: nextFireAt ships optional for one release

Explicitly choosing the optional-field path over documenting an atomic deploy. A browser on the new bundle can be talking to an un-upgraded hub, and a required field would make arktype reject the whole routines payload — blanking every routines surface over a display-only value. The wire schema carries a comment naming the tightening as a follow-up; absent and null read the same ("not scheduled"), which is the honest reading of "the server didn't say."

"Last run" has one definition

lastFireAt is written only inside claimRoutineFire, so a run-now-only routine reported "never run" beside a history table full of runs. It is removed from the wire rather than left as a second, disagreeing source; "last run" is health.lastRunAt — the newest row of the fire history — and the list column and the detail rail both read it.

Mutations report their own failures

useRoutineActions is the one place the three writes live, shared by both surfaces. Run-now, Pause/Resume, and Save schedule each catch and say what happened in words (routineActionFailedToast + describeApiError); Save schedule additionally keeps the draft and repeats it next to the field. No optimistic lies — a row changes when the hub says it changed — and no bare .then left to drop a 403 on the floor.

The rest

• health.ts decides what "healthy" means once: six states, each with a pill label and a caption saying the same thing in words (DESIGN.md, State Pills), plus clean streak, median fire duration, last failure.
• run-language.ts puts run statuses and fire causes into the reader's words — no more running / completed / schedule-failed enum values badged onto the screen.
• A past-due nextFireAt reads "Overdue", not "2h ago" under a "Next run" heading.
• The schedule editor trims once: the same expression is compared, previewed, and sent, and Save is enabled exactly when the expression is both runnable and describable.
• Tests assert the contract of the cron sentence (starts with At/Every, names the zone only with a wall clock, never contains the raw expression) rather than pinning cronstrue's exact phrasing, so a dependency upgrade can't turn into a red build with no behaviour change.
• detail-placeholders.tsx loses only its routine entry; the agent, skill, and plugin placeholders stay for their own tickets.

Deferred, ticketed separately

• ROUTINE_HEALTH_TONE belongs beside health.ts in the package (blocked only on BadgeTone being a react-ui type); noted in the file.
• A server-side health summary on GET /routines to collapse the per-bench client fan-out; noted in global-routines.ts.
• Routines list selection / bulk bar / context-menu parity with DESIGN.md's table grammar.
• Tightening nextFireAt to required once the hub is known-upgraded.
• A real slug column for routines.

Checks

bun run check is green for everything this PR touches (@workbench/web 660 pass / 0 fail; @corbits/routines 268 pass / 0 fail).

Two failures in @corbits/assistant-workflow are pre-existing on main, untouched by this branch: 0a2398d9 bumped @corbits/connections-tools to 0.0.5 without repinning workflows/assistant/src/index.ts, which still pins 0.0.4. Left alone rather than folded into an unrelated PR.

https://claude.ai/code/session_01Shhie5zM8L54bLHq5gFQti