deploy-harness

To safely merge an approved improvement branch, use a no-fast-forward merge to combine the prepared branch into main, preserving a clear commit history while stopping automatically on merge conflicts or uncommitted changes.

The best way to bump a plugin patch version is updating the patch number in `.claude-plugin/plugin.json` during the release process, incrementing it without altering the existing JSON formatting before committing the release.

You can deploy Obsidian plugin changes by verifying the repository origin, merging the prepared feature branch into main, bumping the patch version, and pushing the updated main branch to origin to publish the release.

You cannot release a patched plugin version with uncommitted local changes. The deployment process stops automatically when it detects uncommitted changes or merge conflicts to ensure CI safety and repository hygiene.

Yes, the branch merge and release process deletes the merged feature branch locally after successfully pushing the updated main branch to origin, ensuring your local repository remains clean after deployment.

If the repository origin does not match the target plugin, the deployment process requires verification before proceeding. This check ensures you are deploying the correct harness improvement to the intended Obsidian Claude Code plugin repository.