v0.4.0

comment-policy/no-decorative-comment: cover Unicode dividers

The decorative-marker charset was ASCII-only, so section banners built from
Unicode box-drawing characters passed lint untouched. The rule now detects them,
in both // and /* */ forms.

Now caught:

• box-drawing rows and frames — /* ────────── */, /* ══════ Section ══════ */, /* ── Title ────── */
• en/em-dash rows — /* ———————— */
• ~ runs — // ~~~~~~~~

Unchanged:

• ASCII behavior (=====, ---, #region, ===text===)
• a single divider glyph inside prose stays clean (e.g. 5–10, push — иначе, timeout │ retry)
• fix semantics — // banners autofix (line removed), /* */ banners are report-only

Full Changelog: v0.3.0...v0.4.0

v0.3.0

New rule: comment-policy/no-consecutive-comments

Flags several stand-alone comments stacked one after another, encouraging merging or removing redundant annotations.

Options (defaults):
```js
["error", { types: ["line", "block"], max: 1, skipBlankLines: true, protectedPatterns: [] }]
```

• `types` — which comment kinds participate in a run: `line` (`//`) and/or `block` (`/* /`). A multi-line `/ */` counts as one comment.
• `max` (default `1`) — how many consecutive comments are allowed; a longer run is reported.
• `skipBlankLines` (default `true`) — comments separated only by blank lines still count as consecutive; set `false` to let a blank line break the run.
• `protectedPatterns` — comments matching a pattern are excluded from runs.

Report-only (no autofix). Included in the `recommended` config.

Full Changelog: v0.1.1...v0.3.0

v0.2.0

Remove the SDD (spec-driven development) layer: dropped the sdd config preset and sdd-patterns.ts. The generic protectedPatterns exemption option remains available on all five rules.

Minor bump because configs.sdd is removed from the public config surface.

v0.1.1

Patch release. No rule behavior changes; verifies the release-to-npm pipeline.