fix: address challenge harness review findings
This commit is contained in:
@@ -8,8 +8,8 @@ unrunnable, or surprising.
|
||||
Check in this order:
|
||||
|
||||
1. `wf status`
|
||||
2. `wf cap inspect <capability>`
|
||||
3. `wf cap list --format ids`
|
||||
2. `wf cap list --format ids`
|
||||
3. `wf cap inspect <capability>`
|
||||
|
||||
Remember: MCP control tools are not workflow capabilities. They appear in
|
||||
MCP `tools/list`, not `wf cap list`.
|
||||
|
||||
@@ -24,6 +24,7 @@ validated, runnable deployment.
|
||||
`wf artifact create-from-plan workflow.plan.json --artifact <artifact_id> --version 1 --title "Workflow Title" --outcome ok`
|
||||
7. Save and validate a deployment.
|
||||
- `wf deploy save <deployment_id> --artifact <artifact_id> --version 1 --binding <logical_source>=<concrete_source>` (or `wf deploy create` alias)
|
||||
- `wf deploy validate <deployment_id>`
|
||||
8. Run the deployment.
|
||||
9. Inspect the run summary first; read bounded traces only when needed.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user