stand-generallisted

# Coding Standards Global standards that apply to all projects and languages. ## Single Source of Truth Any value defined in one place and consumed in another should be referenced, not copied. Applies to versions, paths, URLs, schema constants, and configuration. - If two files would need to be updated in lockstep, the second is a derived artifact — generate it, don't hand-maintain it. - CI verification of two files agreeing is a smell: the right pattern is run-the-generator + `git diff --exit-code`, not parse-and-compare. - Hand-maintained mirrors of canonical sources rot silently. The cost of a small generator is always lower than the cost of recurring drift bugs. ## Before You Write Before implementing utility logic (file traversal, string parsing, config lookup, error wrapping), search the codebase for an existing implementation. - Found a close match? Import or extend it instead of reimplementing. - Same pattern already in 2+ files? Extract it to a shared module before adding a third instance. - Duplication accumulates one compliant PR at a time — prevent it at writing time rather than relying on later audits. ## Pre-Implementation Answer three questions before creating a new file, module, or significant function: 1. **Does this logic already exist?** Search first; reuse beats rewrite. 2. **Is this the right module?** An existing module growing too large is a signal to refactor it, not to create a parallel module beside it. 3. **Will this create du