Status: IN
Engineering inconsistencies (naming drift, dual test conventions, style divergence) persist indefinitely because the submission-optimized architecture both causes them (isolation removes forcing functions) and hides them (each solution is tested in isolation, so cross-solution inconsistencies never surface as failures).
Isolation both generates inconsistency (no-consistency-enforcement) and conceals it (tooling unreliability) — the architecture is a self-stabilizing inconsistency trap
Depends on (SL): isolation-creates-undetectable-inconsistency, repo-optimized-for-submission-not-engineering