module-completion-checklisted

# Module Completion Check Run this check only when a module is confirmed 100% complete — skip otherwise. Do NOT create or update `[module]-module-data-flow.md` or `[module]-flow.md` during a task unless the module is 100% complete (all tasks for this module are marked done in project-plan.md). Creating these files mid-module causes repeated read/write cycles during review. Defer until completion. * Does completing this task finish all work for its module in docs/project-plan.md? * If no: this module is not yet complete. Skip the rest of this file. * If yes: this module is now complete. Do all of the following: 1. Insert logger calls into the module's code, following the rules in docs/specs/logging-spec.md. Use the logger instantiation pattern defined in logging-spec.md for this project's language/framework. Direct print/console statements are not allowed. logging-spec.md itself is the rule definition — do not add module-specific content to it. Create or update docs/modules/<module-name>/log-<module-name>.md to list every log point added, in call order. Verify coverage now, while the module is fresh (this is why the check is not run mid-module — see the note above about repeated read/write cycles): `python3 docs/script/validators/verify_module_docs.py --project-type TYPE --src <src-dir> --strict` This confirms both the module-flow file and the log-<module-name>.md file actually exist for this module — ne