@rizom/ops 0.2.0-alpha.254 → 0.2.0-alpha.256
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -0
- package/dist/brains-ops.js +211 -194
- package/dist/deploy.js +23 -23
- package/dist/directory-sync-stress-system.d.ts +63 -0
- package/dist/directory-sync-stress.d.ts +105 -0
- package/dist/index.d.ts +2 -0
- package/dist/index.js +216 -199
- package/dist/run-command.d.ts +3 -0
- package/package.json +1 -1
- package/templates/rover-pilot/.github/actions/varlock-env/action.yml +47 -0
- package/templates/rover-pilot/.github/workflows/deploy.yml +9 -52
- package/templates/rover-pilot/.github/workflows/directory-sync-stress.yml +100 -0
- package/templates/rover-pilot/deploy/scripts/install-health-watchdog.ts +133 -0
- package/templates/rover-pilot/docs/operator-playbook.md +15 -0
package/README.md
CHANGED
|
@@ -15,12 +15,24 @@ Operator CLI package for managing pilot brain fleet registry repos.
|
|
|
15
15
|
- `brains-ops secrets:push <repo>`
|
|
16
16
|
- `brains-ops secrets:encrypt <repo> <handle>`
|
|
17
17
|
- `brains-ops verify-user <repo> <handle>` — checks `/health`, unauthenticated `/mcp`, and site-enabled browser/CMS routes
|
|
18
|
+
- `brains-ops stress:directory-sync <repo> <handle> --profile <regression|load|stress> --confirm stress:<handle>` — runs a smoke-only, reversible directory-sync workload and writes structured evidence
|
|
19
|
+
- `brains-ops stress:directory-sync:cleanup <repo> <handle> --confirm stress:<handle>` — idempotently removes residual stress probes
|
|
18
20
|
- `brains-ops reconcile-cohort <repo> <cohort>`
|
|
19
21
|
- `brains-ops reconcile-all <repo>`
|
|
20
22
|
- `brains-ops reconcile-all <repo> --dry-run` — reconciles an isolated copy twice with external content-repository access blocked, lists both passes' changed files, and requires second-pass zero drift
|
|
21
23
|
|
|
22
24
|
`render` owns the observational `views/users.md` projection. Onboard and reconcile commands own generated per-user config and never rewrite live observed status in that view.
|
|
23
25
|
|
|
26
|
+
## Directory-sync stress profiles
|
|
27
|
+
|
|
28
|
+
Directory-sync stress is deliberately smoke-only. The handle, domain, and content repository must each identify smoke, and the operator must pass the exact `stress:<handle>` confirmation. The runner refuses production-like targets.
|
|
29
|
+
|
|
30
|
+
- `regression`: add 20 files, update all 20, then delete them;
|
|
31
|
+
- `load`: ramp through 50, 150, and 350 files, update 350, rename 100, update again, then delete all probes;
|
|
32
|
+
- `stress`: continue the same deterministic ramp to 700 files and 200 renames.
|
|
33
|
+
|
|
34
|
+
Each run creates a rollback branch, gates on health failures during the monitored workload window, preserves warmup and cleanup health samples as evidence without poisoning that gate, samples container CPU/memory/PIDs, waits for Git and entity persistence, and always attempts cleanup. JSON, Markdown, runtime logs, and samples are written under `.brains-ops/stress/` unless `--artifacts-dir` is supplied. The scaffolded `Directory Sync Stress` workflow is manual-only and has a separate `always()` cleanup job. Successful idempotent cleanup also prunes retained stress backup branches; branches remain available when probes remain for recovery. The workflow never deploys or targets a non-smoke user.
|
|
35
|
+
|
|
24
36
|
## Scope
|
|
25
37
|
|
|
26
38
|
`brains-ops` lives in the `brains` monorepo and is consumed as a separate package.
|