Coverage Audit

This audit is the maintenance check for the SecondPage documentation set. It keeps the docs aligned with product behavior while keeping the public material focused on operating SecondPage, not on how SecondPage is built.

Completion Requirements

Requirement	Evidence
User-facing workflows are inventoried.	The Feature Inventory lists access, organizations, navigation, Pages, Page capacity, design, review, sharing, connections, domains, billing, settings, audit, and Trash.
Agent-facing workflows are inventoried.	The Feature Inventory lists agent onboarding, management, connection, publishing, Page upload continuations, design tools, keys, comment queue, live data, exports, and agent mirrors.
Each workflow has an operating guide.	Every inventory row links to a guide in the MkDocs navigation.
The docs are organized as a living set.	The Documentation Plan defines sections, MkDocs features, and maintenance workflow.
Agent-readable docs are generated from the same source.	The docs build creates llms.txt, skill.md, and manifest.json.
Public docs avoid proprietary implementation details.	The publish payload scan checks for source breadcrumbs, internal provider names, stale tool names, and placeholder text.
The docs are publishable through SecondPage.	The bundle dry run builds a static bundle with an entrypoint and machine-readable agent files.

In Scope

• Customer sign-in, sign-up, organization selection, invitations, and access requests.
• Workspace navigation, the Pages library, and Page capacity.
• Page review, comments, Edits, revisions, sharing, visibility, and Page activity.
• Guided Page design and generated draft review.
• Connections, custom domains, plans, billing, account settings, organization settings, audit, and Trash.
• Agent setup, MCP connection, Page publishing, Page upload continuations, static bundle updates, design tools, live data tools, exports, API keys, and comment queue.

Out Of Scope

The public product docs intentionally exclude internal admin consoles, cron jobs, private health checks, webhook receiver internals, QA harnesses, database structure, credential storage details, vendor implementation details, and private service boundaries.

If one of those surfaces becomes part of a normal customer or agent workflow, add it to the Feature Inventory first, then write an operator-facing guide.

Audit Workflow

1. Compare the Feature Inventory with current app navigation, public access screens, settings screens, Page controls, and agent tool registrations.
2. Add or update guides for any missing customer or agent workflow.
3. Keep hidden verification notes in frontmatter so maintainers can trace each page back to the product surface it describes.
4. Regenerate agent mirrors.
5. Run the strict MkDocs build.
6. Run the SecondPage bundle dry run.
7. Run docs:check to scan the publish payload for sensitive terms and placeholder text.