diff --git a/SKILL.md b/SKILL.md
index 061218b..f03ea2a 100644
--- a/SKILL.md
+++ b/SKILL.md
@@ -1,7 +1,7 @@
 ---
 name: corp-v1-channel-scope
 description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all six same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
-version: 1.3.4
+version: 1.3.5
 author: Hermes Agent
 license: MIT
 metadata:
@@ -133,7 +133,7 @@ Ideas are early opportunities not yet accepted as Epics or Features. Record stab
 
 Questions are governed product decisions, separate from delivery status and approval. Keep a Questions parent page and one sidebar-visible child page per canonical Question. Show the question, why it matters, affected scope, owner, status, answer when available, and original source without using tables.
 
-Render affected or resulting governed records as sharp clickable tags, sorted deterministically by entity type and canonical ID. Every tag resolves the target record's canonical documentation URL; do not emit an unsorted plain list or synthesize a URL from the ID. Label reader-facing source sections **Original source**, not Evidence. For Discord sources, render each link as `Discord – <Channel name> – <Author>` while retaining the exact source-message URL.
+Render affected or resulting governed records as sharp clickable tags, sorted deterministically by entity type and canonical ID. Every governed record is a separate list item containing exactly one full-surface anchor to that record's canonical documentation URL; never combine multiple IDs or links into one visual tag, and never synthesize a URL from the ID. Give each tag its own visible border and spacing, pointer cursor, enabled pointer events, keyboard focus treatment, entity type, canonical ID, directional cue, and accessible label. Validate every generated Idea page by counting separate anchors, requiring one unique valid target per tag, and proving every target route exists. Label reader-facing source sections **Original source**, not Evidence. For Discord sources, render each link as `Discord – <Channel name> – <Author>` while retaining the exact source-message URL.
 
 The Epic registry graph must not expose a `View accessible data table` disclosure. Keep Epic nodes keyboard-accessible, labelled, and linked to canonical records; use the detailed Epic and Feature pages as the reader surface.