You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[S9] Document supported APIs and audit compatibility surface #159
Build on the completed S8 settings/routing foundation without changing runtime behavior.
Deliverables
S9a — Supported architecture and adoption docs: Document the typed extension definition → activation facade → lifecycle hooks path and the Python ToolServer public facade. Explain extension/shared-library ownership, configuration boundaries, and why _settings/_routing remain private implementation details. Show the supported adoption path while preserving isort’s manual-lifecycle, lower-level APIs.
S9b — Compatibility audit: Record actual imports and usage across Black, Flake8, isort, mypy, and Pylint, including the reviewed revisions. Use that evidence to identify genuinely superseded entry points; add conservative compatibility/deprecation annotations only where justified, with replacement guidance. Do not infer that an API is unused.
Acceptance and exclusions
Docs and audit must agree with the supported surface; any proposed deprecation must cite consumer evidence and preserve existing callers. Start these as independent workstreams; introduce a dependency only if implementation demonstrates one. No removals or runtime behavior changes. Exclude deferred S4 (#143), layout/directory moves, dependency upgrades, and lifecycle/execution rewrites.
#162 will be closed without merging. #161 remains the only proposed S9 repository change and is being left open and unmerged, as requested. Existing manual lifecycles and lower-level APIs remain supported; no runtime changes are needed. This issue stays open for the documentation work.
Activity
edvilme commentedon Nov 17, 2026
S9 scope update (maintainer-approved): The five-consumer compatibility audit is complete and found no justified deprecations. Its full revision-linked evidence is preserved in the PR discussion, rather than becoming a permanent repository document.
#162 will be closed without merging. #161 remains the only proposed S9 repository change and is being left open and unmerged, as requested. Existing manual lifecycles and lower-level APIs remain supported; no runtime changes are needed. This issue stays open for the documentation work.
[S9a] Document supported architecture and adoption APIs (#161)