release

# Release Bump `package.json` version, commit, and create a git tag for npm release. ## Current context - Current branch: `!git branch --show-current` - Working tree status: `!git status --short` - Current version: `!node -p "require('./package.json').version"` - Recent tags: `!git tag --sort=-v:refname | head -5` ## Instructions Follow these phases exactly, in order. --- ### Phase 1: Validation 1. **Branch check**: Must be on `main` (or `master`). If not, stop and tell the user. 2. **Clean working tree**: Run `git status --porcelain`. If there are uncommitted changes, stop and tell the user to commit or stash first. 3. **Parse argument**: - If `` is `patch`, `minor`, or `major`: calculate the next version from the current version using semver rules. - If `` is an explicit version (e.g., `1.2.3`): use it directly. Validate it's a valid semver string. - If `` is empty or not provided: default to `patch`. 4. **Duplicate check**: Verify the target version tag (`v<version>`) does not already exist. If it does, stop and tell the user. --- ### Phase 2: Version bump 1. **Update `package.json`**: Change the `"version"` field to the new version. 2. **Update `package-lock.json`**: Run `npm install --package-lock-only` to sync the lockfile version without installing packages. --- ### Phase 3: 릴리즈 노트 작성 `docs/release-notes/v<new-version>.md`에 **영어로** 릴리즈 노트를 작성한다 (GitHub Release는 영어권 사용자 대상 — 한국어로 쓰지 말 것. 단, 전체 커밋 목록의 커밋 메시지는 원문 그대로 둔다). push 후 GitHub Actions(`...