Handbook
Studio — Docs Health UI
Forge Studio exposes Docs Health under each project (see projects/:name/docs-health tokens in the route atlas). Cards and tables consume the GET feeds documented in Docs Health overlays.
Updated
What it is
Forge Studio exposes Docs Health under each project (see projects/:name/docs-health tokens in the route atlas). Cards and tables consume the GET feeds documented in Docs Health overlays.
When to use it
After policy or branch changes, or when First Docs Health scan shows queue growth — use the UI for severity scanning before opening work-items in raw JSON.
API alignment
| Concern | Reference |
|---|---|
| Summary vs work-items totals | Docs Health overlays |
| Safe automation | Schemas and API for builders |
| Session-scoped routes | Atlas Home row (.../docs-health/session/:sessionId) |
Verify
Open Docs Health for a project that should have signal; the UI should list issues consistent with a GET /api/docs-health/work-items sample from the same server (counts may be filtered — compare trends, not literal clones).