mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-19 02:17:09 +00:00
* fix(projects): save new projects in config.yaml again v0.29.0 wrote every project add, edit and remove to a machine-local registry, so a project added on one machine never reached config.yaml or the other machines that share it (#792). Most people share one config.yaml and expect a new project to follow it. config.yaml is the default again. Machine-local storage stays as an explicit choice: --machine-local on add, or projects_storage: machine-local for every new project, with --shared to override it. The new share command moves a local project into config.yaml, and localize still copies one to this machine. Edits and removals stay in the layer that owns the project; removing a local copy of a config.yaml project keeps config.yaml's version unless --shared asks to remove both, so one machine cannot silently drop a project for the others. Exclusions written by v0.29.0 are left as they are. The dashboard picks storage once, in the Add project dialog, and offers the two removal choices only where both copies exist. Moving a project between layers stays a CLI command, so the detail page keeps one job. Closes #792 * fix(projects): recheck both layers after a confirmation, sync the saved key remove and share ask before taking the config lock, then compared only the merged entry after locking. A share or localize from another terminal moves a project between layers without changing that entry, so a remove confirmed for this machine's copy could then delete config.yaml's declaration for every machine, and a confirmed share could overwrite config.yaml settings changed meanwhile. The recheck now compares the owning layer and config.yaml's declaration too (ProjectLayerState). Re-adding a project that v0.29.0 hid restores config.yaml's own key, which can be spelled differently from the folder given to add (~/app versus an absolute path). add --sync looked the project up by the given spelling and failed with "project not found" after saving it; it now syncs the key that was saved. * test(projects): make the layer tests hold on Windows The mutation-sequence test looked the shared project up by filepath.Join, but the fixture spells config.yaml's key $ROOT/app; on Windows the two spellings differ, so the lookup found nothing. It now asks the config for the key it uses. The remove save-failure test blocked the local registry, but removing a config.yaml project now writes config.yaml. On Linux the registry check still failed with ENOTDIR first, which hid the mismatch; on Windows that reads as a missing file and the save went through. The test now blocks config.yaml, as the edit save-failure test does, and its hook no longer shadows the config path with the target path. --------- Co-authored-by: sim <sim@example.invalid>
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, or using the devcontainer/ssenv | testing.md, CONTRIBUTING.md |
e2e-runbooks |
Writing or running ai_docs/tests E2E runbooks, or verifying on a Windows guest |
e2e-runbooks.md |
frontend |
Changing React, CSS, layout, or visual behavior in the dashboard, website, or Herdr panel | frontend.md, website/AGENTS.md, herdr/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 |