Workspace Validation Map

This document is the repo-level source of truth for which npm workspaces are active, which ones are release-critical, and which workflow path validates them.

<!-- docs-discovery-note:start --> For canonical documentation homes and public/internal positioning, use Package and Plugin Docs Map. This file remains the validation-contract ledger, not the primary package/plugin discovery index. <!-- docs-discovery-note:end -->

If a workspace stays active, it must meet one of these conditions:

• it is validated in .github/workflows/ci.yml
• it is validated in the release/staging workflows because that is the only meaningful contract surface
• it is explicitly called out here as intentionally excluded

Release-critical workspace families

These workspaces ship public packages or release-facing operational behavior. They are expected to stay aligned with both CI and release workflows.

Public advanced/runtime packages

These packages are publicly installable, but their canonical docs live primarily in package READMEs and the package/plugin docs map rather than the end-user getting-started flow.

Internal-only active workspaces

These workspaces are part of the active monorepo and ship code or operational behavior inside the repo, but they are not current public publish targets.

Explicit exclusions

There are currently no active npm workspaces that are intentionally excluded from validation. packages/transport-mux now participates in the workspace-coverage job through its package-local lint, typecheck, and test commands alongside build and scorecard:migration.