Rewrite reader docs for Automations

## Original requirement (verbatim, epic body) > When creating a cron, allo user to pick a different type of target. Currently the target is a project. Other types: node, none (just run a task without a project - we have that impelemented), what else? > > When node is a target it runs a task on all selected nodes. > > Implement a nice target selector, that allows to quickly add all, remove all, do all except specific, etc. It has to be a very compact and robust control. It must work for both projects, nodes and other targets. > > Make sure this is naturally working and improves previous work - triggers, crons, etc. All of these things (triggers, webhooks, crons, etc.) are combined into a unified coherent system that is state of the art and uses best practices (do a web research). Epic chain (this breakdown): C2 -> C1 -> C3 API; C4 TargetSelector; C5 TaskSpecFields; C6 Automations UI and C8 dev docs reach; then C7 reader docs (this child). ## This child: C7 Reader docs Replace the Schedules and Triggers reader docs with one Automations section describing the shipped UI (architecture section 8, C7). Owns AC6.2. Acceptance carried verbatim from the PRD: - **AC6.2** Reader docs (`apps/docs/content/using-jaah/schedules/`, `.../triggers/`) are replaced or updated to describe Automations, target types, selector modes and node targets, and the old doc URLs redirect. *Verify:* open the docs portal on dev and observe the new pages plus working redirects. ### How - Replace `apps/docs/content/using-jaah/schedules/` and `apps/docs/content/using-jaah/triggers/` with one `apps/docs/content/using-jaah/automations/` section covering: When kinds (schedule; webhook / GitHub / Gmail / Slack events), the Target part (Projects, Nodes; modes All · Specific · All except; live rules resolved at each run; the "Will run on N of M" preview; removed items shown as named chips), node targets (one task per node, pinned to it, running in an unprivileged folder workspace in the System "Nodes" project visible only to org admins/owners), the Task action (same fields as task create; attachments; optional assignee; no Dependencies / From Jira), the policy lines (missed runs skipped; target with an open previous task skipped), the Runs view (per-target outcomes), System automations (operators only). Follow the reader-doc conventions in `apps/docs/README.md` (frontmatter, route coverage) and `docs/standards/ui-copy-standards.md`; describe the UI as actually shipped by C6 (look at it on dev). - Redirects from every old doc URL under schedules/ and triggers/ to the matching automations page. Credentials & reach: `https://docs.dev.jaah.ai` - **verified after C8** (C8 makes it reachable from runner nodes; this child depends on C8). `https://app.dev.jaah.ai` with `gmind/skynet/dev-orgb` (verified) to look at the shipped UI. Jaah Deploy watch via `jaah-forge` (verified). Out of scope: Do NOT change application code or infra. Do NOT document deferred features ("None" target, other action types, tag/group rules, pause-on-failure, catch-up window, elevated node tasks) as available. Epic out of scope: no feature flag; Playbooks docs untouched. Done means: - AC6.2 - after your merge deploys, the new Automations pages render on `https://docs.dev.jaah.ai` and each old schedules/ and triggers/ URL redirects to its Automations page (no 404) - oracle: curl status + Location for each old URL and screenshots of the new pages, in your report. - The docs build and route-coverage checks pass - oracle: `./dc check full` output. - Content matches the shipped UI (mode names, labels, policy lines) - oracle: side-by-side screenshots of a doc section and the dev UI. - PR merged to develop; Jaah Deploy for the merge commit succeeds (fix and re-merge if not).

The Schedules and Triggers reader docs are replaced by one Automations section. PR #4961 is merged, CI is green and Jaah Deploy succeeded. The 5 new pages render on docs.dev and all 11 old URLs redirect to live pages. Locally, only the live restore stage failed: this host has no pytest. Deferred: the console-reference screen page and 6 UI suggestions (in the report).