@rizom/ops 0.2.0-alpha.76 → 0.2.0-alpha.77

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.
@@ -4,12 +4,16 @@ export interface VerifyPilotUserOptions {
4
4
  fetchImpl?: FetchLike;
5
5
  logger?: (message: string) => void;
6
6
  }
7
+ export interface FailedCheck {
8
+ name: string;
9
+ message: string;
10
+ }
7
11
  export interface VerifyPilotUserResult {
8
12
  handle: string;
9
13
  preset: ResolvedUser["preset"];
10
14
  domain: string;
11
15
  contentRepo: string;
12
16
  checks: string[];
13
- warnings: string[];
17
+ failedChecks: FailedCheck[];
14
18
  }
15
19
  export declare function verifyPilotUser(rootDir: string, handle: string, options?: VerifyPilotUserOptions): Promise<VerifyPilotUserResult>;
package/package.json CHANGED
@@ -4,7 +4,7 @@
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
7
- "version": "0.2.0-alpha.76",
7
+ "version": "0.2.0-alpha.77",
8
8
  "type": "module",
9
9
  "exports": {
10
10
  ".": {
@@ -82,12 +82,11 @@ For `preset: default`, the script also checks:
82
82
 
83
83
  - `https://<handle>.rizom.ai/` loads the browser/site surface
84
84
  - `https://<handle>.rizom.ai/cms` loads the CMS/login surface
85
- - the generated user config has a content repo
86
85
 
87
86
  Manual checks that remain:
88
87
 
89
88
  - initial site build is correct for the expected content/theme
90
- - runtime sync is healthy beyond the basic `/health` response
89
+ - content repo exists and runtime sync is healthy beyond the basic `/health` response
91
90
  - passkey setup/handoff is completed from the setup email
92
91
 
93
92
  ## One-user `rover:default` baseline canary