.changeset/bootstrap-schema-path.md

@@ -0,0 +1,9 @@
+---
+"@united-workforce/cli": patch
+"@united-workforce/util": patch
+---
+
+fix: workflow-authoring flat schema example uses enum, bootstrap adds PATH guidance
+
+- workflow-authoring: flat schema example uses `enum: [done]` instead of bare `const` (#110.3)
+- bootstrap: adds `which hermes` check and PATH guidance for venv installs (#110.4)

packages/cli/src/commands/prompt.ts

@@ -48,6 +48,11 @@ Install an agent adapter (at least one is required):
 pip install hermes-agent[acp]   # or: pip install -e .[acp] if installed from source
 \`\`\`
 
+Verify \`hermes\` is in your PATH: \`which hermes\`. If Hermes is installed in a virtualenv (e.g. \`~/.hermes/hermes-agent/.venv/\`), activate it or add the bin directory to PATH:
+\`\`\`bash
+export PATH="$HOME/.hermes/hermes-agent/.venv/bin:$PATH"
+\`\`\`
+
 Verify the adapter is installed: \`uwf-hermes --version\` (or whichever you chose).
 
 ### Step 2 — Configure provider and model

packages/util/src/workflow-authoring-reference.ts

@@ -92,16 +92,21 @@ Add any fields you need for data passing between roles. These are available in e
 
 ### Flat Schema (Single Status)
 
-When a role has only one outcome:
+When a role has only one outcome, use \`enum\` with a single value:
 
 \`\`\`yaml
 frontmatter:
+  type: object
   properties:
-    $status: { const: "done" }
+    $status:
+      type: string
+      enum: [done]
     summary: { type: string }
   required: [$status, summary]
 \`\`\`
 
+Note: \`$status: { const: "done" }\` is **not** valid in flat schemas — the validator requires \`enum\` or \`oneOf\` with \`const\`. Use \`const\` only inside \`oneOf\` variants.
+
 ## Graph Routing
 
 The graph maps each role's \`$status\` values to the next role: