dodo-mcp 1.4.1 → 1.4.3

package/docs/RELEASE_1.4.2.md

@@ -0,0 +1,66 @@
+# DODO MCP 1.4.2 — Recovery best effort across restart
+
+Automatic source backups no longer make ordinary editing or
+commands depend on Recovery availability. A project with an old strict policy,
+a missing backup volume, or a credential-like example file can continue normal
+work while Recovery reports its failure.
+
+## Changes
+
+- Automatic activation, before-write and before-exec captures are best effort,
+  including stored `strictEnforcement`, `gitRequired` and `gitDirectory` settings.
+  Backup failure no longer turns a permitted `echo ok` or source edit into
+  `RECOVERY_REQUIRED`.
+- The per-project `skipSecretContentFiles` preference persists across restart.
+  Capture reports credential-like files it skips without storing their contents
+  as a completed backup. The Recovery quick action changes this project preference
+  rather than disabling global file permissions or secret screening.
+- `project_overview` includes `blockedPath`, `skippedSecretFiles`, `lastWarning`
+  and `operationsBlocked:false`. `blockedPath` is a relative source path when
+  known, or `null` for a failure without a specific source file. A later global
+  failure clears a previous path instead of pointing at an unrelated file.
+- Recovery storage initializes on first disk access. A broken Recovery directory
+  can no longer prevent the server from booting, while canonical directory
+  identity and private-path checks still reject replacement storage.
+- History, drift and agent bookkeeping failures report diagnostics without
+  hiding a completed operation or repeating its effects. Corrupt Recovery
+  metadata remains visible from the overview.
+- The Recovery dashboard replaces the Strict Blocking switch with the best-effort
+  behavior and describes `BLOCKED` as backup unavailable, not a lock on normal work.
+
+Explicit owner/verified checkpoints and reviewed restores still require their
+backup and integrity checks to succeed. Authorization, secret/path policy,
+expected hashes, and recovery guards for an actual partial file journal remain
+authoritative. A warning means the operation may have no new Recovery checkpoint.
+
+## Upgrade
+
+```sh
+npm install -g dodo-mcp@1.4.2
+dodo --version
+```
+
+Restart the DODO process using the service or launcher that normally runs it.
+Installing the package does not replace code already loaded by a running process.
+Refresh the MCP connection and call `project_overview` again for its current
+workspace epoch. The updated overview exposes `operationsBlocked:false` alongside
+the backup diagnostics. For Docker installations, update the package in the DODO
+image and recreate that service with its existing persistent state.
+
+No live production instance was updated during the patch validation. Installation
+and a real server restart are separate from the fixture restart tests.
+
+## Validation
+
+Windows / Node 24.22.1 patch checks: build, typecheck and lint passed; the main
+Recovery regression group passed 69 tests with 2 platform/dependency skips.
+Storage boot/identity checks passed 2 tests, the owner UI passed 1 test in system
+Chrome, and fresh-install packaging passed 17 tests: 89 passed in total across
+these focused checks. See [the test report](TEST_REPORT.md).
+
+This is focused patch evidence, not a completed full native release gate.
+Native Linux/macOS and live production acceptance were not run for this patch.
+The existing production dependency advisories are not remediated by this change.
+
+See [Recovery usage and limits](RECOVERY.md) for checkpoint, restore and storage
+behavior.

package/docs/RELEASE_1.4.3.md

@@ -0,0 +1,22 @@
+# DODO MCP 1.4.3 — Dependency security updates & raster image signature hardening
+
+## Summary
+
+- **Direct & Runtime Dependency Security Updates:**
+  - `@modelcontextprotocol/server` `2.0.0` → `2.4.0` (`GHSA-jm63-cq47-j5jp`, `GHSA-46jr-4wx8-v453`, `GHSA-rvq5-wwqv-78pq`, `GHSA-f897-62hf-6gxq`)
+  - `@modelcontextprotocol/node` `2.0.0` → `2.1.2` (`GHSA-f897-62hf-6gxq`, plus transitive `hono` / `@hono/node-server` updates)
+  - `@modelcontextprotocol/express` `2.0.0` → `2.0.2` (`GHSA-rvq5-wwqv-78pq`)
+  - `express` `5.2.1` → `5.3.0` (resolving transitive `proxy-addr` `GHSA-jqcg-44mw-7w3h`, `body-parser` `GHSA-27r3-jxmh-p828`, and `qs` `GHSA-6pq8-jhm2-2vcw`)
+  - `sharp` & `@img/sharp-wasm32` `0.35.4` → `0.35.5` (`GHSA-wq5f-xc86-pv6w` / `CVE-2026-96889`)
+  - `zod` `^4.2.0` → `^4.6.7` (`GHSA-mrhx-c7xc-m3w5`)
+- **Defense-in-Depth Raster Image Header Verification:**
+  - `imageView`, `inspectResourceFile`, and `imagePreview` now verify PNG/JPEG/GIF/WebP magic-byte signatures before invoking `sharp` / `libvips`, preventing disguised SVG/XML payloads from reaching native vector decoders.
+- **Development Toolchain Audit Hygiene:**
+  - Updated `@modelcontextprotocol/client` (`2.4.0`), `vitest` (`5.1.0`), `typescript-eslint` (`^8.72.2`), and transitive `minimatch` / `brace-expansion` resolutions (`npm audit` reports `0 vulnerabilities` across both production and development trees).
+
+## Upgrade
+
+```sh
+npm install -g dodo-mcp@1.4.3
+dodo --version
+```

