proof-artifacts 0.1.0-preview.0 → 0.1.0-preview.1

package/README.md

@@ -26,6 +26,7 @@ proof-artifacts stop --name demo
 ```
 
 The noVNC desktop is bound to `127.0.0.1` with a Docker-assigned port by default. The CLI prints the exact URL and writes it to the session manifest.
+The default desktop runtime image is pulled from `ghcr.io/notkainoa/proof-artifacts-desktop:0.1.0-preview.0`; if pulling fails, the CLI can still build the local runtime image as a fallback.
 If your app is running on the VPS host at `localhost`, pass the URL when starting and the CLI will infer host networking:
 
 ```sh
@@ -83,7 +84,7 @@ The agent should then:
 
 ## Still Planned
 
-- Publishing a public prebuilt runtime image from CI.
+- Automating public runtime image publishing from CI.
 - More project-type detectors and runtime images for common Linux desktop dependencies.
 - An MCP server that wraps the stable CLI lifecycle.
 

package/bin/proof-artifacts.js

@@ -17,7 +17,8 @@ import { fileURLToPath } from "node:url";
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
 const rootDir = path.resolve(__dirname, "..");
-const defaultImage = "proof-artifacts/desktop:0.1.0";
+const defaultImage = "ghcr.io/notkainoa/proof-artifacts-desktop:0.1.0-preview.0";
+const localBuildImage = "proof-artifacts/desktop:0.1.0-preview.0";
 const defaultName = "default";
 const defaultWidth = "1280";
 const defaultHeight = "800";
