dhpk-release-creatorlisted

# Release Creator Resolve project-specific release judgment first; delegate the fixed mechanics to the tested runner. ## Output Return a release report containing the resolved configuration, changed version files, changelog result, validation result, runner phase, and the current merge/tag/CI gate. Stop with a blocked report when configuration is ambiguous, validation fails, the PR is not merged, or the tag-triggered workflow cannot be identified; do not infer a release success from a local edit or an unassociated CI run. ## When NOT to Use - PHP package/library publishing: use `dhpk-composer-package-hygiene`. - Ordinary feature or bug commits: use `dhpk-git-smart-commit`. - The integration branch or required tests are not ready. ## 1. Resolve release config 1. Follow project `RELEASE.md` when present. 2. Otherwise inspect the relevant manifests and `references/release-presets.md`. 3. Confirm these values with the user before execution: | Token | Meaning | Typical default | |---|---|---| | `{VERSION_FILES}` | Lockstep version files | `package.json` | | `{VALIDATE_CMD}` | Required validation | `npm test` | | `{BASE_BRANCH}` | Integration branch | `main` or `develop` | | `{RELEASE_BRANCH}` | Published branch | `main` | | `{TAG_PREFIX}` | Tag prefix | `v` | | `{CHANGELOG}` | Changelog file | `CHANGELOG.md` | | `{RELEASE_WORKFLOW}` | Tag-triggered CI workflow | `release.yml` | ## 2. Author the release content - Update every `{VERSION_FILES}` entry to `<version>` in lock