cleanup-codebase

# Cleanup codebase: local simplicity, ruthlessly applied Code rots in two directions: outward (drift from the original design) and downward (accretion of dead state, redundant indirection, speculative ceremony). This skill addresses the second. The thesis is local: you are already in nearby code for some other reason; while you are there, remove what does not earn its keep. See [dead-fields](references/dead-fields.md) for examples of dead fields, properties, and members. See [redundant-wrappers](references/redundant-wrappers.md) for examples of single-line passthrough functions that should be inlined. See [dead-config](references/dead-config.md) for stale feature flags, environment variables, and dead config branches. --- ## Mandates, not suggestions These are mandates, not suggestions. Internalize them as rules; do not paraphrase. ### 1. Minimize concepts, duplication, and ceremony. Every concept the reader has to hold in their head has a cost. Every duplicated piece of logic has two places to drift apart. Every ceremonial wrapper, factory, or builder that does not protect a real boundary is a tax on every future reader. Reducing concepts is not the same as reducing lines. It is reducing the number of distinct things a reader has to track. ### 2. One real owner per contract. No mirroring, no wrappers unless they remove real coupling. A "contract" is the truth about what some piece of state means or what some operation does. It must have exactly one owner. Mirroring ...