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-specnow treatspackages/foundation/contracts-spec/as a high-criticality governance root, likepackages/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 retiredpackages/libs/andpackages/modules/trees (including the formerpackages/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 CodeSessionStartrunscan-help catalog status --host claudecodethroughbun "$CLAUDE_PROJECT_DIR/packages/apps/cli-contractspec/src/cli.ts", and the adoptionbefore-file-edit(Write|Edit|MultiEdit) andbefore-shell-execution(Bash|PowerShell) hooks run throughpackages/bundles/workspace/src/cli/connect-hook-run.ts, because thecontractspecbinary is not on PATH here and the previous entries exited 127 without running the adoption gate.packs/contractspec-contracts-speccarries identicalclaudecodeentries, so outputs deduplicate and the gate keeps running ifcontractspec initorupdate --applyre-materializes the published pack over the override. The published consumer pack (packages/tools/agentpack-contractspec) and the Codex entries keep thecontractspecform. The override directory is a governance root. The contracts-spec pack README andcontracts-spec-connect-looprule 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 asformatting-only, unchanged capsules are counted but not listed, and--writestill normalizes formatting.release fix --writenow quarantines a scalar or mapping value ofdeprecations,affectedRuntimesoraffectedFrameworksin.changeset/<slug>.release.quarantine.yaml, as it already did forknownGaps, instead of dropping it.maintainer
contractspec release checkadds an always-passingvalidation-entriescheck. Its advisory warnings name validation commands that read as labels, outcomes, placeholders or prose, commands that citepackages/orexamples/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 invalidation.commands. The warnings never fail the check, with or without--strict.integrator
ReleaseCapsuleRepairPlangains an optionalformattingOnlyflag; therelease-filesexports 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;revokeandstatusmanage 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 withauthorityErrorand 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 cursortocontractspec connect hook ... --stdinso deny, rewrite, and review verdicts block in the host. Claude Code PreToolUse receivespermissionDecisiondeny/ask JSON, SessionStart receives bounded ConnectadditionalContext, and evaluation failures (exit 40 or unexpected errors) render asask, never as a silent allow. Omitting--hostkeeps 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
contractspeccommand 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 claudecodeand durable authority missing, SessionStartadditionalContextis 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-levelsystemMessage(stderr with--host codex). Stop and before-handoff are silent while durable hook authority is missing. Adoptionbefore-file-editandbefore-shell-executionhooks exit 0 with a skip result whenconnect.enabledis not true, in every mode (previously exit 40, which--host claudecoderendered as an ask). With--host, an adoptionrequire_reviewverdict follows the host run mode: autonomous (bypassPermissions/dontAsk) permits it as deferred review recorded inrun-mode-decisions.ndjson(eventadoption:<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 claudecodeprints one SessionStart hook document with a single-line catalog summary (version, source, stale/degraded state, content hash, counts, discovery command);--host genericprints the plain line.--hosttakes 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 asrunModeScopedGrant/runModeScopedGrantPrefixesrather than asrunMode.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.