Context
The root ports package is a v3 compatibility surface, but new app design should prefer package-local or app-owned interfaces unless a shared root abstraction is clearly justified.
Review paths
- ROADMAP.md
- docs/stable-core.md
- docs/ports-surface.md
- docs/interface-ownership.md
- VERSIONING.md
Questions
- Which existing ports are still useful shared toolkit contracts?
- Which ports are historical compatibility surfaces that should not guide new designs?
- What evidence should be required before adding a new root ports export?
- Are the current app-owned interface recommendations clear enough for adopters?
Desired outcome
A review recommendation for the root ports shape: keep current policy, tighten it, or identify specific v4 cleanup candidates.
Context
The root ports package is a v3 compatibility surface, but new app design should prefer package-local or app-owned interfaces unless a shared root abstraction is clearly justified.
Review paths
Questions
Desired outcome
A review recommendation for the root ports shape: keep current policy, tighten it, or identify specific v4 cleanup candidates.