vc:publish

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 [email protected]: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

1. Read vc-manifest.json from the kit repo checkout.
2. Extract the current version.

Step 3: Resolve Both File Sets

1. Run the resolver against the kit repo to get the kit file list:

   node <kitRepoPath>/resolve-manifest.mjs --root <kitRepoPath> --json
   

   Extract files (kit managed files) and kitOnly (kit-exclusive files).

2. Run the resolver against the dev repo to get the dev file list:

   node <kitRepoPath>/resolve-manifest.mjs --root <devRepoRoot> --json
   

   Extract files (dev managed files).

   Note: The resolver uses the manifest from the --root directory. Since the dev repo has a copy of vc-manifest.json, the resolver works against it. If the dev repo doesn't have the resolver script, copy it from the kit repo first or use the kit repo's copy with --root pointing to the dev repo.