mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-19 02:17:09 +00:00
* fix(ui): show where pull conflict versions differ The pull conflict dialog showed both versions in short 208px panes with no marking, so users had to scroll and compare long files by eye to find what actually conflicted. Panes now use 55vh, lines that only one side has are tinted, each side scrolls to its first difference, and the header counts differing lines. * chore(docs): move ai-context router config into wiki/ The router config describes wiki topics, so it belongs next to the pages it maps; docs/ reads as public documentation. The script is synced with the upstream router, which also normalizes backslash paths and forces UTF-8 output for Windows consoles. The router runs on the host rather than the devcontainer, so the kernel now says to use py or python on Windows when python3 is unavailable. * fix(ui): give pull conflict panes room and tidy the dialog edges Short conflicting files still rendered as cramped strips, so panes now keep a 40vh minimum. A long body scrolled straight under the title, so the header gets a separator like the footer. The conflict banner's text sat above its button because notes align to the top for multi-line errors; it is centered when the message is the fixed conflict text. * fix(ui): bound the pull conflict line diff diffLines keeps an n×m table, so two 16 KiB previews that differ on every line could allocate hundreds of megabytes and freeze the dialog. Matching leading and trailing lines are now skipped before diffing, and versions whose differing middle would still need over a million cells are shown unmarked.
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 |
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 |
|---|---|
| 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 |