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.
The core/ and remote/ proposals described work that has shipped. What they
said that the architecture docs lacked now lives there: the MCP client's
rules, what the gateway does today, what a plugin can reach, adding a plugin
to the host, who changes proprietary/, and the backend's copy of the
scrapers. proposals/plugins/README.md now holds only what is not built: the
chat router step, jobs and scaling on the host, organisation policy, later
MCP features and the open questions. Bundles stay deferred, with their
registry entry moved in. ADRs 0051, 0053 and 0054 are accepted, and links
into the deleted files point at the architecture docs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No REGISTRY_SIGNING_KEY secret exists for the key the app compiled in, so the
sign job could never sign. No released app trusts that key yet, so it is
replaced, not kept beside the new one: its private half is not in SurfSense's
hands. The app, the workflow's verify step and the two tests that pin the key
now name 9498a160...f10395.
A registry entry now says whether SurfSense proved its author runs the server
(a .well-known file, a DNS TXT record or the MCP Registry namespace), in place
of the stored publisher. A checkmark or a Community badge sits by its name with
a tooltip, and connecting a Community plugin first asks. Its page gains About,
Tools, Added and a Publisher row; the publisher column and its compatibility
paths are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each plugin in Browse opens one shared public page, built from its list
entry and the same whether it is connected or not: its publisher, about,
listed tools as chips, authentication, the hosts it connects to, the
month it was added, and its homepage and privacy policy. Yours keeps a
connected plugin's settings and live tools alone.
Entries gain `about`, `tools` and `added`, required in both lists and
checked in review for the registry; the first-party list's tools are
checked against each server by the plugin host's tests. One Connect
serves every listed plugin. Browse lists them in two columns.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
plugins/registry/ holds the list publishers add to by pull request, starting
with DeepWiki, and its icons. registry_check checks every entry and icon rule;
on dev, CI signs the list with Ed25519 into published/, which the release pull
request carries to main, so nothing pushes to main and the source list is
never rewritten. A small Caddy container serves the signed list, its icons and
SurfSense's OAuth client document and callback page on plugins.surfsense.com,
apart from the plugin host so a listing never restarts the scrapers. CI does
not contact listed servers: most need a sign-in, so a maintainer connects each
listing on dev. plugins/README.md is the guide for publishers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>