Skip to content
← Back to changelog index

9.1.3

Oct 28, 2026 · 6 packages · 17 unique changes · 11 release entries

appsbundleslibs

This release affects the contracts, sharedLibs, solutions families.

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

Release summaries

  • authoritative-workspace-adoption-discovery

    Authoritative nested workspace adoption discovery and honest mirrored catalog provenance

    integrator

    Current workspace capabilities remain discoverable without manufacturing published catalog confidence.

  • cmp-connect-hook-pack-sources

    Govern the contracts-spec core in the LSSM Connect host hooks, drop the retired libs/modules roots, and run this repository's Claude Code catalog and adoption hooks through the workspace CLI.

    integrator

    contractspec connect hook contracts-spec now treats packages/foundation/contracts-spec/ as a high-criticality governance root, like packages/platform/delivery/contracts-spec-compat/, so core edits are gated by Connect policy and the host run mode instead of passing ungoverned. Paths under the retired packages/libs/ and packages/modules/ trees (including the former packages/libs/contracts-spec/ governance root) are no longer governed; their canonical successors stay covered. Workspaces without these LSSM paths see no change.

    maintainer

    In this repository the curated consumer-pack hooks (.agentpacks/.curated/lssm-tech-agentpack.contractspec/hooks/hooks.json) are a repo-local override: Claude Code SessionStart runs can-help catalog status --host claudecode through bun "$CLAUDE_PROJECT_DIR/packages/apps/cli-contractspec/src/cli.ts", and the adoption before-file-edit (Write|Edit|MultiEdit) and before-shell-execution (Bash|PowerShell) hooks run through packages/bundles/workspace/src/cli/connect-hook-run.ts, because the contractspec binary is not on PATH here and the previous entries exited 127 without running the adoption gate. packs/contractspec-contracts-spec carries identical claudecode entries, so outputs deduplicate and the gate keeps running if contractspec init or update --apply re-materializes the published pack over the override. The published consumer pack (packages/tools/agentpack-contractspec) and the Codex entries keep the contractspec form. The override directory is a governance root. The contracts-spec pack README and contracts-spec-connect-loop rule now state that the core is governed.

  • cmp-fix-w6-canonical-shell-governance

    Restore canonical-path Connect shell governance for command-only host payloads.

    integrator

    Commands naming canonical governed packages now reach the existing Connect authority and policy flow even without a separate touched-path array. Governance roots retain high criticality, protected targets require review, and immutable targets retain critical classification. A host may therefore ask or deny where the relocated path previously skipped governance.

    maintainer

    Shell recognition reuses the canonical governed-root table. Path hints from raw and analyzed shell forms only tighten policy and raise risk; durable authorization still receives the original target paths and exact command. The repair grants no authority, changes no permission setting, and retains legacy recognition.

  • cmp-fix-w7-local-grant-lineage-paths

    Preserve exact filenames and merge-history changes in local hook grant lineage checks

    integrator

    Local hook lineage now preserves unusual filenames exactly and inspects merge-introduced changes as well as all reachable commits and the net tree. Signed scopes, expiry, lifecycle events and authority requests are unchanged; this repairs enforcement of the existing every-commit contract.

    maintainer

    The Git adapter uses NUL path records and first-parent merge diffs without limiting history traversal to the first parent. Real Git regressions cover quoted and control-character names, reverted operator paths, merge-only changes hidden by a later merge, and valid merges whose second-parent differences predate the grant. The canonical lifecycle DocBlock and design documentation clarify that operator-only policy and best-effort shell/TTY checks do not establish operating-system isolation.

  • cmp-release-tooling-code

    Release capsule repair quarantines scalar string-list values, the release fix dry run no longer fails on formatting-only capsules, and release check warns about validation entries that are not runnable or not backed by a listed command.

    maintainer

    contractspec release fix <slug>|--all (dry run) exits non-zero only while a repair would change capsule content or quarantine something. Capsules that differ from the canonical layout only in YAML formatting are listed as formatting-only, unchanged capsules are counted but not listed, and --write still normalizes formatting. release fix --write now quarantines a scalar or mapping value of deprecations, affectedRuntimes or affectedFrameworks in .changeset/<slug>.release.quarantine.yaml, as it already did for knownGaps, instead of dropping it.

    maintainer

    contractspec release check adds an always-passing validation-entries check. Its advisory warnings name validation commands that read as labels, outcomes, placeholders or prose, commands that cite packages/ or examples/ paths missing from the workspace (a missing file whose directory exists still passes, so test name prefixes work), and evidence entries that quote a run of a command not listed in validation.commands. The warnings never fail the check, with or without --strict.

    integrator

    ReleaseCapsuleRepairPlan gains an optional formattingOnly flag; the release-files exports are unchanged and the module now delegates to private leaves.

  • connect-hook-durable-authority

    Local operator grants wire durable Hook Authority V1 into Connect host hooks

    maintainer

    contractspec connect hook authority grant --path <prefix/> [--command <cmd>] [--ttl <minutes>] [--host-session <id>] --confirm-workspace <root> (interactive terminal only) binds host sessions in a workspace to a signed, HEAD-bound Hook Authority V1 session; revoke and status manage it without printing the session capability.

    integrator

    Host hooks (--host claudecode|codex|cursor) inject the durable SQLite Hook Authority V1 port for before-file-edit, after-file-edit and before-shell-execution when a grant store exists; authority denials block at the authority stage with authorityError and remediation. Without a grant the host output is unchanged apart from guidance text naming the grant command.

  • connect-hook-host-protocol

    Map Connect hook verdicts onto Claude Code, Codex, and Cursor blocking protocols with a fail-closed host mode.

    integrator

    Host integrations add --host claudecode, --host codex, or --host cursor to contractspec connect hook ... --stdin so deny, rewrite, and review verdicts block in the host. Claude Code PreToolUse receives permissionDecision deny/ask JSON, SessionStart receives bounded Connect additionalContext, and evaluation failures (exit 40 or unexpected errors) render as ask, never as a silent allow. Omitting --host keeps the 0/10/20/30/40 exit codes for CI callers.

    maintainer

    Repository Claude Code and Codex hooks now run the workspace CLI entry through bun with the host protocol. Until a durable Hook Authority port is wired (exception connect-hook-authority-port-unwired), governed contracts-spec/LSSM edits and shell commands are evaluated by Connect policy: policy deny/rewrite block, everything else asks the operator. The published Cursor plugin keeps the contractspec command form and requires a CLI release that accepts --host.

  • connect-hook-quiet-claude

    Connect hooks stop injecting operator text into every Claude Code session and stop emitting operator-confirmation messages on every turn; adoption hooks skip when Connect is disabled and follow host run modes for reviews; catalog status gains a one-line host form.

    integrator

    With --host claudecode and durable authority missing, SessionStart additionalContext is agent-facing and at most 300 characters (active run mode, follow deny reasons or report the blocker, grants are operator-only, contractspec connect mode show); an authorized session start keeps the bounded context-pack summary. The authority exception and run-mode mapping move to a top-level systemMessage (stderr with --host codex). Stop and before-handoff are silent while durable hook authority is missing. Adoption before-file-edit and before-shell-execution hooks exit 0 with a skip result when connect.enabled is not true, in every mode (previously exit 40, which --host claudecode rendered as an ask). With --host, an adoption require_review verdict follows the host run mode: autonomous (bypassPermissions/dontAsk) permits it as deferred review recorded in run-mode-decisions.ndjson (event adoption:<event>), supervised asks, readonly denies. Policy deny/rewrite blocking, evaluation failures failing closed, and the generic exit-code contract for governed verdicts are unchanged.

    maintainer

    contractspec can-help catalog status --host claudecode prints one SessionStart hook document with a single-line catalog summary (version, source, stale/degraded state, content hash, counts, discovery command); --host generic prints the plain line. --host takes precedence over --json, and a catalog that cannot be loaded yields an unavailable line with exit 0. The session-start JSON result now also carries the resolved session run mode when durable authority is missing; a path-scoped operator grant appears as runModeScopedGrant/runModeScopedGrantPrefixes rather than as runMode.

  • i18n-check-workspace-discovery

    The i18n check reports each authored catalog once and forwards an identical-value allowlist.

    maintainer

    contractspec i18n check no longer scans node_modules or dist and no longer follows workspace links into duplicate groups, so its counts and warnings match the authored catalogs. A custom catalogGlob that targets dist no longer matches. Each group's catalogDir is relative to its packagePath, so issue paths name the catalog once. Identical-by-design values can be allowlisted with --missing-translation-allowlist.

    integrator

    ai-agent error and export-validation messages quote tool and provider names with double quotes instead of apostrophes in en and es. Code that matches the old apostrophe-quoted text must update its expectation.

  • release-changeset-newline-portability

    Preserve release metadata and native absolute paths across Windows and POSIX

    maintainer

    Windows line endings retain the same package release metadata as LF files.

  • release-workspace-layout-discovery

    Resolve release packages from authoritative workspace patterns after relocation

    integrator

    Nested canonical packages retain their actual versions in release artifacts; excluded and private packages remain excluded.

