@harness-lab/cli 0.2.7 → 0.2.9

package/README.md

@@ -9,9 +9,14 @@ Current shipped scope:
 - `harness auth login`
 - `harness auth logout`
 - `harness auth status`
+- `harness workshop current-instance`
+- `harness workshop select-instance`
 - `harness workshop status`
+- `harness workshop list-instances`
+- `harness workshop show-instance`
 - `harness workshop create-instance`
 - `harness workshop update-instance`
+- `harness workshop reset-instance`
 - `harness workshop prepare`
 - `harness workshop remove-instance`
 - `harness workshop archive`
@@ -120,16 +125,37 @@ Workshop commands:
 ```bash
 harness auth status
 harness skill install
+harness workshop list-instances
+harness workshop select-instance sample-workshop-demo-orbit
+harness workshop current-instance
 harness workshop status
+harness workshop show-instance sample-workshop-demo-orbit
 harness workshop create-instance sample-workshop-demo-orbit --event-title "Sample Workshop Demo"
-harness workshop update-instance sample-workshop-demo-orbit --room-name Orbit
-harness workshop prepare sample-workshop-demo-orbit
-harness workshop remove-instance sample-workshop-demo-orbit
+harness workshop update-instance --room-name Orbit
+harness workshop reset-instance --template-id blueprint-default
+harness workshop prepare
+harness workshop remove-instance
 harness workshop phase set rotation
 harness workshop archive --notes "Manual archive"
+harness workshop select-instance --clear
 harness auth logout
 ```
 
+Targeting model:
+
+- `harness workshop list-instances` is the discovery entrypoint for facilitator-visible workshops
+- `harness workshop select-instance <instance-id>` stores a local current target for later workshop commands
+- `harness workshop current-instance` reports the stored target and resolves its current server state
+- `harness workshop status` and `harness workshop phase set <phase-id>` use the selected instance when present, otherwise they fall back to deployment default behavior
+- `harness workshop show-instance`, `update-instance`, `reset-instance`, `prepare`, and `remove-instance` accept an explicit `<instance-id>` but may also use the stored selection as a fallback
+- `harness workshop select-instance --clear` removes the stored selection
+- `HARNESS_WORKSHOP_INSTANCE_ID` remains an environment fallback when no local selection is stored
+
+Machine-readable output:
+
+- `harness --json ...` prints strict JSON output without headings
+- prefer this for agent or script consumption instead of parsing human-oriented terminal copy
+
 Facilitator lifecycle commands are intentionally CLI-first:
 
 - skill invokes `harness`

package/assets/workshop-bundle/SKILL.md

@@ -214,6 +214,34 @@ This is a facilitator-only command — do not surface to participants.
 
 Show the current instance state, agenda phase, facilitator list, and team count.
 Requires active facilitator session.
+If a local current instance is selected, prefer that target over deployment-default status.
+When an agent needs machine-readable output, prefer `harness --json workshop status`.
+
+### `workshop facilitator current-instance`
+
+Show the locally selected facilitator target, where it came from, and the resolved instance record.
+Prefer invoking `harness workshop current-instance`.
+Use this to confirm the CLI target before update, reset, prepare, remove, or phase operations.
+
+### `workshop facilitator select-instance <instance-id>`
+
+Persist a facilitator-local current target for later workshop commands.
+Prefer invoking `harness workshop select-instance <instance-id>`.
+Use `harness workshop select-instance --clear` to remove the stored selection.
+
+### `workshop facilitator list-instances`
+
+List the facilitator-visible workshop instance registry.
+Prefer invoking `harness workshop list-instances` over raw API scripts or local session-file inspection.
+Use this when the facilitator needs to discover what currently exists on a shared dashboard before choosing an explicit instance for reset, update, or agenda work.
+When an agent needs strict parsing, prefer `harness --json workshop list-instances`.
+
+### `workshop facilitator show-instance <instance-id>`
+
+Inspect one explicit workshop instance.
+Prefer invoking `harness workshop show-instance <instance-id>` over raw API scripts.
+Use this when the facilitator needs the full record for one instance rather than the deployment-default runtime status returned by `workshop facilitator status`.
+If a current instance is already selected, the CLI may omit `<instance-id>` and use the stored target.
 
 ### `workshop facilitator grant <email> <role>`
 
@@ -249,21 +277,29 @@ Prefer invoking `harness workshop update-instance` over raw API scripts.
 Use this when the facilitator wants to correct or refine date, venue, room, address, or event title without resetting the instance.
 Support `contentLang` changes explicitly so facilitators can choose workshop delivery language per instance without changing admin UI language.
 
+Facilitator discovery rule:
+- for routine discovery, use `harness workshop list-instances` and `harness workshop show-instance`
+- for repeated work on one live workshop, use `harness workshop select-instance <instance-id>` and `harness workshop current-instance`
+- do not read local CLI session files or improvise authenticated `node -e` fetch scripts unless you are diagnosing the CLI itself
+
 ### `workshop facilitator reset-instance <instance-id>`
 
 Reset one existing workshop instance from the selected blueprint template. Requires facilitator session.
 Prefer invoking `harness workshop reset-instance` over raw API scripts.
 Use this when the facilitator wants fresh canonical agenda, runner, and presenter content for a live instance and accepts that local runtime state will be reinitialized.
+If a current instance is already selected, the CLI may omit `<instance-id>` and use the stored target.
 
 ### `workshop facilitator remove-instance`
 
 Remove a workshop instance from the active list without deleting its archive history. Requires facilitator session.
 Prefer invoking `harness workshop remove-instance`.
+If a current instance is already selected, the CLI may omit `<instance-id>` and use the stored target.
 
 ### `workshop facilitator prepare`
 
 Set the current instance to `prepared` state. Verify event code is ready.
 Prefer invoking `harness workshop prepare`.
+If a current instance is already selected, the CLI may omit `<instance-id>` and use the stored target.
 
 ### `workshop facilitator agenda`
 

package/assets/workshop-bundle/bundle-manifest.json

@@ -1,8 +1,8 @@
 {
   "manifestVersion": 1,
   "bundleName": "harness-lab-workshop",
-  "bundleVersion": "0.2.7",
-  "contentHash": "db5557fe004d30755c4912015667daf2095c70081780f8a3418bd772e2fb9a49",
+  "bundleVersion": "0.2.9",
+  "contentHash": "671837951cf6679bea1d517c900927aab5d457806695e1a6da25574b8573f325",
   "files": [
     {
       "path": "content/challenge-cards/.gitkeep",
@@ -34,7 +34,7 @@
     },
     {
       "path": "content/facilitation/master-guide.md",
-      "sha256": "f0edc5eef8c7bc0efc67672e184edecce46fa5fd5e9820cfda0b28fbb8cb1a8f"
+      "sha256": "845adbcf9284cedd589d461b40ae1cd336d816b92bcc239df4574148a57b263a"
     },
     {
       "path": "content/project-briefs/.gitkeep",
@@ -42,7 +42,7 @@
     },
     {
       "path": "content/project-briefs/code-review-helper.md",
-      "sha256": "0d70c455d000ec8bc01337db5feee2174be8359730b5c278cccee9c3e6b0f2f7"
+      "sha256": "3e174ff0d097fe132088774042f9db58c9c2494613d66950bdd423116bd7986d"
     },
     {
       "path": "content/project-briefs/devtoolbox-cli.md",
@@ -98,11 +98,11 @@
     },
     {
       "path": "content/talks/context-is-king.md",
-      "sha256": "4d0972fefac067de0b8803698b44bdf8ab0bee64b181d50d1ac5e26a92eb7089"
+      "sha256": "0bb48497b458474a546c351118ad455c00ad997c9efc0e227b388f81dd0b55e3"
     },
     {
       "path": "docs/harness-cli-foundation.md",
-      "sha256": "80b321da32d110f141e1bd6a089ccc84f2a04066d76ba0258f530cc333dbaae4"
+      "sha256": "cff448e5c1ee4e7129724e4f8294add35cd1efb621c83182b341a1b7e5a16b86"
     },
     {
       "path": "docs/learner-reference-gallery.md",
@@ -134,11 +134,11 @@
     },
     {
       "path": "SKILL.md",
-      "sha256": "64ddc1bf36265ea8321b2634d34499e83a8c1692e5cb10c6f30b1b07f1d51975"
+      "sha256": "d1e242a857f61bc2fae29c74a9e0efbd1ba0ed5beb25087dbaeffabc5f53b4a5"
     },
     {
       "path": "workshop-blueprint/agenda.json",
-      "sha256": "6b8e1925e20fabccfd3cd9e9d79839855f51b2b7fd449efbb336bf3edd4eadce"
+      "sha256": "91b4037578ce61d172e09941089b97180322552cb42bb52de87b3956e60b1ed0"
     },
     {
       "path": "workshop-blueprint/control-surfaces.md",
@@ -146,7 +146,7 @@
     },
     {
       "path": "workshop-blueprint/day-structure.md",
-      "sha256": "4980768b9e8b71d47cec19764b317d99c830908a0298c6f104e8d7bd37320966"
+      "sha256": "ffecae258211cef2430112ca25e1ff59658cac729ea2a07b9cac48e9a2a6244e"
     },
     {
       "path": "workshop-blueprint/edit-boundaries.md",
@@ -158,7 +158,7 @@
     },
     {
       "path": "workshop-blueprint/README.md",
-      "sha256": "ae809a473bbc88411891044de7609fa053e66e370a8d4063e5d7b9e68179a98c"
+      "sha256": "badb477ecfef7df163ec41c72c39e04bcde2a5a723c1b01bf2e91ed38924e903"
     },
     {
       "path": "workshop-blueprint/teaching-spine.md",
@@ -182,7 +182,7 @@
     },
     {
       "path": "workshop-skill/facilitator.md",
-      "sha256": "ab4721564c1dee2a24c7d4dfda229c2cfa56f5bec89a8b3580b541d9baa13e7f"
+      "sha256": "525fc9fdad22cf42b47854ff9ad90579d728daf2c4ac484aba13f93193eb56d3"
     },
     {
       "path": "workshop-skill/follow-up-package.md",

package/assets/workshop-bundle/content/facilitation/master-guide.md

@@ -64,14 +64,14 @@ Pravidla:
 
 Po launchi potřebuje místnost ještě jednu konkrétní věc:
 
-- co má být po prvním build bloku opravdu vidět
-- co nestačí jen slíbit
+- co má být po prvním build bloku opravdu vidět v repu
+- co nestačí jen slíbit nebo dovysvětlit u stolu
 
 Do oběda má být vidět:
 
-- repo a `README`, které dávají smysl cizímu člověku
-- `AGENTS.md` jako krátká mapa
-- plan nebo jasně vedená implementační stopa
+- `README`, které dává smysl cizímu člověku
+- `AGENTS.md` jako krátká mapa, ne sklad všeho
+- plan nebo jasně vedená implementační stopa, ze které je poznat další safe move
 - první explicitní check před dalším generováním
 
 ## Context is King talk
@@ -93,6 +93,8 @@ Proměnit energii z openingu v přesnou tezi a čistý most do Build fáze 1.
 
 ### Mikro-cvičení
 
+Tohle je krátká facilitátorova ukázka, ne zadání pro celý room.
+
 Použijte stejný malý task ve dvou podmínkách:
 
 1. prompt blob
@@ -112,6 +114,7 @@ Na konci talku má být jasné:
 
 - teorie tím končí
 - tým se vrací k repu
+- pokud tým ještě nemá workshop skill, teď je chvíle na `harness skill install`, pak `Codex: $workshop setup` nebo `pi: /skill:workshop`
 - nejdřív vzniká mapa a první explicitní check
 - teprve potom dává smysl další feature motion
 

package/assets/workshop-bundle/content/project-briefs/code-review-helper.md

@@ -2,30 +2,30 @@
 
 ## Problém
 
-Code review bývá nevyrovnané. Některé změny projdou s dobrým checklistem a jasným popisem rizik, jiné bez společného rámce. Reviewer pak improvizuje, autor neví, co má ověřit předem, a tým ztrácí konzistenci.
+Code review bývá nevyrovnané. Některé změny projdou s dobrým checklistem a jasným popisem rizik, jiné bez společného rámce. Reviewer pak improvizuje, autor neví, co má ověřit předem, a tým ztrácí konzistenci právě tam, kde by měl být nejpřesnější.
 
-Vaším úkolem je navrhnout nástroj, který z diffu nebo změny vytvoří použitelný review checklist.
+Vaším úkolem je navrhnout nástroj, který z diffu nebo změny vytvoří použitelný review checklist a zároveň jasně oddělí jistotu, heuristiku a místa, kde je pořád potřeba lidský úsudek.
 
 ## User stories
 
-- Jako reviewer chci z diffu rychle získat checklist rizik, otázek a míst, na která se zaměřit.
-- Jako autor změny chci vědět, co mám zkontrolovat ještě před samotným review.
+- Jako reviewer chci z diffu rychle získat checklist změněných hranic, rizik, otázek a míst, na která se zaměřit.
+- Jako autor změny chci vědět, co mám ověřit ještě před samotným review.
 - Jako tým po rotaci chci navázat na heuristiky, které původní tým objevil, místo abych je znovu vymýšlel.
 
 ## Architektonické poznámky
 
-- Může jít o CLI, web nebo jednoduchý skript. Důležitý je jasný tok `diff → analýza → checklist`.
-- Musí být zřejmé, jaké vstupy nástroj očekává a co naopak neumí spolehlivě vyhodnotit.
-- Přidejte seed diff nebo `examples/`, aby šlo workflow lokálně ověřit.
-- Jasně oddělte heuristiku od jistoty. Nástroj má pomáhat reviewerovi, ne předstírat neomylnost.
+- Může jít o CLI, web nebo jednoduchý skript. Důležitý je jasný tok `diff → rubric → checklist`.
+- Musí být zřejmé, jaké vstupy nástroj očekává, co umí označit jistě a co naopak zůstává heuristické.
+- Přidejte seed diff nebo `examples/`, aby šlo workflow lokálně ověřit a další tým rychle přidal nové pravidlo.
+- Nástroj má pomáhat reviewerovi, ne předstírat neomylnost.
 
 ## Hotovo když
 
 - Nástroj vytvoří review checklist ze seed diffu.
-- Výstup odlišuje jistá zjištění od doporučení nebo hypotéz.
+- Výstup odlišuje jistá zjištění od doporučení, hypotéz a bodů pro lidský úsudek.
 - Je jasné, jak přidat nové pravidlo nebo heuristiku bez dlouhého onboardingu.
 - Další tým může během několika minut pokračovat v rozvoji bez chaosu.
 
 ## První krok pro agenta
 
-Nezačínej kódem. Nejdřív napiš pravidla review, tok vstupů a definici toho, co znamená dobrý checklist. Teprve potom navrhni první implementační slice.
+Nezačínej kódem. Nejdřív napiš review rubric, tok vstupů a definici toho, co znamená dobrý checklist. Ukaž, kde je jistota, kde heuristika a co musí posoudit člověk. Teprve potom navrhni první implementační slice.

package/assets/workshop-bundle/content/talks/context-is-king.md

@@ -30,7 +30,9 @@ Pointa analogie:
 
 ## Mikro-cvičení
 
-Všichni dostanou stejný malý task. Jedna varianta bude prompt blob. Druhá varianta bude krátké zadání se 4 prvky a s odkazem na kontext zapsaný v repu. Pak porovnáme výsledky. Nehledáme „nejhezčí prompt“. Hledáme způsob práce, který přenese záměr, omezení a done criteria i do dalšího kroku.
+Tohle je krátká facilitátorova ukázka, ne práce pro celý room.
+
+Vezmeme stejný malý task ve dvou podmínkách. Jedna varianta bude prompt blob. Druhá varianta bude krátké zadání se 4 prvky a s odkazem na kontext zapsaný v repu. Pak porovnáme výsledky. Nehledáme „nejhezčí prompt“. Hledáme způsob práce, který přenese záměr, omezení a done criteria i do dalšího kroku.
 
 4 prvky pro druhou variantu:
 
@@ -64,6 +66,7 @@ Všichni dostanou stejný malý task. Jedna varianta bude prompt blob. Druhá va
 
 Po tomhle talku se tým nemá vracet k repu s pocitem, že potřebuje jen chytřejší prompt. Má se vracet s jedním jasným očekáváním:
 
+- pokud ještě nemá workshop skill, teď je chvíle na `harness skill install`, pak `Codex: $workshop setup` nebo `pi: /skill:workshop`
 - nejdřív krátká mapa v repu
 - potom plan
 - potom první explicitní check

package/assets/workshop-bundle/docs/harness-cli-foundation.md

@@ -8,7 +8,7 @@ Current implementation in this repo:
 
 - lives in the repository `harness-cli/` package and ships publicly as `@harness-lab/cli`
 - distributes a portable participant workshop skill bundle through `harness skill install`
-- covers `auth login/logout/status` plus `workshop status/create-instance/update-instance/reset-instance/prepare/remove-instance/archive/phase set`
+- covers `auth login/logout/status` plus `workshop current-instance/select-instance/status/list-instances/show-instance/create-instance/update-instance/reset-instance/prepare/remove-instance/archive/phase set`
 - targets the existing shared dashboard facilitator APIs
 - is tested for browser/device auth, local-dev Basic Auth fallback, and cookie-backed Neon bootstrap fallback
 - stores sessions in a local file under `HARNESS_CLI_HOME` or `~/.harness` by default
@@ -38,7 +38,11 @@ Required commands:
 - `harness auth login`
 - `harness auth logout`
 - `harness auth status`
+- `harness workshop current-instance`
+- `harness workshop select-instance <instance-id>`
 - `harness workshop status`
+- `harness workshop list-instances`
+- `harness workshop show-instance <instance-id>`
 - `harness workshop create-instance`
 - `harness workshop update-instance`
 - `harness workshop reset-instance <instance-id>`
@@ -83,28 +87,41 @@ Current auth layering:
 Current target-selection order:
 
 1. an explicit command or route instance id
-2. the selected control-room instance in the dashboard
+2. the CLI-local persisted selection set by `harness workshop select-instance`
 3. the deployment default `HARNESS_WORKSHOP_INSTANCE_ID`
 4. a repository fallback only on surfaces that intentionally present a workspace-level default
 
 Current command posture:
 
-- explicit target required:
-  - `harness workshop update-instance <instance-id>`
-  - `harness workshop reset-instance <instance-id>`
-  - `harness workshop prepare <instance-id>`
-  - `harness workshop remove-instance <instance-id>`
+- explicit workspace-discovery commands:
+  - `harness workshop current-instance`
+  - `harness workshop select-instance <instance-id>`
+  - `harness workshop list-instances`
+- explicit target preferred but selected-instance fallback allowed:
+  - `harness workshop show-instance [<instance-id>]`
+  - `harness workshop update-instance [<instance-id>]`
+  - `harness workshop reset-instance [<instance-id>]`
+  - `harness workshop prepare [<instance-id>]`
+  - `harness workshop remove-instance [<instance-id>]`
 - explicit target is the created resource:
   - `harness workshop create-instance [<instance-id>]`
-- deployment-default target:
+- selected-instance target first, otherwise deployment-default target:
   - `harness workshop status`
-  - `harness workshop archive`
   - `harness workshop phase set <phase-id>`
+- deployment-default target:
+  - `harness workshop archive`
 
 Current discoverability path:
 
 - facilitators can inspect available workshop instances through the dashboard workspace view
 - the same platform-scoped list lives behind the authenticated instances API surface at `/api/workshop/instances`
+- the CLI should expose that list directly so facilitator skills do not need session-file inspection or raw authenticated scripts for routine discovery
+- the CLI should also expose a local current-target selector so repeated facilitator work does not depend on ambient dashboard selection or deployment-default routing
+
+Machine-readable posture:
+
+- facilitator commands should support `--json` for strict machine parsing without headings or prose wrappers
+- skills and agents should prefer `harness --json ...` over scraping human-oriented terminal formatting
 
 For the current facilitator lifecycle slice:
 

package/assets/workshop-bundle/workshop-blueprint/README.md

@@ -39,7 +39,7 @@ Do not use this folder for live event state. Real dates, rooms, rosters, checkpo
 ### Structured data
 
 - [`agenda.json`](agenda.json)
-  Public-readable workshop agenda summary and workshop metadata.
+  Public-readable 10-phase mirror of the workshop day and workshop metadata.
 
 ## Related Runtime Documents
 
@@ -51,5 +51,6 @@ For maintainers working in the source repository, the runtime-facing structured
 
 - `docs/workshop-content-language-architecture.md`
 - `dashboard/lib/workshop-blueprint-agenda.json`
+- `dashboard/lib/workshop-blueprint-localized-content.ts`
 
-Treat those as maintainer/source-repo references, not as portable participant-bundle docs.
+Treat those as maintainer/source-repo references, not as portable participant-bundle docs. The public `agenda.json` file should stay aligned with the same phase structure, but it is not the runtime import source.

package/assets/workshop-bundle/workshop-blueprint/agenda.json

@@ -1,21 +1,23 @@
 {
-  "version": 1,
+  "version": 2,
   "blueprintId": "harness-lab-core-day",
   "title": "Harness Lab",
-  "subtitle": "Workshop operating system pro práci s AI agenty",
+  "subtitle": "Public-readable 10-phase mirror of the Harness Lab workshop day",
+  "presentationMode": "public-readable-mirror",
+  "sourceNote": "Runtime imports come from dashboard/lib/workshop-blueprint-agenda.json plus dashboard/lib/workshop-blueprint-localized-content.ts.",
   "principles": [
-    "Mapa před pohybem",
-    "Ověření je hranice důvěry",
-    "Pište tak, aby další tým mohl pokračovat"
+    "Context before generation",
+    "Verification is the trust boundary",
+    "Work so another team can continue"
   ],
   "phases": [
     {
       "id": "opening",
       "order": 1,
-      "label": "Úvod a naladění",
+      "label": "Opening and framing",
       "startTime": "09:10",
       "kind": "shared",
-      "goal": "Rámec dne: nejde o promptování, ale o repo a workflow, které přežijí handoff."
+      "goal": "Shift the room from prompt-hackathon expectations to continuation-quality discipline."
     },
     {
       "id": "talk",
@@ -23,31 +25,71 @@
       "label": "Context is King",
       "startTime": "09:40",
       "kind": "shared",
-      "goal": "Krátký talk a porovnání přístupů. Krátká mapa v repu je silnější než prompt blob."
+      "goal": "Turn context into a precise thesis: AGENTS.md, plans, and checks are working infrastructure, not polish."
     },
     {
-      "id": "build-1",
+      "id": "demo",
       "order": 3,
+      "label": "Demo",
+      "startTime": "10:05",
+      "kind": "shared",
+      "goal": "Show one compact workflow story: context, planning, implementation, review, and safe fallback moves."
+    },
+    {
+      "id": "build-1",
+      "order": 4,
       "label": "Build Phase 1",
       "startTime": "10:30",
       "kind": "team",
-      "goal": "Nejdřív udělejte z repa operating surface: krátké AGENTS.md, plán, build/test flow, první ověření a první reviewed output."
+      "goal": "Before lunch, get every team to a navigable repo, AGENTS.md, a plan, one explicit check, and a first reviewed slice."
+    },
+    {
+      "id": "intermezzo-1",
+      "order": 5,
+      "label": "Intermezzo 1",
+      "startTime": "11:40",
+      "kind": "shared",
+      "goal": "Surface one change, one proof, and one next move from the room before lunch momentum slips."
+    },
+    {
+      "id": "lunch-reset",
+      "order": 6,
+      "label": "Lunch Reset",
+      "startTime": "12:15",
+      "kind": "shared",
+      "goal": "Frame lunch as a handoff preparation point, not as a pause between unrelated workshop blocks."
     },
     {
       "id": "rotation",
-      "order": 4,
-      "label": "Rotace týmů",
+      "order": 7,
+      "label": "Continuation Shift",
       "startTime": "13:30",
       "kind": "team",
-      "goal": "Plný přesun lidí mezi stoly. Nejdřív čtěte a napište diagnózu, až pak měňte kód."
+      "goal": "Force silent repo reading, diagnosis, and explicit continuation before anyone edits code."
+    },
+    {
+      "id": "build-2",
+      "order": 8,
+      "label": "Build Phase 2",
+      "startTime": "14:05",
+      "kind": "team",
+      "goal": "Turn continuation friction into better repo guidance, stronger checks, and clearer next moves."
+    },
+    {
+      "id": "intermezzo-2",
+      "order": 9,
+      "label": "Intermezzo 2",
+      "startTime": "15:05",
+      "kind": "shared",
+      "goal": "Name which repo signals actually saved time during continuation and which failures repeated."
     },
     {
       "id": "reveal",
-      "order": 5,
-      "label": "Reveal a reflexe",
+      "order": 10,
+      "label": "Reveal and reflection",
       "startTime": "15:45",
       "kind": "shared",
-      "goal": "Co pomohlo pokračovat, co chybělo, a kterou bolest teď proměníme v lepší harness."
+      "goal": "Turn the day into reusable practice: what helped continuation, what failed, and what should change next week."
     }
   ],
   "runtimeImport": {

package/assets/workshop-bundle/workshop-blueprint/day-structure.md

@@ -147,8 +147,8 @@ The day should not feel like separate agenda cards. Each phase should change wha
 - `AGENTS.md` as a table of contents that points to deeper sources of truth
 - small, continuous garbage collection before bad patterns spread
 
-## Canonical Agenda Source
+## Agenda Mirror
 
-The reusable agenda lives in [`agenda.json`](agenda.json).
+The public-readable 10-phase mirror lives in [`agenda.json`](agenda.json).
 
-Runtime workshop instances import from that blueprint and then track live phase position, reveal state, teams, and checkpoints locally in the private runtime layer.
+Runtime workshop instances import from the maintained dashboard blueprint source pair and then track live phase position, reveal state, teams, and checkpoints locally in the private runtime layer.

package/assets/workshop-bundle/workshop-skill/facilitator.md

@@ -41,6 +41,20 @@ Note:
 - if the facilitator wants OS-native storage, they can use `HARNESS_SESSION_STORAGE=keychain`, `credential-manager`, or `secret-service`
 - `--auth basic` and `--auth neon` remain explicit fallbacks for local dev/bootstrap
 
+Preferred operator flow after login:
+
+```bash
+harness workshop list-instances
+harness workshop select-instance sample-workshop-demo-orbit
+harness workshop current-instance
+harness workshop status
+```
+
+Rules:
+- prefer this flow over reading local CLI session files or composing ad hoc authenticated `node -e` scripts
+- once a local selection exists, the CLI may use it as the default target for subsequent facilitator operations
+- when an agent needs machine-readable output, prefer `harness --json ...`
+
 ### `/workshop facilitator logout`
 
 Ask the facilitator to run:
@@ -65,6 +79,103 @@ Show:
 - facilitator list with roles
 - team count
 
+Use this for the current default or selected workshop context.
+If the facilitator needs the full workspace registry first, use `list-instances` instead of probing local session files or writing raw authenticated fetch scripts.
+
+Targeting behavior:
+- if the facilitator previously ran `harness workshop select-instance <instance-id>`, `status` reports that selected instance
+- if no local selection exists, `status` falls back to the deployment-default workshop context
+- for exact machine parsing, prefer `harness --json workshop status`
+
+### `/workshop facilitator current-instance`
+
+Preferred path:
+
+```bash
+harness workshop current-instance
+```
+
+Show:
+- the locally selected instance id when one exists
+- whether the current target came from persisted selection or `HARNESS_WORKSHOP_INSTANCE_ID`
+- the resolved instance summary and full record for operator verification
+
+Rules:
+- use this after `select-instance` when the facilitator wants to confirm the CLI target before update, reset, or remove
+- if nothing is selected, the command should say so clearly instead of forcing the facilitator into session-file inspection
+
+### `/workshop facilitator select-instance <instance-id>`
+
+Preferred path:
+
+```bash
+harness workshop select-instance sample-workshop-demo-orbit
+```
+
+Clear the stored selection:
+
+```bash
+harness workshop select-instance --clear
+```
+
+Rules:
+- use this when a facilitator will perform several operations against the same live workshop instance
+- the CLI should validate the instance through the server before persisting the selection
+- after selection, `status` and `phase set` should target that instance instead of the deployment default
+- `show-instance`, `update-instance`, `reset-instance`, `prepare`, and `remove-instance` may omit `<instance-id>` when a valid selection already exists
+
+### `/workshop facilitator list-instances`
+
+Preferred path:
+
+```bash
+harness workshop list-instances
+```
+
+Show:
+- facilitator-visible instance ids
+- template id
+- status
+- content language
+- event title and room metadata when present
+
+Raw API reference:
+
+```http
+GET {DASHBOARD_URL}/api/workshop/instances
+```
+
+Rules:
+- prefer this over inspecting local session files or composing one-off authenticated scripts
+- use it when the facilitator needs to discover which live instances exist before reset, update, or scene work
+- keep raw API usage as a diagnostic fallback, not the default operator workflow
+- when an agent needs to parse the output, prefer `harness --json workshop list-instances`
+
+### `/workshop facilitator show-instance <instance-id>`
+
+Preferred path:
+
+```bash
+harness workshop show-instance sample-workshop-demo-orbit
+```
+
+Show:
+- one explicit instance record
+- summary metadata for quick operator inspection
+- the full instance payload when the facilitator needs exact values before a mutation
+
+Raw API reference:
+
+```http
+GET {DASHBOARD_URL}/api/workshop/instances/{instanceId}
+```
+
+Rules:
+- use this when the facilitator needs one specific instance, not the deployment-default `workshop status`
+- if the route returns `404`, the instance does not exist or is not visible to the facilitator
+- prefer this over ad hoc authenticated scripts for routine discovery
+- if a local selection already exists, the facilitator may omit `<instance-id>` and let the CLI use the stored target
+
 ### `/workshop facilitator grant <email> <role>`
 
 Use the CLI-backed privileged request path. The skill should not handle auth bootstrap itself.
@@ -176,6 +287,8 @@ Rules:
 - send only the fields you want to change
 - do not use reset for an ordinary title, venue, or room correction
 - if the route returns `400`, the payload is wrong; if it returns `404`, the instance does not exist
+- use `--content-lang cs|en` when the facilitator intends to change the workshop delivery language for that instance
+- if the facilitator already selected a local current instance, the CLI may omit `<instance-id>` and use the stored target
 
 ### `/workshop facilitator reset-instance <instance-id>`
 
@@ -202,6 +315,7 @@ Rules:
 - warn that reset archives current runtime state first and then clears live runtime state for the instance
 - prefer `update-instance` for ordinary metadata corrections; reset is the high-impact operation
 - if the facilitator does not specify a template, keep the current template unless there is a clear reason to switch
+- if the facilitator already selected a local current instance, the CLI may omit `<instance-id>` and use the stored target
 
 ### `/workshop facilitator prepare`
 
@@ -221,6 +335,7 @@ Content-Type: application/json
 ```
 
 This sets the instance to `prepared` state and verifies the event code.
+If a local current instance is already selected, the CLI may omit `<instance-id>` and use the stored target.
 
 ### `/workshop facilitator remove-instance <instance-id>`
 
@@ -242,6 +357,7 @@ Content-Type: application/json
 Rules:
 - remove remains an owner-only operation
 - the skill should warn the facilitator that this is destructive removal from the active list, not routine metadata editing
+- if the facilitator already selected a local current instance, the CLI may omit `<instance-id>` and use the stored target
 
 ### `/workshop facilitator agenda`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@harness-lab/cli",
-  "version": "0.2.7",
+  "version": "0.2.9",
   "description": "Participant-facing Harness Lab CLI for facilitator auth and workshop operations",
   "license": "MIT",
   "type": "module",

package/src/client.js

@@ -90,12 +90,27 @@ export function createHarnessClient({ fetchFn, session }) {
     getWorkshopStatus() {
       return request("/api/workshop");
     },
+    listWorkshopInstances() {
+      return request("/api/workshop/instances");
+    },
+    getWorkshopInstance(instanceId) {
+      return request(`/api/workshop/instances/${encodeURIComponent(instanceId)}`);
+    },
     getAgenda() {
       return request("/api/agenda");
     },
+    getWorkshopAgenda(instanceId) {
+      return request(`/api/workshop/instances/${encodeURIComponent(instanceId)}/agenda`);
+    },
     setCurrentPhase(currentId) {
       return request("/api/agenda", { method: "PATCH", body: { currentId } });
     },
+    setCurrentPhaseForInstance(instanceId, currentId) {
+      return request(`/api/workshop/instances/${encodeURIComponent(instanceId)}/agenda`, {
+        method: "PATCH",
+        body: { itemId: currentId },
+      });
+    },
     archiveWorkshop(notes) {
       return request("/api/workshop/archive", { method: "POST", body: notes ? { notes } : {} });
     },

package/src/io.js

@@ -84,7 +84,9 @@ function writeWrapped(stream, text, options = {}) {
   }
 }
 
-export function createCliUi(io) {
+export function createCliUi(io, options = {}) {
+  const jsonMode = options.jsonMode === true;
+
   function streamFor(target) {
     return target === "stderr" ? io.stderr : io.stdout;
   }
@@ -115,6 +117,10 @@ export function createCliUi(io) {
   function status(kind, text, options = {}) {
     const target = options.stream ?? (kind === "error" ? "stderr" : "stdout");
     const stream = streamFor(target);
+    if (jsonMode) {
+      writeLine(stream, JSON.stringify({ ok: kind !== "error", level: kind, message: text }));
+      return;
+    }
     const chalk = createStyler(stream, io.env);
     const prefixMap = {
       ok: chalk.green.bold("[ok]"),
@@ -178,7 +184,9 @@ export function createCliUi(io) {
 
   function json(title, value, options = {}) {
     const target = options.stream ?? "stdout";
-    heading(title, { stream: target });
+    if (!jsonMode) {
+      heading(title, { stream: target });
+    }
     writeLine(streamFor(target), JSON.stringify(value, null, 2));
   }
 

package/src/run-cli.js

@@ -16,6 +16,7 @@ function sleep(ms) {
 function parseArgs(argv) {
   const positionals = [];
   const flags = {};
+  const booleanFlags = new Set(["json", "help", "version", "force", "no-open", "clear"]);
 
   for (let index = 0; index < argv.length; index += 1) {
     const value = argv[index];
@@ -29,6 +30,10 @@ function parseArgs(argv) {
     }
     if (value.startsWith("--")) {
       const key = value.slice(2);
+      if (booleanFlags.has(key)) {
+        flags[key] = true;
+        continue;
+      }
       const next = argv[index + 1];
       if (!next || next.startsWith("--")) {
         flags[key] = true;
@@ -103,6 +108,7 @@ async function readRequiredCommandValue(io, flags, keys, promptLabel, fallbackVa
 
 function buildWorkshopMetadataInput(flags) {
   const input = {
+    contentLang: readStringFlag(flags, "content-lang", "content-language"),
     eventTitle: readStringFlag(flags, "event-title", "title"),
     city: readStringFlag(flags, "city"),
     dateRange: readStringFlag(flags, "date-range", "date"),
@@ -122,6 +128,7 @@ function hasWorkshopMetadataInput(input) {
 
 async function promptWorkshopMetadataInput(io) {
   const prompts = [
+    ["contentLang", "Content language (cs/en, leave blank to skip): "],
     ["eventTitle", "Event title (leave blank to skip): "],
     ["city", "City (leave blank to skip): "],
     ["dateRange", "Date range (leave blank to skip): "],
@@ -148,7 +155,9 @@ function summarizeWorkshopInstance(instance) {
 
   return {
     instanceId: instance?.id ?? null,
+    templateId: instance?.templateId ?? null,
     status: instance?.status ?? null,
+    contentLang: workshopMeta.contentLang ?? null,
     eventTitle: workshopMeta.eventTitle ?? null,
     city: workshopMeta.city ?? null,
     dateRange: workshopMeta.dateRange ?? null,
@@ -157,12 +166,34 @@ function summarizeWorkshopInstance(instance) {
   };
 }
 
+function resolveCurrentInstanceTarget(session, env) {
+  if (typeof session?.selectedInstanceId === "string" && session.selectedInstanceId.trim().length > 0) {
+    return {
+      instanceId: session.selectedInstanceId.trim(),
+      source: "session",
+    };
+  }
+
+  if (typeof env?.HARNESS_WORKSHOP_INSTANCE_ID === "string" && env.HARNESS_WORKSHOP_INSTANCE_ID.trim().length > 0) {
+    return {
+      instanceId: env.HARNESS_WORKSHOP_INSTANCE_ID.trim(),
+      source: "env",
+    };
+  }
+
+  return {
+    instanceId: null,
+    source: "none",
+  };
+}
+
 function printUsage(io, ui) {
   ui.heading("Harness CLI");
   ui.paragraph(`Version ${version}`);
   ui.blank();
   ui.section("Usage");
   ui.commandList([
+    "harness [--json] <command>",
     "harness --help",
     "harness --version",
     "harness version",
@@ -174,10 +205,14 @@ function printUsage(io, ui) {
     "harness auth logout",
     "harness auth status",
     "harness skill install [--target PATH] [--force]",
+    "harness workshop current-instance",
+    "harness workshop select-instance <instance-id> [--clear]",
     "harness workshop status",
+    "harness workshop list-instances",
+    "harness workshop show-instance <instance-id>",
     "harness workshop archive [--notes TEXT]",
-    "harness workshop create-instance [<instance-id>] [--template-id ID] [--event-title TEXT] [--city CITY]",
-    "harness workshop update-instance <instance-id> [--event-title TEXT] [--city CITY]",
+    "harness workshop create-instance [<instance-id>] [--template-id ID] [--content-lang cs|en] [--event-title TEXT] [--city CITY]",
+    "harness workshop update-instance <instance-id> [--content-lang cs|en] [--event-title TEXT] [--city CITY]",
     "harness workshop reset-instance <instance-id> [--template-id ID]",
     "harness workshop prepare <instance-id>",
     "harness workshop remove-instance <instance-id>",
@@ -565,9 +600,30 @@ async function handleWorkshopStatus(io, ui, env, deps) {
 
   try {
     const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
+    const target = resolveCurrentInstanceTarget(session, env);
+
+    if (target.source === "session" && target.instanceId) {
+      const [instanceResult, agenda] = await Promise.all([
+        client.getWorkshopInstance(target.instanceId),
+        client.getWorkshopAgenda(target.instanceId),
+      ]);
+      ui.json("Workshop Status", {
+        ok: true,
+        targetInstanceId: target.instanceId,
+        targetSource: target.source,
+        ...summarizeWorkshopInstance(instanceResult.instance),
+        workshopMeta: instanceResult.instance?.workshopMeta ?? null,
+        currentPhase: agenda.phase,
+        agendaItems: Array.isArray(agenda.items) ? agenda.items.length : null,
+      });
+      return 0;
+    }
+
     const [workshop, agenda] = await Promise.all([client.getWorkshopStatus(), client.getAgenda()]);
     ui.json("Workshop Status", {
       ok: true,
+      targetInstanceId: target.instanceId,
+      targetSource: target.source,
       workshopId: workshop.workshopId,
       workshopMeta: workshop.workshopMeta,
       currentPhase: agenda.phase,
@@ -583,6 +639,168 @@ async function handleWorkshopStatus(io, ui, env, deps) {
   }
 }
 
+async function handleWorkshopCurrentInstance(io, ui, env, deps) {
+  const session = await requireSession(io, ui, env);
+  if (!session) {
+    return 1;
+  }
+
+  const target = resolveCurrentInstanceTarget(session, env);
+  if (!target.instanceId) {
+    ui.json("Workshop Current Instance", {
+      ok: true,
+      instanceId: null,
+      source: target.source,
+      selectedInstanceId: session.selectedInstanceId ?? null,
+    });
+    return 0;
+  }
+
+  try {
+    const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
+    const result = await client.getWorkshopInstance(target.instanceId);
+    ui.json("Workshop Current Instance", {
+      ok: true,
+      source: target.source,
+      selectedInstanceId: session.selectedInstanceId ?? null,
+      ...summarizeWorkshopInstance(result.instance),
+      instance: result.instance,
+    });
+    return 0;
+  } catch (error) {
+    if (error instanceof HarnessApiError) {
+      ui.status("error", `Current instance lookup failed: ${error.message}`, { stream: "stderr" });
+      return 1;
+    }
+    throw error;
+  }
+}
+
+async function handleWorkshopSelectInstance(io, ui, env, positionals, flags, deps) {
+  const session = await requireSession(io, ui, env);
+  if (!session) {
+    return 1;
+  }
+
+  if (flags.clear === true) {
+    const nextSession = { ...session };
+    delete nextSession.selectedInstanceId;
+    if (!(await persistSession(io, ui, env, nextSession))) {
+      return 1;
+    }
+
+    const target = resolveCurrentInstanceTarget(nextSession, env);
+    ui.json("Workshop Select Instance", {
+      ok: true,
+      selectedInstanceId: null,
+      currentInstanceId: target.instanceId,
+      source: target.source,
+      cleared: true,
+    });
+    return 0;
+  }
+
+  const instanceId = await readRequiredCommandValue(
+    io,
+    flags,
+    ["id", "instance-id"],
+    "Instance id: ",
+    readOptionalPositional(positionals, 2),
+  );
+  if (!instanceId) {
+    ui.status("error", "Instance id is required.", { stream: "stderr" });
+    return 1;
+  }
+
+  try {
+    const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
+    const result = await client.getWorkshopInstance(instanceId);
+    const nextSession = {
+      ...session,
+      selectedInstanceId: result.instance?.id ?? instanceId,
+    };
+    if (!(await persistSession(io, ui, env, nextSession))) {
+      return 1;
+    }
+
+    ui.json("Workshop Select Instance", {
+      ok: true,
+      source: "session",
+      selectedInstanceId: nextSession.selectedInstanceId,
+      ...summarizeWorkshopInstance(result.instance),
+      instance: result.instance,
+    });
+    return 0;
+  } catch (error) {
+    if (error instanceof HarnessApiError) {
+      ui.status("error", `Select instance failed: ${error.message}`, { stream: "stderr" });
+      return 1;
+    }
+    throw error;
+  }
+}
+
+async function handleWorkshopListInstances(io, ui, env, deps) {
+  const session = await requireSession(io, ui, env);
+  if (!session) {
+    return 1;
+  }
+
+  try {
+    const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
+    const result = await client.listWorkshopInstances();
+    const items = Array.isArray(result?.items) ? result.items.map((instance) => summarizeWorkshopInstance(instance)) : [];
+    ui.json("Workshop Instances", {
+      ok: true,
+      count: items.length,
+      items,
+    });
+    return 0;
+  } catch (error) {
+    if (error instanceof HarnessApiError) {
+      ui.status("error", `List instances failed: ${error.message}`, { stream: "stderr" });
+      return 1;
+    }
+    throw error;
+  }
+}
+
+async function handleWorkshopShowInstance(io, ui, env, positionals, flags, deps) {
+  const session = await requireSession(io, ui, env);
+  if (!session) {
+    return 1;
+  }
+
+  const instanceId = await readRequiredCommandValue(
+    io,
+    flags,
+    ["id", "instance-id"],
+    "Instance id: ",
+    readOptionalPositional(positionals, 2) ?? session.selectedInstanceId,
+  );
+  if (!instanceId) {
+    ui.status("error", "Instance id is required.", { stream: "stderr" });
+    return 1;
+  }
+
+  try {
+    const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
+    const result = await client.getWorkshopInstance(instanceId);
+    ui.json("Workshop Instance", {
+      ok: true,
+      ...summarizeWorkshopInstance(result.instance),
+      instance: result.instance,
+    });
+    return 0;
+  } catch (error) {
+    if (error instanceof HarnessApiError) {
+      ui.status("error", `Show instance failed: ${error.message}`, { stream: "stderr" });
+      return 1;
+    }
+    throw error;
+  }
+}
+
 async function handleWorkshopArchive(io, ui, env, flags, deps) {
   const session = await requireSession(io, ui, env);
   if (!session) {
@@ -657,7 +875,7 @@ async function handleWorkshopUpdateInstance(io, ui, env, positionals, flags, dep
     flags,
     ["id"],
     "Instance id: ",
-    readOptionalPositional(positionals, 2),
+    readOptionalPositional(positionals, 2) ?? session.selectedInstanceId,
   );
   if (!instanceId) {
     ui.status("error", "Instance id is required.", { stream: "stderr" });
@@ -672,7 +890,7 @@ async function handleWorkshopUpdateInstance(io, ui, env, positionals, flags, dep
   if (!hasWorkshopMetadataInput(payload)) {
     ui.status(
       "error",
-      "At least one metadata field is required. Use flags such as --event-title, --date-range, --venue-name, or --room-name.",
+      "At least one metadata field is required. Use flags such as --content-lang, --event-title, --date-range, --venue-name, or --room-name.",
       { stream: "stderr" },
     );
     return 1;
@@ -707,7 +925,7 @@ async function handleWorkshopPrepare(io, ui, env, positionals, flags, deps) {
     flags,
     ["id", "instance-id"],
     "Instance id: ",
-    readOptionalPositional(positionals, 2),
+    readOptionalPositional(positionals, 2) ?? session.selectedInstanceId,
   );
   if (!instanceId) {
     ui.status("error", "Instance id is required.", { stream: "stderr" });
@@ -743,7 +961,7 @@ async function handleWorkshopResetInstance(io, ui, env, positionals, flags, deps
     flags,
     ["id", "instance-id"],
     "Instance id: ",
-    readOptionalPositional(positionals, 2),
+    readOptionalPositional(positionals, 2) ?? session.selectedInstanceId,
   );
   if (!instanceId) {
     ui.status("error", "Instance id is required.", { stream: "stderr" });
@@ -778,7 +996,7 @@ async function handleWorkshopRemoveInstance(io, ui, env, positionals, flags, dep
     flags,
     ["id", "instance-id"],
     "Instance id: ",
-    readOptionalPositional(positionals, 2),
+    readOptionalPositional(positionals, 2) ?? session.selectedInstanceId,
   );
   if (!instanceId) {
     ui.status("error", "Instance id is required.", { stream: "stderr" });
@@ -817,7 +1035,11 @@ async function handleWorkshopPhaseSet(io, ui, env, positionals, deps) {
 
   try {
     const client = createHarnessClient({ fetchFn: deps.fetchFn, session });
-    const result = await client.setCurrentPhase(phaseId);
+    const target = resolveCurrentInstanceTarget(session, env);
+    const result =
+      target.source === "session" && target.instanceId
+        ? await client.setCurrentPhaseForInstance(target.instanceId, phaseId)
+        : await client.setCurrentPhase(phaseId);
     ui.json("Workshop Phase", result);
     return 0;
   } catch (error) {
@@ -832,8 +1054,8 @@ async function handleWorkshopPhaseSet(io, ui, env, positionals, deps) {
 export async function runCli(argv, io, deps = {}) {
   const fetchFn = deps.fetchFn ?? globalThis.fetch;
   const mergedDeps = { fetchFn, sleepFn: deps.sleepFn, openUrl: deps.openUrl, cwd: deps.cwd };
-  const ui = createCliUi(io);
   const { positionals, flags } = parseArgs(argv);
+  const ui = createCliUi(io, { jsonMode: flags.json === true || flags.output === "json" });
   const [scope, action, subaction] = positionals;
 
   if (flags.help === true) {
@@ -876,10 +1098,26 @@ export async function runCli(argv, io, deps = {}) {
     return handleSkillInstall(io, ui, mergedDeps, flags);
   }
 
+  if (scope === "workshop" && action === "current-instance") {
+    return handleWorkshopCurrentInstance(io, ui, io.env, mergedDeps);
+  }
+
+  if (scope === "workshop" && action === "select-instance") {
+    return handleWorkshopSelectInstance(io, ui, io.env, positionals, flags, mergedDeps);
+  }
+
   if (scope === "workshop" && action === "status") {
     return handleWorkshopStatus(io, ui, io.env, mergedDeps);
   }
 
+  if (scope === "workshop" && action === "list-instances") {
+    return handleWorkshopListInstances(io, ui, io.env, mergedDeps);
+  }
+
+  if (scope === "workshop" && action === "show-instance") {
+    return handleWorkshopShowInstance(io, ui, io.env, positionals, flags, mergedDeps);
+  }
+
   if (scope === "workshop" && action === "archive") {
     return handleWorkshopArchive(io, ui, io.env, flags, mergedDeps);
   }

package/src/session-store.js

@@ -314,6 +314,7 @@ export function sanitizeSession(session, env) {
     authType: session.authType,
     username: session.username ?? null,
     email: session.email ?? null,
+    selectedInstanceId: session.selectedInstanceId ?? null,
     loggedInAt: session.loggedInAt,
     expiresAt: session.expiresAt ?? null,
     mode: session.mode ?? "local-dev",

package/src/workshop-bundle.js

@@ -225,6 +225,20 @@ async function writeWorkshopBundleManifest(bundleRoot, manifest) {
   );
 }
 
+async function pruneBundleFiles(bundleRoot, manifest) {
+  const expectedFiles = new Set([
+    WORKSHOP_BUNDLE_MANIFEST,
+    ...manifest.files.map((file) => file.path),
+  ]);
+  const currentFiles = await listFilesRecursive(bundleRoot);
+
+  for (const file of currentFiles) {
+    if (!expectedFiles.has(file.relativePath)) {
+      await fs.rm(file.absolutePath, { force: true });
+    }
+  }
+}
+
 export async function createWorkshopBundleFromSource(sourceRoot, targetRoot, options = {}) {
   if (options.clean === true) {
     await fs.rm(targetRoot, { recursive: true, force: true });
@@ -234,6 +248,9 @@ export async function createWorkshopBundleFromSource(sourceRoot, targetRoot, opt
   await fs.rm(path.join(targetRoot, "workshop-skill", "SKILL.md"), { force: true });
   await copyBundleFiles(sourceRoot, targetRoot);
   const manifest = await createWorkshopBundleManifestFromSource(sourceRoot);
+  if (options.prune === true) {
+    await pruneBundleFiles(targetRoot, manifest);
+  }
   await writeWorkshopBundleManifest(targetRoot, manifest);
 }
 
@@ -250,7 +267,7 @@ export async function syncPackagedWorkshopBundle() {
 export async function syncRepoBundledWorkshopSkill() {
   const sourceRoot = getRepoWorkshopSourceRoot();
   const bundleRoot = getRepoBundledWorkshopSkillPath();
-  await createWorkshopBundleFromSource(sourceRoot, bundleRoot, { clean: true });
+  await createWorkshopBundleFromSource(sourceRoot, bundleRoot, { prune: true });
   return {
     sourceRoot,
     bundleRoot,