analyze-code-qualitylisted

Analyze the overall quality of the source code in this project. Generate a comprehensive report. The goal is not just "does it compile and are the lines covered" — it is "is the code *correct in the sequences it actually runs*." A green test suite at 100% line coverage routinely ships behavioral bugs (see step 6). Weight the report accordingly. ## Steps 1. **Run unit tests with coverage** ``` npm test ``` Report: total tests, pass/fail count, coverage percentage by directory. Note: `npm test` (vitest) does NOT run the Rust tests. If `src-tauri/` exists, also run `npm run test:rust` (`cargo test` — needs the Rust toolchain) and report those separately. Plugin tests (`plugins/*/src/*.test.ts`) run only when targeted — run `npm run test:all-including-plugins` if you want plugin coverage folded in. 2. **Run E2E tests** ``` npm run test:e2e ``` Report: total E2E tests, pass/fail count. (Use `npm run test:e2e:fast` to skip GitHub-credentialed specs if credentials aren't configured.) 3. **Run linter** ``` npm run lint ``` Report: total errors/warnings, categorized by rule. 4. **Check TypeScript strictness** ``` npx tsc --noEmit ``` Report any type errors. 5. **Check for anti-patterns documented in CLAUDE.md** Read `CLAUDE.md` and the `docs/` requirements files first — the authoritative anti-pattern list lives there and evolves, so treat CLAUDE.md as the source of truth over this list. Prefer **ast-grep** for structural ch