diff --git a/agents/workshop-ta.agent.md b/agents/workshop-ta.agent.md
index 2974cd0a..6dae1d9e 100644
--- a/agents/workshop-ta.agent.md
+++ b/agents/workshop-ta.agent.md
@@ -105,11 +105,10 @@ Use `signal-write` when something needs the operator's attention:
 ### Viewing signals
 
 If the Workshop's canvas extension (🪨 Cairn) is installed — it
-ships with the full plugin at
-[jennyf19/the-workshop](https://github.com/jennyf19/the-workshop)
-— the operator can open a live dashboard showing every desk's
-signals, score bars, and escalations. The canvas reads
-`desks/*/.signals/` for the latest signal JSON per desk.
+ships bundled with the-workshop plugin — the operator can open a
+live dashboard showing every desk's signals, score bars, and
+escalations. The canvas reads `desks/*/.signals/` for the latest
+signal JSON per desk.
 
 Without the canvas, you can still read signals by scanning the
 `.signals/` directories directly and summarizing for the operator.
diff --git a/plugins/the-workshop/README.md b/plugins/the-workshop/README.md
index 055f5404..5dadb901 100644
--- a/plugins/the-workshop/README.md
+++ b/plugins/the-workshop/README.md
@@ -34,7 +34,7 @@ A **desk** isn't a sub-agent — it's a peer with a history. Sub-agents inherit
 
 ## The Cairn Dashboard
 
-The Workshop ships a **canvas extension** (🪨 Cairn) that shows the pulse of every desk — score bars, patterns, escalations — auto-refreshing in the GHCP app. Install the full plugin from [jennyf19/the-workshop](https://github.com/jennyf19/the-workshop) to get the dashboard.
+The Workshop ships a **canvas extension** (🪨 Cairn) that shows the pulse of every desk — score bars, patterns, escalations — auto-refreshing in the GHCP app. It's bundled with the plugin: `copilot plugin install the-workshop@awesome-copilot` includes the dashboard — nothing else to install.
 
 ## Works With Ember
 
diff --git a/skills/signal-write/SKILL.md b/skills/signal-write/SKILL.md
index 70a163a9..c6252cee 100644
--- a/skills/signal-write/SKILL.md
+++ b/skills/signal-write/SKILL.md
@@ -86,11 +86,10 @@ The `subtype` field preserves the specific signal state for
 dashboard consumers. `signal_type` controls sort priority
 (escalation → top).
 
-> **Note:** The signals-dashboard extension (shipped with the full
-> source repo, not the awesome-copilot package) reads `subtype`
-> when present and falls back to `signal_type` for display. If
-> consuming signals in your own tooling, prefer `subtype` for the
-> specific state.
+> **Note:** The signals-dashboard canvas extension (bundled with
+> the-workshop plugin) reads `subtype` when present and falls back
+> to `signal_type` for display. If consuming signals in your own
+> tooling, prefer `subtype` for the specific state.
 
 ### 2. Note the signal in the journal