pr9.2
This commit is contained in:
@@ -1,53 +1,3 @@
|
||||
# PR-9.2 — Public Surface Area Minimization
|
||||
|
||||
## Briefing
|
||||
|
||||
The public API must be minimal and intentional.
|
||||
|
||||
Internal modules must not leak implementation details.
|
||||
|
||||
## Target
|
||||
|
||||
1. Audit all `pub` items.
|
||||
2. Reduce visibility to `pub(crate)` where possible.
|
||||
3. Hide internal modules behind private boundaries.
|
||||
4. Ensure only intended API is exported.
|
||||
|
||||
Focus areas:
|
||||
|
||||
* VM core
|
||||
* Heap internals
|
||||
* Scheduler internals
|
||||
* GC internals
|
||||
|
||||
## Acceptance Checklist
|
||||
|
||||
* [ ] No unnecessary `pub` items.
|
||||
* [ ] Public API documented.
|
||||
* [ ] Internal types hidden.
|
||||
* [ ] `cargo doc` shows clean public surface.
|
||||
|
||||
## Tests
|
||||
|
||||
* Build documentation.
|
||||
* Ensure no accidental public modules remain.
|
||||
|
||||
## Junie Instructions
|
||||
|
||||
You MAY:
|
||||
|
||||
* Restrict visibility.
|
||||
* Refactor module structure.
|
||||
|
||||
You MUST NOT:
|
||||
|
||||
* Break existing internal usage.
|
||||
* Expose new APIs casually.
|
||||
|
||||
If removing `pub` causes architectural issue, STOP and escalate.
|
||||
|
||||
---
|
||||
|
||||
# PR-9.3 — Remove Temporary Feature Flags
|
||||
|
||||
## Briefing
|
||||
|
||||
Reference in New Issue
Block a user