6 Commits

Include renames

Author	SHA1	Message	Date
github-actions[bot]andgithub-actions[bot]	d31df2769c	chore: regenerate registry indexes for b0f7c864 (#106) ... Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	2026-09-14 14:46:03 +09:00
Evan	ff69767793	fix(hands/devteam): raise default token limits (#102) ... * fix(hands/devteam): raise role token limits * fix(hands/devteam): bump patch version	2026-07-16 14:23:35 +09:00
Burak Bayırandkriptoburak	89d0e4c8b3	Add Xquik social data skill (#97) ... Co-authored-by: kriptoburak <kriptoburak@users.noreply.github.com>	2026-06-12 00:34:08 +09:00
github-actions[bot]	89ee8a8a56	chore: regenerate registry indexes for d2153880 (#95)	2026-05-20 08:53:02 +09:00
github-actions[bot]andgithub-actions[bot]	990d22009c	chore: regenerate registry indexes for 102b506b (#93) ... Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>	2026-05-14 14:59:15 +09:00
Evan Hu	ff6f3f2b25	ci: build registry-index.json in-repo for dashboard real-time updates ... Pair with the existing plugins-index.json path (which feeds the daemon's signed install lane). registry-index.json mirrors the dict-shaped payload the registry-worker's cron currently builds via 40+ GitHub Contents API calls — but built locally from the checked-out tree by scripts/build-registry-index.mjs, so the worker only fetches ONE file per category type (2 total: plugins + registry) on refresh. Workflow now picks up content changes across all 8 category dirs (was: plugins/ only) so dashboard updates land within seconds of a push instead of waiting for the 02:00 UTC cron tick. The dashboard's /api/registry endpoint reads kv_store('registry_data'); the worker's forced-refresh now writes that key with these bytes and purges the Cache-API entry, so the next dashboard hit sees fresh data instead of the 1h-cached previous payload. Generated counts on first build: 11p 17h 32a 60s 44c 57pr 22w 33mcp.	2026-05-05 00:43:30 +09:00