Project Analysis (Zoom Out)

Perform a high-level analysis of this project. Follow the procedural workflow below; use the rubric sections as reference when interpreting findings.

Ground rules

• Reproduce before reporting — read the actual files and run the tooling; never assert a finding based on file names, directory shapes, or vibes alone.
• Verify catalog-like claims mechanically — if a claim implies "all N of X", script the check rather than eyeballing a sample.
• Mark anything you couldn't verify as "unverified"; never guess or extrapolate.
• This is an assessment only: no code changes, no pushes, no triggering workflows or releases.
• Honor the target repo's standing context file when present (see step 0).

Usage

When asked to analyze project health: