Summary
Update the repository documentation so it matches the current codebase and namespace layout.
Goal
Remove drift between the docs and the actual public API.
Problem
The repository documentation still references older namespace names and older API shapes in some files, which makes the package harder to learn correctly.
Scope
Design Expectations
- The docs should describe what the package actually exposes.
- Examples should use real namespaces and real entrypoints.
- The reference should be consistent with the current folder structure.
Acceptance Criteria
- Documentation no longer references removed namespaces such as
Core.Features.*.
- The main getting started path uses
ModularityKit.Context.Extensions.
- API reference pages map to the current code surface.
Non-Goals
- No marketing rewrite.
- No redesign of the docs site.
- No new runtime features.
Notes
This issue captures the remaining documentation work around the current code changes.
Summary
Update the repository documentation so it matches the current codebase and namespace layout.
Goal
Remove drift between the docs and the actual public API.
Problem
The repository documentation still references older namespace names and older API shapes in some files, which makes the package harder to learn correctly.
Scope
README.mdto use current namespacesDocs/Getting-Started.mdDocs/Basic-Usage.mdDocs/Core-Concepts.mdDocs/Architecture.mdDocs/API-Reference.mdto match the current namespace layoutDesign Expectations
Acceptance Criteria
Core.Features.*.ModularityKit.Context.Extensions.Non-Goals
Notes
This issue captures the remaining documentation work around the current code changes.