Seam dossier
Support-Level Boundary Packages
Some packages are visible in registries or release machinery but are not framed as normal public developer entry points.
public surface: generated namespace packagespublic surface: lower-level registry artifacts
This pattern matters because it shows package visibility is not the same thing as supportability. A package being on npm does not automatically make it a public contract.
Evidence
Why this seam matters
- some registry-visible packages are not presented as ordinary public developer surfaces
- package visibility and support level do not always match one-to-one