borgmcp-shared 2.2.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/2.2.0
• Live integrity: sha512-sKCKCMBvJWHAVYtFAeBLfpuNZqSJgLqEy7/k1isefgJFlHTMJJSy53bOVj6W+pLWrRSKbhhFkxJheTmFey/cIg==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v2.2.0
• Commit: 3df0b27

News and fixes

This minor release adds design-reference guidance to the Software Development,
Starter, and Local Model templates.

Each issue keeps its mockups and design documents in one GitHub gist, linked
from the issue as Design reference: <gist url> and revised in place. When a
design reference exists it is the acceptance visual: the scope contract names
the gist revision, builders verify against it before handing over and state
any deviation, reviewers treat an unstated mismatch as blocking, and release
quality verifies the final result against the current revision before close.

borgmcp-shared 2.1.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/2.1.0
• Live integrity: sha512-wgx0iOK41bdngq6vqnzwaju+34uUOM3VM/ewrn4LfJlqP17CMjLq6xP7TOQ6E+itIfCh88u7zgGteu/j7HC0KQ==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v2.1.0
• Commit: c0d204c

News and fixes

This minor release adds durable-layer guidance to the human-seat roles in the
Software Development, Starter, and Local Model templates.

It also aligns the exported Decision type with the server decision record and
requires ratified_by, status, and supersedes when decoding decisions.

borgmcp-shared 2.0.1

This patch updates the built-in Software Development Coordinator playbook with
bounded receipt polling and dormant activation and supervision deadlines.

The lifecycle now distinguishes receipt from activation, ends active polling
after receipt, resets one supervision wake from the latest substantive signal,
and prohibits stacked deadlines, open-turn polling, and unauthorized
reassignment.

npm: borgmcp-shared@2.0.1 — integrity sha512-S8ynExOPIosDEeFl8TbeMNAaf+v+1RW2vk5IVlbP6M7rg1EKwWh4g17WVeozPmfF/n2qiyetCU5kPWz38cJ84w==

borgmcp-shared 2.0.0

This release removes unused advisory claims from activity-log reads and advances
the coordination protocol to tag 14.

Compatibility

• The protocol tag changes from 13 to 14. Mixed tag 13 and tag 14 peers fail
  closed during credential-free preflight and must update together.
• The read-log response no longer carries a claims field. Claim visibility
  remains available through acknowledgement status, roster, and diagnostics.

Breaking API changes

• ReadLogResult and ReadLogResponse no longer expose claims.
• The unused ClaimRecord and ReadLogClaim exports are removed.
• The read-log decoder rejects the retired field instead of accepting both wire
  shapes.

Conformance

• The read-log-only durable-claim fixture is removed. Existing acknowledgement
  status and entry-query fixtures continue to verify that claims remain durable,
  distinct from acknowledgements, and unchanged by read-only operations.

borgmcp-shared 1.2.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/1.2.0
• Live integrity: sha512-w6qcOXDngxuj/EN1UMTy5FFX2gPsJxGPnClAzngWTD6dh9lNcQKq71Vx4rD+Et8Xv+CMJZVAC8+/04OyhKX1XA==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v1.2.0
• Commit: f5a3785

News and fixes

This release strengthens portable naming and repository-association conformance
without changing the protocol envelope or any wire shape.

Conformance

• Cube names must be unique per owner under ASCII case-insensitive comparison.
  Different owners may still create cubes with the same display name.
• Role names must be unique per cube under ASCII case-insensitive comparison.
  New role names accept only letters, digits, spaces, periods, underscores, and
  hyphens, must start with a letter or digit, and remain limited to 64 bytes.
• One cube may be explicitly associated with more than one repository, and each
  successful association must be observable through repository resolution.
• The README documents the suite's per-credential request volume and minimum
  request budget for each reset epoch.

Compatibility

PROTOCOL_VERSION remains 13 because this release changes refusal behavior
for invalid input and corrects conformance expectations without changing a wire
shape. Matching client and server releases adopt this contract together.

borgmcp-shared 1.1.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/1.1.0
• Live integrity: sha512-wadK82ok1D3PTE1eWqLEng585qFjfkQ3GqqwZvEnMfoiztwM2L2T9h6jR9UHi2G6ePvI6RdMGu36hlJsdd6L3w==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v1.1.0
• Commit: a4fde81

News and fixes

This release advances the shared contract to protocol tag 13 and removes legacy
surface area before the next coordinated client and server releases.

Compatibility

• The protocol tag changes from 12 to 13. Tag 13 requires a matching consumer pair; mixed tag 12 and tag 13 consumers fail closed.
• The client must stop sending the removed default template before adopting this package. borgmcp-server 3.3.0 and borgmcp 4.7.0 are the adopting releases.

Breaking API changes

