feat(436): OWM parser-class lint (dangling refs, annotation reuse, pipeline range, style typos)

[tractorjuice]

Replaces #479, which auto-closed when its base branch was deleted on #477's merge. Rebased onto main; single commit.

Covers items 2 (parser-class failures) and 4 (coexistence with #435) from the owner's suggested scope on #436.

Parser choice (why no npm dep)

The wardley-script-parser package the issue referenced doesn't exist on npm. The real upstream wmlandscape (v3.0.1) is the full OnlineWardleyMaps React renderer — 894 KB, depends on React/MUI/Next/lodash. Not usable from a Node hook, and pulling it in would blow the millisecond budget the issue called out.

Implemented as inline state-machine checks: zero install, fits the budget, keeps the plugin self-contained.

New checks (all run inside the single OWM-block walk)

1. Dangling references — evolve / pipeline / edge endpoints must target a name declared by component / anchor / note / submap / market earlier in the same block. Reports first-seen line per (name, kind).
2. Annotation index reuse — each annotation N [...] ID must be unique; duplicates report the prior line number.
3. Pipeline range — pipeline NAME [v1, v2] endpoints both in [0.00, 1.00] and v1 < v2. Coord regexes updated to accept a leading - so out-of-range negatives trigger the range check instead of silently failing the pattern match.
4. OWM style whitelist — style NAME must be one of wardley, colour, plain, handwritten, dark. Catches the typos called out in the issue (wardely, handritten, …).

Coexistence with #435 (item 4)

Doc-only:

• This hook owns OWM / wardley-fenced blocks.
• The narrow wardley-beta Mermaid bare-digit check stays here — Wardley-template-specific rendering trap.
• General Mermaid validation belongs to Add Mermaid syntax validation for generated diagrams (linter / pre-commit hook) #435's mermaid-block-scanner. No overlap.

Spelled out in both the hook docstring and arckit-claude/hooks/README.md.

Test plan

• Clean OWM block → empty output (allow)
• Every new check triggers when expected → categorised block report
• TechnoGadget example from the wardley-mapping skill → no false positives
• Pipeline [-0.1, 1.5] → range error captured
• Component [-0.3, 0.85] → range error captured
• markdownlint-cli2 arckit-claude/hooks/README.md → 0 errors
• Integration: /arckit:wardley against a test repo

🤖 Generated with Claude Code