opencode-code-archaeology 2.0.2 → 2.2.0

package/docs/RELEASE.md

@@ -1,6 +1,6 @@
 # Release Process
 
-This checklist is for future `opencode-code-archaeology` releases. `v2.0.2` is the current release example; replace it with the next version when preparing a new release.
+This checklist is for future `opencode-code-archaeology` releases. `v2.1.0` is the current release example; replace it with the next version when preparing a new release.
 
 ## 1. Preflight
 
@@ -12,23 +12,23 @@ This checklist is for future `opencode-code-archaeology` releases. `v2.0.2` is t
 
 ## 2. Version Bump
 
-For a future release, replace `2.0.2` with the target version:
+For a future release, replace `2.1.0` with the target version:
 
 ```bash
-npm version 2.0.2 --no-git-tag-version
+npm version 2.1.0 --no-git-tag-version
 ```
 
 Update `VERSION` to the same value:
 
 ```text
-2.0.2
+2.1.0
 ```
 
 Confirm `package.json`, `package-lock.json`, and `VERSION` agree.
 
 ## 3. Changelog
 
-- Add a `v2.0.2` entry, or the future target version, to `CHANGELOG.md`.
+- Add a `v2.1.0` entry, or the future target version, to `CHANGELOG.md`.
 - Include user-visible changes, safety notes, and any migration instructions.
 - Keep the release notes factual and avoid claiming publication steps that have not happened yet.
 
@@ -43,6 +43,7 @@ npm run typecheck
 npm audit --audit-level=moderate
 npm outdated --json
 bash -n hooks/opencode/*.sh
+bash -n hooks/hermes/*.sh
 npm pack --json --dry-run
 ```
 
@@ -51,7 +52,7 @@ Expected outcomes:
 - Build and typecheck pass.
 - npm audit reports no moderate-or-higher vulnerabilities.
 - npm outdated reports `{}` or no actionable outdated dependencies.
-- Shell hooks pass syntax checks.
+- Shell hooks pass syntax checks (both OpenCode and Hermes).
 - The package dry run includes required files.
 
 ## 5. npm Pack Required Files
@@ -63,7 +64,6 @@ Inspect `npm pack --json --dry-run` output for the package contents. Required fi
 - `hooks/`
 - `commands/`
 - `skills/`
-- `plugins/`
 - `schema/`
 - `prompts/`
 - `docs/`
@@ -77,6 +77,8 @@ Inspect `npm pack --json --dry-run` output for the package contents. Required fi
 - `SECURITY.md`
 - `LICENSE`
 
+`plugins/` is intentionally repo-local and should not appear in npm package contents.
+
 If any required file is missing, update the `files` array in `package.json`, rerun `npm install` if the lockfile needs to change, and repeat the package dry run.
 
 ## 6. Commit, Tag, And Push
@@ -86,10 +88,10 @@ Only perform these steps after verification passes and after confirming the bran
 ```bash
 git status --short
 git add README.md INSTALL.md docs wiki assets .github SECURITY.md CONTRIBUTING.md CHANGELOG.md package.json package-lock.json VERSION .gitignore
-git commit -m "chore: prepare v2.0.2 release"
-git tag v2.0.2
+git commit -m "chore: prepare v2.1.0 release"
+git tag v2.1.0
 git push origin HEAD
-git push origin v2.0.2
+git push origin v2.1.0
 ```
 
 For a future release, use the future version in the commit message and tag.
@@ -99,18 +101,20 @@ For a future release, use the future version in the commit message and tag.
 Create the GitHub release from the matching tag:
 
 ```bash
-gh release create v2.0.2 --title "v2.0.2" --notes-file CHANGELOG.md
+gh release create v2.1.0 --title "v2.1.0" --notes-file CHANGELOG.md
 ```
 
 Before publishing, trim the notes to the specific version section if `CHANGELOG.md` contains multiple releases.
 
 ## 8. npm Publish
 
-Publish only after the GitHub tag and release are correct:
+Publishing is performed by `.github/workflows/release.yml` through npm trusted publishing. Configure npm Trusted Publisher with:
 
-```bash
-npm publish --access public
-```
+- Publisher: `GitHub Actions`
+- Organization or user: `Maleick`
+- Repository: `Code-Archaeology`
+- Workflow filename: `release.yml`
+- Environment name: leave blank unless the workflow adds a GitHub Actions `environment`
 
 If publishing fails, do not create a replacement tag unless the failure requires a new package version. Fix the issue, rerun verification, and follow npm versioning rules.
 
@@ -121,7 +125,7 @@ Confirm the public release surfaces report the expected version:
 ```bash
 npm view opencode-code-archaeology version
 npm view opencode-code-archaeology dist-tags
-gh release view v2.0.2
+gh release view v2.1.0
 ```
 
 Optionally verify a fresh install path: