@dollhousemcp/mcp-server 1.9.20 → 1.9.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (11) hide show
  1. package/CHANGELOG.md +54 -0
  2. package/README.github.md +505 -505
  3. package/README.md.backup +505 -505
  4. package/dist/generated/version.d.ts +2 -2
  5. package/dist/generated/version.js +3 -3
  6. package/dist/index.d.ts.map +1 -1
  7. package/dist/index.js +32 -10
  8. package/dist/utils/ElementFormatter.d.ts +31 -1
  9. package/dist/utils/ElementFormatter.d.ts.map +1 -1
  10. package/dist/utils/ElementFormatter.js +56 -15
  11. package/package.json +6 -6
package/CHANGELOG.md CHANGED
@@ -2,6 +2,60 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [1.9.22] - 2025-10-23
6
+
7
+ **Hotfix Release**: Resolve jsdom test failures
8
+
9
+ ### Fixed
10
+ - **jsdom version compatibility** (Hotfix)
11
+ - Reverted jsdom from 27.0.1 to 27.0.0 due to parse5 ES module import issues
12
+ - Fixes test failures in MemoryManager and other test suites
13
+ - The jsdom 27.0.1 update introduced a breaking change with parse5 becoming an ES module
14
+ - Will revisit jsdom 27.0.1 update in future release with proper ES module configuration
15
+
16
+ ## [1.9.21] - 2025-10-23
17
+
18
+ **Patch Release**: Memory validation system activation and element formatting
19
+
20
+ ### Added
21
+ - **Element file formatter script** (#1388, fixes #1387)
22
+ - New `scripts/fix-element-formatting.ts` to reformat blob content elements
23
+ - Fixes element files stored as single-line blobs (unreadable in editors)
24
+ - Intelligently adds newlines before/after markdown headers
25
+ - Formats code blocks and YAML structures properly
26
+ - Dry-run mode for safe testing
27
+ - Average line length detection (>200 chars triggers formatting)
28
+
29
+ ### Fixed
30
+ - **Background memory validation startup** (#1389)
31
+ - BackgroundValidator service now starts automatically on server initialization
32
+ - Memory entries with UNTRUSTED status will be automatically validated every 5 minutes
33
+ - Trust levels are now properly updated (VALIDATED, FLAGGED, QUARANTINED)
34
+ - Validation runs server-side with zero token cost
35
+
36
+ ### Changed
37
+ - **README version history optimization**
38
+ - Limited version history in README to 1.9.x releases only (21 versions instead of 35)
39
+ - Reduced README size from ~75KB to ~61KB for better readability
40
+ - Complete history remains in CHANGELOG.md (source of truth)
41
+ - Updated `generate-version-history.js` minVersion from 1.6.0 to 1.9.0
42
+ - **Added missing v1.9.20 changelog entry to README**
43
+ - Previous README was missing the v1.9.20 MCP Registry Publishing Fix
44
+
45
+ ### Context
46
+ The BackgroundValidator service was fully implemented in Issue #1314 (Phase 1: Background validation for memory security) but was never activated. The `backgroundValidator.start()` method was missing from server initialization, causing all memories to remain UNTRUSTED indefinitely.
47
+
48
+ This patch release adds proper lifecycle management:
49
+ - Import backgroundValidator singleton in server initialization
50
+ - Start validation service after resource handlers are set up
51
+ - Stop service during server cleanup
52
+
53
+ ### Impact
54
+ - Memory security architecture is now fully operational
55
+ - UNTRUSTED memories will be automatically validated
56
+ - Trust level updates work correctly
57
+ - No performance impact (runs in background outside LLM context)
58
+
5
59
  ## [1.9.20] - 2025-10-17
6
60
 
7
61
  **Fix Release**: MCP Registry Publishing Compatibility