Write One Capability's User Documentation PR

Docs guide-writer run. Write or improve ONE capability's user documentation in apps/docs/content on develop, and open one PR. If apps/docs/GUIDES.md exists, follow it exactly and ignore the rest of this body. Otherwise: 1. Read apps/docs/README.md (layout + frontmatter contract — obey it exactly, including whatever nesting it currently allows) and apps/docs/WRITER.md (rules: Jaah product name, read-only capture helper, the two TimeSaver logins only, never call task_credential_get/list, secrets never leave the capture process). 2. Capability backlog, in this order — pick the FIRST one without a good Get started / Concepts / how-to page: tasks & task lifecycle; epics and the persona pipeline (analysis → architecture → plan → coders → finish); chat (New Chat / advisor); playbooks & personas; schedules (Automation); projects & repositories; nodes & worktrees; model accounts; credentials; team, groups & access; billing & plan. Skip one already well covered; skip one whose sources changed on develop since prod's merge-base (WRITER.md's prod-lag guard). 3. For it write: a concept page (what it is, why, how it relates to other objects, lifecycle) and 1–3 how-to pages (one task each, numbered steps, button labels exactly as rendered on prod). Ground every claim in the live product (prod via the capture helper) and the code; never invent a control, field or step. Link to the existing reference page for the screen. Use screenshots via the capture helper where they help. 4. Pages are self-contained and RAG-friendly (they also train Jarvis, the Help assistant): clear headings, one topic per page, terms defined. 5. Set last_verified, run python3 tools/docs_coverage.py (0 contract errors), ./dc check full green, one PR with auto-merge. If nothing in the backlog needs work, end with no PR (no_code_needed) and say why. Out of scope: the API and real-time reference (separate schedule), changing product code.

Guide-writer backlog empty: every capability has a concept page and how-to guides meeting the bar; changelog and example tasks current. No pages changed, no PR.