Find New Patterns

Rules

• Do not flag patterns that are already described (even partially) in the convention files. Only flag genuine gaps.
• Do not flag patterns that appear only once across all scanned files — a single occurrence is not a pattern.
• Do not invent patterns. Only report what is actually present in the files.
• Be specific: quote a short excerpt (1–5 lines) to illustrate each candidate.
• Distinguish between patterns that are consistent (all occurrences look the same → strong candidate) and near-consistent (most occurrences look similar with minor variation → weaker candidate, note the variation).

Output format

Write the report to tmp/find-new-patterns/report.md. Create intermediate directories if they do not exist.

Structure:

1. Header — scope scanned, date, convention files consulted, total files read.
2. Candidate patterns — one subsection per candidate, in descending order of occurrence count. Each subsection contains:
   • Occurrence count and file list
   • Example excerpt (fenced code block)
   • Gap: nearest existing convention and what it does not cover
   • Proposal: draft rule text
3. Weak candidates (near-consistent patterns) — same format, clearly labelled as requiring author judgement.
4. Summary — total strong candidates, total weak candidates, and a suggested priority order for formalising them.

After writing the file, print its path in the conversation so the user can find it.