v3.15.0: conversational-register patterns (wall-of-text, recap-flatte…

…ry) (conorbronsdon#53)

* v3.15.0: conversational-register patterns (wall-of-text, recap-flattery)

Adds three catalog entries prompted by a real-world GitHub issue exchange
where a maintainer called out an assisted-sounding reply with "I prefer
to talk human to human" (name/repo withheld):

- Wall-of-text replies: reply-length text delivered as one unbroken
  paragraph with no line breaks, where humans in conversational registers
  break at thought boundaries instead. Documented as an LLM-judgment
  rule after a first-pass detector implementation broke an existing
  calibration fixture and, on review, would have fired on any ordinary
  short paragraph rather than anything AI-specific.
- Recap-flattery opener: summarizing the reader's own work back at them
  with praise before getting to the point. LLM-judgment rule.
- Immaculate typography in casual registers: folded into the existing
  Formatting section at the same weak-signal tier as curly quotes, plus
  its inverse (preserve a human's typos when editing their casual text).

Catalog goes from 51 to 53 detection categories; the deterministic
engine stays at 45 types (no new type — see the CATEGORIES.md §C note
and the NOTE in patterns.js for why the detector attempt was reverted).
Also catches the Cursor port up from v3.12.0 to v3.15.0, closing a gap
where it had missed the 3.13.0 and 3.14.0 rule changes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Review fixups: recap-flattery dedup line + wall-of-text carve-out

Two neighbor-standard gaps found in adversarial review of the new
conversational-register rules:

- Recap-flattery opener now explicitly distinguishes from Sycophantic
  tone and Acknowledgment loops (every adjacent category carries a
  "Distinct from X" clause; without it the skill's audience would file
  dupes against those two).
- Wall-of-text replies now carries an explicit legitimate-use carve-out
  (a single dense paragraph is correct in blog/docs/formal registers),
  per CONTRIBUTING's precision-over-recall rule. Notes why a tolerance
  matrix row is the wrong scoping home: a plain issue comment
  auto-detects to the `blog` profile, so a skip-on-blog cell would
  suppress the rule in the exact register it targets.

Ported to cursor-rules/.mdc and synced to the plugin copy.
Contracts still green: npm test (45 detector types), pattern count 53.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>