Complete MolSysSuite Ruff and governance policy adoption

[LMMV]

What — ElastNetMT has the shared Python range but does not yet conform to the common MolSysSuite Ruff, vendored-guide, and governance-pointer requirements.

How — Add the explicit central governance route, configure Ruff target py311 with the shared lint rules and root-guide exclusions, remove active Flake8 configuration, and make the MolSysSuite policy workflow green.

Why — The repository is an incubating suite member and may display the live policy badge, but policy health must remain visibly failing until these measured findings are resolved. Central policy: uibcdf/molsyssuite#6.

[LMMV]

MolSysSuite adoption checkpoint (2026-09-22): the required immutable release is now policy-v1.4.5. The central checker still measures the existing migration work: explicit governance routing, the common Ruff configuration, and removal of active Flake8 configuration. The caller therefore remains deliberately on policy-v1.4.1; this issue is the local migration owner linked from uibcdf/molsyssuite#34.

[LMMV]

Resolved by f3418a8, 3510cf7, 30b031b, and 8d6cacb. The central check_repository gate, Ruff lint/format, and 27 local pytest-receptor tests pass. Hosted CI 35961592607 passes all 6 Python jobs; MolSysSuite policy 35961592959 and MolSysViewer contract 35961592508 pass. The Python 3.11 Conda artifact limitation is tracked separately in uibcdf/lindelint#7; the source-only test route is documented in devtools/conda-envs/test_env.yaml. The policy caller remains compatible with the central release while new MOLI ecosystem reviews remain pending in the suite inventory.