fix(release): bump tauri.conf.json version + sync into cut-release skill (#92)

Author: delexw

.claude/skills/cut-release/references/project-shape.md

@@ -15,17 +15,21 @@ codebase, this file points at the source of truth rather than repeating it.
 
 ## Version-bearing files (skill-specific rule)
 
-Three files must agree on the next-version string. Nothing in the codebase enforces this
+Four files must agree on the next-version string. Nothing in the codebase enforces this
 sync — the skill does.
 
-| File                   | Owns                             | Bumps with                                 |
-| ---------------------- | -------------------------------- | ------------------------------------------ |
-| `package.json` (root)  | Node/TS workspace + binary entry | the Rust crate (lockstep)                  |
-| `src-tauri/Cargo.toml` | Rust crate version               | root `package.json` (lockstep)             |
-| `tui/package.json`     | Terminal UI subpackage           | independently; bumps when TUI code changes |
-
-Root + Cargo move together because the desktop binary the user installs is built from
-both. `tui/package.json` tracks separately because it's shipped as its own npm package.
+| File                        | Owns                                 | Bumps with                                 |
+| --------------------------- | ------------------------------------ | ------------------------------------------ |
+| `package.json` (root)       | Node/TS workspace + binary entry     | the Rust crate (lockstep)                  |
+| `src-tauri/Cargo.toml`      | Rust crate version                   | root `package.json` (lockstep)             |
+| `src-tauri/tauri.conf.json` | Tauri bundle filenames + app version | the Rust crate (lockstep)                  |
+| `tui/package.json`          | Terminal UI subpackage               | independently; bumps when TUI code changes |
+
+Root + Cargo + `tauri.conf.json` move together because the desktop binary the user installs
+is built from all three — `tauri.conf.json`'s `version` field is what `tauri-action`
+templates into the released artifact filenames (`Claude.Code.Trace_<version>_*.dmg`, etc.).
+Missing this file silently ships a release whose artifacts are stamped with the previous
+version. `tui/package.json` tracks separately because it's shipped as its own npm package.
 
 ## Lockfile regen after a version bump
 

.claude/skills/cut-release/steps/phase3-bump-versions.md

@@ -6,19 +6,26 @@ lockfiles.
 Refer to `${CLAUDE_SKILL_DIR}/references/project-shape.md` for the rules on which files
 move in lockstep and which move independently.
 
-## Step 3.1 — Bump root + Cargo (always lockstep)
+## Step 3.1 — Bump root + Cargo + Tauri config (always lockstep)
 
 ```bash
 # Root package.json
 # Edit: "version": "<old>" → "version": "<NEXT_VERSION>"
 
 # src-tauri/Cargo.toml
 # Edit: version = "<old>" → version = "<NEXT_VERSION>"
+
+# src-tauri/tauri.conf.json
+# Edit: "version": "<old>" → "version": "<NEXT_VERSION>"
 ```
 
 Use the Edit tool with `old_string`/`new_string` rather than sed — safer for surrounding
 context.
 
+`tauri.conf.json` is the field `tauri-action` reads when stamping artifact filenames at
+build time (`Claude.Code.Trace_<version>_*.dmg`, etc.). Skipping it produces a release
+whose artifacts are still named with the previous version — the symptom seen on v0.5.1.
+
 ## Step 3.2 — Bump TUI version
 
 If the chosen subset contains any commit that modifies files under `tui/`, bump

src-tauri/tauri.conf.json

@@ -1,6 +1,6 @@
 {
   "productName": "Claude Code Trace",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "identifier": "com.claudecodetrace.app",
   "build": {
     "devUrl": "http://localhost:1420",