investigate-projectlisted

# Investigate Project Perform a thorough, multi-perspective investigation of an external open-source project and produce a comparative analysis document against The Engineer. The output matches the established format in `docs/archived/implementation-docs/considered-projects/`. The goal is an honest, thorough analysis — not marketing. We want to understand what the project actually is (not what it claims to be), what it does well, what The Engineer does better, and what patterns are worth adopting. The document should be useful months later as a reference for architectural decisions. --- ## Step 1: Understand the Format Read 1-2 existing analyses from `docs/archived/implementation-docs/considered-projects/` to internalize the established structure and tone. These are the gold standard — match their depth, honesty, and table-driven comparison style. The standard structure is: 1. **What [Project] Is** — honest description of what's actually built (not what the README claims) 2. **Direct Comparison** — table-driven comparison across all relevant dimensions 3. **Architectural Analysis** — what they do well, what The Engineer does better 4. **Patterns Worth Studying/Adopting** — concrete ideas that could improve The Engineer 5. **Where We Stand** — honest assessment with summary tables --- ## Step 2: Launch Parallel Research Launch 3 Explore sub-agents simultaneously, each with a distinct research focus. Every agent should use WebFetch to read actual file contents from the