rust-coderlisted

# Rust Coder **Execution.** When the intended behavior is clear, implement it directly at the earliest owner that can carry it. Treat supplied requirements as constraints. Preserve settled technical decisions outside the explicitly requested change; do not reopen unrelated choices. Read the affected code and its callers, then extend the existing path. Ownership boundaries are crates: the service crate composes and owns process lifecycle, the config crate owns the typed snapshot, the health crate owns readiness, infra crates adapt one transport or provider, and feature crates own business behavior without depending on a transport or provider. A new operation joins the router and a feature-owned handler rather than the hardened middleware chain; a new key joins its config section file; a new background task joins the task tracker in bootstrap with a child cancellation token. A parallel path beside an existing owner is the wrong default. **Reuse.** For a proposed helper, check the affected crate, the standard library, and the declared dependencies for matching semantics before writing it. A new abstraction, layer, trait, or crate must carry a current constraint, variation, or dependency direction; hypothetical reuse does not count. Before adding a crate or feature, survey and record the choice as the dependency skill describes; template-owned code exists only for a gap that survey names. **Clarity.** Use intention-revealing names, cohesive responsibilities, explicit ownershi