implementlisted

# AEP Phase 3 — Implement Repo conventions (§P.3) win over this floor. Where the repo is silent, these rules apply. ## Typing & structure - Strict static typing; no untyped public surfaces — no implicit `any`/`dynamic`/`object` where a real type exists. Enable and satisfy the strictest checker mode the project already uses. - SOLID and separation of concerns; composition over inheritance; explicit dependency injection over globals and singletons. - Small single-purpose functions; guard clauses over deep nesting; prefer immutability wherever state is contested. ## Naming & documentation - Self-documenting names beat comments. Docstrings state inputs, outputs, side effects, and thrown exceptions. - Comments explain **why**, not **what**. A comment restating the code is noise; a comment recording a non-obvious constraint is gold. ## Errors & boundaries - Validate and normalize at trust boundaries (user input, network, files, IPC); fail fast with actionable errors. - Never swallow exceptions; never log secrets; user-facing messages never leak internals or stack traces. - Errors are typed/structured and logged with context (correlation IDs where the project has them). ## Concurrency - Treat shared state as contested: prove thread-safety, document locking order, avoid time/sleep-based logic for correctness. - Async all the way down or not at all — no sync-over-async deadlock patterns. ## Dependencies & configuration - Prefer the standard library and existing project depe