chore: bump version to 9.0.15

Includes PR #745 isolated credentials fix - prevents API key hijacking from random project .env files by using centralized credentials from ~/.claude-mem/.env Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-04 20:21:01 -05:00
parent a69613b4e0
commit 8f1a260d96
10 changed files with 263 additions and 141 deletions
@@ -0,0 +1,57 @@
+# Phase 02: Merge PR #820 - Health Check Endpoint Fix
+
+**PR:** https://github.com/thedotmack/claude-mem/pull/820
+**Branch:** `fix/health-check-endpoint-811`
+**Status:** Has conflicts, needs rebase
+**Review:** Approved by bayanoj330-dev
+**Priority:** HIGH - Fixes 15-second timeout issue affecting all users
+
+## Summary
+
+Fixes the "Worker did not become ready within 15 seconds" timeout issue by changing health check functions from `/api/readiness` to `/api/health`.
+
+**Root Cause:** `isWorkerHealthy()` and `waitForHealth()` were using `/api/readiness` which returns 503 until full initialization completes (including MCP connection which can take 5+ minutes). Hooks only have 15 seconds timeout.
+
+**Solution:** Use `/api/health` (liveness check) which returns 200 as soon as HTTP server is listening.
+
+## Files Changed
+
+| File | Change |
+|------|--------|
+| `src/shared/worker-utils.ts` | Change `/api/readiness` → `/api/health` in `isWorkerHealthy()` |
+| `src/services/infrastructure/HealthMonitor.ts` | Change `/api/readiness` → `/api/health` in `waitForHealth()` |
+| `tests/infrastructure/health-monitor.test.ts` | Update test to expect `/api/health` |
+
+## Dependencies
+
+- **None** - Independent fix
+
+## Fixes Issues
+
+- #811
+- #772
+- #729
+
+## Tasks
+
+- [ ] Checkout PR branch `fix/health-check-endpoint-811` and rebase onto main to resolve conflicts
+- [ ] Review the endpoint change logic in `worker-utils.ts` and `HealthMonitor.ts`
+- [ ] Verify build succeeds after rebase
+- [ ] Run health monitor tests: `npm test -- tests/infrastructure/health-monitor.test.ts`
+- [ ] Merge PR #820 to main
+- [ ] Manual verification: Kill worker and start fresh session - should not see 15-second timeout
+
+## Verification
+
+```bash
+# After merge, verify hooks work during MCP initialization
+# Start a fresh session and observe logs
+tail -f ~/.claude-mem/logs/worker.log | grep -i "health"
+```
+
+## Notes
+
+- This is a quick fix with minimal code changes
+- The `/api/health` endpoint returns 200 as soon as Express is listening
+- Background initialization continues after health check passes
+- Related to PR #774 which had the same fix but has merge conflicts
@@ -0,0 +1,70 @@
+# Phase 03: Merge PR #827 - Bun Runner for Fresh Install
+
+**PR:** https://github.com/thedotmack/claude-mem/pull/827
+**Branch:** `fix/fresh-install-bun-path-818`
+**Status:** Has conflicts, needs rebase
+**Review:** Approved by bayanoj330-dev
+**Priority:** MEDIUM - Fixes fresh installation issues
+
+## Summary
+
+Fixes the fresh install issue where worker fails to start because Bun isn't in PATH yet after `smart-install.js` installs it.
+
+**Root Cause:** On fresh installations:
+1. `smart-install.js` installs Bun to `~/.bun/bin/bun`
+2. Bun isn't in current shell's PATH until terminal restart
+3. Hooks try to run `bun ...` directly and fail
+4. Worker never starts, database never created
+
+**Solution:** Introduce `bun-runner.js` - a Node.js script that finds Bun in common install locations (not just PATH) and runs commands with it.
+
+## Files Changed
+
+| File | Change |
+|------|--------|
+| `plugin/scripts/bun-runner.js` | NEW: Script to find and run Bun |
+| `plugin/hooks/hooks.json` | Use `node bun-runner.js` instead of direct `bun` calls |
+
+## Dependencies
+
+- **None** - Independent fix
+
+## Fixes Issues
+
+- #818
+
+## Bun Search Locations
+
+The bun-runner checks these locations in order:
+- PATH (via `which`/`where`)
+- `~/.bun/bin/bun` (default install location)
+- `/usr/local/bin/bun`
+- `/opt/homebrew/bin/bun` (macOS Homebrew)
+- `/home/linuxbrew/.linuxbrew/bin/bun` (Linuxbrew)
+- Windows: `%LOCALAPPDATA%\bun\bin\bun.exe` with fallback
+
+## Tasks
+
+- [ ] Checkout PR branch `fix/fresh-install-bun-path-818` and rebase onto main to resolve conflicts
+- [ ] Review `bun-runner.js` for correctness across platforms
+- [ ] Verify hooks.json uses correct `node bun-runner.js` pattern
+- [ ] Verify build succeeds after rebase
+- [ ] Merge PR #827 to main
+- [ ] Test on fresh install (uninstall claude-mem, reinstall) to verify Bun is found
+
+## Verification
+
+```bash
+# After merge, verify bun-runner finds Bun
+node plugin/scripts/bun-runner.js --version
+
+# Check hooks.json uses bun-runner
+grep -i "bun-runner" plugin/hooks/hooks.json
+```
+
+## Notes
+
+- This is a surgical fix that doesn't change core functionality
+- All hooks now go through the Node.js bun-runner script
+- Cross-platform: Linux, macOS, Windows
+- The bun-runner approach is more robust than relying on PATH