opencode-code-archaeology 2.2.0 → 2.2.2

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [2.2.2](https://github.com/Maleick/Code-Archaeology/compare/v2.2.1...v2.2.2) (2026-05-07)
+
+
+### Bug Fixes
+
+* deploy pages with Node 24 actions ([#15](https://github.com/Maleick/Code-Archaeology/issues/15)) ([3d0fb9f](https://github.com/Maleick/Code-Archaeology/commit/3d0fb9fc168ab5b94229966a053fd58986076238))
+
+## [2.2.1](https://github.com/Maleick/Code-Archaeology/compare/v2.2.0...v2.2.1) (2026-05-07)
+
+
+### Bug Fixes
+
+* opt actions into Node 24 runtime ([#14](https://github.com/Maleick/Code-Archaeology/issues/14)) ([1d2b797](https://github.com/Maleick/Code-Archaeology/commit/1d2b797c629ba0c3a7b9245cb596e3fac2c42cd7))
+
 # [2.2.0](https://github.com/Maleick/Code-Archaeology/compare/v2.1.0...v2.2.0) (2026-05-07)
 
 

package/docs/RELEASE.md

@@ -1,6 +1,6 @@
 # Release Process
 
-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.
+This checklist is for future `opencode-code-archaeology` releases. `v2.2.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.1.0` is t
 
 ## 2. Version Bump
 
-For a future release, replace `2.1.0` with the target version:
+For a future release, replace `2.2.0` with the target version:
 
 ```bash
-npm version 2.1.0 --no-git-tag-version
+npm version 2.2.0 --no-git-tag-version
 ```
 
 Update `VERSION` to the same value:
 
 ```text
-2.1.0
+2.2.0
 ```
 
 Confirm `package.json`, `package-lock.json`, and `VERSION` agree.
 
 ## 3. Changelog
 
-- Add a `v2.1.0` entry, or the future target version, to `CHANGELOG.md`.
+- Add a `v2.2.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.
 
@@ -88,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.1.0 release"
-git tag v2.1.0
+git commit -m "chore: prepare v2.2.0 release"
+git tag v2.2.0
 git push origin HEAD
-git push origin v2.1.0
+git push origin v2.2.0
 ```
 
 For a future release, use the future version in the commit message and tag.
@@ -101,7 +101,7 @@ 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.1.0 --title "v2.1.0" --notes-file CHANGELOG.md
+gh release create v2.2.0 --title "v2.2.0" --notes-file CHANGELOG.md
 ```
 
 Before publishing, trim the notes to the specific version section if `CHANGELOG.md` contains multiple releases.
@@ -125,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.1.0
+gh release view v2.2.0
 ```
 
 Optionally verify a fresh install path:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-code-archaeology",
-  "version": "2.2.0",
+  "version": "2.2.2",
   "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",
@@ -37,7 +37,6 @@
     "docs/SECURITY_AUDIT.md",
     "wiki",
     "assets",
-    ".github",
     "AGENTS.md",
     "VERSION",
     "README.md",

package/wiki/Release-Process.md

@@ -2,13 +2,13 @@
 
 [Home](Home) | [Installation](Installation) | [Workflow](Expedition-Workflow) | [Security](Security-and-Safety)
 
-Use this checklist for future `opencode-code-archaeology` releases. `v2.1.0` is the current example version; replace it with the target version.
+Use this checklist for future `opencode-code-archaeology` releases. `v2.2.0` is the current example version; replace it with the target version.
 
 ## Checklist
 
 1. Review the worktree for unrelated changes and local state.
-2. Bump package files with `npm version 2.1.0 --no-git-tag-version`.
-3. Update `VERSION` to `2.1.0`.
+2. Bump package files with `npm version 2.2.0 --no-git-tag-version`.
+3. Update `VERSION` to `2.2.0`.
 4. Update `CHANGELOG.md` with release notes.
 5. Run verification:
 
@@ -22,10 +22,10 @@ bash -n hooks/opencode/*.sh
 npm pack --json --dry-run
 ```
 
-6. Confirm the package dry run includes `dist`, `assets`, `hooks`, `commands`, `skills`, `plugins`, `schema`, `prompts`, `docs`, `wiki`, `README.md`, `INSTALL.md`, `CHANGELOG.md`, `SECURITY.md`, `CONTRIBUTING.md`, `VERSION`, `AGENTS.md`, and `LICENSE`.
-7. Commit release files, tag `v2.1.0`, push the branch, and push the tag.
+6. Confirm the package dry run includes `dist`, `assets`, `hooks`, `commands`, `skills`, `schema`, `prompts`, `docs`, `wiki`, `README.md`, `INSTALL.md`, `CHANGELOG.md`, `SECURITY.md`, `CONTRIBUTING.md`, `VERSION`, `AGENTS.md`, and `LICENSE`.
+7. Commit release files, tag `v2.2.0`, push the branch, and push the tag.
 8. Create the GitHub release from the tag.
 9. Publish npm with `npm publish --access public`.
-10. Confirm `npm view opencode-code-archaeology version` and `gh release view v2.1.0` show the expected release.
+10. Confirm `npm view opencode-code-archaeology version` and `gh release view v2.2.0` show the expected release.
 
 Do not claim GitHub Pages is enabled unless repository settings confirm it.

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,63 +0,0 @@
-name: Bug report
-description: Report a problem with the Code Archaeology OpenCode plugin.
-title: "bug: "
-labels:
-  - bug
-body:
-  - type: markdown
-    attributes:
-      value: Thanks for helping improve Code Archaeology. Do not include secrets, private code, or full `.archaeology/` state.
-  - type: textarea
-    id: summary
-    attributes:
-      label: Summary
-      description: What went wrong?
-    validations:
-      required: true
-  - type: dropdown
-    id: mode
-    attributes:
-      label: Mode
-      options:
-        - survey
-        - excavate
-        - restore
-        - install or CLI
-        - documentation
-        - other
-    validations:
-      required: true
-  - type: input
-    id: version
-    attributes:
-      label: Version
-      description: Package version, commit SHA, or install source.
-      placeholder: v2.0.2
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to reproduce
-      placeholder: |
-        1. Run ...
-        2. See ...
-    validations:
-      required: true
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected behavior
-    validations:
-      required: true
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual behavior
-      description: Include sanitized logs or error output when useful.
-    validations:
-      required: true
-  - type: textarea
-    id: environment
-    attributes:
-      label: Environment
-      description: OS, Node version, OpenCode version, package manager, and target language.
-      placeholder: macOS 14, Node 20, OpenCode ..., npm ..., TypeScript

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,48 +0,0 @@
-name: Feature request
-description: Suggest an improvement for the Code Archaeology OpenCode plugin.
-title: "feat: "
-labels:
-  - enhancement
-body:
-  - type: markdown
-    attributes:
-      value: Please focus on the user workflow and safety impact. Do not include private repository contents.
-  - type: textarea
-    id: problem
-    attributes:
-      label: Problem
-      description: What workflow or limitation should this improve?
-    validations:
-      required: true
-  - type: textarea
-    id: proposal
-    attributes:
-      label: Proposed solution
-      description: What should Code Archaeology do differently?
-    validations:
-      required: true
-  - type: dropdown
-    id: area
-    attributes:
-      label: Area
-      options:
-        - survey reporting
-        - excavate mock patches
-        - restore safety
-        - language support
-        - CLI or install
-        - documentation
-        - CI or release
-        - other
-    validations:
-      required: true
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives considered
-      description: Any workaround or simpler approach?
-  - type: textarea
-    id: safety
-    attributes:
-      label: Safety considerations
-      description: Could this modify user code, expose local state, or affect restore behavior?

package/.github/pull_request_template.md

@@ -1,27 +0,0 @@
-## Summary
-
-- 
-
-## Verification
-
-- [ ] Polish pass completed before commit, push, and PR.
-- [ ] `npm run build`
-- [ ] `npm run typecheck`
-- [ ] `npm test`
-- [ ] `npm audit --audit-level=moderate`
-- [ ] `bash -n hooks/opencode/*.sh`
-- [ ] `npm pack --json --dry-run`
-
-## Safety Checklist
-
-- [ ] I did not commit `.archaeology/`, `.superpowers/`, secrets, logs, or local editor state.
-- [ ] Restore-mode changes are backed by reviewed survey or excavate output.
-- [ ] I did not remove try/catch around I/O or external input boundaries.
-- [ ] I flagged uncertain type or behavior changes for review instead of guessing.
-
-## Docs And Release Checklist
-
-- [ ] README, INSTALL, docs, and wiki source are updated if user behavior changed.
-- [ ] CHANGELOG includes user-visible changes.
-- [ ] Package metadata and npm package contents are correct for release-impacting changes.
-- [ ] Version, tag, publish, and release steps are not included unless this PR is the release PR.

package/.github/workflows/ci.yml

@@ -1,45 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-jobs:
-  verify:
-    name: Verify
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Build
-        run: npm run build
-
-      - name: Typecheck
-        run: npm run typecheck
-
-      - name: Test
-        run: npm test
-
-      - name: Audit dependencies
-        run: npm audit --audit-level=moderate
-
-      - name: Check shell hook syntax
-        run: bash -n hooks/opencode/*.sh
-
-      - name: Validate npm package contents
-        run: npm pack --json --dry-run

package/.github/workflows/release.yml

@@ -1,46 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-
-jobs:
-  release:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      issues: write
-      pull-requests: write
-      id-token: write
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          persist-credentials: false
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '22'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Build
-        run: npm run build
-
-      - name: Type check
-        run: npm run typecheck
-
-      - name: Verify package
-        run: npm run verify:pack
-
-      - name: Test
-        run: npm test
-
-      - name: Release
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          NPM_CONFIG_PROVENANCE: true
-        run: npx semantic-release