@harness-lab/cli 0.2.3 → 0.2.6

package/README.md

@@ -36,6 +36,11 @@ Participant-facing default install:
 npm install -g @harness-lab/cli
 ```
 
+Supported runtime:
+
+- Node `22` or newer
+- npm `10` or newer recommended
+
 Verify the binary:
 
 ```bash
@@ -116,10 +121,10 @@ Workshop commands:
 harness auth status
 harness skill install
 harness workshop status
-harness workshop create-instance developer-hackathon-praha-24-4-saturn --event-title "Developer Hackathon Praha"
-harness workshop update-instance developer-hackathon-praha-24-4-saturn --room-name Saturn
-harness workshop prepare developer-hackathon-praha-24-4-saturn
-harness workshop remove-instance developer-hackathon-praha-24-4-saturn
+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 phase set rotation
 harness workshop archive --notes "Manual archive"
 harness auth logout

package/assets/workshop-bundle/SKILL.md

@@ -18,7 +18,7 @@ allowed-tools:
 
 # Workshop
 
-Participant-facing skill for the Harness Lab workshop. Command semantics stay in English, but participant-facing delivery should follow the active workshop `contentLang` when live runtime data is available and fall back to the best reviewed bundled locale otherwise.
+Participant-facing skill for the Harness Lab workshop. Command semantics stay in English, but participant-facing delivery should follow the active workshop `contentLang` when live runtime data is available and otherwise resolve to a reviewed fallback locale instead of inheriting the raw language of whichever supporting doc was opened first.
 
 ## Purpose
 
@@ -27,12 +27,26 @@ This skill is the primary workshop interface for participants in Codex or pi. It
 The portable install path should make this skill usable from the participant's real working repo without requiring a clone of the Harness Lab source repo.
 
 Core mental model:
-- dashboard participant surface = orientace během dne
-- dashboard facilitator surface = řízení workshop instance
-- workshop skill = AI interface ke stejnému workshop systému
-- workshop blueprint = veřejná kanonická definice workshop method
-- `uiLang` = jazyk product chrome
-- `contentLang` = jazyk workshopového obsahu pro participant-facing delivery
+- dashboard participant surface = orientation during the day
+- dashboard facilitator surface = control of the workshop instance
+- workshop skill = AI interface to the same workshop system
+- workshop blueprint = public canonical definition of the workshop method
+- `uiLang` = language of product chrome
+- `contentLang` = language of workshop content for participant-facing delivery
+
+## Language Resolution
+
+Command semantics stay in English. Resolve the response language in this order:
+
+1. If live workshop data provides `contentLang` and the command is participant-facing workshop delivery, use that locale.
+2. Otherwise, match the user's current language when it maps to a reviewed locale in the repo or bundle.
+3. If there is no clear live or user-language signal, default bundled fallback delivery to English (`en`).
+
+Additional rules:
+- facilitator-control commands are operational rather than room-facing delivery, so prefer the user's current language unless the facilitator explicitly asks for another reviewed locale or you are quoting workshop content
+- the authored language of a supporting doc does not decide the reply language by itself
+- if the requested locale has no reviewed variant, fall back to English and say so explicitly
+- do not let a Czech-authored fallback file force a Czech answer when the resolved response locale is English
 
 ## Sources Of Truth
 
@@ -56,8 +70,8 @@ Rule:
 - if runtime is unavailable, fall back to repo material and say explicitly that the answer is fallback rather than live state
 - runtime edits do not imply blueprint edits; reusable changes belong back in the repo deliberately
 - prefer workshop `contentLang` for participant-facing responses in live mode
-- if there is no live workshop context, prefer the best reviewed bundled locale and say when the answer is fallback content rather than live workshop state
-- for bundled fallback docs, resolve `workshop-skill/locales/<locale>/...` first; if a reviewed localized doc does not exist yet, fall back to the best reviewed bundled locale and say so explicitly
+- if there is no live workshop context, resolve the fallback locale using the Language Resolution rules above and say when the answer is fallback content rather than live workshop state
+- for bundled fallback docs, resolve `workshop-skill/locales/<locale>/...` first; if a reviewed localized doc does not exist yet, fall back to English and say so explicitly
 - do not translate workshop copy ad hoc when a reviewed locale exists in the repo or bundle
 
 ## Commands
@@ -297,7 +311,8 @@ Relevant local files:
 ## Style
 
 - Be concise and directive.
-- Use Czech for explanations.
+- Use the resolved response language.
+- English is the default bundled fallback locale when no live or user-language signal overrides it.
 - Keep command names, file names, and code terms in English.
 - Prefer actionable next steps over theory during build phases.
 - Treat tests and executable checks as the default trust boundary once the agent is doing meaningful implementation work.

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

@@ -1,8 +1,8 @@
 {
   "manifestVersion": 1,
   "bundleName": "harness-lab-workshop",
-  "bundleVersion": "0.2.3",
-  "contentHash": "9e57d44e4a3f9296f4913cd51eefbf9dff7d6d9da8d4afb1ae5a2ce2a7dc4323",
+  "bundleVersion": "0.2.6",
+  "contentHash": "9e7a3c6549f06cbe59278c731c73ae8c21f7e38cf82cbc533f1e708ccf47602c",
   "files": [
     {
       "path": "content/challenge-cards/.gitkeep",
@@ -134,7 +134,7 @@
     },
     {
       "path": "SKILL.md",
-      "sha256": "b25a7730eb123edd941bcb176bd861ad209868189601c49845d1b6892f689647"
+      "sha256": "107f2ba2574d358ed2ccd1c669a47008574517b811475c866247b0199836ae5b"
     },
     {
       "path": "workshop-blueprint/agenda.json",
@@ -182,7 +182,7 @@
     },
     {
       "path": "workshop-skill/facilitator.md",
-      "sha256": "39dcb46914f19b66fd270627f42702b1f394ceb05dd0f3cf1f0c514becb6dca1"
+      "sha256": "22775cb783e825eeec83886932c801db1ff7e3617c170fee848b6071fa63d8a3"
     },
     {
       "path": "workshop-skill/follow-up-package.md",

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

@@ -1,49 +1,49 @@
 # Facilitator Commands
 
-Příkazy pro facilitátory, kteří řídí workshop instance přes AI agenta.
+Commands for facilitators who manage workshop instances through an AI agent.
 
 ## Auth
 
-Facilitátor se musí nejdřív přihlásit přes `harness` CLI. Skill nemá být další secret store pro raw credentials ani dlouhodobou session.
+The facilitator must log in through the `harness` CLI first. The skill should not become another secret store for raw credentials or long-lived sessions.
 
 ### `/workshop facilitator login`
 
-Pokud není aktivní facilitátorská session, řekni facilitátorovi, aby spustil:
+If no facilitator session is active, tell the facilitator to run:
 
 ```bash
 harness auth login
 ```
 
-CLI provede browser/device auth flow, uloží session do lokálního file storage a zpřístupní ji pro další privileged příkazy.
+The CLI performs the browser/device auth flow, stores the session in local file storage, and exposes it to subsequent privileged commands.
 
 Model:
-- `harness auth login` autentizuje facilitátora vůči platformě
-- konkrétní workshop instance se vybírá až při operaci nebo přes default context
-- instance grant se vyhodnocuje při přístupu ke konkrétní akci, ne při samotném loginu
+- `harness auth login` authenticates the facilitator with the platform
+- the specific workshop instance is selected later per operation or via default context
+- the instance grant is evaluated when accessing a specific action, not during login itself
 
-Aktuální praktický path v repu:
+Current practical paths in this repo:
 
 - default / browser-device auth:
 ```bash
 harness auth login --dashboard-url https://harness-lab-dashboard.vercel.app
 ```
-- file mode / lokální demo fallback:
+- file mode / local demo fallback:
 ```bash
 harness auth login --auth basic --dashboard-url http://localhost:3000 --username facilitator --password secret
 ```
-- neon mode / sdílený dashboard bootstrap fallback:
+- neon mode / shared dashboard bootstrap fallback:
 ```bash
 harness auth login --auth neon --dashboard-url https://harness-lab-dashboard.vercel.app --email facilitator@example.com
 ```
 
-Poznámka:
-- CLI dnes defaultně používá browser/device auth a ukládá session do lokálního file storage
-- Pokud facilitátor chce OS-native storage, může použít `HARNESS_SESSION_STORAGE=keychain`, `credential-manager` nebo `secret-service`
-- `--auth basic` a `--auth neon` zůstávají jen jako explicitní fallback pro lokální dev/bootstrap
+Note:
+- the CLI currently defaults to browser/device auth and stores the session in local file storage
+- 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
 
 ### `/workshop facilitator logout`
 
-Požádej o:
+Ask the facilitator to run:
 
 ```bash
 harness auth logout
@@ -53,23 +53,23 @@ harness auth logout
 
 ### `/workshop facilitator status`
 
-Preferovaný path:
+Preferred path:
 
 ```bash
 harness workshop status
 ```
 
-Zobraz:
-- aktivní instanci a její stav
-- aktuální fázi
-- seznam facilitátorů s rolemi
-- počet týmů
+Show:
+- active instance and its status
+- current phase
+- facilitator list with roles
+- team count
 
 ### `/workshop facilitator grant <email> <role>`
 
-Použij CLI-backed privileged request path. Skill nemá řešit auth bootstrap sám.
+Use the CLI-backed privileged request path. The skill should not handle auth bootstrap itself.
 
-API capability zůstává:
+The API capability remains:
 
 ```http
 POST {DASHBOARD_URL}/api/admin/facilitators
@@ -78,78 +78,79 @@ Content-Type: application/json
 { "email": "...", "role": "operator" }
 ```
 
-Vyžaduje `owner` roli. Vrací info o novém grantu.
+Requires `owner` role. Returns the new grant info.
 
 ### `/workshop facilitator revoke <email>`
 
-Nejdřív zavolej `GET /api/admin/facilitators` a najdi grant podle emailu.
-Pak:
-```
+Call `GET /api/admin/facilitators` first and find the grant by email.
+Then call:
+
+```http
 DELETE {DASHBOARD_URL}/api/admin/facilitators/{grantId}
 ```
 
-Vyžaduje `owner` roli.
+Requires `owner` role.
 
 ### `/workshop facilitator create-instance`
 
-Preferovaný path je CLI příkaz nad sdíleným runtime API:
+The preferred path is a CLI command over the shared runtime API:
 
 ```bash
-harness workshop create-instance developer-hackathon-praha-24-4-saturn \
+harness workshop create-instance sample-workshop-demo-orbit \
   --template-id blueprint-default \
-  --content-lang cs \
-  --event-title "Developer Hackathon Praha" \
-  --city Praha \
-  --date-range "24. dubna 2026" \
-  --venue-name "Seyfor Praha jednička 103" \
-  --room-name Saturn \
-  --address-line "CZ, Praha 8, Sokolovska 695/115b" \
-  --location-details "17 osob + lektor" \
-  --facilitator-label Ondrej
+  --content-lang en \
+  --event-title "Sample Workshop Demo" \
+  --city "Example City" \
+  --date-range "June 15, 2026" \
+  --venue-name "Example Campus North" \
+  --room-name Orbit \
+  --address-line "Example Avenue 123" \
+  --location-details "12 participants + facilitator" \
+  --facilitator-label Alex
 ```
 
-Raw API reference zůstává jen jako diagnostická nebo architektonická reference:
+The raw API reference remains diagnostic or architectural reference only:
 
 ```http
 POST {DASHBOARD_URL}/api/workshop/instances
 Content-Type: application/json
 
 {
-  "id": "developer-hackathon-praha-24-4-saturn",
+  "id": "sample-workshop-demo-orbit",
   "templateId": "blueprint-default",
-  "contentLang": "cs",
-  "eventTitle": "Developer Hackathon Praha",
-  "city": "Praha",
-  "dateRange": "24. dubna 2026",
-  "venueName": "Seyfor Praha jednička 103",
-  "roomName": "Saturn",
-  "addressLine": "CZ, Praha 8, Sokolovska 695/115b",
-  "locationDetails": "17 osob + lektor",
-  "facilitatorLabel": "Ondrej"
+  "contentLang": "en",
+  "eventTitle": "Sample Workshop Demo",
+  "city": "Example City",
+  "dateRange": "June 15, 2026",
+  "venueName": "Example Campus North",
+  "roomName": "Orbit",
+  "addressLine": "Example Avenue 123",
+  "locationDetails": "12 participants + facilitator",
+  "facilitatorLabel": "Alex"
 }
 ```
 
-Poznámky pro skill:
-- skill má preferovat CLI, ne ručně skládané `fetch` skripty
-- `id` musí být lowercase slug s písmeny, čísly a pomlčkami
-- `contentLang` určuje jazyk workshopového obsahu pro dashboard, presenter a skill delivery; není to totéž jako UI language
-- když skill volá create opakovaně se stejným `id`, route vrací `created: false` a existující instance record
-- nehádej venue metadata zkráceně, když je facilitátor zná; pošli je rovnou při create
+Notes for the skill:
+- prefer the CLI, not hand-written `fetch` scripts
+- `id` must be a lowercase slug with letters, numbers, and hyphens
+- `contentLang` controls workshop-content language for dashboard, presenter, and skill delivery; it is not the same as UI language
+- when the skill calls create repeatedly with the same `id`, the route returns `created: false` and the existing instance record
+- do not guess venue metadata in abbreviated form if the facilitator already knows it; send it during create
 
 ### `/workshop facilitator update-instance <instance-id>`
 
-Preferovaný path:
+Preferred path:
 
 ```bash
-harness workshop update-instance developer-hackathon-praha-24-4-saturn \
+harness workshop update-instance sample-workshop-demo-orbit \
   --content-lang en \
-  --event-title "Developer Hackathon Praha" \
-  --date-range "24. dubna 2026" \
-  --venue-name "Seyfor Praha jednička 103" \
-  --room-name Saturn \
-  --address-line "CZ, Praha 8, Sokolovska 695/115b" \
-  --location-details "17 osob + lektor" \
-  --facilitator-label Ondrej
+  --event-title "Sample Workshop Demo" \
+  --date-range "June 15, 2026" \
+  --venue-name "Example Campus North" \
+  --room-name Orbit \
+  --address-line "Example Avenue 123" \
+  --location-details "12 participants + facilitator" \
+  --facilitator-label Alex
 ```
 
 Raw API reference:
@@ -161,27 +162,27 @@ Content-Type: application/json
 {
   "action": "update_metadata",
   "contentLang": "en",
-  "eventTitle": "Developer Hackathon Praha",
-  "dateRange": "24. dubna 2026",
-  "venueName": "Seyfor Praha jednička 103",
-  "roomName": "Saturn",
-  "addressLine": "CZ, Praha 8, Sokolovska 695/115b",
-  "locationDetails": "17 osob + lektor",
-  "facilitatorLabel": "Ondrej"
+  "eventTitle": "Sample Workshop Demo",
+  "dateRange": "June 15, 2026",
+  "venueName": "Example Campus North",
+  "roomName": "Orbit",
+  "addressLine": "Example Avenue 123",
+  "locationDetails": "12 participants + facilitator",
+  "facilitatorLabel": "Alex"
 }
 ```
 
-Pravidla:
-- pošli jen fieldy, které chceš změnit
-- nepoužívej reset pro obyčejnou opravu názvu, venue nebo room
-- když route vrátí `400`, payload je špatně; když vrátí `404`, instance neexistuje
+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
 
 ### `/workshop facilitator prepare`
 
-Preferovaný path:
+Preferred path:
 
 ```bash
-harness workshop prepare developer-hackathon-praha-24-4-saturn
+harness workshop prepare sample-workshop-demo-orbit
 ```
 
 Raw API reference:
@@ -190,17 +191,17 @@ Raw API reference:
 POST {DASHBOARD_URL}/api/workshop
 Content-Type: application/json
 
-{ "action": "prepare", "instanceId": "developer-hackathon-praha-24-4-saturn" }
+{ "action": "prepare", "instanceId": "sample-workshop-demo-orbit" }
 ```
 
-Nastaví instanci do stavu `prepared`, ověří event code.
+This sets the instance to `prepared` state and verifies the event code.
 
 ### `/workshop facilitator remove-instance <instance-id>`
 
-Preferovaný path:
+Preferred path:
 
 ```bash
-harness workshop remove-instance developer-hackathon-praha-24-4-saturn
+harness workshop remove-instance sample-workshop-demo-orbit
 ```
 
 Raw API reference:
@@ -212,13 +213,13 @@ Content-Type: application/json
 { "action": "remove" }
 ```
 
-Pravidla:
-- remove zůstává owner-only operace
-- skill má facilitátora upozornit, že jde o destruktivní odebrání z aktivního seznamu, ne o běžnou editaci metadata
+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
 
 ### `/workshop facilitator agenda`
 
-Lokální editace agendy pro konkrétní instanci používá instanční route:
+Local agenda editing for a specific instance uses the per-instance route:
 
 ```http
 GET {DASHBOARD_URL}/api/workshop/instances/{instanceId}/agenda
@@ -227,7 +228,7 @@ POST {DASHBOARD_URL}/api/workshop/instances/{instanceId}/agenda
 DELETE {DASHBOARD_URL}/api/workshop/instances/{instanceId}/agenda
 ```
 
-Příklady:
+Examples:
 
 ```http
 PATCH {DASHBOARD_URL}/api/workshop/instances/{instanceId}/agenda
@@ -269,28 +270,28 @@ Content-Type: application/json
 }
 ```
 
-Pravidla:
+Rules:
 
-- agenda item je facilitátorský pack, ne jen `title/time/description`
-- preferované fieldy jsou `goal`, `roomSummary`, `facilitatorPrompts`, `watchFors`, `checkpointQuestions`
-- `description` zůstává compatibility field pro starší surface; pro room-facing shrnutí preferuj `roomSummary`
-- používej kanonická agenda ids jako `opening`, `talk`, `demo`, `build-1`, `intermezzo-1`, `rotation`, `build-2`, `intermezzo-2`, `reveal`
-- skill nemá vymýšlet vlastní názvy workshop momentů mimo tuto kostru
+- an agenda item is a facilitator pack, not just `title/time/description`
+- preferred fields are `goal`, `roomSummary`, `facilitatorPrompts`, `watchFors`, and `checkpointQuestions`
+- `description` remains a compatibility field for older surfaces; prefer `roomSummary` for room-facing summaries
+- use canonical agenda ids such as `opening`, `talk`, `demo`, `build-1`, `intermezzo-1`, `rotation`, `build-2`, `intermezzo-2`, and `reveal`
+- the skill should not invent custom workshop moment names outside this skeleton
 
 ### `/workshop facilitator scenes`
 
-Presenter scenes jsou agenda-linked room-facing výstupy pro facilitátora a projektor. Skill má umět:
+Presenter scenes are agenda-linked, room-facing outputs for the facilitator and projector. The skill should be able to:
 
-- vypsat scény pro celou instanci nebo konkrétní agenda item
-- vytvořit novou scénu
-- upravit obsah, label, scene type a CTA
-- změnit default scénu pro danou agenda položku
-- přeuspořádat scény
-- skrýt nebo znovu povolit scénu
-- smazat lokální scénu
-- číst a případně upravit `facilitatorNotes`, `sourceRefs` a `blocks`
+- list scenes for the whole instance or a specific agenda item
+- create a new scene
+- edit content, label, scene type, and CTA
+- change the default scene for a given agenda item
+- reorder scenes
+- hide or re-enable a scene
+- delete a local scene
+- read and optionally edit `facilitatorNotes`, `sourceRefs`, and `blocks`
 
-Instanční route:
+Per-instance route:
 
 ```http
 GET {DASHBOARD_URL}/api/workshop/instances/{instanceId}/scenes
@@ -300,7 +301,7 @@ PATCH {DASHBOARD_URL}/api/workshop/instances/{instanceId}/scenes
 DELETE {DASHBOARD_URL}/api/workshop/instances/{instanceId}/scenes
 ```
 
-Příklady:
+Examples:
 
 ```http
 POST {DASHBOARD_URL}/api/workshop/instances/{instanceId}/scenes
@@ -312,28 +313,28 @@ Content-Type: application/json
   "sceneType": "demo",
   "intent": "walkthrough",
   "chromePreset": "agenda",
-  "title": "Nejdřív bez kontextu, potom s mapou",
+  "title": "Context first, then motion",
   "facilitatorNotes": [
-    "Držte jednu story, ne přehlídku funkcí."
+    "Keep one story rather than a feature parade."
   ],
   "blocks": [
     {
       "id": "hero",
       "type": "hero",
-      "title": "Nejdřív bez kontextu, potom s mapou",
-      "body": "Ukažte rozdíl mezi prompt blobem a krátkou mapou zapsanou v repu."
+      "title": "Context first, then motion",
+      "body": "Show the difference between a prompt blob and a short map stored in the repo."
     },
     {
       "id": "questions",
       "type": "bullet-list",
-      "title": "Pointa",
+      "title": "Point",
       "items": [
-        "Co není v repu, neexistuje.",
-        "Kontext je páka, ne kosmetika."
+        "If it is not in the repo, it does not exist.",
+        "Context is leverage, not cosmetics."
       ]
     }
   ],
-  "ctaLabel": "Potom přepnout na participant walkthrough"
+  "ctaLabel": "Then switch to participant walkthrough"
 }
 ```
 
@@ -345,17 +346,17 @@ Content-Type: application/json
   "action": "update",
   "agendaItemId": "talk",
   "sceneId": "scene-123",
-  "label": "Upravený demo flow",
+  "label": "Updated demo flow",
   "sceneType": "demo",
   "intent": "walkthrough",
   "chromePreset": "agenda",
-  "title": "Jedna story, ne přehlídka funkcí",
+  "title": "One story, not a feature parade",
   "blocks": [
     {
       "id": "hero",
       "type": "hero",
-      "title": "Jedna story, ne přehlídka funkcí",
-      "body": "Neukazujte pět režimů práce. Ukažte jeden čitelný workflow."
+      "title": "One story, not a feature parade",
+      "body": "Do not show five working modes. Show one readable workflow."
     }
   ]
 }
@@ -389,22 +390,23 @@ Content-Type: application/json
 { "agendaItemId": "talk", "sceneId": "scene-123" }
 ```
 
-Když facilitátor chce změnit wording, flow nebo participant walkthrough přes coding agenta, preferuj tuto route místo ručního popisu změn v UI.
+When the facilitator wants to change wording, flow, or participant walkthrough through a coding agent, prefer this route instead of manually describing UI edits.
 
-Při práci přes API:
+During API work:
 
-- neznámé `agendaItemId` nebo `sceneId` vrací `404`
-- malformed payload pořád vrací `400`
-- skill má stale target ids hlásit explicitně, ne pokračovat jako by se změna povedla
-- room-facing obsah patří do `blocks`, facilitátorské pokyny do `facilitatorNotes`
-- `title/body` zůstávají kvůli compatibility, ale skill má preferovat strukturované `blocks`
-- když runtime agenda existuje, skill má číst a citovat její `goal`, `roomSummary`, `facilitatorPrompts`, `watchFors`, `checkpointQuestions`, `facilitatorNotes` a `blocks`
-- když runtime data nejsou dostupná, fallbackni na blueprint a facilitační docs z repa a explicitně to řekni
+- unknown `agendaItemId` or `sceneId` returns `404`
+- malformed payload still returns `400`
+- the skill must report stale target ids explicitly rather than acting as if the change succeeded
+- room-facing content belongs in `blocks`, facilitator instructions in `facilitatorNotes`
+- `title/body` remain for compatibility, but the skill should prefer structured `blocks`
+- when runtime agenda exists, the skill should read and cite its `goal`, `roomSummary`, `facilitatorPrompts`, `watchFors`, `checkpointQuestions`, `facilitatorNotes`, and `blocks`
+- when runtime data is unavailable, fall back to the blueprint and facilitation docs in the repo and say so explicitly
 
 ### `/workshop facilitator archive`
 
-Zavolej:
-```
+Call:
+
+```http
 POST {DASHBOARD_URL}/api/workshop/archive
 Content-Type: application/json
 
@@ -413,14 +415,14 @@ Content-Type: application/json
 
 ## Environment
 
-Agent potřebuje vědět URL dashboardu:
-- `HARNESS_DASHBOARD_URL` — URL produkčního nebo preview dashboardu
-- Pokud není nastaveno, použij `https://harness-lab-dashboard.vercel.app`
+The agent needs to know the dashboard URL:
+- `HARNESS_DASHBOARD_URL` - the production or preview dashboard URL
+- if not set, use `https://harness-lab-dashboard.vercel.app`
 
-## Poznámky
+## Notes
 
-- Facilitátorské příkazy jsou oddělené od participant příkazů
-- `/workshop facilitator login` má facilitátora navést do `harness auth login`
-- Všechny ostatní privileged příkazy používají CLI-backed uloženou session
-- Pokud session expiruje, agent řekne facilitátorovi, aby se znovu přihlásil
-- Tyto příkazy nikdy nezobrazuj participant účastníkům
+- facilitator commands are separate from participant commands
+- `/workshop facilitator login` should steer the facilitator into `harness auth login`
+- all other privileged commands use the stored CLI-backed session
+- if the session expires, tell the facilitator to log in again
+- never surface these commands to participants

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@harness-lab/cli",
-  "version": "0.2.3",
+  "version": "0.2.6",
   "description": "Participant-facing Harness Lab CLI for facilitator auth and workshop operations",
-  "license": "UNLICENSED",
+  "license": "MIT",
   "type": "module",
   "repository": {
     "type": "git",
@@ -20,7 +20,7 @@
     "ai-agents"
   ],
   "engines": {
-    "node": "22.x"
+    "node": ">=22"
   },
   "publishConfig": {
     "access": "public"

package/src/workshop-bundle.js

@@ -63,7 +63,29 @@ export async function pathExists(targetPath) {
 
 async function copyDirectoryTree(sourceRoot, targetRoot) {
   for (const [sourceRelativePath, targetRelativePath] of DIRECTORY_COPIES) {
-    await fs.cp(path.join(sourceRoot, sourceRelativePath), path.join(targetRoot, targetRelativePath), { recursive: true });
+    await copyDirectoryRecursive(
+      path.join(sourceRoot, sourceRelativePath),
+      path.join(targetRoot, targetRelativePath),
+    );
+  }
+}
+
+async function copyDirectoryRecursive(sourcePath, targetPath) {
+  const entries = await fs.readdir(sourcePath, { withFileTypes: true });
+  await fs.mkdir(targetPath, { recursive: true });
+
+  for (const entry of entries) {
+    const sourceEntryPath = path.join(sourcePath, entry.name);
+    const targetEntryPath = path.join(targetPath, entry.name);
+
+    if (entry.isDirectory()) {
+      await copyDirectoryRecursive(sourceEntryPath, targetEntryPath);
+      continue;
+    }
+
+    if (entry.isFile()) {
+      await fs.copyFile(sourceEntryPath, targetEntryPath);
+    }
   }
 }