fix: boundary hook parses real-world boundary bullets; doctor accepts n/a (0.15.1)

[stid]

Two fail-safe defects found by dogfooding LCD on a real work-item (private decision log D-023) — both hit while using the plugin, not while reading it.

1. The edit-boundary hook read a boundary differently than people write one

lcd_journal_boundary emitted each EDIT BOUNDARY bullet as a single entry, and the hook matched that whole string against the edited path. So both of these denied every edit to the files they list:

- `CLAUDE.md`, `README.md`, `.gitignore`     ← three paths on one bullet
- `PROPOSALS.md` (historical note only)      ← path plus a trailing note

The deny message names the boundary, so the author sees their own path in the list and is told it isn't in the list — with no hint that the format was the problem. It denied two legitimate edits in the work-item that found it.

Entries are now split on commas, and a trailing parenthesised note is dropped. Two things deliberately survive:

• a brace glob ({src,lib}/**) keeps its commas — there they are pattern, not separator;
• a (group) path segment (Next.js route groups) is untouched, because a note is only recognised after whitespace.

Not addressed here: bash case can't match a brace pattern at all, so {src,lib}/** as a boundary entry still matches nothing. That's a pre-existing matching gap, separate from this parsing fix.

2. lcd:doctor treated n/a as a mistake

A project with no test suite fills the test keys with an explicit n/a (the shipped doctor fixture already does this for eval:). The placement-vs-glob heuristic ran on those strings anyway and emitted a WARN that no edit could clear — permanent noise for docs/prose/decision-record projects. n/a, with or without a reason after it, now counts as filled in and skips the heuristic.

Testing

Tests first, then the fix. New fixture cases in tests/test-boundary-check.sh (multi-path bullet, annotated entry, brace-glob passthrough) and tests/test-doctor.sh (a fully n/a docs-only project → 0 FAIL, 0 WARN). Both failed before the change.

tests/run.sh → 10/10 · claude plugin validate . → passed.

Patch bump to 0.15.1 in plugin.json + marketplace.json (lockstep), CHANGELOG section added.