compartment-runtime-hygiene

To detect unused exports causing dead runtime surface, run the hygiene workflow which identifies and flags exports no longer used at runtime across modules. It automates this detection and flags drift for repository maintenance.

Runtime drift occurs when export, entrypoint, scaffolding, or deletion changes create dead runtime surfaces or misalign Knip configuration. It happens when code alterations accidentally expose convenience exports or alter real runtime entrypoints without proper configuration updates.

To update knip.runtime.json safely, ensure runtime entrypoints remain explicit and update the configuration only for real runtime entrypoints. The hygiene workflow avoids accidental convenience exports by internalizing helpers that tests rely on but should remain outside the runtime surface.

Yes, you can clean up runtime surfaces during deletions or refactoring. The workflow provides guidance to maintain a clean surface and prevent exposure of implementation-mirror tests, ensuring deletions respect runtime entrypoints and do not leave dead code.

The best way to relocate test helpers that bloat the runtime surface is to use the workflow's internalization recommendations. It identifies helpers that tests rely on but should not be part of the runtime surface and applies internalization or relocation to keep surfaces clean.

Knip reports runtime drift after refactoring entrypoints because configuration like knip.runtime.json may still reference old paths or fail to recognize new real entrypoints. The workflow ensures configuration updates only for real runtime entrypoints to prevent this drift.