CL-6362: Routines becomes a global-only surface

[TheGreatAxios]

Summary

• Routines moves from per-workbench chrome to one global page (/routines), added to the shell rail beside Files/Skills/Agents/Plugins/Insights. Every row: name, workbench attribution, running-or-not state, humanized schedule + next run, inline enable/disable, Run now, and an inline-expandable detail (recent runs + its delivery workbench).
• Visibility resolves through bench membership (useBench().memberships, the /api/me/principals principal model) — aggregates across every bench the account belongs to, not just the currently selected one, and is never creator-scoped (GET /routines already lists every routine a bench's own grant covers). Data stays workbench-scoped; this is UI consolidation only.
• Removed, not hidden: the workbench header's Routines and Insights buttons, the composer's /run command, and the canvas routine panel's list/runs views. The panel is editor-only now (create/edit), reached from the composer's /routine command, "New routine in this space", and the global page's own New/Edit actions.
• In-room routine cards (created-routine notices, run-now approval cards) are untouched — "visible where it was made" stays true. The routine-created/enabled notice's copy no longer points to the retired "Routines panel".
• check:ui-vocabulary passes; consumer language throughout (no raw cron strings — cadenceLabel/approximateNextRun are the only source).

Known gap (named, not half-built)

Run outcome delivery (a routine's own result messages landing in its delivery workbench) already exists via apps/hub/src/routine-launcher.ts's joinDeliveryWorkbench, covered by apps/hub/src/routine-launcher.test.ts — this PR surfaces that fact in the row ("Run updates post into ") but does not add new hub-level wiring or tests for it, since the mechanism predates this PR and lives outside apps/web/packages/chat-ui/packages/routines' scope here.

Creation-path polish beyond what already exists (in-room /routine create, "assign a workflow as a routine" from the library) was not in this box — the page, rail entry, and membership-based visibility are the complete slice; a richer creation flow is a follow-up.

Test plan

• bun run typecheck (apps/web, packages/chat-ui, packages/routines)
• bun test — apps/web (565 pass), packages/chat-ui (581 pass), packages/routines (228 pass)
• bun run lint (prettier + eslint) — clean on all touched files
• bun run check:ui-vocabulary — ok
• New test: a second bench's routine (not the selected one, not created by the viewer's own principal) renders on /routines, proving membership-based aggregation