vcpublish

# vc-publish 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: ```json {"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`. ### Step 3: Resolve Both File Sets 7. Run the resolver against the **kit repo** to get the kit file list: ```bash node <kitRepoPath>/resolve-manifest.mjs --root <kitRepoPath> --json ...