Maintenance

How to keep this topic truthful as herdr and the marketplace move. Herd’s plugin surface is young (0.9.x); details drift. Each check below names its trigger and effort; the whole loop takes about 15 minutes after a notable release.

Trigger: a notable herdr release

Herd ships via GitHub releases. When a release touches plugins, events, or the agent API:

  1. Diff the docs. The 0.9.3 docs used throughout this topic live in-repo at _repos/herdrdev-herdr/docs/versions/0.9.3/website/src/content/docs/. Compare plugins.mdx, agent-automation.mdx, and configuration.mdx against the new version directory. Do not cite docs/next/: it holds unreleased drafts.

  2. Check the event list. The 26-event list in event-model.md comes from _repos/herdrdev-herdr/src/api/schema/events.rs. New events are declarations, not breaks, but record them.

  3. Re-verify Context7’s snapshot age. The /herdrdev/herdr corpus is a 0.9.0 snapshot; anything version-sensitive learned from it must be re-checked against the in-repo docs of the target version.

  4. Refresh the mirrors.

    ./scripts/sync-repos.sh update-manifest

    This refreshes the _repos/*-herdr* clones and the manifest. Shallow mirrors; never build in them.

Trigger: before naming any new plugin

The collision check is cheap and the cost of skipping it is destroying a stranger’s install:

curl -s https://assets.herdr.dev/plugins/index.json -o /tmp/index.json
jq -r '.. | objects | select(has("id")) | .id' /tmp/index.json | sort -u | grep -i "^peteretelej\." || echo "id clear"
# and check the display name
jq -r '.. | objects | select(has("name")) | .name' /tmp/index.json | sort -u | grep -i "<your name>" || echo "name clear"

If your id or display name appears: pick another. See marketplace-landscape.md for why flat names collide and prefixes do not.

Trigger: quarterly, or when a claim feels stale

CheckHowWhat to update
Marketplace countsRe-pull index.json; count repos/pluginsNumbers in marketplace-landscape.md
Archetype mapSkim the index for new categories or standout reposArchetype table, exemplars, unclaimed niches
Exemplar repos still aliveCheck the mirrored repos for new commits/releasesTeardowns (teardown-pane-topic-sync.md, teardown-collie.md, teardown-herdr-agent-usage.md)
Open plugin-API issuesgh api repos/herdrdev/herdr/issues/3380 and 3801common-failures.md rows when they close
Context7 snapshot ageRe-resolve /herdrdev/herdr; check snippet version claimsSources blocks noting “0.9.0 snapshot - verify against X”
Lab suite statusRoadmap table vs reality in peteretelej/herdr-pluginslab-conventions.md

Tracking the two known API gaps

Source-of-truth priorities

When sources disagree, trust in this order:

  1. _repos/herdrdev-herdr/src/ source code (current clone)
  2. In-repo versioned docs (docs/versions/<release>/)
  3. Live site (herdr.dev/docs/...)
  4. Context7 snapshots (note their age)
  5. This topic’s pages (update them when 1-4 contradict)