Package and Plugin Docs Map

This page is the canonical discovery index for package and plugin documentation in the Babysitter monorepo.

Use it to answer three questions quickly:

1. Is this surface public, public-but-advanced, or internal-only? 2. Where is the canonical documentation home for that surface right now? 3. Which surfaces still rely on a package README or this map instead of a dedicated docs-site page?

docs/workspace-validation.md remains the validation-contract ledger. It is **not** the primary docs discovery entrypoint anymore.

Status labels

• **Public package**: supported public npm or app surface.
• **Public advanced/runtime package**: public and supported, but primarily for operator/runtime workflows rather than first-time users.
• **Public family package**: a published package that belongs to a larger package family whose overview docs also matter.
• **Public harness plugin**: a supported harness/plugin surface for a specific host.
• **Internal-only workspace**: active inside this monorepo, but not documented as a productized public offering.
• **Internal-only companion app**: repo-active support app surface with no separate public docs contract.

Family entrypoints

Public core and runtime packages

Public product and operator apps

Public package families

Public harness plugins

Internal-only workspaces and companion apps

Coverage rules for future changes

• If a new active workspace or plugin is added, update this map in the same change.
• If a public surface still relies only on a package README, note that explicitly here until a docs-site page exists.
• If a surface is internal-only, say so plainly here or in the package README instead of implying external product support.
• If a package or plugin is promoted from internal-only to public, update the package metadata, README status block, and this map together.