No, it's:

⟩ Refactor these components into standalone modules that communicate across well-defined APIs. Write the API specifications to docs/API.md. Add a note to AGENTS.md instructing agents to preserve the modular seams and focus work on one module at a time.

It's a weird world where we're refactoring everything, but not just using a type system that can enforce those seams and limitations at compile time.

We are though. Why do you think Rust has become the defacto standard for vibe-coding? Most vibe coders can't read a line of Rust, but the strong ML-inspired type system, and also having native performance, is why it is the king of the hill right now.

[delayed]