SurfSense/plugins/registry/check/tests
Anish Sarkar a73e6d5951 feat(registry): Verified by maintainers, and CI connects to each new or changed plugin
Verified is a maintainer's judgement: the domain rule, which only checked
that an entry agreed with itself and stopped 2.2.1's signing, is gone.
`registry_check live` connects to each plugin a pull request adds or
changes with the app's own MCP client, no credentials: it fails a server
the app could not use (unreachable, not MCP, sign-in where auth says none,
tools differing from the entry, or OAuth it cannot find, register with or
reach on the listed hosts) and only warns on what MCP leaves optional.
Failures are reported in its own words, never with what a server answered,
since a pull request's log is public. Pull requests only; the sign job
never contacts servers. ADR 0055 records the decision.
2026-10-14 15:07:04 +05:30
..
__init__.py feat(plugins): the third-party plugin registry, its check, signing and container 2026-10-12 15:59:55 +05:30
live_servers.py feat(registry): Verified by maintainers, and CI connects to each new or changed plugin 2026-10-14 15:07:04 +05:30
registry_files.py feat(plugins): a registry plugin is Verified or Community, proven by its domain 2026-10-13 20:48:50 +05:30
test_commands.py feat(plugins): the third-party plugin registry, its check, signing and container 2026-10-12 15:59:55 +05:30
test_icon_check.py feat(plugins): the third-party plugin registry, its check, signing and container 2026-10-12 15:59:55 +05:30
test_live_check.py feat(registry): Verified by maintainers, and CI connects to each new or changed plugin 2026-10-14 15:07:04 +05:30
test_signing.py fix(registry): trust a new signing key, one the maintainer holds 2026-10-13 20:48:26 -07:00
test_static_check.py feat(registry): Verified by maintainers, and CI connects to each new or changed plugin 2026-10-14 15:07:04 +05:30