buildai-cli 0.3.86__tar.gz → 0.3.87__tar.gz

{buildai_cli-0.3.86 → buildai_cli-0.3.87}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: buildai-cli
-Version: 0.3.86
+Version: 0.3.87
 Summary: Build AI CLI (Typer)
 Requires-Python: >=3.11
 Requires-Dist: httpx>=0.27.0

{buildai_cli-0.3.86 → buildai_cli-0.3.87}/cli/commands/ingest_docs.py

@@ -55,12 +55,13 @@ All operator workflows go through the BuildAI CLI from a monorepo checkout:
   uv run buildai ingest <group> <command> [options]
 
 Command groups:
-  deploy   — artifact build, staged rollout, status, resume, rollback
+  deploy   — artifact build, role-parallel rollout, status, resume, rollback
   fleet    — preflight, auth, readiness (read-only gates)
   host     — bootstrap and repair (host toolchain, not app code)
   docs     — this guide
 
 Canonical runbook (more detail): apps/buildai-ingest/docs/deploy.md
+Remote operations guide: apps/buildai-ingest/docs/remote-operations.md
 Semantic contract: apps/buildai-ingest/docs/deploy-contract.md
 Topology source of truth: apps/buildai-ingest/fleet/inventory.json
 """,
@@ -157,16 +158,20 @@ STANDARD DEPLOY WORKFLOW
 4. Plan (dry run — targets, rollout order, git warnings)
      uv run buildai ingest deploy plan --scope active
 
-5. Deploy (build artifact + staged rollout)
+5. Deploy (build artifact + role-parallel rollout)
      uv run buildai ingest deploy run --scope active --reason "describe change"
 
 6. Verify
      uv run buildai ingest deploy status
 
 Rollout order for multi-target scopes:
-  • Canary: ingest-mini-1 first
-  • Then station batches (minis per station, then servers, aggregator)
-  • Convergence audit at the end when in rollout plan
+  • Selected minis in parallel
+  • Then selected upload servers in parallel
+  • Then aggregator
+  • Convergence audit at the end
+
+Use --strategy staged only when deliberately requesting the slower
+canary/station rollout.
 
 Partial failure:
   uv run buildai ingest deploy status
@@ -193,7 +198,7 @@ Comma lists: station:1,station:2
 Notes:
   • ingest-mini-11 is maintenance by default — target explicitly if needed
   • Targeted deploys do not satisfy full-fleet convergence alone; follow with active scope
-  • First production cutover to release layout: prefer --scope mini:1 as canary
+  • Use --strategy staged for deliberate canary/station serialization
 """,
     "host-layout": """
 ON-HOST RELEASE LAYOUT
@@ -224,7 +229,7 @@ COMMAND REFERENCE
 =================
 
 deploy plan     Dry plan: targets, rollout order, git warnings
-deploy run      Build artifact + execute staged rollout
+deploy run      Build artifact + execute role-parallel rollout by default
 deploy status   Latest or specific run state (ledger under ~/.buildai/ingest-deploy-runs/)
 deploy resume   Continue a non-terminal run from saved artifact
 deploy rollback Flip current to previous release (re-stage only if pruned)

{buildai_cli-0.3.86 → buildai_cli-0.3.87}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "buildai-cli"
-version = "0.3.86"
+version = "0.3.87"
 description = "Build AI CLI (Typer)"
 requires-python = ">=3.11"
 dependencies = [