vcupdate

# vc-update Pull the latest agent harness improvements from the remote vibecode-pro-max-kit repository into the current project. ## When to Use - After being told a new harness version is available - Periodically to check for updates - After bootstrapping a project with `vc-setup` and wanting the latest improvements ## Workflow Follow these steps exactly. Do NOT skip the dry-run or confirmation step. ### Step 1: Check Worktree Status Run `git status --porcelain` in the project root. - If output is non-empty: **warn** the user that they have uncommitted changes and suggest `git stash` or committing first. **Do not block** -- continue after warning. - If output is empty: proceed silently. ### Step 2: Read Current Version Read the file `.vc-version` in the project root. - If it exists: store its contents as `currentVersion` (a semver string like `2.0.4`). - If it does not exist: set `currentVersion` to `"0.0.0"` (treat as first update). ### Step 3: Clone Remote Repository ```bash TMPDIR="/tmp/vc-update-$(date +%s)" git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git "$TMPDIR" ``` If the clone fails (network error, auth error, repo not found): - Print the error message. - Clean up the temp directory if it was partially created. - **Stop.** Do not proceed. ### Step 4: Resolve Remote Manifest Run the resolver script from the cloned repo: ```bash node "$TMPDIR/resolve-manifest.mjs" --root "$TMPDIR" --json ``` Parse the JSON output to extract: ...