Migration guide

  • Optionally provision a local hook authority grant

    Additive only; without a grant, hooks behave as before. A grant replaces operator confirmation prompts for governed edits with durable authority, and binds the current HEAD, so re-grant after commits.

    1. Run contractspec connect hook authority grant --path <prefix/> --confirm-workspace <root> from an operator terminal.
    2. Check it with contractspec connect hook authority status --json; revoke with contractspec connect hook authority revoke.
  • Provision durable hook authority before editing governed paths from a host

    Connect verdicts 10/20/30 used to surface as non-blocking hook errors in Claude Code and Codex; with --host they block, so governed contracts-spec/LSSM edits need durable hook authority.

    1. Provision durable hook authority through contractspec connect review provision-authority.
    2. Keep CI callers on the default exit-code contract by omitting --host.

Upgrade steps

  • Verify exact path and merge lineage enforcement

    auto

    Run the real Git and existing operator lifecycle regression suites.

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

    1. Run bun test packages/bundles/workspace/src/cli/commands/connect/hook-authority-local-git.test.ts packages/bundles/workspace/src/cli/commands/connect/hook-authority-lineage.test.ts.
    2. Run bun test packages/platform/governance/contractspec-connect/src/lifecycle-authority.
  • Regenerate the repository agent outputs from the pack sources

    manual

    Pack sources changed; .claude/settings.json, the generated rule copies and the exported Cursor plugin are refreshed by the operator, never edited by agents.

    Packages: @lssm-tech/bundle.workspace

    1. Run bun run agentpacks:validate, then bun run agentpacks:all (or agentpacks:claude), and confirm bun run agentpacks:diff exits 0.
    2. Run bun run agentpacks:export:contractspec-contracts-spec to refresh the Cursor marketplace plugin copy of the pack README and rule.
    3. If contractspec init or contractspec update --apply rewrites .agentpacks/.curated/lssm-tech-agentpack.contractspec/hooks/hooks.json, restore it with git checkout -- .agentpacks/.curated/lssm-tech-agentpack.contractspec/hooks/hooks.json and regenerate.
  • Regenerate Claude Code hook wiring

    manual

    The contracts-spec pack no longer wires before-handoff to the Claude Code Stop event, because Claude Code has no handoff event. Regenerated settings run only contracts-spec stop.

    Packages: @lssm-tech/bundle.workspace, @lssm-tech/app.cli-contractspec

    1. As the operator, regenerate the agent outputs with agentpacks so .claude/settings.json picks up the single Stop entry.
    2. Run bun run agentpacks:diff afterwards and confirm only the Stop, SessionStart and adoption hook entries and the catalog-memory rule scope changed.
  • Regenerate agent hook outputs with the matching host protocol

    assisted

    Hook commands must pass the --host value for their agent host; update the CLI and the Cursor plugin together.

    Packages: @lssm-tech/bundle.workspace, @lssm-tech/app.cli-contractspec, @lssm-tech/lib.cli-runtime

    1. Run bun run agentpacks:validate and regenerate the agentpacks hook outputs.
    2. Confirm generated hook commands include --host claudecode, --host codex, or --host cursor.

