What problem does it solve? Maintainers of a shared harness kit need a controlled way to push improvements from their development repo to the remote kit repository without leaking project-specific content, skipping manifest reconciliation, or pushing unreviewed changes. ## Core Features & Use Cases - Resolver-driven diffing: Computes added, modified, deleted, and preserved files between the dev repo and kit repo using resolve-manifest.mjs and compute-sync-plan.mjs. - Leak detection gate: Scans the full shipped text surface for product names, absolute paths, and dangling context references before any commit, reverting on failure. - Version and release management: Bumps the manifest version (patch/minor/major), syncs the legacyDeletions ledger, commits, tags, pushes only after explicit approval, and creates a GitHub Release. - Use Case: After adding a new skill and fixing a hook in your dev repo, run the publish workflow to diff the changes, confirm a minor version bump, verify no project content leaks, and push v2.2.0 with a GitHub Release. ## Quick Start Ask the assistant to publish the current harness improvements to the kit repo and walk through the diff, version bump, and push confirmation steps.
