mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 20:34:19 +00:00
Updating a tracked repo is a fail-closed sequence: check for uncommitted changes, pull, audit what was pulled, reset to the pre-pull commit when the audit blocks. The CLI had two copies of the pull flow, the dashboard a third, and the audit gate existed four times (CLI, dashboard, and two in install). The copies had drifted: the dashboard ignored a failed git status and never refreshed root-skill metadata, and each copy worded a failed rollback on its own. update.TrackedRepo now owns the sequence and returns a structured result; install.AuditGate is the only gate. internal/update is a new package because internal/git already imports internal/install. The CLI keeps its spinner, rows and the "Apply anyway?" prompt, passed in as one Confirm callback; the dashboard turns the result into its JSON item. Behaviour changes, all towards the stricter copy: - the dashboard reports a failed git status as an error instead of pulling; - the dashboard refreshes root-skill metadata after an update, like the CLI; - a prompt that fails rolls the update back instead of leaving it applied; - the rollback-failed and rollback-unavailable texts come from one place. Accepted findings stay as they were (CLI honours and records them, the dashboard does neither), now as the explicit AcceptedFindings input. The "blocked and rolled back" texts are unchanged per caller because the dashboard matches on them. Refs #443
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, 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 |