@rizom/ops 0.2.0-alpha.260 → 0.2.0-alpha.262

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rizom/ops",
-  "version": "0.2.0-alpha.260",
+  "version": "0.2.0-alpha.262",
   "description": "Operator CLI for managing private brain fleet registry repos",
   "keywords": [
     "brains",

package/templates/rover-pilot/.github/workflows/deploy.yml

@@ -235,7 +235,7 @@ jobs:
           WWW_DOMAIN: ${{ steps.user_config.outputs.www_domain }}
           PREVIEW_DOMAIN: ${{ steps.user_config.outputs.preview_domain }}
         run: |
-          curl -I -k --max-time 20 --resolve "$BRAIN_DOMAIN:443:$SERVER_IP" "https://$BRAIN_DOMAIN/health"
+          curl -I -k --max-time 20 --resolve "$BRAIN_DOMAIN:443:$SERVER_IP" "https://$BRAIN_DOMAIN/health/live"
           if [ -n "$WWW_DOMAIN" ]; then
             curl -I -k --max-time 20 --resolve "$WWW_DOMAIN:443:$SERVER_IP" "https://$WWW_DOMAIN/"
           fi

package/templates/rover-pilot/README.md

@@ -37,7 +37,7 @@ When a push changes only deploy contract files, CI prints `No affected user conf
 ## Commands
 
 - `brains-ops init <repo>`
-- `brains-ops render <repo>` — regenerates `views/users.md` with live DNS, `/health`, and unauthenticated `/mcp` status checks
+- `brains-ops render <repo>` — regenerates `views/users.md` with live DNS, `/health/ready`, and unauthenticated `/mcp` status checks
 - `brains-ops user:add <repo> <handle> --cohort <cohort>` — scaffolds a user file, per-user secrets template, and cohort membership
 - `brains-ops onboard <repo> <handle>` — creates/seeds the user's content repo with separate admin and sync tokens
 - `brains-ops age-key:bootstrap <repo>`

package/templates/rover-pilot/docs/onboarding-checklist.md

@@ -24,7 +24,7 @@
 11. Commit and push `users/<handle>.secrets.yaml.age`.
 12. Run `bunx brains-ops onboard <repo> <handle>`.
 13. Verify the deployed canonical contract:
-    - `https://<handle>.rizom.ai/health` returns `200`
+    - `https://<handle>.rizom.ai/health/operate` returns `200`
     - `https://<handle>.rizom.ai/chat` loads the web chat and accepts passkey sign-in
     - unauthenticated `POST https://<handle>.rizom.ai/mcp` returns the expected auth failure
     - content repo exists and runtime sync is healthy

package/templates/rover-pilot/docs/operator-playbook.md

@@ -51,7 +51,7 @@ Before the window, record and review:
 - the exact unified `@rizom/brain` and `@rizom/ops` versions;
 - every unified image tag and immutable digest;
 - canary-first rollout order, followed by the remaining cohorts;
-- expected `/health` version, unauthenticated MCP response, site marker, and content repository identity for each posture.
+- expected `/health/operate` version, unauthenticated MCP response, site marker, and content repository identity for each posture.
 
 Run `bunx brains-ops reconcile-all <canonical-review-copy> --dry-run` against the isolated review copy. The command blocks external content-repository access, leaves the review copy untouched, lists both passes' changed files, and must report second-pass zero drift. Reconciliation owns generated per-user config; only `render` owns the observational `views/users.md` projection.
 
@@ -65,7 +65,7 @@ During the approved window:
 6. Enable Deploy and deploy one handle at a time in the approved order. After each deploy, run `bunx brains-ops verify-user . <handle>`, render observed fleet status, and complete the manual identity, content-sync, and app-managed site checks.
 7. Run Reconcile a second time. Require no reconciler-owned generated diff and no deploy work before re-enabling normal automation and lifting the merge/release freeze. Observed status rendering remains separate from this convergence gate.
 
-If any gate fails, disable all three workflows again. Restore the prior pilot desired-state and dependency revision, reconcile with the prior ops version, and redeploy the prior image tag/digest as one rollback pair. Verify the prior `/health` version and identity/content/site checks before re-enabling automation. Never restore only config or only an image.
+If any gate fails, disable all three workflows again. Restore the prior pilot desired-state and dependency revision, reconcile with the prior ops version, and redeploy the prior image tag/digest as one rollback pair. Verify the prior `/health/operate` version and identity/content/site checks before re-enabling automation. Never restore only config or only an image.
 
 ## Directory-sync stress gate
 
@@ -130,7 +130,7 @@ bunx brains-ops verify-user . <handle>
 
 For every bundle posture it checks:
 
-- `https://<handle>.rizom.ai/health` returns `200`;
+- `https://<handle>.rizom.ai/health/operate` returns `200`;
 - unauthenticated `POST https://<handle>.rizom.ai/mcp` returns the expected auth failure;
 - background jobs are not repeatedly failing, except for missing optional integrations.