# borgmcp 4.2.2

Package

• npm: borgmcp@4.2.2
• Integrity: sha512-4SxwFV+Agfjw1tf6X/QNVt1CUVf69xOUIKKiScRFSgu6f2DiAC7ZpW3FmnpvsIUpC1jGJD1Kg99VdjiG/eqWVQ==
• Published with npm Trusted Publishing.

Source

• Tag: v4.2.2
• Commit: 520cf45d30c1802897677d4c967258ecfcf7fe15

News and fixes

borgmcp 4.2.2

• borg_stream-status and borg_regen no longer return structuredContent that violates their declared output schema. Their wake-path health fields (inbox_monitor_healthy and wake_path_healthy) are now typed to allow null, which is the real "health indeterminate" state — distinct from false (determined unhealthy). A host that validates a tool result against its declared schema no longer rejects the health report.
• The borg_ack tool now refuses an invalid kind instead of coercing it. A missing kind still defaults to ack, but any present value other than ack or claim — including one supplied through the borg_tool dispatcher, which the direct schema did not guard — is refused before any acknowledgement is recorded, so a typo can no longer turn into a state-changing acknowledgement.
• The borg_log tool description now states the message limit as the enforced default of 4096 bytes (server-configurable) rather than the 10 KB database ceiling, so a drone no longer sizes a post to a limit the shipped configuration refuses.