@ai-outfitter/outfitter 1.11.0 → 1.12.0

package/docs/documentation/containers.md

@@ -13,9 +13,6 @@ servers, or other use-case behavior. The default runtime user and group are
 both `1000` (named `outfitter`), with `/tmp` as the home directory and
 `/workspace` as the working directory.
 
-A Nix closure variant of the image is also published under the `-nix` suffix;
-see [the `-nix` variant](#the--nix-variant) below.
-
 ## Run a resident agent
 
 A resident container is an ordinary `outfitter run` whose harness stays in RPC
@@ -47,7 +44,7 @@ spec:
         fsGroup: 1000
       containers:
         - name: agent
-          # The primary Debian-based image; append -nix for the Nix variant.
+          # The published Debian-based image.
           image: ghcr.io/ai-outfitter/outfitter:<version>
           stdin: true
           workingDir: /workspace
@@ -85,8 +82,8 @@ The image is a normal Debian base: extend it with an ordinary Dockerfile.
 `apt-get` works, and so does `COPY`ing binaries. A dynamically linked binary
 runs when it matches the image — same architecture, glibc-linked, and its
 shared-library dependencies present. The standard ELF interpreter is where
-tools expect it (unlike the `-nix` variant), but the slim base ships a small
-library set: `apt-get install` a binary's runtime libraries when it needs more.
+tools expect it, but the slim base ships a small library set. Use `apt-get
+install` when a binary needs more runtime libraries.
 Switch to `root` for the layers that install, then drop back to `1000`:
 
 ```dockerfile
@@ -111,77 +108,3 @@ docker run --rm --entrypoint /bin/sh example-agent \
 
 The entrypoint stays `outfitter`; override `ENTRYPOINT` only when the derived
 image wraps the launch itself.
-
-## The `-nix` variant
-
-The Nix closure image that was previously the primary tag remains published
-for `lib.mkContainer` consumers:
-
-```text
-ghcr.io/ai-outfitter/outfitter:<version>-nix
-```
-
-It is built by the flake, includes the Nix CLI, Bash, core utilities, Git,
-SSH, and CA certificates, and its entrypoint is an absolute `/nix/store` path.
-It is not conventionally extensible — there is no apt, and foreign dynamic
-binaries do not run — so extend it through Nix instead: the flake exports
-`lib.mkContainer` for reproducible derivative images:
-
-```nix
-{
-  inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
-    outfitter = {
-      url = "github:ai-outfitter/outfitter/v1.4.0";
-      inputs.nixpkgs.follows = "nixpkgs";
-    };
-  };
-
-  outputs =
-    { nixpkgs, outfitter, ... }:
-    let
-      system = "x86_64-linux";
-      pkgs = nixpkgs.legacyPackages.${system};
-    in
-    {
-      packages.${system}.default = outfitter.lib.mkContainer {
-        inherit pkgs;
-        outfitterPackage = outfitter.packages.${system}.outfitter;
-        name = "example-agent";
-        extraPackages = [
-          pkgs.jq
-          pkgs.ripgrep
-        ];
-      };
-    };
-}
-```
-
-Build and exercise the exact image:
-
-```sh
-nix build
-docker load < result
-docker run --rm example-agent:latest --version
-docker run --rm --entrypoint /bin/sh example-agent:latest \
-  -c 'nix --version && jq --version && rg --version'
-```
-
-Prefer adding known runtime packages through `extraPackages`. The resulting
-image stays reproducible, and it avoids the trap below.
-
-**Do not mount an empty volume over `/nix` of the `-nix` variant.** That image
-_is_ its Nix store: the entrypoint is an absolute store path and every binary
-in `/bin` is a symlink into `/nix/store`. Mounting a fresh volume there hides
-all of it, so the container cannot start — it fails before it could initialize
-the very store you mounted the volume to populate. (The primary Debian image
-has no `/nix` and is not affected.)
-
-Runtime installation in the `-nix` variant therefore needs one of:
-
-- a volume **pre-populated** with the image's closure, seeded from the image
-  before the agent starts (an init container copying `/nix` into the volume);
-- an **overlay** whose lower layer is the image's `/nix`, so the closure stays
-  visible while writes land in the upper layer; or
-- writable Nix **state** only — `/nix/var` and a per-user profile — leaving the
-  store itself as the image shipped it.

package/docs/documentation/settings.md

@@ -41,6 +41,8 @@ remote_settings:
     ref: 9c47d1e2b8a05f36c4d7e90a12b3f8c5d6e71a04
 
 cache_directory: ./cache # optional; relative to this settings file
+source_cache:
+  policy: repair # repair (default), locked, or offline
 
 # Pseudonymous product analytics consent; defaults to true when absent.
 telemetry:
@@ -53,6 +55,9 @@ telemetry:
 - `remote_settings` — shared settings a repository distributes; cached locally and merged below your project and user settings, so anything you set locally wins.
 - `cache_directory` — the repository cache root used consistently by sync, remote settings, remote
   source resolution, and default-catalog setup. It defaults to `~/.agents/cache`; repositories live
+- `source_cache.policy` — verifies remote caches before `run`: `repair` reuses healthy caches and
+  atomically repairs unhealthy ones, `locked` also requires full commit pins, and `offline` never
+  accesses the network.
   below its `repos/` directory.
 - `telemetry.enabled` — the primary and sole persistent control for pseudonymous product analytics. Edit it directly to enable or disable telemetry. See [Telemetry](./telemetry.md) for consent precedence, automatic identifier cleanup, the event contract, and the current inert-build status.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-outfitter/outfitter",
-  "version": "1.11.0",
+  "version": "1.12.0",
   "description": "Profile-oriented wrapper for launching pi, Claude Code, and future agent CLIs with reproducible configuration.",
   "type": "module",
   "repository": {

package/src/schemas/settings.schema.json

@@ -11,6 +11,11 @@
       "description": "Whether a run stands on the machine's native harness configuration (inherit, the default) or on the projection alone (isolated). Honored only from home-scope settings."
     },
     "cache_directory": { "type": "string", "minLength": 1 },
+    "source_cache": {
+      "type": "object",
+      "properties": { "policy": { "enum": ["repair", "locked", "offline"] } },
+      "additionalProperties": false
+    },
     "state_persistence": {
       "type": "object",
       "description": "Maps adapter-declared state paths to a persistence strategy.",