@@ -208,20 +209,22 @@ function buildImage(image) {
 
 function ensureRuntimeImage(opts = {}) {
   const requestedImage = opts.image ?? process.env.PROOF_ARTIFACTS_IMAGE ?? defaultImage;
+  const usesDefaultImage = requestedImage === defaultImage;
   if (isTruthy(opts.rebuild)) {
-    buildImage(requestedImage);
-    return { image: requestedImage, requestedImage, imageSource: "rebuilt" };
+    const image = usesDefaultImage ? localBuildImage : requestedImage;
+    buildImage(image);
+    return { image, requestedImage, imageSource: "rebuilt" };
   }
 
   if (imageExists(requestedImage)) {
     return { image: requestedImage, requestedImage, imageSource: "local" };
   }
 
-  if (requestedImage !== defaultImage && !isTruthy(opts.pull)) {
+  if (!usesDefaultImage && !isTruthy(opts.pull)) {
     throw new Error(`Runtime image ${requestedImage} is not available locally. Build it locally first or pass --pull to pull a remote image explicitly.`);
   }
 
-  const shouldPull = isTruthy(opts.pull);
+  const shouldPull = usesDefaultImage || isTruthy(opts.pull);
   if (shouldPull) {
     console.log(`Runtime image not found locally. Pulling ${requestedImage}...`);
     const pull = dockerTry(["pull", requestedImage], { stdio: "inherit" });
@@ -231,18 +234,18 @@ function ensureRuntimeImage(opts = {}) {
     if (isTruthy(opts["no-build"])) {
       throw new Error(`Could not pull runtime image ${requestedImage}, and --no-build was set.`);
     }
-    console.log(`Pull failed; building local runtime image ${defaultImage} instead.`);
+    console.log(`Pull failed; building local runtime image ${localBuildImage} instead.`);
   }
 
   if (isTruthy(opts["no-build"])) {
     throw new Error(`Runtime image ${requestedImage} is not available locally, and --no-build was set.`);
   }
 
-  buildImage(defaultImage);
+  buildImage(localBuildImage);
   return {
-    image: defaultImage,
+    image: localBuildImage,
     requestedImage,
-    imageSource: requestedImage === defaultImage ? "built" : "built-fallback",
+    imageSource: "built-fallback",
   };
 }
 
@@ -1175,7 +1178,7 @@ function cmdDoctor(input = []) {
   if (dockerAvailable) {
     const dockerDaemon = spawnSync("docker", ["info"], { encoding: "utf8", stdio: "pipe" });
     addCheck(dockerDaemon.status === 0 ? "pass" : "fail", "Docker daemon", dockerDaemon.status === 0 ? "reachable" : dockerDaemon.stderr.trim());
-    addCheck(imageExists(defaultImage) ? "pass" : "warn", "Default runtime image", imageExists(defaultImage) ? defaultImage : "not built yet; first start/smoke can build it");
+    addCheck(imageExists(defaultImage) ? "pass" : "warn", "Default runtime image", imageExists(defaultImage) ? defaultImage : "not available locally; first start/smoke will pull it or build a local fallback");
   }
 
   try {

package/docs/ARCHITECTURE.md

@@ -29,7 +29,7 @@ Each session is one Docker container:
 On Unix hosts, the container runs as the invoking UID/GID when available so screenshots, recordings, and reports stay removable by the VPS user.
 Bridge-mode sessions also add `host.docker.internal` as a Docker host-gateway alias for VPS-host app access when the provider allows bridge-to-host traffic. That path is best-effort: some VPS firewall/Docker setups block bridge-to-host traffic. For localhost dev servers on the VPS host, `start --url http://127.0.0.1:<port>` infers host networking so Chromium can use the same network namespace as the app. Host-network sessions bind noVNC to VPS localhost and auto-probe noVNC/VNC ports when possible.
 
-The CLI can use a configured runtime image with local Docker build fallback. A public prebuilt image still needs CI publishing before the first-run experience is fast.
+The CLI defaults to the preview GHCR runtime image at `ghcr.io/notkainoa/proof-artifacts-desktop:0.1.0-preview.0` and falls back to a local Docker build when pulling fails. CI should publish the image automatically before stable release so the npm package and runtime image stay version-matched.
 
 The host keeps artifacts at:
 
@@ -99,4 +99,4 @@ Linux lets us create virtual displays without OS-private APIs or driver installa
 - `proof-artifacts list/status` lets agents understand existing sessions before starting, stopping, or replacing anything.
 - `proof-artifacts install-skill` gives Codex agents the workflow.
 
-Future v0 success criteria should include CI-published prebuilt images, more project/runtime coverage, and an MCP wrapper after CLI semantics settle.
+Future v0 success criteria should include automated CI image publishing, more project/runtime coverage, and an MCP wrapper after CLI semantics settle.

package/docs/VPS.md

@@ -16,6 +16,7 @@ proof-artifacts smoke
 
 Some providers ship newer Docker packages through their own images. If `docker.io` is old or unavailable, install Docker Engine from Docker's official apt repository instead.
 After the package is published, replace the local source install with `npm install -g proof-artifacts`.
+The first desktop start pulls `ghcr.io/notkainoa/proof-artifacts-desktop:0.1.0-preview.0` by default. Use `proof-artifacts smoke --rebuild` only when testing local runtime changes or when you intentionally want to bypass the published image.
 
 ## Start A Desktop
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "proof-artifacts",
-  "version": "0.1.0-preview.0",
+  "version": "0.1.0-preview.1",
   "description": "Proof artifacts for coding agents using isolated Linux desktops.",
   "type": "module",
   "bin": {

package/skills/proof-artifacts/SKILL.md

@@ -36,6 +36,7 @@ proof-artifacts doctor
 ```
 
 If Node/npm is missing, install Node.js 18+ first or tell the user the machine needs Node.js before the skill can continue. If Docker is missing or the user cannot access the Docker daemon, explain that Docker Engine is the required Linux desktop substrate and give the exact next command for the detected distro when it is obvious. On a new VPS, run `proof-artifacts doctor --deep` when you want the CLI to perform a disposable smoke capture.
+The CLI pulls the preview GHCR desktop runtime by default and falls back to a local Docker build if the pull fails. Use `--rebuild` only when testing local runtime changes.
 
 ## Workflow
 
@@ -134,7 +135,7 @@ Do not put secrets in scripts passed over stdin; the CLI does not record stdin c
 
 - `proof-artifacts smoke --keep` leaves the test desktop running for inspection.
 - `proof-artifacts smoke --rebuild` rebuilds the local runtime image before testing local runtime changes.
-- `proof-artifacts start --image <image> --pull` tries a configured runtime image before local build fallback.
+- `proof-artifacts start --image <image> --pull` tries a custom runtime image before local build fallback.
 - `proof-artifacts open <url> --name <task-name> --fullscreen` opens Chromium as a full-display browser window with browser chrome still visible.
 - `proof-artifacts detect --project <repo-path>` suggests whether the project is web, Linux desktop, or unsupported in the Linux runtime.
 - `proof-artifacts launch --name <task-name> --window-match <title> -- <command...>` starts a Linux desktop app inside the session.