[Dobbes]

Summary

Documentation-only follow-up to merged PR #95, targeting feature/python-client (not develop). Changes only python-client/docs/develop-worldview-compatibility-issue.md.

Make the Ferdinando/Java-platform handoff explicit about which tests expose each compatibility blocker:

• List exact pytest node IDs, named-suite mappings, prerequisites and assertions.
• Separate the uncaptured ODO import case from the post-provisioning land domain failure; include commands and expected server diagnostics.
• Pin the Python tools separately from the unchanged-develop Java baseline and give setup instructions.
• Explain direct pytest invocation, the default live-test exclusion, already-running-state requirements and expected JUnit/log evidence.
• Identify the original scientific tests that encountered HTTP 500, and distinguish actually recorded test failures from new reproduction recipes.
• Include the full compatibility test command and explain which scientific/restart assertions remain unreached.

Validation

• Collection-only check: all four documented functional test IDs collected successfully; exit 0. No services or remote scientific objects started/created.
• Cross-checked the exact failed test names against retained JUnit from the original scientific run, both historical full compatibility runs, and the readiness-only baseline run.
• Local source/evidence links verified; git diff --check passed.
• No new live tests or fresh-clone builds were run for this documentation-only change. The existing semantic blocker and Java CI dependency-resolution failure are not fixed or represented as passing.

The old SHA-pinned document link is immutable; use this PR's revised document for the expanded reproduction instructions. No Java/API, worldview, ontology, executable Python or test code changes are included.