• The deprecated ErrorResponse export is removed.
• Eight unused ErrorCode members are removed: SUBSCRIPTION_REQUIRED, MISSING_PARAMETER, RATE_LIMIT_EXCEEDED, DATABASE_ERROR, EXTERNAL_SERVICE_ERROR, ROLE_HAS_FROZEN_DRONES, DRONE_FROZEN, and CURSOR_INVALID. SESSION_REJECTED and INTERNAL_ERROR remain available.
• LEGACY_DEFAULT_TEMPLATE_LABEL and the legacy default cube-template branch are removed.

Reliability and verification

• getTemplate now rejects inherited object keys instead of treating them as registered templates.
• The portable adapter conformance suite now observes behavior without implementation-specific state inspection (#149, #150). Prerequisite failures are isolated, hostile-mutation controls prove refusal atomicity, and human-seat occupancy remains in force until eviction.
• Release CI is smaller and uses the repository's current release-identity and packed-artifact checks (#152, #154). CI tests both the supported minimum Node.js 22.12.0 runtime and the Node.js 24.19.0 release runtime (#156).

borgmcp-shared 1.0.1

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/1.0.1
• Live integrity: sha512-P04ATCkJJebqkMElnEKD1kGky6Cbmgs05wRsMAAWBzlPmzKVq2Yd2b3VP1BTxIJWOs5lfuJdzrBOdR5xxTW1Kw==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v1.0.1
• Commit: 6829cd6

News and fixes

This patch keeps the credential-free protocol mismatch diagnostic aligned with
the protocol version enforced by the package.

• The preflight mismatch message now derives its expected version from PROTOCOL_VERSION instead of repeating a separate version literal.
• The existing fail-closed order, non-reflective text, and matching-release guidance remain unchanged.

borgmcp-shared 1.0.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/1.0.0
• Live integrity: sha512-c55kxgfpo3GWXQB2pxy65CV4zjgoWRLZKidVfdR7/k8kKX9m5cqV7gUckUJ15BuvkIGrha5PFO7NAz5xPUXaeQ==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v1.0.0
• Commit: 0196421

News and fixes

This major release introduces the protocol v12 trustworthy-messaging contracts
used by the matching Borg MCP server and client major releases.

• Every append requires an explicit audience: scalar "broadcast" or a non-empty array of recipient selectors.
• Omitted, null, empty, malformed, and retired addressing inputs refuse before persistence; classification never supplies an audience or falls open.
• Public append requests no longer expose visibility or recipientDroneIds; stored and read entries retain resolved visibility and recipient IDs.
• Message taxonomy retains class, prefixes, and lifecycle only. Every bundled template and playbook requires explicit to, including to: "broadcast" for cube-wide messages.
• Routing echoes contain only the resolved class and recipients.
• Cursorless entry lookup accepts a canonical full UUID or one unique eight-hex prefix and returns the complete enriched log entry.
• Unknown or inaccessible entries return NOT_FOUND; ambiguous prefixes return LOG_ENTRY_PREFIX_AMBIGUOUS without selecting an arbitrary match.
• Entry lookup conformance proves no unread, acknowledgement, claim, log, or authority-state mutation.

borgmcp-shared v0.14.0

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/0.14.0
• Live integrity: sha512-rKRMxnxTnW+o3WOqtAFoih9IeRKCZw/lltqz7CbjC1riNq52CsZ871o1Fo7Fdk0WqwuzdFQmRJ7qOzPi08Q/QA==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v0.14.0
• Commit: a699260

News and fixes

This release introduces the protocol v11 acknowledgement-status contract used
by the matching Borg MCP server and client releases.

• A read-only entry-specific query reports the entry visibility and each intended recipient's nullable acknowledgement timestamp.
• Advisory claims remain separate from acknowledgements, with nullable current drone labels and roles in both collections.
• Unknown entries return a typed refusal instead of being represented as missing acknowledgement state.
• Conformance vectors prove that status queries do not acknowledge, claim, or consume unread activity.
• Shipped Coordinator guidance uses borg_ack-status to inspect receipt without advancing unread cursors.

borgmcp-shared v0.13.1

Package

• Registry: https://www.npmjs.com/package/borgmcp-shared/v/0.13.1
• Live integrity: sha512-AT5xOpd99U1Xd2waRJs01i2fz9ApMzd+NXQh0WMwTUknSsHpaQaEtGjcxtEDZG6MbB6nWfhoWG1ZZm9Fdkoytg==
• Published through npm Trusted Publishing with provenance.

Source

• Tag: https://github.com/Byte-Ventures/borg-mcp-shared/releases/tag/v0.13.1
• Commit: 6a2f852

News and fixes

This maintenance release removes fixed coordination deadlines from the shipped
software templates while retaining protocol v10 unchanged.

• Coordinating roles follow concrete work milestones instead of elapsed-time activation or progress deadlines.
• Silence or uncertain liveness permits one direct status request and a report to the human, never autonomous rerouting or reassignment.
• Coordinator, Queen, and Director ownership changes require explicit human operator approval for the exact work item and recipient.
• Builders report substantive milestones without interrupting slow local work merely to satisfy cadence.