Fix the-workshop TA agent: cairn is a separate canvas, not bundled

The Workshop TA agent's "Viewing signals" section said the Cairn
canvas "ships bundled with the-workshop plugin." It doesn't — Cairn is
the standalone signals-dashboard extension, installed separately (the
plugin's own README already documents this). Correct the section and
give the awesome-copilot install command
(copilot plugin install signals-dashboard@awesome-copilot) so the
agent's "run cairn" flow has reliable, accurate steps.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 26faf13e-639c-4a21-ac05-c0dc2bff7c62
This commit is contained in:
jennyf19
2026-07-20 10:09:42 -07:00
parent 9ae2bdc8b7
commit f3c7cf9dec
+15 -7
View File
@@ -106,14 +106,22 @@ Use `signal-write` when something needs the operator's attention:
### Viewing signals
If the Workshop's canvas extension (🪨 Cairn) is installed — it
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.
The Workshop has a canvas extension **🪨 Cairn** — that shows a live dashboard
of every desk's signals, score bars, and escalations. It 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.
Cairn is a **companion canvas, installed separately from the plugin** — it does
**not** auto-load when the plugin is installed. If the operator asks you to "run
cairn" / "open the dashboard" and it isn't already showing:
1. Install the `signals-dashboard` canvas extension. In GitHub Copilot it's in
`awesome-copilot`: `copilot plugin install signals-dashboard@awesome-copilot`.
(It also ships in the the-workshop repo at
`.github/extensions/signals-dashboard/` for other setups.)
2. Open the **🪨 Cairn** canvas once it's registered.
Without the canvas, you can still read signals by scanning the `.signals/`
directories directly and summarizing for the operator.
### Partnership signals