Release summaries
cmp-agent-platform-contracted-invariants
Connect tool authority, CommunicationOS channel admission and a personalization authority guard implement three contracted agent-platform invariants
integrator
Connect tool authority V1 (root entry of @lssm-tech/lib.contractspec-connect): filterConnectVisibleToolsV1 shows a caller only discovered MCP or registry tools whose server-qualified key is exactly in its Connect scope, and admitConnectToolInvocationV1 projects a call to an effect only through a durable pre-mutation permit for exactly that tool and the Runtime Node V3 work order Connect issued for it (descriptor and argument digests, tenant and environment), re-runs Connect's revocation, policy and trusted-clock currency check, and spends each order on exactly one invocation. Runtime Node dispatch still passes verifyDispatch. Advertised annotations, claimed scopes or identity and model selection grant nothing.
integrator
@lssm-tech/lib.communication-runtime/channel-admission links channel accounts to principals only through an explicit admission backed by a Connect trust decision, a one-time pairing the exact admitted account confirms, quarantine (release needs a permit and a new pairing) and terminal revocation. Its context compiler plugs into receiveAndAdmitCommunicationIngressV1; display names, mentions, thread membership, forwarded messages and provider wrappers are never read as identity.
integrator
@lssm-tech/lib.personalization/authority-guard: telemetry may propose changes (effectAuthority 'none') but guardAuthorityWriteV1 refuses every telemetry-originated write to effect authorizations, policies, constraints, standing approvals, persistent memory, roles or permissions and identity links; only a verified governed decision bound to the exact proposal digest writes, and only a payload whose digest equals that proposal digest.
cmp-connect-lifecycle-authority
Connect host hooks get durable lifecycle authority, and an operator hook grant survives the agent's own in-scope commits without permitting self-grants
integrator
lib.contractspec-connect adds the ./lifecycle-authority leaf (lifecycle authority V1): event semantics where no lifecycle hook terminalizes an operator grant and merge is never delegated to it, a lineage evaluator that lets a grant follow HEAD through descendant commits on its branch that stay inside the signed path prefixes, an ordered lifecycle decision, and the operator-only grant targets hosts use to deny agent self-grants. Hosts supply a read-only git port and their path classification.
customer
contractspec connect hook authority grantgrants now follow the agent's own commits on the same branch while every commit since the grant stays inside its path prefixes and leaves hook, autonomy and grant control files alone;--pin-headkeeps the exact-commit binding. A grant also establishes SessionStart, Stop and handoff (Claude Code SessionEnd) without ever ending; merge keeps asking. Agent tool calls that run the grant command or touch the grant store are denied in every run mode.statusreports the head binding, lifecycle events and lineage.maintainer
The workspace bundle implements the lifecycle ports (git lineage port, governed and operator-only path classifier), routes lifecycle events to resolveLocalLifecycleAuthority, sends V1 the anchor SHA once lineage holds, records lineage in hook receipts, and adds the self-grant guard before hook classification. The hook trust root (connect-hook-run.ts, the cli-runtime Connect policy services and the lifecycle-authority contract) joins the governance roots, so edits to it are high criticality and commits to it outside a grant's prefixes end the grant. The contracts-spec pack's Claude Code section adds SessionEnd running the before-handoff hook.
fo2-s01-connect-effect-admission-approvals
Connect-side effect admission, Connect operation-approval receipts with durable single-use nonces, owner-signed standing mandates and declared-required operation status readiness.
integrator
Bind support/communication approvals with createConnectOperationApprovalPortV1 over createPostgresOperationApprovalStoreV1 and the Connect issuer verify key. Issue approvals only from an authenticated human approver session with createConnectOperationApprovalIssuerV1. Agent Host effect admission needs the Connect-role database URL, a mounted PKCS#8 issuer key and deployment effectProfiles.
maintainer
Standing mandates now require ownerSignature over mandateDigest verified against a registered human owner key; unsigned mandates (only possible in pre-release data from cohort 2) deny. Approval and mandate-approval evidence is append-only; nonces are consumed once per tenant.
review-governance-audit-ownership
Move review, governance and audit operation declarations to canonical owners
integrator
Compatibility operation imports retain the same schemas, policy references and authority requirements through canonical owners.