@clawscarf/cli 0.1.0-alpha.3 → 0.1.0-alpha.5

package/recipes/README.md

@@ -30,8 +30,9 @@ menu; `--recipe /path/to/recipe.json` uses a custom definition. Both use the sam
 validation and editable settings. `clawscarf recipes` lists available choices.
 Recipe changes never reconfigure an existing server automatically.
 
-**Team server:** GPT-6 Astra through OpenAI, medium reasoning,
-hosted login, Connections enabled, browser off, and no packs selected. It supplies
-a basic team server, not a document ingestion or question-answering workflow. A future document recipe remains separate in [TODO.md](../TODO.md).
+**Team server** supplies a basic team server. Its exact model, reasoning, resource,
+capability and pack defaults are defined in [recipe.json](team-server/recipe.json);
+`clawscarf recipes` displays the bundled selection. Document workflows are separate
+[open work](../TODO.md#openclaw-curation).
 
 See [runtime and package distribution](../release/README.md).

package/recipes/team-server/recipe.json

@@ -1,7 +1,7 @@
 {
   "id": "team-server",
-  "version": "0.1.0",
-  "runtime": "../../runtime/releases/0.1.0-alpha.3.json",
+  "version": "0.1.1",
+  "runtime": "../../runtime/releases/0.1.0-alpha.5.json",
   "name": "Team server",
   "description": "A protected OpenClaw server for your team, with hosted login, managed models and optional Connections.",
   "maturity": "supported",

package/release/README.md

@@ -16,35 +16,14 @@ catalog entries; model protocols and limits have one definition.
 
 ## Published and development use
 
-```sh
-npm install -g @clawscarf/cli@next
-clawscarf configure
-# Or use staging for hosted login and Connections:
-clawscarf configure --cloud-url https://cloud-staging.clawscarf.com
-```
+Use the [installation guide](../deploy/deployment/installation.md) for published
+CLI installation, platform requirements and runtime downloads. Use the
+[development command](../scripts/README.md#development-command) for this checkout.
 
-No recipe argument opens the bundled recipe menu. `--recipe team-server` selects
-that bundled definition; `--recipe /path/to/recipe.json` reads a custom one. Its
-`runtime` path resolves relative to the recipe file. The runtime cannot be changed
-in the settings menu. `--directory` defaults to `~/clawscarf-team`.
-
-The tracked [development runtime](../runtime/releases/0.1.0-dev.json) currently names
-locally built Docker image IDs and checksum-pinned OpenShell tools under ignored
-`runtime/tools/0.0.116/`. It works on the prepared development machine; it is **not a
-published, clean-machine release**. Definitions belong in the tracked directories
-above. Compiled images, binaries and test artifacts are not source definitions.
-
-Published candidates include macOS arm64 and Linux arm64/x86-64 tools, with Linux
-container images for both architectures. Windows uses the Linux CLI inside WSL2
-(experimental);
-Docker Desktop must expose its Linux engine to that distribution. Intel Mac is blocked
-by the pinned upstream OpenShell release lacking a Darwin x86-64 executable.
-See the [upstream support matrix](https://docs.nvidia.com/openshell/reference/support-matrix)
-for host requirements. Setup validates the host,
-tools and ports; it pulls registry images by digest and downloads missing runtime tools
-when their definition supplies an HTTPS URL and SHA-256. It cannot recover a missing
-local development image ID. See the
-[installation guide](../deploy/deployment/installation.md) for diagnostics.
+The tracked [development runtime](../runtime/releases/0.1.0-dev.json) is an input
+for a prepared development environment, not a clean-machine release. Its exact
+images and executable paths are data in that definition. Packaging resolves those
+inputs to immutable candidate artifacts; runtime startup never selects latest.
 
 ## Publishing structure
 
@@ -53,20 +32,13 @@ Release candidates contain:
 - npm `@clawscarf/cli`: compiled CLI, recipes, pack files, model catalog and runtime
   definitions. No Docker images or large OpenShell executables in npm.
 - GitHub Releases: standalone CLI archives with a private Node runtime and installed
-  dependencies, an installer, runtime tool archives, checksums and required notices.
+  dependencies, an installer, runtime tool archives, checksums, required notices and
+  the OpenClaw source provenance and patch series used by the image build.
 - GHCR: runtime/companion images referenced by immutable registry digest.
 
-Installing a newer CLI supplies newer recipes. Each recipe still selects an exact
-runtime; startup never resolves “latest.” Existing installations retain their
-accepted settings and runtime. Explicit configuration changes preserve unrelated
-native edits. The CLI package version and a runtime version need not be the same.
-
-New installations copy their runtime definition and tools into their own `runtime/`
-directory and retain selected pack files under `state/pack-sources/`. Removing the
-checkout, an npm cache entry or an older CLI package does not remove those files.
-Downloads are bounded, checked before becoming executable inputs, and reused on
-subsequent configuration. Corrupt retained tools fail verification rather than being
-silently replaced. Docker verifies image digests. No start command resolves latest.
+The [installation guide](../deploy/deployment/installation.md#change-an-existing-installation)
+owns retained configuration and acquisition behavior. CLI, recipe and runtime
+versions are independent; recipe versioning belongs to [recipes](../recipes/README.md).
 
 ## Build and publish
 
@@ -74,13 +46,18 @@ silently replaced. Docker verifies image digests. No start command resolves late
 with an exact version, such as `0.1.0-alpha.1`. It:
 
 1. Runs checks and tests the compiled operator outside the checkout on macOS arm64.
-2. Builds the pinned OpenClaw source and ClawScarf images on Linux arm64 and x86-64,
+2. Reconstructs OpenClaw from the pinned upstream commit and the ordered
+   [patch series](../runtime/openclaw/README.md), verifies the resulting source tree,
+   then builds ClawScarf images on Linux arm64 and x86-64,
    checks runtime capabilities and the Chromium sandbox, then starts a protected
-   installation with private LiteLLM networking and verifies stop/start retention.
-   It publishes image indexes containing both architectures to GHCR.
+   installation with private LiteLLM networking, exercises native administrator
+   access through the companion, and verifies stop/start retention.
+   Both architectures must report identical OpenClaw source provenance and patch
+   archives before it publishes image indexes containing both architectures to GHCR.
 3. Downloads checksum-pinned OpenShell tools, records the image digests, and assembles
    one runtime archive per host platform, individual executable assets, npm CLI,
-   checksums and notices.
+   checksums and notices. Candidate assembly verifies the image builds' patch archive
+   and provenance against this checkout before including them in the release.
 4. Installs the resulting npm archive into a temporary prefix and checks its CLI/catalog.
 5. Builds standalone CLI archives on macOS ARM64 and Linux ARM64/x86-64 using the
    same npm payload and frozen production dependency lockfile. Downloads Node using
@@ -90,12 +67,10 @@ with an exact version, such as `0.1.0-alpha.1`. It:
 
 [Standalone packaging](../scripts/release/standalone.ts) adds a private Node executable
 and a small launcher; it does not change the CLI implementation. The
-[installer](install.sh) is versioned with each release and downloads only that
-version's archive, verifies SHA-256, and installs under `~/.local` by default.
-`--prefix` selects another absolute directory. It never installs a host service,
-changes system Node, edits shell profiles or needs sudo. To upgrade the CLI, run
-the newer release's installer; it switches the command and retains the old version.
-Runtime upgrades and installation data are separate from CLI installation.
+[installer](install.sh) is versioned with the release and verifies its archive.
+Its user-facing options and upgrade behavior belong to the
+[installation guide](../deploy/deployment/installation.md); archive layouts belong to
+[operator packaging](operator.md).
 
 The [image builder](../scripts/release/build-images.sh) and
 [candidate assembler](../scripts/release/candidate.ts) contain the build commands;
@@ -104,17 +79,20 @@ and Linux installation checks use Depot ARM64/x86-64 runners; macOS checks and p
 use GitHub-hosted runners. The Depot Managed Runners app connects the ClawScarf organization
 to the RAW Labs Depot organization. The image job installs Docker 29.5.3 on its
 disposable runner for the network features required by installations.
+The [patch guide](../runtime/openclaw/README.md#release-and-verification-boundaries)
+owns source identity and reconstruction. Candidate assembly packages
+[openclaw-source.json and openclaw-patches.tgz](../scripts/release/candidate.ts)
+with checksums; each runtime archive includes both. The runtime definition's `sourceRevision`
+identifies the ClawScarf commit that owns those inputs.
 The source recipe pins the development
 runtime. Packaging resolves that same runtime to the candidate's immutable definition;
-it does not make recipes select latest. The first release uses the same CLI/runtime
-version. Recipe versions remain independent; bump them when defaults, pack selection
-or the selected runtime changes. Published definitions must not be overwritten.
+it does not make recipes select latest. Published definitions must not be overwritten.
 
 The `release-candidate` Actions artifact is the reviewable output. Download it and test
 a fresh supported installation, administrator login, real inference and stop/start
 before publication. GitHub's macOS runner does not provide our Docker Desktop journey;
-its packaging checks alone do not establish that journey. The browser-selection bug
-remains a separate, explicit limit; the Team server recipe leaves browser disabled.
+its packaging checks alone do not establish that journey. Check the owning component
+limitations before claiming support for optional capabilities.
 
 [Publish release candidate](../.github/workflows/publish-release.yml) accepts a successful
 build run from `main`. It checks the source commit and artifact checksums, creates the
@@ -130,32 +108,28 @@ Repository setup:
   organization `@clawscarf` owns the public `@clawscarf/cli` package.
 - npm trusted publishing is configured for repository `clawscarf/clawscarf`, workflow
   [publish-release.yml](../.github/workflows/publish-release.yml), environment `release`.
-  The first tested tarball was published using the owner's authenticated npm CLI because
-  npm requires a package to exist before configuring trust. Subsequent publication
-  uses the workflow's short-lived identity rather than a stored npm token; alpha.2
-  was published through that workflow successfully.
+  Publication uses the workflow's short-lived identity rather than a stored npm token.
 - Transitive notices/source review remains open in [TODO.md](../TODO.md).
   Debian copyright files remain in the images; runtime assets include upstream notices
   and the image build exports its network-tool sources. Those files are not a claim of
   a completed license audit. Pinned Debian packages still depend on mirror retention.
 
-[Candidate 35532613602](https://github.com/clawscarf/clawscarf/actions/runs/35532613602)
-passed full checks, compiled archive installation and all eight image builds on
-native ARM64 and x86-64 Depot runners. The same artifacts are available in the
-[0.1.0-alpha.2 GitHub prerelease](https://github.com/clawscarf/clawscarf/releases/tag/v0.1.0-alpha.2)
-and as `@clawscarf/cli@0.1.0-alpha.2`, tagged `next`.
-
-Both Linux architectures passed protected runtime startup, native WebSocket forwarding,
-authenticated TLS to the private model gateway, retained stop/start and deletion on
-Docker 29.5.3. The final ARM64 images also passed real GPT-6 Astra inference and retained
-restart on macOS Docker Desktop. Candidate downloads passed SHA-256 verification and
-the CLI tarball installed independently of the repository. Disposable test containers,
-volumes and networks were deleted afterward.
-
-Staging hosted administrator login and the packaged interactive setup previously
-passed on macOS with alpha.1. Hosted login and real provider inference on Linux,
-actual Windows/WSL2 installation, production first-time signup and changed-version
-upgrades remain unverified; see [TODO.md](../TODO.md).
+## Release evidence
+
+[GitHub Releases](https://github.com/clawscarf/clawscarf/releases) owns published
+versions, release notes and checksummed assets. The linked candidate CI run owns its
+build/test results. Inspect the selected release's runtime definition and
+OpenClaw source provenance to establish what actually shipped; current source docs are
+not evidence that a setting or patch is present in an older installation.
+
+Keep release-specific acceptance logs/screenshots in CI or ignored local artifacts,
+with the tested revision/image, platform and actual outcomes. Promote only the tested
+candidate; publishing reuses its bytes. Do not maintain a second release journal in
+component READMEs. Current capability limits remain with their owners:
+[browser integration](../deploy/execution/browser-node/README.md#verified-release-limits),
+[runtime boundary](../deploy/openshell/README.md), [models](../deploy/models/README.md),
+[Access](../services/access/README.md) and [Connections](../plugins/connections/README.md).
+Open acceptance requirements live only in [TODO.md](../TODO.md).
 
 ## Assemble runtime artifacts
 

package/release/components.json

@@ -1,8 +1,8 @@
 {
   "openclaw": {
+    "sourceTree": "b4ea62c5851510a4914ac95878f6e657344e6caf",
     "version": "2026.9.4",
-    "sourceRevision": "7bc487d39dc9e059bb9b19ea08152883022f83fe",
-    "image": "clawscarf-openclaw:7bc487d39dc9e059bb9b19ea08152883022f83fe"
+    "sourceRevision": "7bc487d39dc9e059bb9b19ea08152883022f83fe"
   },
   "openshell": {
     "version": "0.0.116",

package/release/operator.md

@@ -1,89 +1,37 @@
-# ClawScarf operator
+# CLI archive
 
-The operator archive contains the compiled configuration/lifecycle CLI and its controller, model and pack
-operators. It runs outside the contributor checkout. It is not the complete
-distribution: runtime/companion images and the pinned OpenShell executables are
-separate inputs. The archive includes recipes, packs, the model catalog and runtime definitions.
-The interactive menu lists those recipes; each fixes its runtime. For a published runtime it downloads missing OpenShell tools by checksum and pulls
-registry images by digest. Local development image IDs cannot be downloaded. The npm
-package is named `@clawscarf/cli` and exposes the `clawscarf` command. Development archives
-remain private; the release candidate builder makes the package publishable. [Release contents](README.md) defines the publication model.
+For normal installation and operation, use the [quickstart](../README.md#get-started)
+and [CLI guide](../deploy/deployment/installation.md). This file describes the archive
+layout; [release assembly](README.md) owns how artifacts are built and published.
+The source links refer to the repository, not additional files in this archive.
 
-## Install from npm
+## Standalone layout
 
-```sh
-npm install -g @clawscarf/cli@next
-clawscarf configure
-```
-
-The `next` tag selects the current alpha. Use an exact version instead when needed.
-npm installs the CLI dependencies; runtime images and tools are fetched during setup.
-See [release contents](README.md) for supported platforms and verification.
-
-## Standalone download
-
-Standalone CLI archives include Node and installed dependencies. Download the archive
-for your platform and its `SHA256SUMS` from the same GitHub Release. The release's
-[installer](install.sh) selects the correct archive, verifies it and installs
-`clawscarf` under `~/.local/bin`. It accepts `--prefix /absolute/directory`.
-No system Node, npm or pnpm is required. These archives are separate from both the
-npm package and the runtime-tool archives.
+The standalone archive contains `clawscarf/` with the command launcher, a private
+`node/bin/node`, Node's license, and `package/` with the CLI, installed dependencies
+and catalogs. Verify it against the same release's `SHA256SUMS`, then extract it.
+Run `./clawscarf/clawscarf configure`; moving the complete directory preserves its
+runtime and dependencies. The release installer performs this verification and
+installation for normal use.
 
-The layout is `clawscarf/` containing the launcher, `node/bin/node`, Node's LICENSE,
-and `package/` with the CLI, dependencies and catalogs. You can also verify and
-extract the archive yourself, then run `./clawscarf/clawscarf configure`.
-Moving the whole directory preserves the bundled runtime and dependencies.
+## JavaScript archive
 
-## Run the JavaScript archive
+The development JavaScript archive contains compiled operator code, its production
+dependency lockfile, migrations, policy/helpers, recipes, packs and runtime definitions.
+It excludes companion servers, Docker images, OpenShell executables and installation
+state. Publisher dependencies and TypeScript sources are not runtime requirements.
 
-Verify the archive against its accompanying `SHA256SUMS`, then extract it into a new
-directory. Unlike the standalone download, this requires Node 24.16 or later in the Node 24 line, or Node 26.1 or later, and
-pnpm 10.33.0. In the extracted `package` directory:
+With Node/pnpm matching [package.json](../package.json), verify the archive against
+its `SHA256SUMS` and extract it into a new directory. Inside `package`:
 
 ```sh
 pnpm install --prod --frozen-lockfile --ignore-scripts
 node scripts/clawscarf.js --help
 node scripts/clawscarf.js configure --directory /absolute/new-team
-node scripts/clawscarf.js configure --help
-node scripts/clawscarf.js people --help
-node scripts/clawscarf.js connections --help
 ```
 
-Dependencies are installed from the included frozen lockfile. Its root importer
-contains only the production dependencies referenced by the staged operator;
-publisher and browser dependencies are omitted. Locked transitive versions are retained.
-No TypeScript compiler, contributor source or build step is needed to run the commands.
-Platform support is determined by the selected runtime definition. Published candidates
-include macOS arm64 and Linux arm64/x86-64 tools; Windows runs the Linux CLI inside WSL2.
-
-The installer reviews recipe settings before credentials, prepares the installation,
-and offers **Start now**. It starts Docker services and protected OpenShell containers, then exits; closing
-the terminal leaves them running. Administrator setup supplies a private sign-in link and waits for successful
-browser setup, with replacement links offered on expiry. The same public
-operations use `configure` for new or existing installations, with `--non-interactive`
-for automation. `start`, `stop`, `status` and `logs` operate the selected `--directory`.
-Validation and preview/apply are internal. See the source installation guide for
-supported retained changes and administrator setup.
-
-Recipes select runtime definitions relative to their own files. New installations
-retain the runtime and selected packs outside the package. The development descriptor
-still uses local image IDs and tools prepared separately; that development archive alone
-cannot install on a clean machine. Published candidates instead contain registry digests
-and checksummed tool download URLs. Custom recipes can point to a separately prepared
-runtime bundle. Team server supplies a basic team server, not a document workflow.
-
-Keep installation data outside this extracted package. Stop retains state; replacing
-an operator archive is not a runtime upgrade or backup. Docker services keep running after
-terminal exit; Docker must remain available. No host service is installed.
-The pack operator additionally needs the pinned Python environment from
-`scripts/packs/requirements.txt`. Models require an external LiteLLM gateway or the unified configuration’s pinned local
-LiteLLM service. This archive contains no model/provider credentials. Unified preparation
-can issue initial scoped model and Connections credentials for fresh installations;
-normal start never rotates or reactivates them. Use `configure` for capability changes;
-`connections` manages application accounts and grants.
-
-The source checkout owns full local setup, model and pack qualification instructions.
-[Third-party notices](../THIRD_PARTY_NOTICES.md) are retained verbatim; their relative source references refer
-to the source checkout, not additional runtime payload in this archive. Installed
-dependencies retain their own notices. Full binary-release license qualification
-remains separate from this operator packaging check.
+Keep installation data outside the extracted package. A development runtime that
+references local image IDs needs those images prepared separately; see
+[development releases](README.md#published-and-development-use).
+The optional pack operator also needs its [Python dependencies](../packs/README.md#requirements-and-bindings).
+Required [notices](../THIRD_PARTY_NOTICES.md) and dependency licenses accompany the payload.

package/runtime/configuration.js

@@ -28,6 +28,7 @@ export function initialConfiguration(input) {
     const settings = configurationInput.parse(input);
     const identity = settings.administratorIdentity;
     return {
+        marketplace: { enabled: false },
         gateway: {
             publicOrigin: settings.publicOrigin,
             mode: "local",

package/runtime/releases/{0.1.0-alpha.3.json → 0.1.0-alpha.5.json}

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
-  "version": "0.1.0-alpha.3",
-  "sourceRevision": "b5e0988a9dbbf28b40974cc1a8b38e1d9466e6f2",
+  "version": "0.1.0-alpha.5",
+  "sourceRevision": "42c66a0697e4f1d3ee09f5a669595d66e100e6e7",
   "platforms": [
     "darwin-arm64",
     "linux-arm64",
@@ -9,16 +9,16 @@
   ],
   "images": {
     "postgres": "postgres@sha256:742f40ea20b9ff2ff31db5458d127452988a2164df9e17441e191f3b72252193",
-    "gateway": "ghcr.io/clawscarf/clawscarf/runtime@sha256:fa6cb6ee1116a17577369166e6d73391f0194b78a69743e4f8bc137dbffb1c5c",
-    "companion": "ghcr.io/clawscarf/clawscarf/companion@sha256:cc2a9f4caf2f9a2e97d198270b8d02cfc7fc082a97c5982eb40e223fe1d2f9a8",
-    "openshellClient": "ghcr.io/clawscarf/clawscarf/openshell-client@sha256:48167a723eac58247b5e07d8266495b7b71e51e72491a1ed63c45e2f1e5590d1",
-    "relay": "ghcr.io/clawscarf/clawscarf/browser-relay@sha256:a6958a6ee43bb6ebcbf18a0aae477a76ac1c8d8c4ed914d319a40dca40571ae7",
+    "gateway": "ghcr.io/clawscarf/clawscarf/runtime@sha256:facac1180479217a9d2508512fe998eb509980b87a855d7c52a8dd7604011eea",
+    "companion": "ghcr.io/clawscarf/clawscarf/companion@sha256:597c060a40d2cb0b858d93322a157e64618e837b9fd061c78064fe8ca9e44191",
+    "openshellClient": "ghcr.io/clawscarf/clawscarf/openshell-client@sha256:a02e79a590510a3947d4930218ad8a686d37846bad1fcbd551ea02c36c4df2a1",
+    "relay": "ghcr.io/clawscarf/clawscarf/browser-relay@sha256:e0684c033305b6d2f85e808645796e5ea4b71a921560c42cf12d93d7c9b1ec10",
     "models": "ghcr.io/berriai/litellm:v1.100.1@sha256:a3715fa7ad8387941ab697259bd2881d68931657247a41984f90fae6d11c62bf",
     "browser": {
-      "chromium": "ghcr.io/clawscarf/clawscarf/browser@sha256:b765e4698c471f26ff50d7f18d14ecf2fb903b92bb22e0299c3758a6429c2121",
-      "node": "ghcr.io/clawscarf/clawscarf/browser-node@sha256:c55268a56d45f65c05f1dd7c5f6a45c2b5cdaefb552606148c42fff0967a7654",
-      "dns": "ghcr.io/clawscarf/clawscarf/browser-dns@sha256:c9d1a557c8bb897eccd2f83693ba3bef71f8fd681e5cd4ce189942460e67e449",
-      "egress": "ghcr.io/clawscarf/clawscarf/browser-egress@sha256:b1b69e03629211ceaf84f7fd6c3bea7fbe659f81b4a4ab00fbc30588810cd970"
+      "chromium": "ghcr.io/clawscarf/clawscarf/browser@sha256:3cef37e3b2de8a8f6fbad677a191837dbe391b720484aa40a5af4ef028d61781",
+      "node": "ghcr.io/clawscarf/clawscarf/browser-node@sha256:b75b37f97b721b1aae5924b70ae78149f519196ed86ac325829f4df99acd67ff",
+      "dns": "ghcr.io/clawscarf/clawscarf/browser-dns@sha256:45b3d18efe12fff755acf00fc2629ca0d8084e215be548003645a6e8183de34f",
+      "egress": "ghcr.io/clawscarf/clawscarf/browser-egress@sha256:cd3a89ad06d35ecf14da695578500f8874362d6789a1590858db6c7f12489c9d"
     }
   },
   "tools": {
@@ -28,34 +28,34 @@
         "darwin-arm64": {
           "file": "tools/darwin-arm64/openshell",
           "sha256": "0baeeffe0e4c184b08fde910ac9e8815fb0b8cfb808e49c0e634d7db65fb03bb",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-darwin-arm64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-darwin-arm64"
         },
         "linux-arm64": {
           "file": "tools/linux-arm64/openshell",
           "sha256": "84df9f059b16b66c83748606cc87d9edcda84b57effea19543f5c368aba7eb18",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-linux-arm64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-linux-arm64"
         },
         "linux-x64": {
           "file": "tools/linux-x64/openshell",
           "sha256": "24e85062073d512d1951c76cd3890b7bce1ab01cc36a08f88b3b43c067a402da",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-linux-x64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-linux-x64"
         }
       },
       "gateway": {
         "darwin-arm64": {
           "file": "tools/darwin-arm64/openshell-gateway",
           "sha256": "298706259ef18350f334c222e981e91583558511d50bce22727c689d261203e6",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-gateway-darwin-arm64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-gateway-darwin-arm64"
         },
         "linux-arm64": {
           "file": "tools/linux-arm64/openshell-gateway",
           "sha256": "0e660428e655e7481f34ba8a4b351554400baf791863d32555c98dddb3f09ae2",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-gateway-linux-arm64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-gateway-linux-arm64"
         },
         "linux-x64": {
           "file": "tools/linux-x64/openshell-gateway",
           "sha256": "780fc7ad871e2163f3fb866a2d0254ee682fc0d83e6261a84b350c8dcdd9f47b",
-          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.3/openshell-gateway-linux-x64"
+          "url": "https://github.com/clawscarf/clawscarf/releases/download/v0.1.0-alpha.5/openshell-gateway-linux-x64"
         }
       }
     }

package/scripts/deployment/certificates.js

@@ -32,6 +32,7 @@ export async function ensureCertificates(directory) {
         const key = createPrivateKey(await readFile(join(directory, "management-key.pem")));
         if (!cert.checkPrivateKey(key) ||
             !cert.checkHost("host.docker.internal") ||
+            !cert.checkHost("companion") ||
             !cert.checkIP("127.0.0.1") ||
             !cert.raw.equals(ca.raw) ||
             !cert.ca ||
@@ -64,7 +65,7 @@ export async function ensureCertificates(directory) {
         "-subj",
         "/CN=ClawScarf local management",
         "-addext",
-        "subjectAltName=DNS:localhost,DNS:host.docker.internal,DNS:models.clawscarf.internal,IP:127.0.0.1",
+        "subjectAltName=DNS:localhost,DNS:companion,DNS:host.docker.internal,DNS:models.clawscarf.internal,IP:127.0.0.1",
         "-addext",
         "basicConstraints=critical,CA:TRUE",
     ]);

package/scripts/deployment/configuration.js

@@ -187,9 +187,6 @@ export const localInput = z
 export function parseLocalInput(value) {
     return localInput.parse(value);
 }
-export function managementOrigin() {
-    return "https://localhost:18801";
-}
 function mountedPrivateFile(directory, path, name) {
     absolutePath.parse(path);
     if (resolve(path) !== join(directory, name))
@@ -225,7 +222,8 @@ export function generateLocalConfiguration(options) {
         },
         runtime: {
             origin: `http://application:${String(input.ports.native)}`,
-            managementOrigin: managementOrigin(),
+            // Native proxy attribution needs the real Docker peer, not a loopback client.
+            managementOrigin: "https://companion:18801",
             widgetOrigin,
             widgetUpstream: `http://widgets:${String(input.ports.nativeWidgets)}`,
         },

package/scripts/deployment/entrypoint.js

@@ -3,5 +3,8 @@ import { fileURLToPath } from "node:url";
 export function nodeEntrypoint(relative) {
     const source = import.meta.url.endsWith(".ts");
     const file = new URL(relative + (source ? ".ts" : ".js"), import.meta.url);
-    return [...(source ? ["--import", "tsx"] : []), fileURLToPath(file)];
+    return [
+        ...(source ? ["--import", import.meta.resolve("tsx")] : []),
+        fileURLToPath(file),
+    ];
 }