Generate a workspace context summary for the CODER role.

Explore this workspace and capture tactical facts needed to edit code consistently with this project.

Cover:
- Naming and module conventions observed in the codebase
- Helper APIs and canonical utilities to reuse rather than reinvent
- Error-handling patterns used locally
- Async and state-management patterns
- Dependency policy — what libraries are already used for common tasks
- Where tests live and how they are organized
- Self-check commands for quick local verification where documented in the workspace

Search the web for official documentation of language and framework APIs the coder is likely to use. Anchor to versions from project files and lockfiles.

Output ONLY the summary text. No JSON, no markdown fences, no explanatory text.
