chore(release): prepare v1.6.8 navigation polish

Refs #15
Refs #16

Proof:
- Frontend (typecheck + build): pass
- Rust (fmt + clippy + check): pass
- E2E (Playwright over WebView2): pass
- Local frontend tests/check/build: pass
- Local cargo fmt/check/clippy: pass

Author: xt0n1-t3ch

CHANGELOG.md

@@ -5,6 +5,24 @@ All notable changes to DLSSync are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.6.8] - 2026-06-12
+
+The navigation-polish release. DLSSync now respects the back and forward side buttons on gaming mice, but keeps that movement inside the app instead of handing it to Chromium history. You can jump back to the previous menu, restore the next app state when one exists, and reopen or close the game-detail drawer through the same history stack.
+
+### Added
+
+- Mouse side-button navigation across DLSSync app state: button 3 goes back and button 4 goes forward through views and game-detail drawer open/close states.
+- A small app-navigation history contract with unit coverage for back/forward movement, duplicate-state suppression, forward-branch dropping after new navigation, and mouse-button mapping.
+
+### Changed
+
+- The app shell now intercepts recognized side-button `mouseup` events and writes the target state back into `currentView` and `drawerGameId`, so browser history is never used for internal navigation.
+- README and release-marketing docs now point at v1.6.8 as the current public release line.
+
+### Fixed
+
+- Mouse users no longer have to return to the sidebar or keyboard shortcuts just to move back to the previous DLSSync menu or detail-drawer state.
+
 ## [1.6.7] - 2026-06-10
 
 The vendor-parity, trust, and color release. AMD one-click driver install works now — it was quietly broken before. The catalog is cryptographically enforced: a tampered manifest is rejected, and an offline first run still loads a signed catalog instead of a blank screen. Two full security passes closed holes around the driver installer, backup restore, elevated restores, and downloads. FSR and XeSS now update as coherent multi-DLL sets in one atomic click — with a hardware gate so FSR 4 is never pushed onto a GPU that can't run it. And the whole interface learned to speak in color: vendor-brand tech badges, a status hero in the Library, traffic-light state everywhere, and game art that tints the app around it.
@@ -222,6 +240,7 @@ of the Arc desktop package, and install progress no longer breaks when you switc
 - AMD opens its official download page instead of a constructed installer URL. The direct `.exe` is gated behind a license prompt and its filename changes per release, so a fabricated link was unreliable; version and changelog detection are unchanged.
 - Vendor installer exit codes are reported with a readable message. Intel's "no compatible device" (exit code 8) now explains the GPU may be OEM-locked or need a different driver branch, pointing to the manufacturer or Windows Update.
 
+[1.6.8]: https://github.com/xt0n1-t3ch/DLSSync/releases/tag/v1.6.8
 [1.6.7]: https://github.com/xt0n1-t3ch/DLSSync/releases/tag/v1.6.7
 [1.6.6]: https://github.com/xt0n1-t3ch/DLSSync/releases/tag/v1.6.6
 [1.6.5]: https://github.com/xt0n1-t3ch/DLSSync/releases/tag/v1.6.5

Cargo.lock

@@ -3,7 +3,7 @@ resolver = "2"
 members = ["src-tauri", "crates/*"]
 
 [workspace.package]
-version = "1.6.7"
+version = "1.6.8"
 edition = "2021"
 license = "Apache-2.0"
 repository = "https://github.com/xt0n1-t3ch/DLSSync"

Cargo.toml

@@ -18,7 +18,7 @@
 </p>
 
 <p align="center">
-  <sub><b>New in v1.6.7:</b> AMD one-click driver install, signed manifest enforcement, hardware-gated FSR/XeSS set updates, reverted-swap detection, catalog fallback, and a cleaner color-coded interface. See <a href="CHANGELOG.md#167---2026-06-10">CHANGELOG</a>.</sub>
+  <sub><b>New in v1.6.8:</b> mouse side buttons now move backward and forward through DLSSync menus and the game-detail drawer, with the v1.6.7 driver, manifest, catalog, and color-system work carried forward. See <a href="CHANGELOG.md#168---2026-06-12">CHANGELOG</a>.</sub>
 </p>
 
 <p align="center">
