prometeu-runtime/files/TODOs.md

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

During refactor phases, temporary feature flags or conditional compilation may have been introduced.

These must not remain in the final baseline.

Target

1. Identify all feature flags related to transitional behavior.
2. Remove obsolete cfg gates.
3. Remove commented legacy branches.
4. Ensure single authoritative execution path.

Acceptance Checklist

• No transitional feature flags remain.
• No commented-out legacy logic.
• Single execution model.
• All tests pass.

Tests

• Full test suite passes without feature toggles.

Junie Instructions

You MAY:

• Remove obsolete flags.
• Simplify code paths.

You MUST NOT:

• Remove legitimate platform flags.
• Leave partial dead branches.

If unsure whether a flag is temporary or architectural, STOP and ask.

---

PR-9.4 — Final Cleanup & Quality Sweep

Briefing

This PR performs the final cleanup pass.

Goal: Zero warnings. No dead code. No outdated examples.

Target

1. Remove dead modules/files.
2. Remove unused imports and code.
3. Eliminate compiler warnings.
4. Update outdated examples.
5. Remove stale TODOs referencing removed architecture.

Optional (if present):

• Enforce cargo clippy clean baseline.
• Ensure rustfmt compliance.

Acceptance Checklist

• No dead code.
• Zero compiler warnings.
• Clippy clean (if configured).
• Examples reflect new baseline.
• No TODO referencing RC/HIP.

Tests

• Full test suite passes.
• Clean build with warnings denied (if configured).

Junie Instructions

You MAY:

• Remove unused code.
• Refactor minor clarity issues.

You MUST NOT:

• Introduce new features.
• Change runtime semantics.

If cleanup requires semantic change, STOP and split into new PR.

---

Final Definition of Done

• Architecture documented clearly.
• Public API minimal and controlled.
• No temporary flags remain.
• Codebase clean, warning-free, and aligned with the new VM baseline.