Unique release changes

  • Connect verdicts 10/20/30 used to surface as non-blocking hook errors in Claude Code and Codex; with --host they block, so governed contracts-spec/LSSM edits need durable hook authority.

    3 packages · 3 occurrences

  • Hook commands must pass the --host value for their agent host; update the CLI and the Cursor plugin together.

    3 packages · 3 occurrences

  • Map Connect hook verdicts onto Claude Code, Codex, and Cursor blocking protocols with a fail-closed host mode.

    3 packages · 3 occurrences

  • The i18n check reports each authored catalog once and forwards an identical-value allowlist.

    3 packages · 3 occurrences

  • Additive only; without a grant, hooks behave as before. A grant replaces operator confirmation prompts for governed edits with durable authority, and binds the current HEAD, so re-grant after commits.

    2 packages · 2 occurrences

  • Connect hooks stop injecting operator text into every Claude Code session and stop emitting operator-confirmation messages on every turn; adoption hooks skip when Connect is disabled and follow host run modes for reviews; catalog status gains a one-line host form.

    2 packages · 2 occurrences

  • Local operator grants wire durable Hook Authority V1 into Connect host hooks

    2 packages · 2 occurrences

  • Preserve exact filenames and merge-history changes in local hook grant lineage checks

    2 packages · 2 occurrences

  • Release capsule repair quarantines scalar string-list values, the release fix dry run no longer fails on formatting-only capsules, and release check warns about validation entries that are not runnable or not backed by a listed command.

    2 packages · 2 occurrences

  • Run the real Git and existing operator lifecycle regression suites.

    2 packages · 2 occurrences

  • The contracts-spec pack no longer wires before-handoff to the Claude Code Stop event, because Claude Code has no handoff event. Regenerated settings run only contracts-spec stop.

    2 packages · 2 occurrences

  • Authoritative nested workspace adoption discovery and honest mirrored catalog provenance

    1 package · 1 occurrence

  • Govern the contracts-spec core in the LSSM Connect host hooks, drop the retired libs/modules roots, and run this repository's Claude Code catalog and adoption hooks through the workspace CLI.

    1 package · 1 occurrence

  • Pack sources changed; .claude/settings.json, the generated rule copies and the exported Cursor plugin are refreshed by the operator, never edited by agents.

    1 package · 1 occurrence

  • Preserve release metadata and native absolute paths across Windows and POSIX

    1 package · 1 occurrence

  • Resolve release packages from authoritative workspace patterns after relocation

    1 package · 1 occurrence

  • Restore canonical-path Connect shell governance for command-only host payloads.

    1 package · 1 occurrence

Impacted packages

  • @lssm-tech/app.cli-contractspec

    Layer: apps · 3 changes

  • @lssm-tech/bundle.managed-companyos

    Layer: bundles · 1 change

  • @lssm-tech/bundle.workspace

    Layer: bundles · 1 change

  • @lssm-tech/lib.ai-agent

    Layer: libs · 1 change

  • @lssm-tech/lib.cli-runtime

    Layer: libs · 3 changes

  • @lssm-tech/lib.contractspec-connect

    Layer: libs · 2 changes