vibepro-npm-publishlisted

# VibePro npm Publish Adapter ## Purpose `npm-package-publish`へVibePro固有の公開profileを渡す薄いadapter。共通の安全条件、exact-SHA照合、部分失敗、復旧手順はここへ複製しない。 ## When to Use VibeProのrelease PR、npm公開、post-merge workflow監視、dist-tag/GitHub Release/docsの照合や復旧に使う。一般的なnpm公開だけなら共通Skillを使う。 ## Required Skill 最初に`npm-package-publish`を読む。見つからない場合は公開操作を始めず、brainbase-unsonの`.claude/skills/npm-package-publish`をSkill配布経路から導入する。 ## Release Profile | Key | Value | |---|---| | `repository` | `Unson-LLC/vibepro` | | `package` | `vibepro` | | `default_branch` | `main` | | `version_source` | `package.json` | | `release_workflow` | `.github/workflows/post-merge-release.yml` | | `release_plan` | `node scripts/post-merge-release.mjs plan --event <merged-pr-event.json>` | | `targeted_checks` | 下記「VibePro checks」 | | `fresh_install_check` | 隔離先へ`vibepro@<version>`を導入し、`vibepro runtime identity --json`を実行 | | `product_convergence` | runtime identity、GitHub Release、VitePress/docs同期、release history | ## VibePro Checks ```bash node --test test/post-merge-release.test.js test/github-release-convergence.test.js npm run typecheck npm pack --dry-run ``` source変更を含む、またはexact-SHAへ結び付いた全体証拠がない場合: ```bash node --test --test-concurrency=2 ``` Skill自体を変更した場合: ```bash node bin/vibepro.js skills lint . --json node --test --test-name-pattern='skills commands list install and verify bundled VibePro skills' test/vibepro-cli.test.js cmp -s CLAUDE.md AGENTS.md git diff --check ``` ## Required Workflow 1. `npm-package-publish`を読み