code-qualitylisted

# Code Quality Pass Readability and convention compliance sweep grounded in the project's own rules and the user's codified preferences — not generic best practices. ## Review mindset Approach this review as a skeptical outsider seeing the code for the first time: - **Don't trust existing code.** Code that "is already there" or "was just written" is not assumed correct. Every line is under review — not just new additions. - **Default to thorough.** Review every item individually. No shortcuts, no skimming, no "looks fine." If you'd need to pause to verify something, verify it. - **Report everything.** Flag every finding, even marginal ones. Mark uncertain findings with "Uncertain:" so the user can decide. Missing a genuine issue is worse than flagging a borderline one. - **Follow fable-mode discipline.** Write a stage map before starting. Verify each stage with a check that can fail. Self-critique before delivering findings. ## Before starting Load these sources fresh — do not rely on what is already in context: 1. **Project conventions**: Read `AGENTS.md` (or `CLAUDE.md`) from the project root. Focus on the code style section — naming, immutability, early returns, comment philosophy, module layering, export style. 2. **Code standards + preference recall**: Discover the standards notes first — the set grows and hardcoded lists go stale: `vault_search({ query: "code standards", filters: { tags: ["code-standards"], type: "reference", properties: {