docs(stage): guardrail comment — zot needs rpc driver before autospawn
The spawner uses stdin(Stdio::null()); zot's --json and rpc modes both require input. Pi's --mode json is autonomous. Document the blocker inline so nobody tries the pi→zot config flip without the driver. Ref: colibri issue zot-rpc-driver + ADR-agent-harness-consolidation.md.
This commit is contained in:
parent
98c1010bc4
commit
eb919a435f
1 changed files with 6 additions and 1 deletions
|
|
@ -157,7 +157,12 @@ BW_SERVER="https://vault.smilepowered.org"
|
|||
#
|
||||
# Behavior toggles (non-secret):
|
||||
# COLIBRI_AUTOSPAWN_PI="YES" # auto-spawn one Pi on daemon startup
|
||||
# COLIBRI_PI_BINARY="pi" # Pi executable name/path
|
||||
# COLIBRI_PI_BINARY="pi" # Pi executable name/path; zot is staged on
|
||||
# # the image but needs the zot-rpc driver
|
||||
# # before it can autospawn (spawner uses
|
||||
# # stdin(Stdio::null()) — zot needs stdin).
|
||||
# # See: ADR-agent-harness-consolidation.md
|
||||
# # + colibri issue zot-rpc-driver.
|
||||
# COLIBRI_AUTOSPAWN_PI_ARGS="--mode json" # Pi argv
|
||||
# COLIBRI_MCP_EXTERNAL_CALL="1" # allow Pi (via colibri-mcp) to call
|
||||
# # external MCP servers; set by
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue