harness-publish

This repo is the workshop; mvp-harness/plugins/mvp-plugin is the one plugin both Claude Code and Codex install. Publishing is a manual, user-run step.

Steps

1. Prerequisites and scope. Confirm this is the source workshop and the mvp-harness submodule is initialized with publish-plugin.sh available. If absent, report the missing prerequisite; do not pretend publication ran. Read the current publish manifest/help. Confirm publication and commit authority separately; a no-commit instruction remains binding.

   For the .repo-context/ layout, verify the plugin-owned template, installer, updater, and doctor use that shared location and preserve the glossary. See docs/usage/mvp-plugin.md for the migration boundary; publishing skills alone does not update the adoption contract.

   Preflight here. Required root gates must pass; the publish script may require committed source unless an explicitly authorized dirty-tree mode applies:

   python3 .claude/scripts/skill-catalog.py --check     # no failures; assess warnings
   git status --short                                     # clean (or know why not)
   

2. Dry run. Shows the gates, the provider-neutrality audit on the source, and what rsync would change — writes nothing:

   bash mvp-harness/plugins/mvp-plugin/scripts/publish-plugin.sh --check
   

   Fix anything it reports in this repo (never in the plugin's skills/ — they are overwritten on publish), re-run the catalog check, return here.

3. Publish. Pick the bump from what changed (patch: text/fixes; minor: new or removed skills, behaviour changes; major: adopt/update contract change):

   bash mvp-harness/plugins/mvp-plugin/scripts/publish-plugin.sh --bump patch --smoke
   

   --smoke installs the result into a throwaway $HOME with codex and asserts discovery; drop it if codex is not on PATH. --allow-dirty only when the user has explicitly accepted publishing from an uncommitted tree.

4. Review the plugin repo (a separate repository on its own branch). Commit only when commit authority was granted:

   git -C mvp-harness status --short
   git -C mvp-harness diff --stat
   

   Stage explicit paths, commit with a message that names the plugin version and the source commit from plugins/mvp-plugin/publish-info.txt. Do not push; the user pushes and decides the branch/merge.

5. Bump the submodule pointer and commit only when authorized. Otherwise report the prepared plugin state and proposed pointer update:

   git add mvp-harness && git commit -m "chore(plugin): mvp-plugin vX.Y.Z (source <sha>)"
   

   Give consumers the update command verified against their current local CLI help, then start a new session to verify discovery. Do not assume a historical marketplace command is supported.

What the script enforces (so you know what a failure means)

Never edit mvp-harness/plugins/mvp-plugin/skills/ or agents/ by hand — they are build output of this repo. Plugin-owned skills and scripts/ are edited in the plugin.