Docs: 0.34.2 is the published release (run 36515721147)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: ShadowfetchStudio

docs/FLAGSHIP_IMPLEMENTATION.md

@@ -4,7 +4,7 @@ Goal: a dependable, easy-to-use native workspace combining supported vendor logi
 
 Baseline: `e371baaa4c690527173a322f7e0e1cfae4db329a`. Implementation branch: `flagship/reliability-foundation`. Preserve the existing architecture and provider integrations. The complete [acceptance specification](FLAGSHIP_ACCEPTANCE_SPEC.md) remains in scope; this ledger is not a narrowed definition of completion.
 
-Current release checkpoint (September 28, 2026): signed **0.33.1 is published and installed**; 0.34.2 is prepared (see [the 0.34 pass](#034-consolidation-and-consumer-readiness-pass)), with retained data and successful installed-window checks. See [the final release and installation evidence](#signed-0331-publication-and-installed-app-verification). Earlier pending statements below describe their historical checkpoints. Broader physical desktop, GPU endurance and live provider lifecycle acceptance remain open.
+Current release checkpoint (September 28, 2026): signed **0.33.1 is published and installed**; **0.34.2 is published** (run 36515721147: all 15 gates, signing and publication passed; installed here with the authenticated installer; see [the 0.34 pass](#034-consolidation-and-consumer-readiness-pass)), with retained data and successful installed-window checks. See [the final release and installation evidence](#signed-0331-publication-and-installed-app-verification). Earlier pending statements below describe their historical checkpoints. Broader physical desktop, GPU endurance and live provider lifecycle acceptance remain open.
 
 ## 0.34 consolidation and consumer-readiness pass
 

docs/RELEASE_AUTHENTICATION.md

@@ -4,6 +4,10 @@ The helpers in `scripts/native-release-auth.mjs` and `scripts/verify-native-rele
 
 The Bash verifier loads `scripts/native-release-auth-lib.sh` from its own script directory. Keep both reviewed code files together in the trusted tooling bundle; do not obtain the library from the candidate download or source metadata as shell code. The installer uses the same reviewed routines for current candidates and signed historical receipts; it never sources release metadata as code.
 
+## Published release: 0.34.2
+
+[Version 0.34.2](https://github.com/Shadowfetchapps/ShadowCode/releases/tag/v0.34.2) was published on September 29, 2026 from `3f81044e1fe3d8f24cc1293e8efde79db5533213` by [run 36515721147](https://github.com/Shadowfetchapps/ShadowCode/actions/runs/36515721147): all 15 required gates, protected signing and publication completed in the workflow. The downloaded AppImage and .deb verify with `verify-native-release.sh` against the tracked trust bundle, and the authenticated installer upgraded an installed 0.33.1 to it. The `v0.34.0` and `v0.34.1` attempts stopped in required gates before signing and stay unchanged (see [RELEASING.md](RELEASING.md)).
+
 ## Published release: 0.33.1
 
 The `v0.33.0` release attempt at `9e385cb` failed its source-integrity gate

docs/RELEASING.md

@@ -1,6 +1,6 @@
 # Release procedure
 
-The most recent documented release is [**0.33.1**](https://github.com/Shadowfetchapps/ShadowCode/releases/tag/v0.33.1). Updating version files or
+The most recent documented release is [**0.34.2**](https://github.com/Shadowfetchapps/ShadowCode/releases/tag/v0.34.2), published on September 29, 2026 from `3f81044` by [run 36515721147](https://github.com/Shadowfetchapps/ShadowCode/actions/runs/36515721147) with all 15 gates, protected signing and publication passing. 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.