vc-publish

Output style: Follow process/development-protocols/communication-standards.md, answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Push harness improvements from the current development repo to the remote kit repository (vibecode-pro-max-kit). This is the maintainer counterpart to vc-update.

• vc-update = user pulls latest harness INTO their project FROM the remote
• vc-publish = maintainer pushes improvements FROM the development repo TO the remote kit repo

Prerequisites

• Local checkout of the kit repo (git clone git@github.com:withkynam/vibecode-pro-max-kit.git)
• .vc-publish-config file in the current repo root (see Configuration below)
• Git push access to the remote kit repo

Configuration

Create .vc-publish-config in the repo root:

{"kitRepoPath": "/path/to/vibecode-pro-max-kit"}

If this file is missing, ask the user for the kit repo checkout path and offer to create it.

Workflow

Step 1: Load Configuration

1. Read .vc-publish-config from the current repo root.
2. If missing, ask the user for the kit repo local checkout path.
3. Verify the path exists and contains vc-manifest.json.
4. Verify the kit repo worktree is clean (git -C <kitRepoPath> status --porcelain). If dirty, warn and ask whether to proceed or abort.

Step 2: Read Manifest

5. Read vc-manifest.json from the kit repo checkout.
6. Extract the current version.
7. Before computing a version bump, check if the current kit version already matches the intended target version (e.g. 3.0.0). If the kit version already equals the target: skip the bump step entirely and proceed directly to Step 3 with a tag-as-is note, do not increment the version. Record in the publish summary that the version was unchanged.