visualization: sweep unit, gate the design canvas mention and bake the design row's integration into visualize

[kyle-sexton]

Parent

Refs #4047. Unit 7 of 9 (sweep unit for the visualization plugin, plan Phase 9). Predecessor: #4053 (review sweep unit). Start only after #4053 has merged green.

Agent Brief

Type: Task

Summary: close the reverse-parity advisory the tooling fix raises on visualize and apply the store's integration value for its design row (proposed route or suggest; design is registered model-disabled, so wrap is not available). The design-sync row stays defer and is untouched.

Current behavior: the visualize description says "where the bundled design skill is available", a presence-gated native reference without the gate token, which the fixed self-check reports as an advisory; the body's Boundary section covers the first-party playground plugin.

Desired behavior:

• The description's design-canvas mention is rewritten to carry the gate token and the routing split (the bundled design skill produces a hand-editable canvas; this skill chooses the form and medium), within the per-entry cap; baked.description_phrase is set on the design row.
• Where the store says suggest, a suggest sentence for /design at the point the decision matrix picks the canvas, its basis a same-file four-part verification record; where route, the existing Boundary is kept as is.
• The playground row's existing marketplace phrase is untouched.
• Baked flags, the view regenerated, the skill-quality check passing, the next minor of visualization at PR time with a CHANGELOG entry stating the rules.

Key interfaces:

• The visualize skill description and body.
• The design and design-sync store rows and the generated view.

Acceptance criteria:

• bash plugins/skill-quality/scripts/check-skill.sh visualize passes.
• python3 plugins/claude-ops/skills/audit-native-overlap/scripts/overlap.py self-check --upstream-sha ed404106fcd80ba98ecb7c851e531dcb626d13b7 2>&1 | grep -c "visualization:visualize" prints 0 and the command exits 0.
• The PR is a draft, quotes the two store rows, and flips to ready when green; the unit closes only when the PR merges green.

Out of scope:

• Any row or skill outside the visualization plugin; the design-sync row; changing either verdict.

Blocked by

• review: sweep unit, bake the route phrases for the code-review and security-review lanes #4053

[kyle-sexton]

Deferred; scope narrowed (2026-09-11). The Boundary sections for the design and playground rows on visualize landed with native-references 1.1.0 (#4058). The design row is route on job merits: the design canvas registration is model-invocable (the model-disabled design registration is the claude.ai/design hub, which no row describes), so wrap is admissible and is this unit's one revisit before it starts. What remains is bringing "where the bundled design skill is available" under the gate token (the self-check advisory unit 1 built now names this skill) and the baked flags. Still blocked by #4049.

---

Generated by Claude Code

[kyle-sexton]

Audit follow-up (2026-09-29 audit of the Cursor run). Issue stays closed; no owner decision needed.

What the audit found: the acceptance criteria are met on main (the visualize SKILL.md description clause and the self-check both pass). One leftover remained: plugins/visualization/.claude-plugin/plugin.json:5 kept the ungated "where the bundled design skill is available" after #4810, and docs/catalog.md mirrored it. The native-overlap self-check scans SKILL.md descriptions only, so CI did not catch it.

What happens next: fixed in #5253 (draft; Refs #4054, Refs #4055). It removes the clause from the manifest form list, adds one sentence using the canonical gate token, and regenerates docs/catalog.md.

Also found: #4928 was merged with zero changed files under a feat title and added no work. It is history only and is not reverted.

Follow-up for the check gap: the claude-ops group has been asked (low priority) to make check_presence_mentions in plugins/claude-ops/skills/audit-native-overlap/scripts/overlap.py also scan the plugin.json description. No issue for it exists yet; it will be linked here once filed.