Skip to content
← Back to changelog index

0.1.5

Oct 28, 2026 · 8 packages · 11 unique changes · 4 release entries

appsbundlesintegrationslibs

This release affects the contracts, integrations, sharedLibs, solutions families.

Run contractspec connect adoption resolve --family contracts to see how it impacts your project.

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 grant grants 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-head keeps 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. status reports 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.

Migration guide

  • Route discovered-tool calls through Connect tool authority

    Additive. Hosts that invoke MCP or registry tools should list tools with filterConnectVisibleToolsV1 and call admitConnectToolInvocationV1 with the caller's scope, the Connect permit and the Runtime Node V3 order before dispatching the operation; a projected admission does not replace Runtime Node verifyDispatch. Tool keys are server-qualified (<source>:<serverRef>#<toolName>).

    1. Grant tool keys in Connect scopes as connectToolKeyV1 derives them.
    2. Bind the Runtime Node order's step capability to the tool key and descriptor digest and its payload digest to the argument digest.
    3. Pass the ports already given to createConnectRuntimeV3Authority (policy, receipt, issuance and revocation stores, signature, clock, issuerRef) plus a durable insert-if-absent ConnectToolInvocationLedgerPortV1 keyed by the operation scope.
    4. Recover from a crash after admission through the Runtime Node operation, not by re-admitting; a second admission of the same order is refused.
  • Compile ingress context from channel admission records

    Additive. Persist ChannelAdmissionRecordV1 by compare-and-swap on revision, back ChannelTrustDecisionPortV1 with Connect, and pass createChannelAdmissionContextCompilerV1 as the ingress context compiler.

    1. Import from @lssm-tech/lib.communication-runtime/channel-admission.
    2. Compute the pairing codeDigest as a keyed digest (HMAC with a host secret), never a plain hash of the code.
  • Guard authority-bearing writes

    Additive. Wrap writers of policies, approvals, constraints, memory, roles and identity links with createAuthorityGuardedWriterV1, a Connect-backed GovernedDecisionVerifierPortV1 and the host's payload digester.

    1. Import from @lssm-tech/lib.personalization/authority-guard.
    2. Digest the exact payload a decision approves as the proposal digest, and pass the same digester to createAuthorityGuardedWriterV1.
    3. Back GovernedDecisionVerifierPortV1 with the decision authority; it receives the proposal and payload digests and decides whether the decision is current and may be applied now.
  • Re-grant to get lineage and lifecycle coverage

    Additive. Grants issued before this change keep their exact HEAD binding and establish no lifecycle event; new grants follow in-scope commits and establish SessionStart, Stop and handoff.

    When: When an operator grant issued before this change is still active.

    1. From the operator's own terminal, run contractspec connect hook authority grant --path <prefix/> --confirm-workspace <root> again (add --pin-head to keep the exact-commit binding).
    2. Check it with contractspec connect hook authority status --json (headBinding, lifecycleEvents, lineage).
  • Regenerate the Claude Code hook settings for SessionEnd

    The contracts-spec pack adds a Claude Code SessionEnd entry that runs the before-handoff hook. Generated .claude/settings.json picks it up only after agentpacks regeneration, which is an operator step.

    When: In this repository, after the pack source change merges.

    1. Run bun run agentpacks:claude from an operator terminal and confirm bun run agentpacks:diff exits 0.
  • Apply the operation approval migration and register owner keys

    Required

    Apply LSSM_OS_POSTGRES_OPERATION_APPROVAL_MIGRATION_V1 after 0017, register each mandate owner's Ed25519 key, then re-issue every standing mandate revision with ownerSignature.

    When: When standing mandates or Connect operation approvals are used.

    1. Apply LSSM_OS_POSTGRES_OPERATION_APPROVAL_MIGRATION_V1 (proposed id 0018_connect_operation_approvals).
    2. Register owner keys with createPostgresPrincipalKeyStoreV1(...).register through the Connect role.
    3. Record a new mandate revision signed by the owner key over mandateDigest.

Upgrade steps

  • Verify lifecycle authority and lineage

    auto

    Run the contract unit tests and the workspace hook tests.

    Packages: @lssm-tech/lib.contractspec-connect, @lssm-tech/bundle.workspace

    1. Run bun test packages/platform/governance/contractspec-connect/src/lifecycle-authority.
    2. Run bun test packages/bundles/workspace/src/cli/commands/connect/hook-authority-lineage.test.ts packages/bundles/workspace/src/cli/commands/connect/host-hook-session.cli.test.ts packages/bundles/workspace/src/cli/commands/connect/host-hook-run-mode.cli.test.ts.

Unique release changes

  • Additive. Hosts that invoke MCP or registry tools should list tools with filterConnectVisibleToolsV1 and call admitConnectToolInvocationV1 with the caller's scope, the Connect permit and the Runtime Node V3 order before dispatching the operation; a projected admission does not replace Runtime Node verifyDispatch. Tool keys are server-qualified (<source>:<serverRef>#<toolName>).

    3 packages · 3 occurrences

  • Additive. Persist ChannelAdmissionRecordV1 by compare-and-swap on revision, back ChannelTrustDecisionPortV1 with Connect, and pass createChannelAdmissionContextCompilerV1 as the ingress context compiler.

    3 packages · 3 occurrences

  • Additive. Wrap writers of policies, approvals, constraints, memory, roles and identity links with createAuthorityGuardedWriterV1, a Connect-backed GovernedDecisionVerifierPortV1 and the host's payload digester.

    3 packages · 3 occurrences

  • Apply LSSM_OS_POSTGRES_OPERATION_APPROVAL_MIGRATION_V1 after 0017, register each mandate owner's Ed25519 key, then re-issue every standing mandate revision with ownerSignature.

    3 packages · 3 occurrences

  • Connect tool authority, CommunicationOS channel admission and a personalization authority guard implement three contracted agent-platform invariants

    3 packages · 3 occurrences

  • Connect-side effect admission, Connect operation-approval receipts with durable single-use nonces, owner-signed standing mandates and declared-required operation status readiness.

    3 packages · 3 occurrences

  • Move review, governance and audit operation declarations to canonical owners

    3 packages · 3 occurrences

  • Additive. Grants issued before this change keep their exact HEAD binding and establish no lifecycle event; new grants follow in-scope commits and establish SessionStart, Stop and handoff.

    2 packages · 2 occurrences

  • Connect host hooks get durable lifecycle authority, and an operator hook grant survives the agent's own in-scope commits without permitting self-grants

    2 packages · 2 occurrences

  • Run the contract unit tests and the workspace hook tests.

    2 packages · 2 occurrences

  • The contracts-spec pack adds a Claude Code SessionEnd entry that runs the before-handoff hook. Generated .claude/settings.json picks it up only after agentpacks regeneration, which is an operator step.

    2 packages · 2 occurrences

Impacted packages

  • @lssm-tech/app.agent-host

    Layer: apps · 2 changes

  • @lssm-tech/bundle.workspace

    Layer: bundles · 4 changes

  • @lssm-tech/integration.lssm-os-state-postgres

    Layer: integrations · 2 changes

  • @lssm-tech/lib.communication-runtime

    Layer: libs · 4 changes

  • @lssm-tech/lib.contracts-spec

    Layer: libs · 1 change

  • @lssm-tech/lib.contractspec-connect

    Layer: libs · 1 change

  • @lssm-tech/lib.observability

    Layer: libs · 1 change

  • @lssm-tech/lib.personalization

    Layer: libs · 4 changes