Docs automation

Keep Taskcenter documentation generated from real project surfaces

Docs automation turns project files into documentation pages that the docs shell, search index, and docs assistant can read. It is a build-time feature: it scans source files, generates a typed manifest, and keeps generated pages separate from authored product docs.

Entry route

Entry route: /docs/introduction/docs-automation. Status: Live as a local build-time generator. Data source: docs/source/*.md, src/features/**, src/app/api/**/route.ts, src/app/**/page.tsx, .agents/skills/**/SKILL.md, skills/**/SKILL.md, and src/lib/permissions.ts. Required permissions: none at runtime because generation is local and read-only; authenticated access is still required for the docs assistant route. Empty state: if no generated sources are present, the authored docs still render. Failure state: the generator exits with a clear error and leaves the previous generated manifest untouched.

Operating model

The generator creates pages from authored Markdown sources and from project inventory scans. Generated pages are merged into the existing docs registry instead of replacing manually curated pages. That keeps the current shadcn-style shell while reducing the maintenance burden.

Agent-facing behavior

Generated docs become part of the docs assistant context through the same read-only documentation registry as authored pages. The docs assistant remains docs-only: it can summarize generated documentation, but it cannot mutate records, run tools, deploy, or inspect private workspace data. North Star can also inspect this registry through the read-only `searchDocs` and `readDocs` runtime tools. Those tools let the general agent fetch Taskcenter product docs, route contracts, feature status, failure states, and Cloudflare mapping before it explains or operates a feature. They do not grant private workspace access and they do not execute product actions.

Completion rule

Feature work should update either an authored docs source file or enough real project surface for the generator to discover it. A generated inventory page is evidence of what exists, not a substitute for a complete feature-specific docs page when behavior, permissions, or data contracts change.