gotchas.
- **Modular pipelines** — see [modular.md](references/modular.md) for modular pipeline conventions, patterns, and gotchas.
- **Tests** — see [testing.md](references/testing.md) for test conventions: required test layers, tester mixins, and dummy-component rules.
- **Reporting
editing it. Check only verified checklist items; explain skipped or inapplicable checks in `Testing`.
## Code Quality
- No `any` unless absolutely necessary.
- **NEVER use `ReturnType<>`** — use the actual type name.
- **NEVER
agents MUST analyze the affected
`test/openapi-test` coverage and update the API IT scenario matrix, test
cases, and coverage registry in the same change set. If the functional path
cannot
process communication must go through the IPC bridge (`packages/desktop/src/preload/`).
See [docs/architecture/overview.md](docs/architecture/overview.md) for details.
## Testing
**Framework**: Vitest 4 (`vitest.config.ts`). Project coverage target is ≥ 80%; ordinary changes should add focused tests
SECURITY.md` and `SECURITY-NOTICE.md` — when touching parsing, files, subprocesses, generated content, or dependencies.
5. Existing tests closest to the code being changed.
For the progressive-disclosure research/evaluation initiative, also read:
- `docs/research/progressive-disclosure-evals.md
from the OpenAI API schema. Follow `CONTRIBUTING.md` before
changing generated files. Handwritten policy, automation, tests, and examples
should remain small and should not alter exported SDK APIs unless the change
Agent Instructions
Project context (architecture, commands, conventions, tests) is in `CLAUDE.md`. This file holds the rules for every coding agent working in this repository.
## Non-Interactive Shell Commands
limit.
- **Naming an interactive element has a cost:** named participants are skipped by hit-testing while a transition runs ([csswg#10930](https://github.com/w3c/csswg-drafts/issues/10930)) — clicks and hover fall through
work with the cognee repository: how it’s organized, how to build, test, lint, and contribute. It mirrors our actual tooling and CI while providing quick commands for local development
Manager**: Use `pnpm` instead of `npm` for Node.js package management in this repository.
## Build & Test
> [!IMPORTANT]
> **Test Coverage**: The `codecov/patch` check requires that new or modified lines are covered
skill references, compatibility mirrors, or validation.
- `bug-fixing`: fixing a defect and choosing regression tests.
- `cross-sdk-parity`: aligning TypeScript and Python behavior, generated client bumps, or API contract drift
your plan step by step
- Write clean, idiomatic code that matches existing patterns
- Run tests after each significant change
- If tests fail, debug and fix before moving on
- Update your
skills, sandbox bootstrap, and slash-command surface.
For monorepo-wide conventions (commit titles, lint, testing, docs, CI, benchmarks), see the root `AGENTS.md`. For a high-level map of the package
aggregate-only`.
- `pytest_reporter` rewrites pytest's session exit status to `0` even when
tests fail, so `pytest_returncode` is not a reliable failure signal —
use `counts.failed.mean` instead.
Per-trial
name. Each partner package is independently versioned and owns its environment, `pyproject.toml`, `Makefile`, and tests.
## Adding a partner package
Wire a new partner into all relevant repository surfaces:
- Area options