mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-11-10 22:13:07 +09:00
Juan DenisandClaude Opus 5
da4346ccee
20 tests across five files failed on any checkout with the serverkit-wordpress sibling repo present, with the message "the serverkit-wordpress extension is not installed". That message is what made this hard to see: the extension WAS available, and the suite is explicitly built so a fresh clone passes without it. The cause is that wordpress_bridge.ensure_loadable() gates on an ACTIVE InstalledPlugin ROW, not on importability. That is deliberate (audit F2): a DISABLED extension's modules stay importable so its blueprints can be re-mounted, but its services must not be reachable. When that check landed, wp_extension_package quietly stopped being able to deliver what its docstring promised -- it only registers the package in sys.modules, and it took no `app` fixture, so it could not create a row even in principle. Its sibling wp_extension seeds one, which is exactly why those tests passed and these did not. So the fixture now seeds the active row too. Nothing about the extraction was wrong; a fixture lost a capability and the error message blamed the wrong thing. Verified: the five affected files plus test_setup_reconcile (the other consumer of this fixture) -- 96 passed, 0 failed, where 20 failed before. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>