Skip to content

dev-visualizer: shipped document-pdf.md cites private devlog/_plan paths that do not resolve for consumers #182

Description

@lidge-jun

Symptom

plugins/codexclaw/skills/dev-visualizer/reference/document-pdf.md cites private devlog paths as provenance. Those paths do not exist anywhere in the published repo or the installed plugin snapshot, so every consumer gets dead pointers.

Lines (verified on main, 2026-09-16):

  • L94: Probe: devlog/_plan/260909_visualizer_report_quality/evidence/chrome-paged-probe.md.
  • L132: Findings with sources are in devlog/_plan/260909_visualizer_loop_merge/evidence/aside-G_cjk_typography.md.

grep -r devlog/_plan plugins/codexclaw/skills/ finds nothing else shipped at those paths.

Why it matters

The provenance habit is the point of these files, but a citation that cannot be resolved is worse than none: it makes the CJK print recipe (klreq margins, word-break: auto-phrase, hanging-punctuation limits) look unverifiable. An agent following the skill either hallucinates the referenced file or stops trusting the numbers.

Suggested fix

Either inline the load-bearing findings next to the citation (a two-line summary of what the probe measured), or move the evidence files under the skill's reference/ and link relatively. Keep the dated provenance; just make it resolve.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions