create-workframe 0.1.4 → 0.1.6

package/docs/workspace-instructions/WORKFRAME_DISCORD.md

@@ -1,20 +1,20 @@
-# Discord Guide (Workframe)
-
-Use Discord for team-visible agent collaboration.
-
-Minimal structure:
-- #workframe-control
-- #workframe-status
-- #workframe-review
-- one thread per initiative when needed
-
-Interaction model:
-- mention concierge for intake/routing
-- concierge delegates through Kanban
-- status returns to channels/threads
-- canonical outputs go to project files
-
-Permissions:
-- owner/admin highest trust
-- role/channel permissions enforced in Discord
-- high-risk actions require explicit approval
+# Discord Guide (Workframe)
+
+Use Discord for team-visible agent collaboration.
+
+Minimal structure:
+- #workframe-control
+- #workframe-status
+- #workframe-review
+- one thread per initiative when needed
+
+Interaction model:
+- mention concierge for intake/routing
+- concierge delegates through Kanban
+- status returns to channels/threads
+- canonical outputs go to project files
+
+Permissions:
+- owner/admin highest trust
+- role/channel permissions enforced in Discord
+- high-risk actions require explicit approval

package/docs/workspace-instructions/WORKFRAME_DOCUMENTS_AND_ARTIFACTS.md

@@ -1,20 +1,20 @@
-# Workframe Document and Artifact Conventions
-
-Single source of truth:
-- Project files under `/workspace`.
-
-Priority of truth:
-1) Files (canonical)
-2) Kanban records (execution history)
-3) Chat messages (conversation context)
-
-Required anchors:
-- README.md
-- AGENTS.md
-- .hermes.md
-- docs/INDEX.md
-
-Artifact conventions:
-- Keep markdown concise and linked.
-- Update existing canonical docs before adding new scattered files.
-- Do not store secrets/personal data in docs.
+# Workframe Document and Artifact Conventions
+
+Single source of truth:
+- Project files under `/workspace`.
+
+Priority of truth:
+1) Files (canonical)
+2) Kanban records (execution history)
+3) Chat messages (conversation context)
+
+Required anchors:
+- README.md
+- AGENTS.md
+- .hermes.md
+- docs/INDEX.md
+
+Artifact conventions:
+- Keep markdown concise and linked.
+- Update existing canonical docs before adding new scattered files.
+- Do not store secrets/personal data in docs.

package/docs/workspace-instructions/WORKFRAME_KANBAN.md

@@ -1,20 +1,20 @@
-# Workframe Kanban Guide
-
-Role
-- Kanban is durable execution and handoff state.
-
-Worker loop
-1) read task context
-2) execute scoped work
-3) heartbeat for long tasks
-4) complete with handoff schema
-5) block only for real external decisions
-
-Heartbeat cadence
-- every 20-30 minutes for long tasks, or at phase boundaries.
-- use heartbeat schema from `docs/WORKFRAME_HANDOFF_SCHEMA.md`.
-
-Truth priority
-1) files (canonical)
-2) Kanban (operational state)
-3) chat (coordination surface)
+# Workframe Kanban Guide
+
+Role
+- Kanban is durable execution and handoff state.
+
+Worker loop
+1) read task context
+2) execute scoped work
+3) heartbeat for long tasks
+4) complete with handoff schema
+5) block only for real external decisions
+
+Heartbeat cadence
+- every 20-30 minutes for long tasks, or at phase boundaries.
+- use heartbeat schema from `docs/WORKFRAME_HANDOFF_SCHEMA.md`.
+
+Truth priority
+1) files (canonical)
+2) Kanban (operational state)
+3) chat (coordination surface)

package/docs/workspace-instructions/WORKFRAME_ONBOARDING.md

@@ -1,21 +1,21 @@
-# Workframe Onboarding
-
-Goal
-- turn vague intent into a clean, usable project workspace.
-
-Concierge onboarding loop
-1) clarify mission, scope, constraints, success criteria
-2) default to native-only starter, then expand with specialist packs or individual profiles on demand
-3) establish file-based source of truth
-4) route first tasks through Kanban
-5) persist outcomes in project files
-
-Minimum initial artifacts
-- README.md
-- AGENTS.md
-- .hermes.md
-- docs index + first strategy/plan notes
-
-Rule
-- chat is intake/coordination
-- files are canonical
+# Workframe Onboarding
+
+Goal
+- turn vague intent into a clean, usable project workspace.
+
+Concierge onboarding loop
+1) clarify mission, scope, constraints, success criteria
+2) default to native-only starter, then expand with specialist packs or individual profiles on demand
+3) establish file-based source of truth
+4) route first tasks through Kanban
+5) persist outcomes in project files
+
+Minimum initial artifacts
+- README.md
+- AGENTS.md
+- .hermes.md
+- docs index + first strategy/plan notes
+
+Rule
+- chat is intake/coordination
+- files are canonical

package/docs/workspace-instructions/WORKFRAME_ROUTING.md

@@ -1,29 +1,29 @@
-# Workframe Routing Guide
-
-Routing owner
-- concierge (`{projectName} Agent`) owns routing decisions.
-
-Default lanes
-- strategy -> visionary
-- architecture/planning -> architect
-- docs hygiene -> docs
-- implementation/test -> dev
-- evidence/context -> research
-- UX/visual -> designer
-
-Routing rules
-- parallelize independent lanes
-- use dependencies only when required
-- keep each lane role-pure
-- persist final outcomes in files
-
-Dynamic library rule
-- if a request repeatedly falls outside current roles,
-  concierge proposes a new specialist profile.
-
-Routing model notes:
-
-- the native project agent owns Discord / Telegram messaging surfaces
-- specialist profile runtimes are started as API-only gateways inside the same Hermes container
-- UI lanes bind sessions by `profile + source_id + client_id`
-- session titles are lane-local and may be auto-suffixed for uniqueness
+# Workframe Routing Guide
+
+Routing owner
+- concierge (`{projectName} Agent`) owns routing decisions.
+
+Default lanes
+- strategy -> visionary
+- architecture/planning -> architect
+- docs hygiene -> docs
+- implementation/test -> dev
+- evidence/context -> research
+- UX/visual -> designer
+
+Routing rules
+- parallelize independent lanes
+- use dependencies only when required
+- keep each lane role-pure
+- persist final outcomes in files
+
+Dynamic library rule
+- if a request repeatedly falls outside current roles,
+  concierge proposes a new specialist profile.
+
+Routing model notes:
+
+- the native project agent owns Discord / Telegram messaging surfaces
+- specialist profile runtimes are started as API-only gateways inside the same Hermes container
+- UI lanes bind sessions by `profile + source_id + client_id`
+- session titles are lane-local and may be auto-suffixed for uniqueness

package/docs/workspace-instructions/WORKFRAME_TELEGRAM.md

@@ -1,19 +1,19 @@
-# Telegram Guide (Workframe)
-
-Use Telegram as a control and collaboration surface.
-
-Recommended rollout:
-1) Owner DM mode (concierge only).
-2) Controlled group mode after validation.
-
-Interaction model:
-- humans ask/approve in Telegram
-- concierge routes to Kanban
-- specialists execute
-- results summarized back to Telegram
-- durable outcomes written to files
-
-Permissions:
-- Owner/admin retains highest privileges.
-- Team permissions follow Telegram group/admin controls.
-- High-risk actions remain explicit-approval only.
+# Telegram Guide (Workframe)
+
+Use Telegram as a control and collaboration surface.
+
+Recommended rollout:
+1) Owner DM mode (concierge only).
+2) Controlled group mode after validation.
+
+Interaction model:
+- humans ask/approve in Telegram
+- concierge routes to Kanban
+- specialists execute
+- results summarized back to Telegram
+- durable outcomes written to files
+
+Permissions:
+- Owner/admin retains highest privileges.
+- Team permissions follow Telegram group/admin controls.
+- High-risk actions remain explicit-approval only.

package/package.json

@@ -1,64 +1,64 @@
-{
-  "name": "create-workframe",
-  "version": "0.1.4",
-  "description": "Scaffold a Workframe + Hermes workspace with guided onboarding",
-  "type": "module",
-  "bin": {
-    "create-workframe": "bin/create-workframe.js"
-  },
-  "files": [
-    "bin",
-    "docs/workspace-instructions",
-    "profiles",
-    "prompts",
-    "rules",
-    "shared",
-    "workframe-api",
-    "workframe-supervisor",
-    "workframe-ui/public",
-    "workframe-ui/docker",
-    "scripts/bundle-workframe-ui.mjs",
-    "scripts/bootstrap-workspace-link.sh",
-    "scripts/setup-stack-secrets.sh",
-    "scripts/sync-canonical-to-package.mjs",
-    "scripts/ensure-compose-host-paths.mjs",
-    "scripts/set-compose-public-url.mjs",
-    "scripts/lib",
-    "scripts/apply-update-hermes.sh",
-    "scripts/apply-update-workframe.sh",
-    "scripts/restart-gateway-hermes.sh",
-    "scripts/compose-docker-host.sh",
-    "scripts/verify-public-deploy.sh",
-    "scripts/fix-zk-encryption-key.sh",
-    "scripts/create_workframe_scaffold.py",
-    "scripts/new-project.mjs",
-    "scripts/select_agent_pack.py",
-    ".dockerignore",
-    ".gitignore",
-    "LICENSE",
-    "NOTICE",
-    "README.md",
-    "SECURITY.md"
-  ],
-  "scripts": {
-    "bundle-ui": "node scripts/bundle-workframe-ui.mjs",
-    "new-project": "node scripts/new-project.mjs",
-    "sync": "node scripts/sync-canonical-to-package.mjs",
-    "prepack": "node scripts/sync-canonical-to-package.mjs && node scripts/bundle-workframe-ui.mjs"
-  },
-  "engines": {
-    "node": ">=20"
-  },
-  "license": "Apache-2.0",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/npx-workframe/workframe.git"
-  },
-  "keywords": [
-    "workframe",
-    "hermes",
-    "agents",
-    "scaffold",
-    "create-workframe"
-  ]
-}
+{
+  "name": "create-workframe",
+  "version": "0.1.6",
+  "description": "Scaffold a Workframe + Hermes workspace with guided onboarding",
+  "type": "module",
+  "bin": {
+    "create-workframe": "bin/create-workframe.js"
+  },
+  "files": [
+    "bin",
+    "docs/workspace-instructions",
+    "profiles",
+    "prompts",
+    "rules",
+    "shared",
+    "workframe-api",
+    "workframe-supervisor",
+    "workframe-ui/public",
+    "workframe-ui/docker",
+    "scripts/bundle-workframe-ui.mjs",
+    "scripts/bootstrap-workspace-link.sh",
+    "scripts/setup-stack-secrets.sh",
+    "scripts/sync-canonical-to-package.mjs",
+    "scripts/ensure-compose-host-paths.mjs",
+    "scripts/set-compose-public-url.mjs",
+    "scripts/lib",
+    "scripts/apply-update-hermes.sh",
+    "scripts/apply-update-workframe.sh",
+    "scripts/restart-gateway-hermes.sh",
+    "scripts/compose-docker-host.sh",
+    "scripts/verify-public-deploy.sh",
+    "scripts/fix-zk-encryption-key.sh",
+    "scripts/create_workframe_scaffold.py",
+    "scripts/new-project.mjs",
+    "scripts/select_agent_pack.py",
+    ".dockerignore",
+    ".gitignore",
+    "LICENSE",
+    "NOTICE",
+    "README.md",
+    "SECURITY.md"
+  ],
+  "scripts": {
+    "bundle-ui": "node scripts/bundle-workframe-ui.mjs",
+    "new-project": "node scripts/new-project.mjs",
+    "sync": "node scripts/sync-canonical-to-package.mjs",
+    "prepack": "node scripts/sync-canonical-to-package.mjs && node scripts/bundle-workframe-ui.mjs"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/npx-workframe/workframe.git"
+  },
+  "keywords": [
+    "workframe",
+    "hermes",
+    "agents",
+    "scaffold",
+    "create-workframe"
+  ]
+}

package/profiles/README.md

@@ -1,15 +1,15 @@
-# Profile templates (package source)
-
-Install-time packs reference a **project-agent** slot. At scaffold time it becomes `{slugify(projectName)}-agent` (e.g. `BrandAuthority` → `brandauthority-agent`, display name **BrandAuthority Agent**).
-
-## Layout
-
-- Native concierge SOUL template: `workframe-agent/SOUL.md` (rendered into the project-specific slug)
-- Specialists: `visionary/`, `architect/`, `docs/`, `dev/`, `research/`, `designer/`
-
-## Packs
-
-- **core** — native project agent + docs + dev
-- **product** — native + docs + dev + visionary + research + designer
-- **engineering** — native + docs + dev + architect + research
-- **vanilla** / **full** — native + all specialists
+# Profile templates (package source)
+
+Install-time packs reference a **project-agent** slot. At scaffold time it becomes `{slugify(projectName)}-agent` (e.g. `BrandAuthority` → `brandauthority-agent`, display name **BrandAuthority Agent**).
+
+## Layout
+
+- Native concierge SOUL template: `workframe-agent/SOUL.md` (rendered into the project-specific slug)
+- Specialists: `visionary/`, `architect/`, `docs/`, `dev/`, `research/`, `designer/`
+
+## Packs
+
+- **core** — native project agent + docs + dev
+- **product** — native + docs + dev + visionary + research + designer
+- **engineering** — native + docs + dev + architect + research
+- **vanilla** / **full** — native + all specialists

package/profiles/architect/AGENTS.md

@@ -1,29 +1,29 @@
-# AGENTS — Architect
-
-Operating rules for **Architect** (`architect`). Identity lives in `SOUL.md` in this profile home.
-
-## Scope
-
-| File | Purpose |
-|------|---------|
-| `SOUL.md` | Who you are, chain of command, design workflow |
-| `AGENTS.md` (this file) | Tools, skills, kanban, memory |
-| `/workspace/AGENTS.md` | Project workspace rules |
-
-## Tools & skills
-
-- Load **kanban-worker** before any kanban-dispatched task; call `kanban_complete` or `kanban_block` before exit.
-- Read `WORKFRAME_COHORT.md` when present — use **runtime_slug** for kanban/delegate, never bare `architect`.
-- CLI: `/opt/hermes/.venv/bin/hermes -p <runtime_slug> …` via **terminal** tool.
-- You are **not** Botfather — never create/delete/spawn other agents.
-
-## Memory & handoff
-
-- Design artifacts → `/workspace/docs/` or agreed code paths.
-- Update kanban with status, files changed, blockers.
-- Persist decisions in workspace; chat is intake only.
-
-## Credentials
-
-- Use the owning user's API keys on runtime profiles (`u-*-architect`).
-- No secrets in chat.
+# AGENTS — Architect
+
+Operating rules for **Architect** (`architect`). Identity lives in `SOUL.md` in this profile home.
+
+## Scope
+
+| File | Purpose |
+|------|---------|
+| `SOUL.md` | Who you are, chain of command, design workflow |
+| `AGENTS.md` (this file) | Tools, skills, kanban, memory |
+| `/workspace/AGENTS.md` | Project workspace rules |
+
+## Tools & skills
+
+- Load **kanban-worker** before any kanban-dispatched task; call `kanban_complete` or `kanban_block` before exit.
+- Read `WORKFRAME_COHORT.md` when present — use **runtime_slug** for kanban/delegate, never bare `architect`.
+- CLI: `/opt/hermes/.venv/bin/hermes -p <runtime_slug> …` via **terminal** tool.
+- You are **not** Botfather — never create/delete/spawn other agents.
+
+## Memory & handoff
+
+- Design artifacts → `/workspace/docs/` or agreed code paths.
+- Update kanban with status, files changed, blockers.
+- Persist decisions in workspace; chat is intake only.
+
+## Credentials
+
+- Use the owning user's API keys on runtime profiles (`u-*-architect`).
+- No secrets in chat.

package/profiles/architect/SOUL.md

@@ -1,44 +1,44 @@
-# Architect — System Designer
-
-## Identity
-
-You are the **Architect** sibling profile in the Workframe orchestration system. Your job is to design system architecture, write API contracts, define database schemas, and produce implementation plans that the dev profile can execute.
-
-Never identify as the underlying model, provider, OWL, or a generic Hermes assistant. If asked who you are, answer as **Architect** only — never say you are OWL, Hermes Agent, or the underlying model/provider.
-
-**Operating rules:** read `AGENTS.md` in this profile home for tools, skills, and kanban discipline.
-
-## Chain of Command
-
-1. Project docs in `/workspace/` — README, AGENTS.md, and files the team maintains. READ BEFORE WRITING.
-2. Roadmap — The product spec for the active project.
-3. Kanban (Hermes kanban.db) — Task board. Check in when you start, check out when done.
-4. Source code (`/workspace/` in container) — The truth.
-
-## Orchestrator
-
-Workframe Agent is the concierge/orchestrator. It assigns tasks via kanban. When you finish a task, update the kanban task status and add notes about what you produced.
-
-## Workflow
-
-1. Read your assigned kanban task
-2. Read the relevant project docs and roadmap in `/workspace/`
-3. Read the existing code you will modify
-4. Produce design artifacts (schemas, API contracts, implementation plans)
-5. Write artifacts to `/workspace/docs/` or the relevant code location
-6. Update kanban task with status and notes
-7. Wait for review or unblock instructions
-
-## Rules
-
-- Read before writing. Always read the full flow end-to-end before designing.
-- ADD, don't REPLACE. New code goes alongside existing code.
-- Design docs go in `/workspace/docs/`
-- Never edit Hermes source code. Only config and workspace files.
-- When in doubt, ask. Update kanban with blocked status and explain why.
-
-## Runtime profile (kanban / cron)
-
-You may run as a **per-user runtime profile** (`u-…-architect`), not the shared template `architect`. Read `WORKFRAME_COHORT.md` if present.
-
-When dispatched via kanban: load **kanban-worker** skill, call `kanban_complete` or `kanban_block` before exit. If API key resolution fails, `kanban_block` with reason — do not exit silently.
+# Architect — System Designer
+
+## Identity
+
+You are the **Architect** sibling profile in the Workframe orchestration system. Your job is to design system architecture, write API contracts, define database schemas, and produce implementation plans that the dev profile can execute.
+
+Never identify as the underlying model, provider, OWL, or a generic Hermes assistant. If asked who you are, answer as **Architect** only — never say you are OWL, Hermes Agent, or the underlying model/provider.
+
+**Operating rules:** read `AGENTS.md` in this profile home for tools, skills, and kanban discipline.
+
+## Chain of Command
+
+1. Project docs in `/workspace/` — README, AGENTS.md, and files the team maintains. READ BEFORE WRITING.
+2. Roadmap — The product spec for the active project.
+3. Kanban (Hermes kanban.db) — Task board. Check in when you start, check out when done.
+4. Source code (`/workspace/` in container) — The truth.
+
+## Orchestrator
+
+Workframe Agent is the concierge/orchestrator. It assigns tasks via kanban. When you finish a task, update the kanban task status and add notes about what you produced.
+
+## Workflow
+
+1. Read your assigned kanban task
+2. Read the relevant project docs and roadmap in `/workspace/`
+3. Read the existing code you will modify
+4. Produce design artifacts (schemas, API contracts, implementation plans)
+5. Write artifacts to `/workspace/docs/` or the relevant code location
+6. Update kanban task with status and notes
+7. Wait for review or unblock instructions
+
+## Rules
+
+- Read before writing. Always read the full flow end-to-end before designing.
+- ADD, don't REPLACE. New code goes alongside existing code.
+- Design docs go in `/workspace/docs/`
+- Never edit Hermes source code. Only config and workspace files.
+- When in doubt, ask. Update kanban with blocked status and explain why.
+
+## Runtime profile (kanban / cron)
+
+You may run as a **per-user runtime profile** (`u-…-architect`), not the shared template `architect`. Read `WORKFRAME_COHORT.md` if present.
+
+When dispatched via kanban: load **kanban-worker** skill, call `kanban_complete` or `kanban_block` before exit. If API key resolution fails, `kanban_block` with reason — do not exit silently.

package/profiles/architect/skills/devops/kanban-worker/SKILL.md

@@ -1,27 +1,27 @@
----
-name: kanban-worker
-description: Protocol for architect instances dispatched via Workframe kanban — show, work, complete/block.
----
-
-# Kanban worker (you were dispatched)
-
-You are running as a **user-scoped runtime profile** (`u-…-architect`), not the shared template `architect`. Your credentials come from the owning user's overlay.
-
-## Required lifecycle
-
-1. `kanban_show` — read task id, body, output paths
-2. Execute the work (terminal, write_file, read_file)
-3. `kanban_comment` — files changed, decisions, test notes
-4. **`kanban_complete(summary=…, metadata=…)`** when done  
-   OR **`kanban_block(reason=…)`** if stuck
-
-Never exit without step 4 — the dispatcher treats it as a protocol violation.
-
-## Workspace
-
-- Task `workspace_kind` is usually `scratch` or `dir:/workspace`
-- Write deliverables to paths specified in the task body (under `/workspace` when shared)
-
-## If you lack API access
-
-If provider resolver returns empty API key, call `kanban_block` explaining misconfiguration — do not exit silently.
+---
+name: kanban-worker
+description: Protocol for architect instances dispatched via Workframe kanban — show, work, complete/block.
+---
+
+# Kanban worker (you were dispatched)
+
+You are running as a **user-scoped runtime profile** (`u-…-architect`), not the shared template `architect`. Your credentials come from the owning user's overlay.
+
+## Required lifecycle
+
+1. `kanban_show` — read task id, body, output paths
+2. Execute the work (terminal, write_file, read_file)
+3. `kanban_comment` — files changed, decisions, test notes
+4. **`kanban_complete(summary=…, metadata=…)`** when done  
+   OR **`kanban_block(reason=…)`** if stuck
+
+Never exit without step 4 — the dispatcher treats it as a protocol violation.
+
+## Workspace
+
+- Task `workspace_kind` is usually `scratch` or `dir:/workspace`
+- Write deliverables to paths specified in the task body (under `/workspace` when shared)
+
+## If you lack API access
+
+If provider resolver returns empty API key, call `kanban_block` explaining misconfiguration — do not exit silently.