@rizom/ops 0.2.0-alpha.204 → 0.2.0-alpha.205

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.
@@ -34,6 +34,8 @@ export interface ResolvedSetupDelivery {
34
34
  }
35
35
  export interface ResolvedAtprotoConfig {
36
36
  identifier: string;
37
+ /** Owner account DID served at /.well-known/atproto-did for handle verification. */
38
+ accountDid?: string | undefined;
37
39
  }
38
40
  export interface ResolvedPlaybooksConfig {
39
41
  onboarding?: boolean | undefined;
package/dist/schema.d.ts CHANGED
@@ -46,6 +46,7 @@ declare const setupDeliverySchema: z.ZodObject<{
46
46
  }>;
47
47
  declare const atprotoSchema: z.ZodObject<{
48
48
  identifier: z.ZodString;
49
+ accountDid: z.ZodOptional<z.ZodString>;
49
50
  }>;
50
51
  declare const siteOverrideSchema: z.ZodObject<{
51
52
  package: z.ZodString;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rizom/ops",
3
- "version": "0.2.0-alpha.204",
3
+ "version": "0.2.0-alpha.205",
4
4
  "description": "Operator CLI for managing private brain fleet registry repos",
5
5
  "keywords": [
6
6
  "brains",
@@ -167,11 +167,17 @@ Notes:
167
167
 
168
168
  Use this when enabling AT Protocol publishing for a single pilot user.
169
169
 
170
- 1. Add the public PDS identifier to the user file:
170
+ 1. Add the public PDS identifier to the user file. Prefer the account DID as
171
+ the identifier — it survives handle changes. Add `accountDid` too when the
172
+ member wants their handle verified against their subdomain
173
+ (`@<handle>.<domainSuffix>`): the brain then serves it at
174
+ `/.well-known/atproto-did` and Bluesky's "I have my own domain" HTTP
175
+ verification passes with no DNS records.
171
176
 
172
177
  ```yaml
173
178
  atproto:
174
- identifier: rizom-test.bsky.social
179
+ identifier: did:plc:example123
180
+ accountDid: did:plc:example123
175
181
  ```
176
182
 
177
183
  2. Put the app password in `users/<handle>.secrets.yaml`:
@@ -185,7 +191,7 @@ Use this when enabling AT Protocol publishing for a single pilot user.
185
191
  4. Reconcile/deploy the user or cohort:
186
192
  - `bunx brains-ops onboard . <handle>`
187
193
  - or `bunx brains-ops reconcile-cohort . <cohort>`
188
- 5. Verify the generated `users/<handle>/brain.yaml` contains `plugins.atproto.identifier` and `appPassword: ${ATPROTO_APP_PASSWORD}`.
194
+ 5. Verify the generated `users/<handle>/brain.yaml` contains `plugins.atproto.identifier` (plus `accountDid` when configured) and `appPassword: ${ATPROTO_APP_PASSWORD}`.
189
195
 
190
196
  Notes:
191
197