tags are how the marketplace is browsed rather than scrolled: a list of them on
the left, the plugins that carry one on the right. a closed vocabulary
(PLUGIN_TAGS in the platform) because free text becomes homelab, home-lab, Home
Lab and selfhosted inside a month, and a filter list of synonyms is worse than
no filter at all.
declared here rather than curated in the catalogue, so a plugin can say what it
is and nobody edits a table when one ships. the marketplace caches it on sync,
exactly as it already does for label and summary.
The reference plugin named web/Router.tsx as the way to ship a frontend. Discovery checks for
web/panels.ts and web/layout.ts by those exact names and refuses a web/ directory missing either — so
anyone following the example would have written a plugin the platform rejects.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The reference plugin — deliberately the smallest thing that is still a real
plugin, and what EXTRACTING-A-PLUGIN.md sends people to read.
It leaves the platform tree with music and offscale, so that `plugins/` in the
platform repository holds documentation and nothing else. That is the point of
the move: a directory that contains both tracked source and untracked installs
is one where "is this mine or is this installed" has no answer you can see.
Same extraction as the two before it: source only, no history. The platform's
history still holds every commit that shaped this.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pastilhas
