Cap powerio below 0.10 so a fresh install resolves a usable version

[qian-harvard]

The problem

pip install powermcp==0.3.0 has been broken since powerio 0.10.0 shipped, and main's CI has been red for 12 days for the same reason.

pyproject.toml:52 declares powerio[mcp,matrix]>=0.9.0,<1. powerio is pre-1.0, so a <1 ceiling admits every future minor — today the resolver picks 0.11.3. But the code targets the 0.9 API, and 0.11 removed powerio.Package, which powermcp/solver_case.py calls at seven sites (:115, :130, :253, :257, :261, :267), and renamed most of the powerio.mcp.server surface.

Verified against the published wheels:

	powerio 0.9.0	powerio 0.11.3
class Package	present	gone
parse_file	present	gone

CI run 34049789070 on main@97e3dd9 — 61 failed, 283 passed, 17 skipped on both 3.10 and 3.12:

module 'powerio' has no attribute 'Package'              x32
module 'powerio.mcp.server' has no attribute 'save'      x32
module 'powerio.mcp.server' has no attribute 'matrix'    x24
module 'powerio.mcp.server' has no attribute 'convert'   x20
module 'powerio' has no attribute 'parse_file'            x4

That run installed powerio-0.11.0. A run today would install 0.11.3 and fail the same way. The last green run on main was the v0.3.0 release itself (2026-08-22).

Worth noting the knock-on cost: every open PR is currently being evaluated against a red baseline. In #68 the author absorbed all of #64's work into his branch because his own clean two-file commit failed with 78 errors, none of them in his code.

The change

Cap the ceiling at <0.10 in all thirteen declaration sites — the root pyproject.toml, PSCAD/pyproject.toml, and eleven requirements.txt files. Bump to 0.3.1. Add a comment at the root declaration recording why the ceiling is 0.10 rather than 1, so it doesn't regress.

No code changes. Moving to the 0.11 API is #64's job, and this pin is superseded the moment that lands.

tests/test_doctor.py:124 also contains the string powerio[mcp,matrix]>=0.9.0,<1, deliberately left alone: it is a synthetic fixture feeding doctor._declared_requirement to test specifier parsing, not a declaration of this repo's dependency, and its Version("1.0.0") not in req.specifier assertion is still exactly what it means to test.

Verification

• pip download "powerio[mcp,matrix]>=0.9.0,<0.10" resolves to powerio 0.9.0, and that wheel's __init__.py exports both class Package and parse_file — the two names solver_case.py needs.
• All four pyproject.toml files parse under tomllib; all eleven requirements.txt files intact.
• pytest tests/test_doctor.py — 16 passed, 3 failed, and those same 3 fail identically on unmodified main (they concern hope/PyYAML in my local environment, not this change). The test that reads a powerio specifier, test_the_floor_is_found_without_top_level_distribution_metadata, passes.
• The full suite was not run locally: this machine has mcp 1.29.0, which lacks mcp.server.mcpserver, so ~66 tests fail here for environmental reasons. CI is the real check, and it should go green on this branch.

Suggested follow-up

Tag v0.3.1 and publish once this is green. There is currently no released version of PowerMCP that installs and works.

🤖 Generated with Claude Code