refactor(plugin-sdk): annotate dormant reserved subpaths

This commit is contained in:
Peter Steinberger 2026-04-28 04:39:29 +01:00
parent 0ff60d162c
commit 4fb543796b
No known key found for this signature in database
6 changed files with 414 additions and 48 deletions

View file

@ -96,8 +96,11 @@ compatibility records, cross-owner reserved SDK imports, or unused reserved SDK
subpaths without a dormant classification. The report groups deprecated
compatibility records by removal date, counts local code/docs references,
surfaces cross-owner reserved SDK imports, classifies dormant reserved SDK
subpaths, and summarizes the private memory-host SDK bridge so compatibility
cleanup stays explicit instead of relying on ad hoc searches.
subpaths with owner/replacement/remove-after metadata, and summarizes the
private memory-host SDK bridge so compatibility cleanup stays explicit instead
of relying on ad hoc searches. Dormant reserved SDK subpaths are package exports
with no tracked repo imports; keep them until their recorded removal date unless
a separate compatibility review proves the external import never shipped.
If a manifest field is still accepted, plugin authors can keep using it until
the docs and diagnostics say otherwise. New code should prefer the documented

View file

@ -11,7 +11,9 @@ This page catalogs the commonly used subpaths grouped by purpose. The generated
full list of 200+ subpaths lives in `scripts/lib/plugin-sdk-entrypoints.json`;
reserved bundled-plugin helper subpaths appear there but are implementation
detail unless a doc page explicitly promotes them. Maintainers can audit active
and dormant reserved helper subpaths with `pnpm plugins:boundary-report:summary`.
and dormant reserved helper subpaths with `pnpm plugins:boundary-report:summary`;
the full JSON report includes dormant helper owner, replacement, and
remove-after metadata.
For the plugin authoring guide, see [Plugin SDK overview](/plugins/sdk-overview).