By seam

Public-Private Seam Map

These are the most important places where the public package set still has incomplete boundaries, mixed support levels, or backend-oriented artifacts.

mixed

Maker TypeScript Discovery Boundary

In the public materials reviewed for this repo, Maker exposes a function-discovery path whose standalone install workflow is not clearly documented.

discovery boundary with incomplete public install guidance confidence high

Inspect seam ->

mixed

Internal-Shaped Output Artifacts

Some public packages emit outputs that look like platform or backend contracts rather than polished end-user artifacts.

internal-shaped output artifact confidence medium

Inspect seam ->

mixed

Public Wrapper Around Non-Public Runtime

Some packages are intentionally public as installers or access layers while the full runtime remains outside the visible package surface.

public wrapper around non-public runtime confidence high

Inspect seam ->

mixed

Support-Level Boundary Packages

Some packages are visible in registries or release machinery but are not framed as normal public developer entry points.

visible package with limited public support confidence high

Inspect seam ->