Files
skillshare/wiki
Willie 78a8dc7c0d fix(trash): keep install metadata when restoring from the trash (#680)
* fix(trash): keep install metadata when restoring from the trash

Uninstall pruned a skill's, tracked repo's or agent's entry from the
central .metadata.json, and only the files went to the trash, so a
restore brought back a remote install as a local one: update and check
no longer knew its source (#679).

Uninstall now saves the entries it prunes, with their audit acceptances
and target overrides, beside the trash entry, re-keyed to the trash
name so they match where restore puts the item. uninstall.Restore and
RestoreAgent merge them back after the files return, and every restore
path (CLI, trash TUI, dashboard) goes through them; the dashboard
passes its cached store so it does not go stale. The saved copy is
taken with the same rule RemoveByNames uses and copies each entry, so
legacy repo-group entries are kept and re-keying never touches the
live store.

In project mode uninstall also drops the skill's .gitignore rule and
lock pin, so a skill restore reconciles the project skills afterwards.

trash.Delete removes an entry with its saved metadata, and replaces the
direct RemoveAll calls in delete, empty and the 7-day cleanup. Items
trashed before this change have no saved metadata and still restore as
local.

* fix(trash): keep live records of another path when restoring metadata

A legacy store keys a grouped skill by its basename, so the saved copy of
frontend/foo was keyed "foo". If a different skill was installed as
root-level foo while frontend/foo sat in the trash, restoring it replaced
the root skill's record and lost its source.

Extract now writes full source-relative keys (legacy repo-group entries
keep theirs, since their Group is not their path), and Merge keeps a live
entry whose key names a different path instead of overwriting it. Merge
is shared by skill and agent restore, so both are covered.
2026-10-31 17:25:04 +08:00
..

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 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