@rizom/ops 0.2.0-alpha.169 → 0.2.0-alpha.170

package/dist/entries/deploy.d.ts

@@ -1,2 +1,3 @@
 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

@@ -1,4 +1,5 @@
-import type { ResolvedSiteOverride } from "./load-registry";
+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
@@ -38,3 +39,38 @@ export interface RequiredImage {
  * 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,6 +1,6 @@
 export { initPilotRepo } from "./init";
 export { loadPilotRegistry, type LoadPilotRegistryOptions, } from "./load-registry";
-export { siteImageTag, sitePackagesFor, requiredImages, type ImageRequirementSource, type RequiredImage, } from "./images";
+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";