mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-18 18:04:17 +00:00
* fix(update): honor accepted findings in dashboard tracked updates The dashboard ignored findings accepted through the CLI, so a tracked repo that `update --force` let through was blocked again on the next dashboard update, and every dashboard Force Retry had to be repeated. Regular skill updates in the dashboard already honored and recorded acceptances, so only tracked repos differed. Tracked-repo updates now always honor accepted findings and record the ones an override lets through, for both callers. The opt-in option and the AuditGate flag it fed are removed, since no caller turns them off. Dashboard agent tracked repos passed an empty source dir, so a nested repo kept acceptances in its group folder under a different key than the CLI. They now pass the agents source, as the CLI does. * fix(update): reload the agents store after agent repo refresh Dashboard agent tracked repos now refresh metadata in the agents source, but a metadata change reloaded the skills store, leaving the agents store as it was until the next request. Reload the store that matches the source. Every caller of update.TrackedRepo now passes a source dir, so the empty-dir guard and its doc no longer describe a supported mode. The new agent test reuses the tracked fixture instead of rebuilding it.
skillshare Wiki Router
The wiki stores development background, procedures, references, and history, but no task needs all of it at once. Rules that apply to every task live in the root AGENTS.md. wiki/ai-context.json is the only source of truth for topic-to-source mappings.
python3 scripts/ai-context.py list
python3 scripts/ai-context.py <topic>
Task Routing
| Topic | Use when | Main sources |
|---|---|---|
architecture |
Tracing repository structure, data flow, or CLI/Web API boundaries | architecture.md |
cli-development |
Adding or changing Go CLI commands, flags, handlers, TUIs, or mutating behavior | cli-development.md |
testing |
Building, testing, reproducing bugs, using the devcontainer/ssenv, or running E2E runbooks | testing.md, CONTRIBUTING.md |
frontend |
Changing React, CSS, layout, or visual behavior in the dashboard or website | frontend.md, website/AGENTS.md |
documentation |
Updating README files, website docs, flags, translations, or the built-in skill | documentation.md, CONTRIBUTING.md |
release |
Writing changelogs or release notes, bumping versions, tagging, or releasing | release.md |
audit |
Running read-only consistency audits | audit.md |
pull-requests |
Opening a pull request or handling its review comments, including Codex review | pull-requests.md |
ai-context |
Maintaining router topics, budgets, and orphan checks | ai-context.md |
Run python3 scripts/ai-context.py check after changing topics. This table is the human entry point; the JSON configuration controls what the loader renders.
History (Milestone Logs; Read on Demand)
Completed milestones are recorded here and read only when relevant.
| File | Contents |
|---|---|
| OMP native support | Native MCP/Hooks, safe Extension selection, bounded Plugin support and shared-cache blocker |
| Shared memory notes | Shared Markdown source, CLI/API/dashboard, recent notes, trial/organization prompts, versioned edits and native memory boundaries |
| Git hooks management | Config-mode destinations, includes, ownership, native verification and execution limits |
| Native hooks management | Native formats, CLI/dashboard scope, ownership and verification evidence |
| MCP: Pi built-in only and tool policy | 0.23.0 Pi migration, per-Agent tool policy translation, evidence and limits |