fix: workflow-authoring flat schema, bootstrap PATH guidance
CI / check (pull_request) Successful in 2m18s
CI / check (pull_request) Successful in 2m18s
- #110.3: flat schema example uses enum: [done] instead of bare const (bare const fails validate-semantic hasStatusEnum check) - #110.4: bootstrap adds 'which hermes' PATH check and venv guidance - #110.1: already fixed in rc.1 (inline hello.yaml) - #110.2: already fixed in rc.1 (capabilities: [] present) Fixes #110
This commit is contained in:
@@ -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)
|
||||||
@@ -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
|
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).
|
Verify the adapter is installed: \`uwf-hermes --version\` (or whichever you chose).
|
||||||
|
|
||||||
### Step 2 — Configure provider and model
|
### Step 2 — Configure provider and model
|
||||||
|
|||||||
@@ -92,16 +92,21 @@ Add any fields you need for data passing between roles. These are available in e
|
|||||||
|
|
||||||
### Flat Schema (Single Status)
|
### 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
|
\`\`\`yaml
|
||||||
frontmatter:
|
frontmatter:
|
||||||
|
type: object
|
||||||
properties:
|
properties:
|
||||||
$status: { const: "done" }
|
$status:
|
||||||
|
type: string
|
||||||
|
enum: [done]
|
||||||
summary: { type: string }
|
summary: { type: string }
|
||||||
required: [$status, summary]
|
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
|
## Graph Routing
|
||||||
|
|
||||||
The graph maps each role's \`$status\` values to the next role:
|
The graph maps each role's \`$status\` values to the next role:
|
||||||
|
|||||||
Reference in New Issue
Block a user