Guidelines

  • Keep changes focused and well-tested.
  • Prefer configuration-driven behavior over hard-coded constants.
  • Update docs when behavior changes (workflow stages, config keys, env vars).

Before opening a PR

1
pytest -q