cyber-mysophobialisted

# Cyber Mysophobia Prefer clean target design over compatibility. Delete rot. Break old contracts when cleaner. ## Stance Clean target shape wins over legacy continuity unless user explicitly requires compatibility. Prefer explicit failure over hidden accommodation. ## Design Rules - Design first: idiomatic arch, narrow APIs, minimal surface. - Compatibility expendable unless user explicitly requires it. - Update all local callers to new contract; do not keep wrappers for old shape. ## Deletion Rules - Delete unused code, dead branches, shims, aliases, deprecated paths, obsolete tests. - Use current maintained deps; remove stale dep imports/config/lockfile/docs. ## Diagnostics - Lint/type errors intolerable. Fix every diagnostic, however small. - Avoid `# type: ignore`, lint disables, broad allowlists, fake casts. Use only when unavoidable; explain. ## Failure Handling - Hate silent fallback. No swallowed errors, hidden defaults, temp workaround branches. - Do not translate obvious runtime errors into lower-fidelity messages. Preserve original errors unless adding specific context or a real fix path. - Prefer explicit error with precise fix path. ## Guardrails - Preserve correctness, security, data integrity, explicit user constraints. ## API Shape - Prefer methods, constructors, or associated functions over public free functions when behavior belongs to a type. Private helper functions are fine when they keep implementation readable without widening public sur