Odoo-derived Python compatibility

tools/python_compatibility.py is the CLI bridge to the shared implementation in the sibling _pmiguidelines repository. See its compatibility contract for source ownership, regeneration, runtime gates, and validation boundaries.

python tools/python_compatibility.py matrix --odoo-root /srv/pmiverse/_pmisuite18/repos/OCB
python tools/python_compatibility.py verify --odoo-root /srv/pmiverse/_pmisuite18/repos/OCB

Run verify with the interpreter intended for the selected Odoo checkout. The compatibility bridge checks Python support; it does not create virtual environments or install dependencies. Runtime requirement inventories are maintained separately by the requirement collector.

Addon test and lint runners accept PMISUITE_VENV, defaulting to the suite's existing venv. CI templates use this override to isolate each Odoo-supported Python version. They remain templates requiring the documented workspace layout, runner provisioning, and addon selection before activation.

Ruff's minimum target is generated alongside the packaged Odoo support policy. Run the shared refresh command with an explicit --ruff-config, then the read-only check command. Existing addon copies can be synchronized separately using the existing Ruff policy synchronization tool. Dependency markers remain version-specific where upstream packages require them.