how to contribute

How to contribute

Start by deciding which layer you are changing: CLI, daemon, indexing, storage, graph resolution, context packs, or tooling. Then run the validators from .github/workflows/ci.yml locally before opening a pull request.

Work pickup

Change area	Start with
CLI command behavior	`src/lode/cli.py`
HTTP endpoint behavior	`src/lode/daemon.py`, `openapi/loded.openapi.yml`
Source parsing	`src/lode/indexer.py`
SQLite schema or queries	`src/lode/storage.py`
Imports, calls, inheritance, impact	`src/lode/graph.py`
Agent context output	`src/lode/context.py`
Validation and CI	`.github/workflows/ci.yml`, `scripts/`

Definition of done

Code matches the conventions in AGENTS.md.
Tests cover the changed behavior, usually in tests/test_lode.py or tests/test_graph.py.
OpenAPI docs are updated when daemon endpoints change.
Validators pass locally or the skipped check is documented in the PR.

Review expectations

The PR template in .github/pull_request_template.md asks for validation, risk, and release notes. CODEOWNERS in .github/CODEOWNERS assigns all files to the repository owner.