simplify-codebaselisted

# Simplify Codebase Reduce the repository to the smallest clear implementation that satisfies current requirements. Minimize maintenance surface, not line count. ## Rules - Preserve required behavior, outputs, repository standards, and identified external contracts. No in-repository caller is not enough to remove a public API, CLI/configuration contract, data format, migration requirement, or supported platform. - **KISS:** Prefer readable, explicit control and data flow, standard primitives, and the fewest useful layers over clever or dense code. - **DRY:** Consolidate duplicated knowledge or equivalent logic only when one representation is clearer; do not merge distinct concerns or remove useful abstractions merely to reduce repetition. - **YAGNI:** Remove functionality, flexibility, compatibility, configuration, or infrastructure without a current requirement. - Simplify in this order: delete unused material, reuse existing code, inline needless indirection, consolidate equivalent paths, then abstract only stable repeated knowledge. - Reduce unnecessary nesting, pass-through wrappers, redundant abstractions, weak naming, and comments that only restate obvious code when doing so improves clarity. - Invoke proactively when high-confidence simplification would materially improve maintainability, but keep the scope proportional and do not displace the user's primary task with unrelated cleanup. - Do not add features, dependencies, tools, speculative abstractions, or unrelat