From 239faf7e56429172b194285400705a24278e5ff6 Mon Sep 17 00:00:00 2001 From: Danijel Martinek Date: Thu, 14 May 2026 10:13:08 +0000 Subject: [PATCH] docs(claude-md): add library evaluation policy bullet to Key Conventions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit New runtime dependencies require a library trace produced by the /evaluate-library skill — without this bullet the policy is invisible to agents starting a fresh session (ADR-022). --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index 336639a..a0efc28 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -124,6 +124,7 @@ See `docs/guides/coverage.md` for the cookbook and ADR-020 for the full rational - **Manifest-first ordering** — for any new use case, the workflow is **(1) manifest entry** → **(2) contracts** (`xInputSchema`, `xOutputSchema`, `IXUseCase`) → **(3) tests (red)** → **(4) implementation (green)**. The generator emits the manifest + a self-asserting `bind-production.ts` so new features are conformance-compliant by default - **Self-asserting `bindProductionX(ctx)`** — every feature's bind-production calls `assertFeatureConformance(container, manifest, symbols, ctx)` at its tail. `pnpm dev` refuses to boot on drift - **`pnpm conformance`** — cross-feature event-closure check; fails CI on orphan consumers +- **New runtime dependencies require a library trace** — adding a runtime dependency to a feature- or core-tier package requires a trace at `docs/library-decisions/-.md` produced by the `/evaluate-library` skill; see ADR-022 and `docs/guides/adding-a-library.md` ## MCP Servers