discovery: 406 candidate(s) awaiting triage (2026-09-11)

[github-actions]

Automated sweep of every dsh discovery topic, npm, and GitHub code search.

Coverage this run — each topic swept exhaustively, past GitHub's
1000-result search cap, by slicing on creation date and star count:

discover: topic:dsh-plugin -> examined 14355 new / 14357 in topic
discover: topic:dsh-plugins -> examined 67 new / 1736 in topic
discover: topic:dsh-theme -> examined 3 new / 24 in topic
discover: topic:dsh-skin -> examined 1 new / 17 in topic
discover: topic:dsh-skill -> examined 25 new / 169 in topic
discover: topic:dsh-bundle -> examined 9 new / 159 in topic
discover: topic:dsh -> examined 1010 new / 6672 in topic
discover: topic:deepseek-harness -> examined 759 new / 10632 in topic
discover: topic:deepseek-harness-plugin -> examined 6 new / 607 in topic
discover: topic:deepseek-harness-plugins -> examined 1 new / 206 in topic
discover: topic:deepseekharness -> examined 2 new / 15 in topic
discover: 4061 find(s) over the 400/run cap were NOT queued; raise DISCOVER_MAX_NEW or run again after triage

What reading them found — scripts/triage.mjs --dry-run, which
fetches each repo's own files and looks for an install path:

triage: decide 400/406 (api 308)
triage: 152 admitted, 14 rejected, 232 rejection(s) re-dated, 60 rejection(s) overturned, 2 held for review, 6 routed to themes (api 311)
triage: --dry-run, nothing written

To apply that verdict, on a branch off main:

npm run triage && npm run render && npm run validate

It writes the provable ones into data/plugins.json with the file
each install path was proven in, the unprovable ones into
data/rejected.json with a reason and a recheckAfter date, and
leaves in the queue only what a machine should not decide: theme
routing and the close calls. This branch is rebuilt from main and
force-pushed on every run, so merge or close whenever; the next run
reopens or refreshes it.