@rizom/ops 0.2.0-alpha.22 → 0.2.0-alpha.220

package/dist/entries/deploy.d.ts

@@ -1,2 +1,3 @@
-export { readJsonResponse, parseEnvFile, parseEnvSchema, parseEnvSchemaFile, requireEnv, writeGitHubOutput, writeGitHubEnv, } from "@brains/utils";
-export type { EnvSchemaEntry } from "@brains/utils";
+export { readJsonResponse, parseEnvFile, parseEnvSchema, parseEnvSchemaFile, requireEnv, writeGitHubOutput, writeGitHubEnv, } from "@brains/deploy-support";
+export type { EnvSchemaEntry } from "@brains/deploy-support";
+export { siteImageTag, sitePackagesFor, requiredImages, resolveImageBuilds, runResolveMissingImages, type ImageRequirementSource, type RequiredImage, type ResolveImageBuildsOptions, type RunResolveMissingImagesOptions, } from "../images";

package/dist/images.d.ts

@@ -0,0 +1,76 @@
+import { type ResolvedSiteOverride } from "./load-registry";
+import { type RunCommand } from "./run-subprocess";
+/**
+ * Resolve a fleet image tag as a pure function of a single instance's own
+ * config. This is the shared contract between the build (which tags the image
+ * it pushes) and the deploy (which waits for and runs that tag), so both must
+ * import this — never recompute it independently.
+ *
+ * The default path is deliberately untouched: an instance with no site packages
+ * resolves to the plain `brain-{version}` tag every other fleet instance uses.
+ * A site override is a per-instance opt-in that hashes only *that instance's*
+ * package set into a distinct `brain-{version}-sites-{hash}` image, so it can
+ * never collide with — or leak into — the shared default image.
+ */
+export declare function siteImageTag(brainVersion: string, sitePackages: string[]): string;
+/**
+ * The npm packages a site override installs into its per-instance image.
+ * A @rizom-scoped theme is an independently published package and rides along
+ * at the same lockstep version; @brains/* themes are bundled inside
+ * @rizom/brain and must not be npm-installed.
+ */
+export declare function sitePackagesFor(siteOverride: ResolvedSiteOverride | undefined): string[];
+/** The per-user slice of the registry that determines which image it runs. */
+export interface ImageRequirementSource {
+    brainVersion: string;
+    siteOverride?: ResolvedSiteOverride | undefined;
+}
+export interface RequiredImage {
+    tag: string;
+    brainVersion: string;
+    /** Sorted, deduped — build args for the image, empty for the default. */
+    sitePackages: string[];
+}
+/**
+ * The image set the declared fleet state requires: one default
+ * `brain-{version}` per distinct brain version in use, plus one
+ * `brain-{version}-sites-{hash}` per distinct site-override package set.
+ * Derived purely from resolved users (pass `registry.users`), so CI can build
+ * exactly what a config push declares — nothing reactive, nothing manual.
+ */
+export declare function requiredImages(users: ImageRequirementSource[]): RequiredImage[];
+export interface ResolveImageBuildsOptions {
+    users: ImageRequirementSource[];
+    /**
+     * Explicit dispatch override — the manual/backfill path. When set, exactly
+     * this one image is built, skipping both the registry and the exists check.
+     */
+    brainVersionInput?: string | undefined;
+    sitePackagesInput?: string | undefined;
+    imageExists: (tag: string) => Promise<boolean>;
+}
+/**
+ * Decide which images a Build run must produce: the declared required set
+ * filtered to tags the registry does not already hold, or the single image an
+ * explicit dispatch input forces.
+ */
+export declare function resolveImageBuilds(options: ResolveImageBuildsOptions): Promise<RequiredImage[]>;
+export interface RunResolveMissingImagesOptions {
+    rootDir: string;
+    /** e.g. `ghcr.io/rizom-ai/rover-pilot` */
+    imageRepository: string;
+    env?: NodeJS.ProcessEnv;
+    runCommand?: RunCommand;
+    writeOutput: (key: string, value: string) => void;
+    log?: (line: string) => void;
+}
+/**
+ * The Build workflow's resolve step: derive the image set the declared fleet
+ * state (pilot.yaml + cohorts + users) requires, probe the container registry
+ * for each tag, and emit the missing ones as a GitHub Actions build matrix
+ * (`images_json`, entries `{tag, brain_version, site_packages}`). Dispatch
+ * inputs `BRAIN_VERSION_INPUT`/`SITE_PACKAGES_INPUT` force a single explicit
+ * build instead. Deriving and probing here means a config push builds exactly
+ * what it declares — nothing reactive, nothing manual.
+ */
+export declare function runResolveMissingImages(options: RunResolveMissingImagesOptions): Promise<RequiredImage[]>;

package/dist/index.d.ts

@@ -1,7 +1,9 @@
 export { initPilotRepo } from "./init";
 export { loadPilotRegistry, type LoadPilotRegistryOptions, } from "./load-registry";
+export { siteImageTag, sitePackagesFor, requiredImages, resolveImageBuilds, runResolveMissingImages, type ImageRequirementSource, type RequiredImage, type ResolveImageBuildsOptions, type RunResolveMissingImagesOptions, } from "./images";
 export { writeUsersTable } from "./render-users-table";
 export { onboardUser } from "./onboard-user";
+export { addPilotUser } from "./user-add";
 export { reconcileCohort } from "./reconcile-cohort";
 export { reconcileAll } from "./reconcile-all";
 export { parseArgs, type ParsedArgs } from "./parse-args";
@@ -10,4 +12,5 @@ export { bootstrapPilotSshKey, runPilotSshKeyBootstrap, } from "./ssh-key-bootst
 export { bootstrapPilotOriginCertificate, runPilotCertBootstrap, } from "./cert-bootstrap";
 export { encryptPilotSecrets } from "./secrets-encrypt";
 export { pushPilotSecrets } from "./secrets-push";
+export { verifyPilotUser } from "./verify-user";
 export { runCommand, type CommandResult } from "./run-command";