Docs

Update documentation

Use when the user asks to update docs (e.g. "update docs for this change", "add docstrings to X", "document the new API", "update README/CHANGELOG").

Input

• What changed: the user describes the change or points to code/diff (e.g. new function, new module, config change).
• Where to document: README, docstrings, CHANGELOG, docs/, or "wherever needed".

What to update (as relevant)

1. Docstrings – Public modules, classes, and functions in src/kalvi_library_template/: summary, args, returns, raises (Google or NumPy style; project may prefer one). Keep in sync with .cursor/rules/python.mdc (type hints; mypy strict).
2. README.md – Install/usage if the change affects how users run or configure the project; new commands or options; layout if new top-level paths.
3. CHANGELOG.md – If present: add an entry under Unreleased (or next version) with the change; use Conventional Commits style (feat/fix/docs).