Document qualified Windows 2.3.1 release and current downloads

Author: ShadowfetchStudio

README.md

@@ -72,16 +72,15 @@ The code is open source; the Shadowfetch and ShadowCode product identity is cove
   own terminal, go from commit to pull request, preview the app you're
   building, dictate with your voice, and follow along from your phone.
 
-ShadowCode **2.3.0** is the current public release for Windows, Linux and macOS,
-available from [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.3.0)
+ShadowCode **2.3.1** is the current public release for Windows, Linux and macOS,
+available from [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.3.1)
 and [shadowcode.org](https://shadowcode.org/).
 
-**2.3.1 is a release candidate** improving guidance when write delegation is
-requested in a folder without Git history. Its qualification is in progress.
-See the [release notes](docs/RELEASE_NOTES.md),
+This release improves guidance when write delegation is requested in a folder
+without Git history. See the [release notes](docs/RELEASE_NOTES.md),
 [Windows qualification record](docs/WINDOWS_LAPTOP_QUALIFICATION.md), and
 [release history](CHANGELOG.md). Download instructions below use the published
-2.3.0 packages.
+2.3.1 packages.
 
 
 ## Install
@@ -101,10 +100,10 @@ From 2.2.0 each release also carries Flatpak bundles for both architectures
 checked with `ShadowCode_VERSION_flatpak.sha256`; see [Flatpak](docs/FLATPAK.md))
 and macOS disk images (see [macOS](#macos)).
 Check [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases)
-for published versions. The 2.3.0 x86_64 packages and checksums are:
+for published versions. The 2.3.1 x86_64 packages and checksums are:
 
-- `ShadowCode_2.3.0_amd64.AppImage`
-- `ShadowCode_2.3.0_amd64.deb`
+- `ShadowCode_2.3.1_amd64.AppImage`
+- `ShadowCode_2.3.1_amd64.deb`
 - `SHA256SUMS`, `RELEASE-MANIFEST.json`, `RELEASE-AUTH` and
   `RELEASE-AUTH.sig` (download these beside the package; the installer checks
   the publisher's signature before running anything)
@@ -138,7 +137,7 @@ cmake.
 
 ### Windows
 
-Release 2.3.0 includes `ShadowCode_2.3.0_x64-setup.exe` for
+Release 2.3.1 includes `ShadowCode_2.3.1_x64-setup.exe` for
 64-bit Windows 10 (version 1809 or later) and 11, with its SHA-256 checksum in
 `ShadowCode_VERSION_windows.sha256`. It installs for your user only (no
 administrator rights) and includes llama.cpp for local models (CPU) and the
@@ -189,7 +188,7 @@ bundle and bootstrap requirements.
 From that independently authenticated installer bundle, run:
 
 ```bash
-bash /path/to/trusted-bundle/scripts/install-appimage.sh /path/to/downloads/ShadowCode_2.3.0_amd64.AppImage
+bash /path/to/trusted-bundle/scripts/install-appimage.sh /path/to/downloads/ShadowCode_2.3.1_amd64.AppImage
 ```
 
 The installer takes the AppImage path (or `--recover`), resolves its own trusted
@@ -235,7 +234,7 @@ as `--trust-dir` are not installer options.
   cannot corrupt it.
 
 After obtaining and verifying the intended package, run the AppImage without installing it:
-`./ShadowCode_2.3.0_amd64.AppImage --appimage-extract-and-run`. FUSE is not
+`./ShadowCode_2.3.1_amd64.AppImage --appimage-extract-and-run`. FUSE is not
 required.
 
 ### Debian package
@@ -283,16 +282,16 @@ installed. The repository is published by the release workflow only; nothing
 in ShadowCode adds or contacts it by itself.
 
 To install one release by hand instead, verify the Debian artifact using the independently trusted verifier bundle.
-`verified-deb-2.3.0` must not already exist; install the verified snapshot:
+`verified-deb-2.3.1` must not already exist; install the verified snapshot:
 
 ```bash
 bash /path/to/trusted-bundle/scripts/verify-native-release.sh \
   --bundle-dir /path/to/downloads \
   --trust-dir /path/to/trusted-bundle/release/trust \
-  --artifact ShadowCode_2.3.0_amd64.deb \
-  --stage-dir ./verified-deb-2.3.0 \
-  --expect-version 2.3.0
-sudo apt install ./verified-deb-2.3.0/ShadowCode_2.3.0_amd64.deb
+  --artifact ShadowCode_2.3.1_amd64.deb \
+  --stage-dir ./verified-deb-2.3.1 \
+  --expect-version 2.3.1
+sudo apt install ./verified-deb-2.3.1/ShadowCode_2.3.1_amd64.deb
 ```
 
 A `.deb` installed by hand this way gets no updates and none of the APT

docs/DISTRIBUTING.md

@@ -49,7 +49,7 @@ The Flatpak bundles are attached after publication by
 `.github/workflows/release-flatpak.yml` (from 2.2.0), with SHA-256 checksums
 in `ShadowCode_VERSION_flatpak.sha256` rather than publisher signatures; the
 macOS disk images likewise (`release-macos.yml`, `ShadowCode_VERSION_macos.sha256`),
-and, once 2.3.0 is published (Windows is not released yet), the Windows installer with the complete source of its bundled
+and the Windows installer (from 2.3.0), with the complete source of its bundled
 busybox-w32 (`release-windows.yml`, `ShadowCode_VERSION_windows.sha256`).
 
 Releases before 2.1.0 have no aarch64 packages; build them from source (below)

docs/RELEASE_NOTES.md

@@ -1,12 +1,19 @@
-# ShadowCode 2.3.1 — candidate
+# ShadowCode 2.3.1
 
 Write-subagent guidance now names its Git-history prerequisite and directs
 plain-folder tasks to direct editing or read-only agents. A prerequisite check
 runs before worktree preparation, with regression coverage for plain folders,
 unborn repositories and committed repositories.
 
-This candidate is still being qualified. It does not change Windows
-AppContainer permissions: external Git commands that open the null device can
+The public Windows installer passed installation, clean-PATH startup, native
+editor/settings checks and a bounded Gemma 4 E4B coding task on a Windows 11
+x64 laptop. The agent ran tests inside AppContainer; all five original tests
+were preserved and passed independently. Windows local inference is CPU-only;
+Windows 10, ARM, GPU and real cloud-provider accounts remain unqualified on
+that hardware. The installer is not code-signed.
+
+Version 2.3.1 is published for Windows, Linux and macOS. It does not change
+Windows AppContainer permissions: external Git commands that open the null device can
 still fail inside the sandbox. See the [Windows port notes](WINDOWS_PORT.md)
 and [qualification record](WINDOWS_LAPTOP_QUALIFICATION.md). The published
 2.3.0 notes follow below.

docs/RELEASING.md

@@ -1,13 +1,23 @@
 # Release procedure
 
-The most recent documented release is [**2.2.0**](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.2.0), published on October 17, 2026 from `444e75f` by [run 39059462934](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/39059462934) (attempt 1) with all 15 gates on both x86_64 and aarch64, protected signing, publication and the signed APT repository passing. The macOS disk images (Apple silicon and Intel) and the Flatpak bundles were attached afterwards by `release-macos.yml` and `release-flatpak.yml`, dispatched by hand because a release published with `GITHUB_TOKEN` does not trigger other workflows; `release.yml` now dispatches them itself. Before it, [**2.1.0**](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.1.0), published on October 11, 2026 from `a32c2af` by [run 38169859337](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/38169859337) (attempt 3). Updating version files or
-these instructions does not publish or sign a release. Bind final build, test
-and authentication receipts to the exact candidate before publication.
+The current release is [**2.3.1**](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.3.1),
+from `e7fdef1b774affa2d288944b4384dba21a806d46`. The
+[Linux release and signed APT workflow](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/41248454973),
+[Windows installer](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/41253795862),
+[macOS disk images](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/41253793352),
+and [Flatpak bundles](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/41253794538)
+all passed and published their assets. Public downloads were verified against
+their release checksums; Linux packages and the APT indexes also passed
+publisher-signature verification. The Windows laptop checks are recorded
+separately in [the qualification record](WINDOWS_LAPTOP_QUALIFICATION.md).
+Updating version files or these instructions does not publish or sign a release.
+Bind final build, test and authentication receipts to the exact candidate before
+publication.
 
 Pushing a `v*` tag starts `.github/workflows/release.yml`. Publication follows
 build/qualification, protected signing review and verification of all seven
-public assets. The signing environment must permit the tag being released. As verified
-on October 31, 2026, it permits `v2.3.0`, updated after PR #11 passed
+public assets for each Linux architecture. The signing environment must permit the tag being released. As verified
+for 2.3.1, it permits `v2.3.1`, updated after PR #12 passed
 Windows, both macOS architectures, and both Linux qualification jobs. Every later version needs reviewed trust-policy,
 deployment-rule and tooling-pin updates. The workflow uses
 `docs/RELEASE_NOTES.md` as the release text.
@@ -186,18 +196,18 @@ verifies and indexes both `.deb` files. The pinned tooling commit must include
 this multi-target signer and publisher; an older pin refuses the aarch64
 signing call, so the release fails rather than shipping x86_64 alone.
 
-Public trust in `release/trust` currently allows the x86_64 and aarch64 targets, epoch 1 and versions 0.33.0–2.3.0
+Public trust in `release/trust` currently allows the x86_64 and aarch64 targets, epoch 1 and versions 0.33.0–2.3.1
 (raise the key's maximum version in the release commit, as for earlier releases);
 `release/install-policy` fixes the first authenticated version at 0.33.0.
 The `release-signing` environment has the signing secret and requires review by
 `ShadowfetchStudio` (User ID `209457103`). Self-review is allowed and GitHub's
-default administrator override remains unchanged. For 2.3.0 its sole
-deployment rule is `v2.3.0`, updated after candidate qualification on
+default administrator override remains unchanged. For 2.3.1 its sole
+deployment rule is `v2.3.1`, updated after candidate qualification on
 October 31, 2026. `NATIVE_RELEASE_SIGNING_ENVIRONMENT` points to
 `release-signing`. Before pushing the tag, set `NATIVE_RELEASE_TOOLING_COMMIT`
-to the reviewed tagged release commit itself and read it back. The prior
-2.2.0 pin was `444e75f13c3512d57c226b39d6edf59fdb08a4c6`; it must not be
-reused for this release. A permitted tag does not prove publication.
+to the reviewed tagged release commit itself and read it back. The verified
+2.3.1 pin is `e7fdef1b774affa2d288944b4384dba21a806d46`. A permitted tag
+does not prove publication.
 
 Before tagging, finish review and push the tooling commit, then set
 `NATIVE_RELEASE_TOOLING_COMMIT` to that exact 40-character SHA. Read back this pin from GitHub configuration before dispatching the release. Verify the environment protections and source/candidate

docs/WINDOWS_LAPTOP_QUALIFICATION.md

@@ -1,5 +1,10 @@
 # Windows laptop qualification — October 31, 2026
 
+Current status: the **public Windows 2.3.1 installer passed** the bounded laptop
+qualification. See [the final public-installer record](#231-public-installer-qualification)
+for its exact hashes and results. Earlier sections retain the development and
+preview history, including failures.
+
 Test machine: Windows 11 Home x64, Ryzen 3 5300U, 32 GB RAM. Baseline:
 `9c82cae76d4c94a4416405c93f00e198080a18ac`, Windows CI preview 2.3.0.
 Tests use disposable profiles and projects; no vendor credentials are needed.
@@ -217,7 +222,7 @@ all distribution patches verified against APKBUILD SHA-512 values. Full
 packaging qualification must pass on the refreshed inputs. Both Apple
 silicon and Intel macOS builds passed in run 41219097984.
 
-## Latest merged-main candidate
+## 2.3.0 merged-main candidate
 
 Source commit: `0b255b89874b1216530b3e8b7c51470f30d7020e` (PR #11).
 The Windows release-workflow artifact from
@@ -301,3 +306,33 @@ benchmark or proof about a different release installer. The final published
 installer requires its own verification. An earlier development-binary run
 omitted the sandbox shell path and could not execute its test; it was not
 counted as a passing qualification.
+
+
+## 2.3.1 public installer qualification
+
+Release source: `e7fdef1b774affa2d288944b4384dba21a806d46`.
+The public `ShadowCode_2.3.1_x64-setup.exe` came from successful
+[Windows release run 41253795862](https://github.com/ShadowfetchStudio/ShadowCode/actions/runs/41253795862).
+Its download size, published SHA-256 checksum and GitHub asset digest matched.
+Installer SHA-256: `7a957342206b1413ecaf153f284880bc5df562971094c50b703096bbb26a3bba`.
+Installed executable SHA-256: `62c405b64b18c440eda1300d08f39056dab6d546d4b604eb8c0026095bfb55f2`.
+
+The official PowerShell installer was exercised with the verified public files
+via its local setup-directory option. Clean-PATH checks passed for the desktop,
+llama-server and llama-cli, including the isolated-profile async CLI status call.
+The native WebView test passed editor replace-all, undo, Ctrl+Shift+Z and Ctrl+Y
+redo, disk-verified save and settings visibility, with no observed page errors.
+
+The fresh Gemma 4 E4B Q4_0 task started at `2026-11-01T00:40:14.865078+00:00` and finished in
+352.77 seconds. The agent returned exit 0 and executed the exact
+`python3 -m unittest -q` command inside AppContainer, returning all five tests
+passing. The independent verifier also returned exit 0; all five original tests
+were unchanged. The run used a 16,384-token context and a 100,000-token task
+budget. It read files, edited the helper and ran its tests; the event record
+contains no subagent or external Git attempt.
+
+This qualifies these exact public bytes and this bounded fixture on this laptop.
+Windows 10, Windows ARM, GPU inference and real cloud-provider accounts were not
+qualified on this hardware. The Windows runtime is CPU-only, the installer is
+not code-signed, and the external-Git/null-device limitation remains documented
+in the port notes. No permissions were relaxed to obtain this result.

docs/WINDOWS_PORT.md

@@ -1,20 +1,21 @@
 # Windows port
 
-Status: Windows 2.3.0 is published. Installation, clean-PATH startup and native
-editor checks passed on a Windows 11 Home x64 laptop (Ryzen 3 5300U, 32 GB RAM).
-The latest public-installer model run repaired the test fixture but exited
-unsuccessfully after failed delegation attempts; it is not a qualification pass.
-Version 2.3.1 is a follow-up candidate with clearer delegation prerequisites.
-See [the laptop qualification record](WINDOWS_LAPTOP_QUALIFICATION.md) for exact
-artifact evidence, failed attempts and remaining limitations.
+Status: Windows 2.3.1 is published. The exact public installer passed installation,
+clean-PATH startup, native editor/settings checks and a local-model coding task
+on a Windows 11 Home x64 laptop (Ryzen 3 5300U, 32 GB RAM). Gemma 4 E4B on CPU
+completed the repair, executed its tests inside AppContainer, and preserved all
+five original tests; the independent check also passed. This is one bounded
+fixture, not a broad model-reliability or Windows-hardware benchmark.
+See [the laptop qualification record](WINDOWS_LAPTOP_QUALIFICATION.md#231-public-installer-qualification)
+for exact hashes, workflow provenance, earlier failed attempts and limitations.
 
 External programs that open the Windows null device themselves can fail in
-AppContainer; external Git commands demonstrated this in the public-installer
+AppContainer; external Git commands demonstrated this in the 2.3.0 public-installer
 run. The patched bundled shell has an inherited null handle, but this does not
 make every external program compatible. Use the app's dedicated Git operations
 for supported repository actions or run explicit Git setup in the terminal.
 Write subagents require an existing repository with a commit; ordinary file
-editing and read-only delegation do not. The follow-up does not weaken the
+editing and read-only delegation do not. Version 2.3.1 does not weaken the
 sandbox or grant device access.