code-standardslisted

# Code Standards Every rule here is checkable by reading the code — no vibes. Generators comply; reviewers cite CS-n. A rule that can't be verified by inspection doesn't belong in this file. ## Naming - **CS-1** Class names carry their type suffix: `Controller`, `Job`, `Service`, `Event`, `Listener`, `Factory`. - **CS-2** Queued classes carry the `Job` suffix; trigger-listeners are named `{Verb}On{Event}Listener`. - **CS-3** Service primary methods are intent-named (`check`, `create`, `process`, `store`) — `handle()` is reserved for framework contracts. - **CS-4** Enum cases are `ALL_CAPS_SNAKE_CASE`. - **CS-5** A name states what comes out, not how it works (`priorComposites`, not `loopAndFilterList`). ## Structure - **CS-6** Guard clauses and early returns over nested conditionals; no `else` after a return. - **CS-7** A self-contained block of 4+ lines (input → transform → one output) becomes an intent-named private method. - **CS-8** Never extract: guard clauses, single statements, or blocks mutating 2+ enclosing-scope locals — over-extraction reads worse than inline code. - **CS-9** One responsibility per class; a method reads top-to-bottom at one level of abstraction. - **CS-10** Paired classes (sibling drivers, mirrored paths) stay symmetric: same shape, same extractions. ## Comments - **CS-11** No inline what-comments — the code self-explains through names; a comment restating the next line is deleted. - **CS-12** A genuine why (race condition, idempotency gate,