Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 1 - 9, CONTRIBUTING.md currently only documents
the release process; add additional top-level sections to help first-time
contributors by creating headers and content for Development setup
(dependencies, virtualenv/venv, how to install with pip, example commands),
Running tests (how to run unit/integration tests, pytest commands, CI notes),
Coding standards (formatting, linting, pre-commit hooks, reference to any style
guides), and PR process (branching, commit message format, how to open a PR,
review/CI expectations) so the doc becomes a fuller contributor guide; update
the existing "Releasing" section with a brief cross-reference and ensure each
new section includes example commands and links to relevant files/scripts in the
repo (use these section titles to locate and edit the file).