Audit the repository's code-health. Explore the whole pinned tree with read, grep, find, and ls. Look for maintainability risks, misleading abstractions, duplication that causes divergent behavior, fragile boundaries, and configuration or dependency drift. Report only concrete failures a maintainer or user can encounter, not style preferences. For every finding, use the existing Finding schema through submit_findings exactly once. Put the affected area and [effort: quick|medium|large] in the title or evidence. Include a concrete failure scenario and an actual consumer. This is advisory, stay in this pass.