@rizom/ops 0.2.0-alpha.561 → 0.2.0-alpha.562

package/dist/user-add.d.ts

@@ -1,5 +1,6 @@
 export interface AddPilotUserOptions {
     cohort: string;
+    discord?: boolean | undefined;
     anchorId?: string | undefined;
 }
 export interface AddPilotUserResult {

package/package.json

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

package/templates/rover-pilot/README.md

@@ -39,7 +39,7 @@ When a push changes only deploy contract files, CI prints `No affected user conf
 - `brains-ops init <repo>`
 - `brains-ops upgrade <repo>` — bumps `@rizom/ops` (or `--to <version>`) and refreshes the generated scaffold; the Upgrade workflow runs this on a schedule and opens a PR
 - `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 user:add <repo> <handle> --cohort <cohort> [--discord] [--anchor-id <id>]` — scaffolds a browser-chat-first user with Discord disabled by default; use `--discord` to include Discord config and its per-user secret
 - `brains-ops onboard <repo> <handle>` — creates/seeds the user's content repo with separate admin and sync tokens
 - `brains-ops age-key:bootstrap <repo>`
 - `brains-ops ssh-key:bootstrap <repo>`

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

@@ -9,9 +9,9 @@
    - confirm `agePublicKey`
 4. Run `bunx brains-ops user:add <repo> <handle> --cohort <cohort>`.
    - Web chat is the primary interface; it needs no per-user setup beyond the passkey.
-   - `user:add` currently writes `discord: enabled: true`; set it to `false` unless the user's cohort actually uses Discord.
-   - if the user should be an anchor on Discord, add `--anchor-id <discord-user-id>`.
-   - the command creates `users/<handle>.yaml`, `users/<handle>.secrets.yaml`, and the cohort membership without duplicating existing entries.
+   - The default scaffold writes `discord.enabled: false` and does not add `discordBotToken` to the per-user secrets template.
+   - To enable Discord, add `--discord`. If the user should be an anchor on Discord, also add `--anchor-id <discord-user-id>`; `--anchor-id` alone still enables Discord for compatibility.
+   - The command creates `users/<handle>.yaml`, `users/<handle>.secrets.yaml`, and the cohort membership without duplicating existing entries.
 5. Edit the generated user file if the anchor profile needs richer metadata.
    - Set `setup.delivery: email` and `setup.email` so the user gets the passkey setup email — this is the default onboarding path.
    - For ATProto publishing, add `atproto.identifier` to the user file; put only `atprotoAppPassword` in the per-user secrets file.

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

@@ -430,9 +430,11 @@ Notes:
 
 ## Discord application credential checklist
 
-Use this when enabling Discord for a pilot user.
+Discord is optional. Browser chat with passkey setup is the default pilot interface. Use this checklist only when enabling Discord for a user.
 
-1. Pick the user handle (for example `smoke`).
+1. Add the user with Discord enabled:
+   - `bunx brains-ops user:add . <handle> --cohort <cohort> --discord`
+   - Add `--anchor-id <discord-user-id>` if the user should be a Discord anchor. For compatibility, `--anchor-id` also enables Discord when `--discord` is omitted.
 2. Open the Discord Developer Portal.
 3. Create a **new application** for that user's brain.
 4. Add a **Bot** to the application.
@@ -441,7 +443,7 @@ Use this when enabling Discord for a pilot user.
    - `DISCORD_BOT_TOKEN=...`
    - `DISCORD_PUBLIC_KEY=...`
    - `DISCORD_APPLICATION_ID=...`
-7. Keep `discord.enabled: true` in `users/<handle>.yaml` unless you explicitly want to disable the primary pilot interface.
+7. Confirm `users/<handle>.yaml` contains `discord.enabled: true` and its secrets template contains `discordBotToken`.
 8. Encrypt the current per-user credential payload:
    - `bunx brains-ops secrets:encrypt . <handle>`
 9. Reconcile/deploy the user or cohort:
@@ -454,7 +456,7 @@ Notes:
 
 - Use **one Discord application credential set per user/brain**.
 - Do not reuse the same Discord application across multiple pilot users.
-- Discord is the default pilot interface moving forward.
+- Discord-disabled users generate `anchors: []`, no `plugins.discord` block, and require no Discord secret.
 - The encrypted `users/<handle>.secrets.yaml.age` file is the durable checked-in deploy input; your local env is only the operator staging source.
 - Direct MCP client access should use OAuth/passkey-capable clients where possible.
 - When explaining the content workflow, describe it first as a normal **git repo** of **markdown/text files**.