Excess Worker 0.2.3

Release sequence 32. Anonymous Minisign release signing. Windows executables have no trusted Authenticode publisher signature.

Changes since 0.2.2: the worker status now records why the last job failed or was cancelled (lastJobFailure: job and attempt IDs, outcome and a fixed reason code). Error messages are never recorded, because they can quote prompts, outputs, paths or responses.

Windows CPU/CUDA: the eight release-gate routes passed, plus Phi-4-mini, Qwen3-8B and Llama 3.1 8B on CPU and CUDA, and Phi-4, Qwen3-14B and gpt-oss-20b on CPU. Linux CPU (WSL2): Qwen3-4B, Qwen3-8B and Qwen3-14B passed. See docs/verification/candidate31-other-models.md.

Linux NVIDIA CUDA: the signed 0.2.3 candidate, with the same worker payload as this release, ran actual buyer jobs for all 17 pinned local catalogue models on one recorded NVIDIA B300 configuration (driver 580.178.04, CUDA 12.9). Drain, restart, revocation and cleanup passed there. Cancelled text, image, transcription and embedding jobs ended with no charge; the runtime monitor recorded the runtime stopping for transcription and embedding only. GPU memory budgets are sampled whole-device limits, not hard partitions. Other GPUs, drivers and distributions are unverified. See docs/verification/linux-b300-cuda-sequence31.md.

Updating: Windows and Linux 0.2.2 installations update with excess-worker update after draining. See docs/INSTALLATION.md ("Stop, revoke and update").

Excess Worker 0.2.2

Release sequence 30. Anonymous Minisign release signing. Windows executables have no trusted Authenticode publisher signature.

Changes since 0.2.1: streamed text is metered correctly when the pinned llama.cpp runtime withholds token IDs inside a multibyte character (seen with gpt-oss), so those jobs no longer fail.

Linux NVIDIA CUDA: the signed 0.2.2 candidate, with the same worker payload as this release, ran actual buyer jobs for all 17 pinned local catalogue models on one recorded NVIDIA B300 configuration (driver 580.178.04, CUDA 12.9). Drain, restart, revocation and cleanup passed there. GPU memory budgets are sampled whole-device limits, not hard partitions. Other GPUs, drivers and distributions are unverified. See docs/verification/linux-b300-cuda-sequence29.md.

Windows CPU/CUDA: the eight release-gate routes passed, plus Phi-4-mini and Qwen3-8B on CPU and CUDA. Linux CPU (WSL2): Qwen3-4B, Qwen3-8B and Qwen3-14B passed. See docs/verification/candidate29-other-models.md.

Updating: Windows and Linux 0.2.1 installations update with excess-worker update after draining. Linux 0.2.0 installations still upgrade by running the verified 0.2.2 installer in place. See docs/INSTALLATION.md ("Stop, revoke and update").

Excess Worker 0.2.1

Release sequence 28. Anonymous Minisign release signing. Windows executables have no trusted Authenticode publisher signature.

Linux 0.2.0 installations: excess-worker update in 0.2.0 refuses this package because the 0.2.0 updater accepts only the earlier GPU helper profile; it leaves 0.2.0 unchanged. Drain the worker, verify the downloaded files, then run the 0.2.1 install.sh over the same install location. Windows 0.2.0 installations update with excess-worker update. See docs/INSTALLATION.md ("Stop, revoke and update").

Excess Worker 0.2.0

Excess Worker 0.2.0 improves the bounded Windows native admission ordering and publishes the verified successor to 0.1.0.

Recorded execution covers eight Windows buyer routes (four models, CPU and CUDA) and five additional serial SD-Turbo CUDA jobs. Linux Qwen3-4B CPU execution was verified on the recorded WSL2 configuration. The final release reuses that execution evidence through verified unchanged executable payloads and passes signed installation, authenticated updates, tamper/downgrade refusal and actual recovery probes. The original intermittent CUDA buyer failure has no established cause; the native ordering fixture and the successful repeat jobs are scoped evidence.

Linux NVIDIA execution remains candidate-unverified. Catalogue availability and estimated hardware fit do not establish successful execution. See verification and model coverage.

Authenticate release.json with the established project Minisign key before installing. The signed manifest authenticates the archive hashes. Windows executables have no trusted Authenticode publisher signature. Two independent clean builds produced identical archives. Release 0.1.0, its tag, assets and signing key are retained.

Excess Worker 0.1.0

Excess Worker 0.1.0 packages a supplier worker with anonymous Minisign release authentication and isolated inference.

Verified configurations: Windows x64 CPU, Windows11 x64 CUDA Qwen3-4B on RTX3070Ti/driver596.49 WDDM with separate6GiB host/GPU budgets, and WSL2 Linux x64 CPU in a bounded cgroupv2 service. The GPU watchdog measures combined dedicated/shared process usage; it is not a hard VRAM reservation or hardware fault partition. Linux GPU remains unsupported/refused.

Fresh application installation, live HTTPS pairing, project-funded testnet buyer inference, correct output, device-signed receipts/accounting, drain, restart, revoke and cleanup are verified. Windows CPU/CUDA also verify live buyer cancellation. Controlled HTTPS updates verify the real signed packages, pinned key, integrity, tamper/downgrade refusal and high-water-preserving rollback/recovery. These are measured workstation configurations, not fresh operating systems, independent suppliers or organic demand.

Download the archive for your platform plus release.json and release.json.minisig. Establish the anonymous project key from a trusted checkout at releases/minisign.pub; then verify the signature and the authenticated filename, size and SHA256 before running the offline installer from scripts/worker-install. Model/runtime downloads are separate, opt-in, hash-pinned and licensed.

Windows executables have no trusted Authenticode publisher signature. Trusted Windows publisher signing, paid certificates and identity verification are outside scope. Complete assembled archives reproduce across independent A/B builds; official Node/model/runtime binaries and OS/driver/toolchain dependencies are external pinned inputs, not independently rebuilt upstream source.

Source: 2980a6e
Release sequence:18. See the current platform and verification documentation in the repository.