@rizom/ops 0.2.0-alpha.271 → 0.2.0-alpha.272

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.
Files changed (4) hide show
  1. package/dist/brains-ops.js +1 -1
  2. package/dist/index.js +179 -179
  3. package/package.json +1 -1
  4. package/templates/rover-pilot/docs/operator-playbook.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rizom/ops",
3
- "version": "0.2.0-alpha.271",
3
+ "version": "0.2.0-alpha.272",
4
4
  "description": "Operator CLI for managing private brain fleet registry repos",
5
5
  "keywords": [
6
6
  "brains",
package/templates/rover-pilot/docs/operator-playbook.md CHANGED
@@ -176,7 +176,7 @@ Rollback must restore the prior desired-state revision and prior runtime image t
176
176
 
177
177
  Start with the public [site mockup migration guide](https://github.com/rizom-ai/brains/blob/main/docs/site-mockup-migration.md), then apply these hosted-fleet requirements:
178
178
 
179
- - A site package must default-export a valid `SitePackage` and use documented public APIs such as `@rizom/brain/site`.
179
+ - A site package must default-export `defineSite(...)` and import its authoring API only from `@rizom/site`.
180
180
  - A theme package must default-export its CSS as a string. Hosted custom themes currently use the `@rizom/*` scope so the fleet image installs them with the site package; `@brains/*` themes are bundled with `@rizom/brain`.
181
181
  - Site and custom theme packages must be public npm packages that install without registry credentials.
182
182
  - Site, theme, and brain packages publish independently. Hosted configuration requires exact site and external-theme version pins and never derives one package version from another.