Demo CLI
The unified Vultron demo CLI provides a single entry point for all demo
scripts via the vultron-demo command (DC-01-001 through DC-01-005).
Usage
vultron-demo --help
vultron-demo receive-report
vultron-demo trigger
vultron-demo all
vultron-demo vultrabot cvd
A demo that opens a case takes the CaseActor's identity from VULTRON_ACTOR__CASE_ACTOR_SERVICE_URL only.
When the variable is unset, it stops with an error that names the variable.
The demo service in docker/docker-compose.yml sets it to the server's own API base, http://localhost:7999/api/v2.
Module Reference
vultron.demo.cli
Unified Vultron demo CLI (DC-01-001 through DC-01-005).
Each sub-command maps to one demo script in vultron/demo/.
The all sub-command runs every demo in sequence and prints a
pass/fail summary.
The multi-container scenario sub-commands are not declared here at all:
they are generated, one per registered scenario, by
:func:~vultron.demo.cli.scenario_commands._make_scenario_command from the
scenario registry (DEMOCI-11-011, ADR-0098). The registry is the sole declaration
point for which scenarios exist, so this package cannot be a place a
scenario is omitted from or added to independently of it — which it was while it
hand-wired one @main.command block each. Each scenario module supplies the
two things the registry deliberately does not carry: its ROLES list (the
container-URL and actor-id options, whose env bindings key to physical container
slots rather than roles) and its CLI_HELP text.
A vultrabot sub-group provides access to the three standalone
behaviour-tree demos (pacman, robot, cvd).
The seed sub-command bootstraps actor records in the DataLayer on
container startup, supporting multi-actor demo scenarios (D5-1-G2).
main(ctx, debug, log_file)
Vultron demo CLI — run individual demos or all demos in sequence.
run_all(skip_health_check)
Run every demo in sequence and print a pass/fail summary (DC-01-003, DC-01-004).
seed(config_path, actor_name, actor_type, actor_id, api_url)
Bootstrap actor records in the local DataLayer (D5-1-G2).
Creates the local actor and any configured peer actors in the DataLayer
via POST /actors/. Safe to re-run: existing records are returned
unchanged (idempotent).
Configuration is loaded from (in decreasing priority):
1. A YAML config file (--config / VULTRON_SEED_CONFIG).
2. Individual CLI options / environment variables.
vultrabot_cvd(print_tree, verbose, debug)
Run the CVD Vultron behaviour-tree demo.
vultrabot_group()
Standalone behaviour-tree demos (pacman, robot, cvd).
vultrabot_pacman(print_tree, verbose, debug)
Run the Pacman behaviour-tree demo.
vultrabot_robot(print_tree, verbose, debug)
Run the Robot behaviour-tree demo.