chore(release): cut engine v0.2.0 (#4176)

* chore(release): cut engine v0.2.0

* fix: widen gittensory-engine dependency ranges past caret's 0.x ceiling

npm ci failed with "Missing: @jsonbored/gittensory-engine@0.1.0 from lock
file" once this PR bumped packages/gittensory-engine to 0.2.0: semver
caret ranges for 0.x versions only allow patch bumps (^0.1.0 means
>=0.1.0 <0.2.0), so gittensory-mcp's "^0.1.0" and gittensory-miner's
exact "0.1.0" pin both broke on this release's own minor bump. Widened
both to ">=0.1.0" -- these are internal, same-monorepo dependencies
whose real compatibility guarantee comes from this repo's own test
suite, not from strict semver-range enforcement against a pre-1.0
package expected to move through minor versions somewhat often.

* fix(engine): derive ENGINE_VERSION instead of hand-syncing it

Same root cause as the package-lock.json/dependency-range fixes already
pushed to this branch: ENGINE_VERSION was a hardcoded literal that
test/unit/engine-version.test.ts correctly caught as stale against this
release's package.json bump. See fix/release-please-lockfile-sync (#4179)
for the full story and verification.

* fix: cap engine dependency ranges below 1.0.0, use compile-time JSON import

Two fixes squashed onto this branch, both already landed on
fix/release-please-lockfile-sync (#4179):

- Superagent correctly flagged >=0.1.0 as overly permissive (unbounded
  above, would accept a future major/compromised version with no review).
  Capped at ">=0.1.0 <1.0.0" -- tolerates all current and future 0.x
  releases without needing a re-bump, while still rejecting 1.0.0+.
- ENGINE_VERSION's readFileSync approach broke the Workers runtime test
  suite (no real filesystem in the workerd sandbox). Switched to a
  compile-time JSON import, matching src/services/mcp-compatibility.ts's
  existing pattern -- Node's ESM loader resolves it at runtime for real
  installs, while the Worker's own esbuild bundling inlines it at build
  time for the bundled path, so neither consumer ever does runtime file I/O.

* chore: force re-scan (dependency range fix already verified correct)

packages/gittensory-mcp and packages/gittensory-miner both already pin
@jsonbored/gittensory-engine to >=0.1.0 <1.0.0 (in package.json and
package-lock.json). Superagent's check-run on this branch is stuck
reporting the pre-fix finding; this empty commit forces a clean
re-scan.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: JSONbored <49853598+JSONbored@users.noreply.github.com>

Author: github-actions[bot]

.release-please-manifest.json

@@ -1,4 +1,4 @@
 {
   "packages/gittensory-mcp": "0.7.0",
-  "packages/gittensory-engine": "0.1.0"
+  "packages/gittensory-engine": "0.2.0"
 }

package-lock.json

@@ -1,5 +1,20 @@
 # Changelog
 
+## [0.2.0](https://github.com/JSONbored/gittensory/compare/engine-v0.1.0...engine-v0.2.0) (2026-07-08)
+
+
+### Features
+
+* **review:** add REES complexity and Go/Python error-defect analyzers ([#4155](https://github.com/JSONbored/gittensory/issues/4155)) ([f5c5c52](https://github.com/JSONbored/gittensory/commit/f5c5c5237da04910688369dbf0cf2a1d9371593e))
+* **review:** per-repo opt-in to let a confident AI-judgment blocker gate the merge ([#4171](https://github.com/JSONbored/gittensory/issues/4171)) ([4664ad2](https://github.com/JSONbored/gittensory/commit/4664ad25f4c729ded6a37c3d5d6d5a56857d73e7))
+
+
+### Fixes
+
+* **engine:** fix stale test fixtures, wire the suite into test:ci ([#4150](https://github.com/JSONbored/gittensory/issues/4150)) ([5a4de69](https://github.com/JSONbored/gittensory/commit/5a4de69a67ae0d1704284d6237cd70d34ee2461a))
+
+## Changelog
+
 ## engine-v0.1.0 - 2026-07-01
 
 ### Features

packages/gittensory-engine/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "@jsonbored/gittensory-engine",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "license": "AGPL-3.0-only",
   "type": "module",
   "description": "Shared deterministic engine logic for the Gittensory review stack and gittensory-miner.",