Release v0.4.24: add missing harnesses during updates

AGENTS.md

@@ -12,13 +12,13 @@ Also hosted: https://vaultedagent.com/AGENTS.md
 
 Glossary for domain terms (harness, manifest, backend, …): [CONTEXT.md](CONTEXT.md).
 
-Current release pin (product install): **v0.4.23**
+Current release pin (product install): **v0.4.24**
 
 ```bash
 curl -fsSL https://vaultedagent.com/install.sh | bash
 # pin:
-VAULTED_AGENT_VERSION=v0.4.23 curl -fsSL https://vaultedagent.com/install.sh | bash
-vaulted-agent version   # expect 0.4.23 (git stamp may appear in parentheses)
+VAULTED_AGENT_VERSION=v0.4.24 curl -fsSL https://vaultedagent.com/install.sh | bash
+vaulted-agent version   # expect 0.4.24 (git stamp may appear in parentheses)
 ```
 
 ## What you must not do
@@ -80,7 +80,7 @@ elevated launches always read the machine config dir).
 | Auth mode | `va auth-mode` / `va auth-mode prompt` / `va auth-mode file` |
 | Interactive install-time config | `va setup` |
 | Store / rotate the manager token | `printf %s "$TOKEN" \| sudo va setup bitwarden --set-token` |
-| Replace the installed launcher binary | `va update` (latest GitHub release) / `va update v0.4.23` |
+| Replace the installed launcher binary | `va update` (latest GitHub release) / `va update v0.4.24` |
 | Uninstall | `sudo va uninstall` |
 
 Launcher flags **before** the harness name: `-p` / `--prompt-auth`,

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "vaulted-agent"
-version = "0.4.23"
+version = "0.4.24"
 edition = "2021"
 description = "Launch AI coding agents with vault-resolved secrets in-process"
 license = "MIT"

MIGRATION.md

@@ -1,4 +1,4 @@
-# Migration: updates add missing Harnesses (unreleased)
+# Migration: updates add missing Harnesses (v0.4.24)
 
 `va update` now asks the newly installed binary to create missing Harnesses for
 detected agents. Existing profiles stay unchanged. New profiles inherit a
@@ -37,7 +37,7 @@ refresh. `va update` (or a reinstall) is the way off that writer.
 `va update` downloads a GitHub release asset for this OS/arch and overwrites
 the running launcher (`current_exe`, usually `/usr/local/bin/vaulted-agent`).
 Default target is `VAULTED_AGENT_VERSION`, else the latest GitHub release.
-`va update v0.4.23` pins. `--check` and `--dry-run` write nothing.
+`va update v0.4.24` pins. `--check` and `--dry-run` write nothing.
 
 This is not `install.sh`. Existing Harnesses, manifests, and token files stay
 put; newer updaters add missing Harnesses as described above. If the binary

README.md

@@ -37,7 +37,7 @@ curl -fsSL https://vaultedagent.com/install.sh | bash
 
 Installs `vaulted-agent` and `va`, detects agents on PATH (`claude`, `codex`,
 `grok`, `kimi`, `agy`, `muse`) and `bash`, and can ask for a vault backend + auth mode. Pin:
-`VAULTED_AGENT_VERSION=v0.4.23` (or `latest`).
+`VAULTED_AGENT_VERSION=v0.4.24` (or `latest`).
 
 ### 2. Wire a vault
 
@@ -95,7 +95,7 @@ va edit-manifest          # open a refs file in $EDITOR; check on save
 va auth-mode prompt       # or: file
 va update                 # update the binary and add missing detected Harnesses
 va update --sync-harnesses # add missing Harnesses without downloading a binary
-va update v0.4.23         # pin; --check / --dry-run do not write
+va update v0.4.24         # pin; --check / --dry-run do not write
 sudo va uninstall
 ```
 

install-remote.sh

@@ -37,7 +37,7 @@ REPO="${VAULTED_AGENT_REPO:-JacobStephens2/vaulted-agent}"
 # Default pin. Overridden by VAULTED_AGENT_VERSION=... or "latest".
 # Bump this when cutting a release so unpinned one-liners stay intentional.
 # Must match a published GitHub release tag (and Cargo.toml version).
-DEFAULT_VERSION="v0.4.23"
+DEFAULT_VERSION="v0.4.24"
 VERSION="${VAULTED_AGENT_VERSION:-$DEFAULT_VERSION}"
 GITHUB_API="${GITHUB_API:-https://api.github.com}"
 GITHUB="${GITHUB:-https://github.com}"