borgmcp-server 3.2.3

Package

• Registry: https://www.npmjs.com/package/borgmcp-server/v/3.2.3
• Live integrity: sha512-HUcrnBO+dhdEaAPIiJ9WjDkt8dDbWF/A6b6unyy3JFSuiHZLm/dPWhjDF0e+3yU6WzUusiItKxsbCksF2Y8gag==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-server/releases/tag/v3.2.3
• Commit: 5bb4f7d

News and fixes

borgmcp-server 3.2.3

• Activity reads enrich a page with three statements (entries with drone and role, recipients, document citations) instead of three statements per entry; a 500-entry page goes from 1,505 prepared statements to 8. Page payloads, ordering, cursors, counts and claims are unchanged. Tracked in #371.
• Runtime telemetry, including slow_request and slow_liveness_scan, now writes to <server data directory>/logs/runtime.log (10 MiB, three generations) instead of logs/managed.stderr.log; existing managed stderr logs are preserved, and managed stderr remains the sink for startup, crash, debug, and liveness-failure output. (#373)
• The runtime log sink is bounded in memory (1,024 records / 1 MiB) with a reserve so slow_request and slow_liveness_scan survive saturation, repairs partial writes, validates and repairs the log tail at startup, and shuts down within a one-second bound. An unsafe log file (symlink, foreign owner, group/other access) disables runtime telemetry with one sanitized stderr warning; the server keeps serving. Recovery is documented in the operator reference.
• No migration: schema stays at 27; 3.2.2 ↔ 3.2.3 stores are interchangeable.
• This release changes no API shape and no request behaviour.