bindings docs: development and testing pages drift from the tests, scripts, and workflows #62

A read-only audit of bindings/python/docs/development/ (including the testing pages) against the tests, scripts, CI workflows, and pyproject found about 115 places where the pages had drifted:

• Testing pages that said a test asserts something it does not (for example "the edge flush runs on more than one worker", "bools survive the round trip", "persisted" where nothing reopens).
• Build instructions with a JAR path glob that never expands, and run commands that do not match pyproject or the scripts.
• Tests, CI jobs, and build steps no page describes.
• Hand-carried test counts and dated narrative.

Apply each finding after checking it against the files, under the repository's documentation rules (docs say what is; no carried counts; retire rather than annotate).