lev-os Workflow: Beads Rollout
Trigger
Use when you want to standardize many repos onto one Beads playbook instead of fixing each project manually.
Inputs
- One or more root directories to scan for repos with
.beads/ - Machine role:
primaryfor push-first machinesecondaryfor pull-first machine
Steps
- Upgrade and verify
bdon the machine. - Scan all target roots for repos with
.beads/. - For each repo:
- derive deterministic Dolt database name
- set
database,host, andport - patch config to shared-server mode
- start local Dolt server access
- Sync:
primary->bd dolt pushsecondary->bd dolt pull
- Verify with
bd dolt showandbd ready.
Team
| Role | Responsibility |
|---|---|
| operator | chooses roots and machine role |
| workflow | runs the rollout helper and reports failures |
Outputs
- JSON rollout report per repo
- Deterministic DB name per repo
- Shared-server Beads config stamped into each repo
Validation
bd dolt show --jsonsucceeds for each repobd ready --jsonsucceeds for each repo- config shows shared-server semantics and port
3308
Canonical Command
# audit only
python3 $HOME/.agents/skills/beads-dolt-native/scripts/beads_rollout.py scan --roots $HOME/digital
# primary machine
python3 $HOME/.agents/skills/beads-dolt-native/scripts/beads_rollout.py apply --roots $HOME/digital --sync push
# secondary machine
python3 $HOME/.agents/skills/beads-dolt-native/scripts/beads_rollout.py apply --roots $HOME/digital --sync pull