dev-visualizer: hard sibling dependency on ../dev/references/reader-documents.md blocks standalone install/port

[lidge-jun]

Symptom

dev-visualizer is not self-contained: its reader-document rules live in a sibling skill and are reached by relative path. Porting or installing the skill standalone (I ported it to an Aside account skill today) requires bundling dev/references/reader-documents.md by hand and rewriting every link.

Links into the sibling (verified on main, 2026-09-16):

• plugins/codexclaw/skills/dev-visualizer/SKILL.md: 4 links to ../dev/references/reader-documents.md
• plugins/codexclaw/skills/dev-visualizer/reference/document-pdf.md: 1 link to ../../dev/references/reader-documents.md

Everything else the skill needs (assets, scripts, its own reference/) ships inside the skill directory, so this is the single hard coupling that breaks standalone use.

Why it matters

• skill-hub-style installs that copy a single skill directory produce a skill whose "Read when selected" table points into nothing.
• The READER-DOC rules are the backbone for the report routes (report-writing storyline, claim headings, appendix discipline), so a broken link is not cosmetic; agents that cannot resolve it skip the rules.

Suggested fix

Either bundle reader-documents.md under dev-visualizer/reference/ (canonical owner stays dev, with a "copied from" header), or degrade gracefully: when the sibling path does not resolve, state the five READER-DOC rules inline in a short block. A mklink-style check in skill-hub could warn at install time.