agent-packPackage manifestv2.0.4

agentpack.contractspec

Canonical repository-local Claude, Codex, and agent guidance for ContractSpec consumers.

@lssm-tech/agentpack.contractspec

Source, release and verification context

Source snapshot bcc79fcc · Declared package version 2.0.4. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.

Package source ↗ Manifest ↗

servernode

EXPLORE THE PACKAGE

See where this package fits.

Follow a declared connection, inspect an import, then open the source guide when you need the detail.

THIS PACKAGEagentpack.contractspectools

Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.

Search this view

0 declarationsSELECT TO INSPECT

No Runtime dependencies are declared here.

PACKAGE GUIDERead at source ↗

`@lssm-tech/agentpack.contractspec`

Canonical repository-local guidance for teams consuming ContractSpec packages. It supplies marker-owned Claude Code, Codex, OpenCode, and Cursor rules, compact catalog memory, adoption hooks, one adoption skill, and local MCP wiring.

contractspec init materializes this pack into the repository-local agentpacks cache and invokes the existing agentpacks compiler. User-owned AGENTS.md and CLAUDE.md content is preserved by agentpacks managed markers. The pack never writes global Claude Desktop or Codex configuration.

Claude Code hooks use the Claude blocking protocol (--host claudecode), so an adoption denial actually blocks in Claude Code instead of surfacing as a non-blocking exit code, and an adoption review follows the session permission mode (no prompt in bypassPermissions/dontAsk, where the review is deferred and recorded; a prompt in default; a deny in plan). A workspace that has not enabled Connect (connect.enabled, off by default) is not prompted: the adoption hooks stay silent there. The shell hook matches both Bash and PowerShell, and SessionStart runs contractspec can-help catalog status --host claudecode, which adds one line of catalog context (version, source, freshness, content hash, counts, and the can-help discovery command) instead of raw JSON. These hooks need a ContractSpec CLI that supports can-help catalog status --host and connect hook adoption ... --host. The catalog memory rule loads only when package manifests or .contractspec/** files are read.

The adoption skill activates for capability selection, replacement, or a new public surface/dependency. It uses current catalog provenance and task-bound Connect decisions, then verifies affected consumers. Routine unrelated edits do not need an adoption ceremony.

Published rule/skill files and the materialized contractSpecAgentPackFiles map are one surface; bun test src/index.test.ts checks their parity.

Declared capabilities.