The install lists are inconsistent about tests and generated code

[mandli]

Comparing tracked py files against the meson install show some suspicious looking leftovers from the switch to meson more than likely. Found these while using a new check tool tools/check_installed_imports.py in clawpack/clawpack.

[mandli]

Comparing tracked .py files against the meson install plan (--drift mode of clawpack/clawpack's new tools/check_installed_imports.py) shows choices that look accidental rather than decided:

• src/pyclaw/tests/__init__.py and tests/test_io.py are installed, but tests/test_state.py is not.
• src/petclaw/tests/ holds only test_io.py, which is not installed, and has no __init__.py at all — so it is not an importable package either way.
• src/pyclaw/limiters/weno/codegen.py is not installed, though limiters/weno/reconstruct.c — which it generates via PyWENO — is checked in and compiled.
• src/pyclaw/sharpclaw/weno.py is installed but imports pyweno at module scope, so it cannot be imported in any normal install (PyWENO is unmaintained). It is a code generator, not runtime code.
• The legacy setup.py shims and build/fcompiler.py are correctly not installed.

Not a bug on its own, but worth one decision: ship tests or don't; and if the generated Fortran/C is checked in deliberately, say so near codegen.py and consider moving it and sharpclaw/weno.py out of the installed package.

Assisted-by: claude claude-opus-5[1m]