package/docs/RELEASE_NOTES.md

@@ -1,5 +1,28 @@
 # DODO MCP — Release Notes
 
+## 1.4.3 — Dependency security updates & raster image signature hardening
+
+- Upgraded runtime dependencies `@modelcontextprotocol/server` (`2.4.0`), `@modelcontextprotocol/node` (`2.1.2`), `@modelcontextprotocol/express` (`2.0.2`), `express` (`5.3.0`), `sharp` / `@img/sharp-wasm32` (`0.35.5`), and `zod` (`^4.6.7`), clearing all advisories reported on `npm.io` and `npm audit --omit=dev`.
+- Added strict PNG/JPEG/GIF/WebP magic-byte header validation before passing image buffers or files to `sharp`, ensuring disguised SVG/XML payloads are rejected before native decoding.
+- Updated development test/lint dependencies (`@modelcontextprotocol/client@2.4.0`, `vitest@5.1.0`, `typescript-eslint@^8.72.2`, and transitive glob dependencies) to `0 vulnerabilities` across the full `npm audit` tree.
+- See [upgrade details](RELEASE_1.4.3.md).
+
+## 1.4.2 — Recovery best effort across restart
+
+- Automatic source backup failures no longer block normal commands or edits,
+  including after restart with legacy strict or Git-required settings.
+- Persist the per-project secret-skip preference; show relative `blockedPath`,
+  `skippedSecretFiles`, warnings and `operationsBlocked:false` in the overview.
+- Initialize Recovery disk storage lazily, and keep optional history/drift/agent
+  bookkeeping failures from masking successful work. Explicit checkpoints,
+  reviewed restores, authorization, path/hash and actual journal guards remain.
+- Replace Recovery's Strict Blocking and global permission quick actions with
+  project-scoped backup controls and truthful unavailable-backup diagnostics.
+- Focused Windows patch validation: 89 passed / 2 skipped across Recovery,
+  storage, Chrome UI and fresh-install packaging checks. Full native platform
+  gates and live production acceptance remain separate; see [validation](TEST_REPORT.md).
+- See [upgrade details](RELEASE_1.4.2.md) and [Recovery usage](RECOVERY.md).
+
 ## 1.4.1 — Immediate Upgrade Unblock, Full Edit Defaults & Concurrent Multi-Project UI
 
 - Automatically clears pre-existing write blocks (`recovery_required` changesets, `PREPARING` snapshots, `recovery_drift`, strict `recovery_policies`, `read`/`inspect` defaults, and read-only OAuth grants/tokens) immediately upon upgrading and opening `state.db`.

package/docs/TEST_REPORT.md

@@ -1,5 +1,50 @@
 # DODO MCP — Test Report
 
+## 1.4.2 Recovery best-effort patch — Windows, 2026-11-11
+
+Focused checks on Windows / Node 24.22.1: **build, typecheck and lint passed**.
+These results cover the Recovery patch and are not a full native release gate.
+
+| Check | Passed | Failed | Skipped |
+|---|---:|---:|---:|
+| Main Recovery regressions (7 files) | 69 | 0 | 2 |
+| Recovery-only storage failure at boot and pinned directory identity | 2 | 0 | 0 |
+| Owner UI in installed system Chrome | 1 | 0 | 0 |
+| Fresh tarball install and packaging | 17 | 0 | 0 |
+| Total focused checks | 89 | 0 | 2 |
+
+The main group's skips were the Windows directory-fsync case and the existing
+owner UI case whose bundled Chromium was unavailable. A separate UI regression
+used installed system Chrome and exercised the actual Recovery dashboard code.
+
+Real isolated SQLite/workspace/process fixtures verify persisted secret skipping
+with an AWS-like test key after restart; actual `echo ok` and edits despite
+legacy strict/Git settings or unavailable storage; corrupt prior snapshots and
+policy/drift metadata; relative failure paths and stale-path clearing; live
+authority revocation; and failed required backups before a reviewed restore.
+Bookkeeping trigger failures preserve the operation's result and do not repeat
+effects. Existing regressions retain stale-hash, secret/path, backup integrity
+and actual partial-journal recovery checks.
+
+The storage restart test replaces only a disposable Recovery directory with a
+plain file, confirms the server boots and performs normal work, and verifies that
+the occupied file and old backup bytes stay intact. A separate identity test
+rejects a replacement directory after successful lazy initialization.
+
+The Chrome case checks legacy `BLOCKED` diagnostics, secret-skip settings in both
+states, project-only skip actions and an unsuccessful retry notice. Packaging
+checks install a fresh tarball and verify its Compact MCP backup/restore flow and
+the new overview fields.
+
+**Not completed:** the full Windows suite/native gate (the host lacks enabled
+Administrator and symlink prerequisites), native Linux/macOS validation, and live
+gufile/production acceptance. The earlier production-only npm audit reported
+10 affected packages (1 critical, 5 high, 4 moderate); this Recovery patch does not
+remediate those advisories or claim a clean dependency audit. Publication is
+verified separately from these tests.
+
+See [release scope and upgrade steps](RELEASE_1.4.2.md).
+
 ## 1.3.2 Recovery maintenance — macOS release gate, 2026-09-25
 
 `AUTOMATED_PASS` on macOS: build, typecheck and lint; full core suite **926 passed,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dodo-mcp",
-  "version": "1.4.1",
+  "version": "1.4.3",
   "author": "Arthittakun",
   "description": "DODO — local-first MCP server with multi-project coding, AI providers, sub-agents, context, memory, media and workflow tools; embedded OAuth and workspace permissions.",
   "type": "module",
@@ -56,6 +56,8 @@
     "docs/RELEASE_1.3.2.md",
     "docs/RELEASE_1.4.0.md",
     "docs/RELEASE_1.4.1.md",
+    "docs/RELEASE_1.4.2.md",
+    "docs/RELEASE_1.4.3.md",
     "docs/RELEASE_NOTES.md",
     "docs/SCHEDULES.md",
     "docs/SECURITY.md",
@@ -96,26 +98,26 @@
     "test:desktop:native": "npm run build && node scripts/test-desktop-native.mjs"
   },
   "dependencies": {
-    "@modelcontextprotocol/express": "2.0.0",
-    "@modelcontextprotocol/node": "2.0.0",
-    "@modelcontextprotocol/server": "2.0.0",
+    "@modelcontextprotocol/express": "2.0.2",
+    "@modelcontextprotocol/node": "2.1.2",
+    "@modelcontextprotocol/server": "2.4.0",
     "better-sqlite3": "13.0.3",
     "commander": "15.0.0",
     "cron-parser": "5.10.0",
     "diff": "^9.0.0",
-    "express": "5.2.1",
+    "express": "5.3.0",
     "ignore": "^7.0.9",
     "jose": "6.2.12",
     "oidc-provider": "9.12.2",
     "picomatch": "^4.0.7",
     "playwright": "1.63.0",
-    "sharp": "0.35.4",
+    "sharp": "0.35.5",
     "tar-stream": "3.2.1",
     "typescript": "5.9.3",
-    "zod": "^4.2.0"
+    "zod": "^4.6.7"
   },
   "devDependencies": {
-    "@modelcontextprotocol/client": "2.0.0",
+    "@modelcontextprotocol/client": "2.4.0",
     "@types/better-sqlite3": "^7.6.13",
     "@types/diff": "^7.0.2",
     "@types/express": "^5.0.0",
@@ -125,8 +127,8 @@
     "eslint": "^9.39.0",
     "pyright": "^1.1.413",
     "sweetalert2": "11.26.25",
-    "typescript-eslint": "^8.70.0",
-    "vitest": "5.0.0"
+    "typescript-eslint": "^8.72.2",
+    "vitest": "5.1.0"
   },
   "keywords": [
     "dodo",
@@ -166,6 +168,16 @@
     "url": "https://github.com/arthittakun/dodo-mcp/issues"
   },
   "optionalDependencies": {
-    "@img/sharp-wasm32": "0.35.4"
+    "@img/sharp-wasm32": "0.35.5"
+  },
+  "overrides": {
+    "@typescript-eslint/typescript-estree": {
+      "minimatch": "^11.0.7"
+    },
+    "eslint": {
+      "minimatch": {
+        "brace-expansion": "^1.1.21"
+      }
+    }
   }
 }