opencode-code-archaeology 2.3.0 → 2.3.1

package/CHANGELOG.md

@@ -1,21 +1,15 @@
-# [2.3.0](https://github.com/Maleick/Code-Archaeology/compare/v2.2.6...v2.3.0) (2026-05-08)
+## [2.3.1](https://github.com/Maleick/Code-Archaeology/compare/v2.3.0...v2.3.1) (2026-05-08)
 
 
 ### Bug Fixes
 
-* allow Hermes to initialize shared sessions ([#22](https://github.com/Maleick/Code-Archaeology/issues/22)) ([8a484c4](https://github.com/Maleick/Code-Archaeology/commit/8a484c481a895bc8c9b818c831551c435380a438))
-* protect Hermes session initialization from symlinks ([#25](https://github.com/Maleick/Code-Archaeology/issues/25)) ([be855df](https://github.com/Maleick/Code-Archaeology/commit/be855dfeeb1c5173e4db3d5e4b4c32e17f3d2271))
-* use local release version sync plugin ([#24](https://github.com/Maleick/Code-Archaeology/issues/24)) ([221085d](https://github.com/Maleick/Code-Archaeology/commit/221085dc0d3e958c824b474e958bfef15e726094))
-
-
-### Features
-
-* sync yolo docs and tests ([#23](https://github.com/Maleick/Code-Archaeology/issues/23)) ([b42d9b7](https://github.com/Maleick/Code-Archaeology/commit/b42d9b794fd9460dcfd82ff0b56ebdf18bb1d071))
+* **ci:** restrict manual release credentials ([#30](https://github.com/Maleick/Code-Archaeology/issues/30)) ([768c10f](https://github.com/Maleick/Code-Archaeology/commit/768c10f9a0221da004be2c50df5f58c4b6c15d6a))
 
 ## Unreleased
 
 ### Features
 
+* document manual release reruns and workflow dispatch trigger settings in `docs/RELEASE.md` and `CONTRIBUTING.md`
 * add Hermes integration docs coverage for `yolo` and explicit docs smoke coverage for `--yolo` across wiki/INTEGRATION pages
 
 ## [2.2.6](https://github.com/Maleick/Code-Archaeology/compare/v2.2.5...v2.2.6) (2026-05-07)

package/CONTRIBUTING.md

@@ -19,6 +19,13 @@ Use Node 20 for CI parity. Node 18 or newer is supported by the package metadata
 - Keep `.archaeology/`, `.superpowers/`, `node_modules/`, logs, secrets, and editor state out of commits.
 - Do not commit, tag, push, or publish release artifacts unless you are intentionally performing a reviewed release step.
 
+## PR Checklist
+
+- Keep `dist/` checked in only when runtime or source output changes; `dist/` is part of the published package surface and must reflect shipped behavior.
+- Add `dist/` updates in the same PR for source changes (for example: `src/`, `commands/`, `prompts/`, hooks, or `scripts/` changes).
+- Do not add or track `disk/`; it is runtime scratch space and belongs in `.gitignore`.
+- If a change is docs-only (`README`, `INSTALL`, `docs/`, `wiki/`), `dist/` updates are not required.
+
 ## Testing Commands
 
 Run the most focused checks for your change, and run the release checks before release-impacting changes are merged:
@@ -43,6 +50,13 @@ Before committing, pushing, or opening a PR, run a polish pass over the changed
 - Do not include secrets, credentials, private repository contents, or full local runtime state.
 - Preserve the safety model: survey first, excavate for mock patches, restore only after review.
 
+## Release Behavior
+
+- The `release.yml` workflow supports manual `workflow_dispatch` reruns.
+- Manual reruns with `publish=false` validate setup, build, package verification, and tests without running `semantic-release` or exposing release credentials.
+- Do not treat a feature-branch manual rerun as full release validation; publish behavior is restricted to the configured release branch (`main`).
+- Use `publish=true` only for an explicit publish attempt from `main`; the workflow enforces this branch restriction before granting release permissions.
+
 ## Release Notes Expectations
 
 - Add user-visible changes to `CHANGELOG.md`.

package/VERSION

@@ -1 +1 @@
-2.3.0
+2.3.1

package/docs/RELEASE.md

@@ -116,6 +116,14 @@ Publishing is performed by `.github/workflows/release.yml` through npm trusted p
 - Workflow filename: `release.yml`
 - Environment name: leave blank unless the workflow adds a GitHub Actions `environment`
 
+Manual validation reruns are available from GitHub Actions using `workflow_dispatch`:
+
+```bash
+gh workflow run release.yml --ref <branch> -f publish=false
+```
+
+This default path is useful for fast validation of setup, build, package verification, and test steps on any branch. It does not run `semantic-release` and does not expose release credentials or publish permissions to the dispatched ref. Set `publish=true` only for an explicit publish attempt from `main`; the workflow enforces this branch restriction before granting release permissions.
+
 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.
 
 ## 9. Final Checks

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-code-archaeology",
-  "version": "2.3.0",
+  "version": "2.3.1",
   "description": "Excavate, catalog, and restore a codebase by removing accumulated sediment—dead code, legacy fallbacks, circular dependencies, weak types, and defensive programming slop.",
   "type": "module",
   "main": "./dist/index.js",