@fabr-client/core 1.0.6 → 1.0.8

package/README.md

@@ -36,10 +36,11 @@ cannot be resolved, prints the final absolute path and size, and does not upload
 the bundle to a server.
 
 The main package is a thin launcher. It installs the matching native payload
-through platform-specific optional dependencies, so end users only need the one
-global install command above. Each platform payload contains `bin/fabr-client`
-plus the managed Codex Runtime executable at `bin/runtime/codex` (`.exe` on
-Windows).
+through platform-specific optional dependencies, so end users only need the one
+global install command above. Each platform payload contains `bin/fabr-client`
+plus the managed Codex Runtime payload under `bin/runtime/`. The official Codex
+entrypoint is `bin/runtime/bin/codex` (`.exe` on Windows), and helper
+binaries/resources from the official platform release are bundled with it.
 
 ## Platform Support
 
@@ -67,49 +68,88 @@ Use `latest` only for stable production versions such as `0.1.19`. Use
 prerelease versions for test channels, for example `0.1.19-beta.0` or
 `0.1.19-rc.0`.
 
-For maintainers, build the Windows payload with PowerShell:
-
-```powershell
-pwsh ./scripts/package-fabr-client.ps1 `
-  -Profile release `
-  -PackNpm `
-  -CodexRuntimeMode build `
-  -CodexRuntimeRepo C:\path\to\codex-runtime
-```
-
-On macOS, build both `darwin-x64` and `darwin-arm64` payloads:
+For maintainers, build the Windows payload with PowerShell:
+
+```powershell
+pwsh ./scripts/package-fabr-client.ps1 `
+  -Profile release `
+  -PackNpm `
+  -CodexRuntimeMode official `
+  -CodexRuntimeVersion 0.152.0
+```
+
+On macOS, build both `darwin-x64` and `darwin-arm64` payloads:
 
 ```bash
-./scripts/package-macos-all.sh \
-  --profile release \
-  --pack-npm \
-  --codex-runtime-mode build \
-  --codex-runtime-repo /path/to/codex-runtime
-```
-
-On Linux ARM64, build the `linux-arm64` payload on an ARM64 Linux build host:
+./scripts/package-macos-all.sh \
+  --profile release \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0
+```
+
+On Linux ARM64, build the `linux-arm64` payload on an ARM64 Linux build host:
 
 ```bash
 ./scripts/package-fabr-client.sh \
-  --profile release \
-  --target aarch64-unknown-linux-gnu \
-  --pack-npm \
-  --codex-runtime-mode build \
-  --codex-runtime-repo /path/to/codex-runtime
-```
-
-On Linux x64, build the `linux-x64` payload on an x86_64 Linux build host:
-
-```bash
-./scripts/package-fabr-client.sh \
-  --profile release \
-  --target x86_64-unknown-linux-gnu \
-  --pack-npm \
-  --codex-runtime-mode staged \
-  --codex-runtime-bin /path/to/codex-x86_64-linux-binary
-```
-
-## Release Artifact Manifest
+  --profile release \
+  --target aarch64-unknown-linux-gnu \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0
+```
+
+On Linux x64, build the `linux-x64` payload on an x86_64 Linux build host:
+
+```bash
+./scripts/package-linux-x64.sh \
+  --profile release \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0
+```
+
+Offline packaging can use a local official platform archive:
+
+```bash
+./scripts/package-linux-x64.sh \
+  --profile release \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0 \
+  --codex-runtime-release-file-linux-x64 /path/to/codex-0.152.0-linux-x64.tgz
+```
+
+```bash
+./scripts/package-fabr-client.sh \
+  --profile release \
+  --target aarch64-unknown-linux-gnu \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0 \
+  --codex-runtime-release-file /path/to/codex-0.152.0-linux-arm64.tgz
+```
+
+macOS offline packaging requires separate release archives per architecture:
+
+```bash
+./scripts/package-macos-all.sh \
+  --profile release \
+  --pack-npm \
+  --codex-runtime-mode official \
+  --codex-runtime-version 0.152.0 \
+  --codex-runtime-release-file-darwin-x64 /path/to/codex-0.152.0-darwin-x64.tgz \
+  --codex-runtime-release-file-darwin-arm64 /path/to/codex-0.152.0-darwin-arm64.tgz
+```
+
+For local debugging, maintainers can still use `staged` with a raw executable
+or `build` with a local `codex-runtime` checkout:
+
+```powershell
+pwsh ./scripts/package-fabr-client.ps1 -Profile release -PackNpm -CodexRuntimeMode staged -CodexRuntimeBin C:\path\to\codex.exe
+```
+
+## Release Artifact Manifest
 
 Desktop installers consume versioned release artifacts and checksums instead of
 importing source files from this repository. Place finalized payload archives in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fabr-client/core",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "Cross-platform launcher for Fabr Client",
   "license": "MIT",
   "homepage": "https://pivot.enclaws.com",
@@ -19,11 +19,11 @@
     "smoke": "node bin/fabr-client.js --help"
   },
   "optionalDependencies": {
-    "@fabr-client/core-win32-x64": "1.0.6",
-    "@fabr-client/core-darwin-x64": "1.0.6",
-    "@fabr-client/core-darwin-arm64": "1.0.6",
-    "@fabr-client/core-linux-arm64": "1.0.6",
-    "@fabr-client/core-linux-x64": "1.0.6"
+    "@fabr-client/core-win32-x64": "1.0.8",
+    "@fabr-client/core-darwin-x64": "1.0.8",
+    "@fabr-client/core-darwin-arm64": "1.0.8",
+    "@fabr-client/core-linux-arm64": "1.0.8",
+    "@fabr-client/core-linux-x64": "1.0.8"
   },
   "files": [
     "bin/",