@@ -226,7 +226,7 @@ The DLL-sync path has no driver, no kernel-mode hook, no in-process injection 
 
 <p align="center">
   <a href="https://github.com/xt0n1-t3ch/DLSSync/releases/latest">
-    <img src="./.github/assets/download-button.svg" alt="Download DLSSync v1.6.7 for Windows 10 / 11" width="520"/>
+    <img src="./.github/assets/download-button.svg" alt="Download DLSSync v1.6.8 for Windows 10 / 11" width="520"/>
   </a>
 </p>
 

README.md

@@ -8,7 +8,7 @@
 | [anticheat.md](anticheat.md) | Per-game anti-cheat detection (local binary scan + bundled dataset) and the false-positive ban warning shown before any DLL swap or DLSS override |
 | [cdp-validation.md](cdp-validation.md) | Visual validation via CDP: attach to the app's own WebView2 remote-debugging port (NOT Edge, NOT localhost), `Page.captureScreenshot` regardless of foreground, and why the other approaches fail |
 | [translations.md](translations.md) | Contributor + translator guide for the i18n catalogs: where every UI string lives (`locales/<locale>.json`), the `area.component.purpose` key scheme, `{placeholder}` and `_one`/`_other` plural rules, the `_meta.json` sidecar, how to translate or add a language without touching code, the two parity validators, and what a parity failure looks like |
-| [release-marketing.md](release-marketing.md) | GitHub/Nexus discovery strategy, current v1.6.7 value proposition, SEO-safe wording, Nexus description order, and the canonical public asset map |
+| [release-marketing.md](release-marketing.md) | GitHub/Nexus discovery strategy, current v1.6.8 value proposition, SEO-safe wording, Nexus description order, and the canonical public asset map |
 
 Project-level references live at the repo root: [README.md](../README.md),
 [CHANGELOG.md](../CHANGELOG.md), and the test-suite index at [tests/index.md](../tests/index.md).

docs/index.md

@@ -9,7 +9,7 @@ DLSSync should be discoverable without looking like keyword spam. The public pro
 - Lead with the minimalist banner: `.github/assets/nexus/banner-2560x720.png`.
 - Keep the first paragraph under 90 words and include the real search phrases users type: DLSS updater, FSR updater, XeSS updater, GPU driver updater, DLSS swapper alternative.
 - Keep the visible "Also useful if you searched for" line. Do not hide a keyword block in HTML comments.
-- Keep the release chip current with the exact app version and changelog anchor.
+- Keep the release chip current with the exact app version and changelog anchor. For v1.6.8, the public hook is mouse side-button back/forward navigation through DLSSync menus and the game-detail drawer, plus the v1.6.7 trust/driver foundation.
 - Keep security claims tied to the implementation: signed manifest, SHA-256 catalog hashes, Authenticode publisher gate, official vendor domains, local backup snapshots, one-click rollback, zero telemetry.
 
 ## Nexus Mods

docs/release-marketing.md

@@ -1,7 +1,7 @@
 {
   "name": "dlssync-frontend",
   "private": true,
-  "version": "1.6.7",
+  "version": "1.6.8",
   "type": "module",
   "scripts": {
     "dev": "vite",

frontend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dlssync",
-  "version": "1.6.7",
+  "version": "1.6.8",
   "private": true,
   "scripts": {
     "dev": "tauri dev",

package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://schema.tauri.app/config/2",
   "productName": "DLSSync",
-  "version": "1.6.7",
+  "version": "1.6.8",
   "identifier": "io.github.xt0n1-t3ch.dlssync",
   "build": {
     "beforeBuildCommand": "pnpm -w run prebuild:kill && pnpm --filter dlssync-frontend build",