* chore(main): release 0.30.12
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.12 for users
Turn the generated entries into the user-facing notes the changelog keeps, with the --scan example and what each fix changes.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Some tools, such as Codex, look for project skills only up to the Git root
of the folder you open. When one workspace folder holds several checkouts
or worktrees, skills synced to the workspace are not seen inside them, and
registering each checkout by hand repeats the same settings many times.
`project add <root> --scan DIR` registers the root and each Git checkout
found below the scan folders as ordinary project entries with the same
settings, in one write. No scan setting is saved; rerun it after a new
clone. It only adds: a checkout already registered with the same settings
is kept, one with different settings or its own .skillshare/ is skipped
with the reason, and a name clash derives the name from the path. A scan
folder that is missing or cannot be read is skipped with a warning so one
unreadable folder does not block the rest. Rows carry a root-relative path
and a skip code so the dashboard can explain them in its own words.
Dashboard:
The dashboard should offer what `project add --scan` does, so a workspace
with many checkouts can be set up without the terminal.
The Add project dialog gains "Also add each checkout inside this folder"
with the folders to look in. Review runs the scan as a dry run through the
new POST /api/projects/scan and lists each folder as Added, Kept or Skipped
with a translated reason and a link to a project whose settings differ;
nothing is written until it is confirmed. The write scans again and counts
what it actually added, so a checkout registered in the meantime is not
reported as new. MCP and Hooks, when picked, are set up for each added
project. Without an explicit storage choice the default follows
projects_storage, as the CLI does without a flag.
Closes#953
Release-As: 0.30.12
* refactor(ui): isolate resource operations and cancellable reads
Keep resource toggle rollback and move reconciliation outside the view. Preserve the preview and revision protocols and distinguish cancelled resource reads from connection failures.
* refactor(ui): standardize JSON requests across dashboard APIs
Keep HTTP verbs, paths and payloads visible at each endpoint without repeating serialization. Preserve bodyless requests, raw JSON imports and streaming responses, and cover the extras request contracts.
* refactor(ui): share sync eligibility and upgrade recovery
Use scoped plans for sync counts and writes, share restart polling, and restore only the edited target field when a resource write fails.
* fix(ui): show pending MCP source migrations in sync preview
Render the migration counted by the global plan rather than an empty preview when no MCP target file changes. Cover the mismatch through the rendered sync page.
Format the dashboard with Oxfmt and use tsrs for project builds and Oxlint type analysis. Fix the initial typed findings and check formatting and typed lint in CI to keep new changes consistent.
Removing a project keeps its mcp.projects and hooks.projects entries on
purpose: they are separate lists that no project command edits, and the
dashboard lists such a folder on its own. But nothing said so. The CLI
warned "mcp.projects still contains root X" with no next step, and the
dashboard dialog only mentioned it for a machine-local project, so a
removed project's MCP settings looked like a cleanup bug.
The CLI warning now names the settings and where to remove them. The
remove dialog says they stay and that removing the leftover row deletes
them, except when only this machine's copy goes and config.yaml's
project remains. project.md, ui.md and the skill reference describe it.
* fix(ui): show each MCP server's Agents once and animate target pickers
MCP server rows drew the same Agent logos twice: a stack inside the
n/N pill and a row of chips under the name, so a list of servers read
as a wall of repeated icons. Rows now keep only the pill's stack, as
plugin rows do. Opening the pill shows the toggles with each Agent's
name, and Pi's exposure mode moves to a tag beside the Pi toggle.
The toggles of MCP rows, MCP defaults and plugin rows popped in and
out. They now grow and shrink with Reveal, and the pill chevrons
rotate, matching the hooks pages.
The MCP and dashboard reference pages and their four translations
described the chips; they now describe the logos on the count button.
* fix(ui): stop disclosure folds animating under reduced motion
The reduced-motion reset named only .ss-collapse, which .ss-collapse.grow
and .ss-collapse.grow.shut outrank with their own transitions. So every
Reveal fold, now including the MCP and plugin target pickers, still grew
and shrank for people who asked for less motion. Naming both selectors
in the reset lets it win.
* fix(ui): fold and simplify a project's MCP targets, animate Agent ticks
A project's MCP tab opened its Targets picker instantly, under a bare
label, with a segmented "Same as global / Choose for this project"
control above the toggles. It now reads like the global MCP defaults: the
setting and its pill on one row, the toggles folding in below. While the
project inherits, the global targets show ticked and the first tick
starts the project's own list from them; a small "Back to global" link
returns, still behind the confirm dialog. The unused key behind the old
control is dropped from every locale.
That first tick used to leave the toggles blank until the refetch landed,
so a second tick in that gap saved from an empty list, and a failed save
left an empty own list on screen. The list just sent now stays on screen
until the saved one comes back, and a failed save shows the config again.
Agent toggles on MCP and plugin rows snapped their check badge in and
out. The badge now pops in and shrinks away with transitions, only fades
under reduced motion, and the half-lit hover is limited to fine pointers
so a tap on a touch screen doesn't leave it behind.
* fix(ui): let Back to global drop a list that has not come back yet
The first tick on an inheriting project saves an own list, but the
project's targets stay undefined until the refetch lands. Back to global
read those stale targets, saw no list, skipped the confirm dialog and
the write, and the saved list came back with the refetch. It now goes by
the list on screen, so it asks and then saves the reset as usual.
Apply rejected its own preview with "plugin state changed since preview"
when an OMP removal ran while other OMP plugins were registered: their
package files were fingerprinted in map iteration order.
* chore(main): release 0.30.11
* chore(release): synchronize release metadata
* docs(changelog): write the 0.30.11 entry for users
The generated entry listed commit subjects. Describe what changes for the user, and list the two fixes of #945 separately.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The Latest callout still named 0.30.10. Point it at Pi package sharing and the in-place Antigravity and Copilot hook edits, in every translated README.
The ja, ko, zh-Hans and zh-Hant plugin guide and the dashboard page table never described Share. Add it with the Pi packages it now lists, using the dashboard's own label for the ask option.
The "Hooks in targets" dialog could change or remove a hook without
importing it only when the Agent keeps hooks as events of one settings
file. Antigravity blocks and Copilot hook files had to be imported first,
even though both are plain configuration the dialog can address exactly.
Candidates now carry the block or file they were read from (source), and
NativeEdit uses it: an Antigravity edit replaces or removes the whole named
block, keeping enabled: false; a Copilot edit rewrites only the file's
hooks key or deletes the file. Both keep the preview diff, the stale-file
check, the backup, and the hook stays unmanaged. Code hooks (Pi, Oh My Pi,
Amp, OpenCode) still need importing.
Dialog rows are keyed by source, so two Copilot files that read as the same
hook name (lint.json, skillshare-lint.json) can no longer be removed
together. Copilot rows show the file name, the editor names the file, and
removal says the file is deleted.
Share listed only the plugins added from an HTTPS Git source, so a Pi
setup made of npm packages could not be passed on from the dashboard.
Pi downloads an npm package itself, and `plugin add npm:<package>` needs
a Pi target. The dialog now lists the npm Pi packages after the plugins,
each under its own heading, and copies
`skillshare plugin add npm:<package> --target pi -g --no-tui` for them.
The built-in target is named because the sharer's own may be an account
only they have. With the ask option ticked, the command leaves the
target to the prompt. Packages Pi has from Git or a local path are not
listed.
Plugins stay first in the copied line, so a machine without Pi still
adds every plugin before the first Pi package stops the list.
Release-As: 0.30.11
* fix(ui): keep the page width steady when its scrollbar comes and goes
The styled 8px scrollbar takes layout width even where the system uses
overlay scrollbars. Whenever the page stopped needing to scroll (a short
tab, a filtered list) or a dialog locked scrolling, the bar vanished and
the whole page grew 8px wider, then shrank again.
The page itself now uses the system scrollbar: an overlay one takes no
width, and a classic one keeps its gutter reserved. Scrolling areas
inside the page keep the styled scrollbar.
* fix(ui): list custom targets in the skill target menus
"Available in..." and "Set targets" built their list from the known
tools and kept the installed ones. A target with a custom name is in no
built-in list, so it could not be picked from the dashboard, and the
order changed between openings because the known tools come from a map.
The menus now list the configured targets, sorted by name.
The Latest callout still named 0.30.9. Point it at the Codex hook trust
that 0.30.10 ships, in every translated README, and add the author of
#914 to the contributors.
The squash commit of #829 carries this footer in the middle of its
message, followed by co-author trailers, so Release Please did not read
it and moved the release to 0.31.0. Keep the next release on the patch
version the maintainer asked for.
Release-As: 0.30.10
* feat(hooks): record Codex hook trust on sync with --trust
Codex runs a user-level hook only after its trusted_hash is stored in that
home's config.toml, keyed by the hook's position in hooks.json. Only the
TUI's /hooks review writes it, so every hook Skillshare adds or moves starts
untrusted and codex exec skips it without a word.
`hooks sync --trust` (global mode, opt-in) asks each Codex home's
`codex app-server` for the current hash of the hooks Skillshare owns and
writes trusted_hash through config/batchWrite, the same calls /hooks makes,
so the hash is always the one Codex computes. It changes nothing else in
config.toml: disabled hooks stay disabled and are reported. Trust it wrote
is remembered in the hooks state directory, so when a hook moves or is
removed the next --trust sync clears the old position, unless that trust
has changed since. Without codex on PATH the hook files are still written
and the command fails saying trust was not recorded.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(hooks): scope Codex trust to config owner
Scope trust selection and saved hashes to the active config owner so a global config cannot trust or reconcile another config’s hooks.
Recheck hooks.json after hooks/list to avoid trusting a handler from a stale position, and only report trusted or cleared actions after config/batchWrite succeeds. Keep v1 ownerless hashes cleanup-only so upgraded installs clear stale trust after hook removal without trusting foreign hooks.
* fix(hooks): retain parked Codex trust receipts
Locate hooks using all records for their canonical file before selecting the active config owner, so identical hooks remain identifiable across shared and symlinked homes. Keep cleanup receipts for parked registrations whose native group still matches, including when duplicate counts make locate ambiguous, while clearing receipts for removed hooks.
Add regressions for identical hooks across config owners, symlink aliases, parked-home restoration, ambiguous duplicates, and stale receipt cleanup.
* fix(hooks): coalesce symlinked Codex trust homes
Canonicalize current-owner and legacy trust receipts so symlink spellings of one hooks.json are processed once. Remove the redundant parked-position branch because the hash-matching fallback below covers it. Add regression coverage for current and legacy receipts.
* fix(hooks): coalesce removed Codex hook homes
Resolve existing home directories when hook files have been removed so trust receipts for symlink aliases reconcile once. Correct canonical key expectations and exercise coalescing without unsupported ledger migration.
* fix(hooks): read reconciled trust fixture into fresh state
JSON decoding retains existing map entries, so reusing the seeded receipt map makes the alias appear to survive reconciliation. Decode the persisted state into a new value to verify its actual contents.
* feat(hooks): confirm Codex trust before recording it and drop the receipts file
`hooks sync --trust` recorded trust for every owned hook without showing
what it was trusting, and tracked its own writes in codex-trust.json so
it could clear them later. Codex's review exists so that a person sees a
command before it runs, and the receipts file was the source of most of
the edge cases found in review.
Trust is now two steps. A preview asks Codex which owned hooks are new
or changed and returns them with their commands and a revision; the
write takes that revision and is refused when the hooks changed since.
The CLI lists the hooks and asks once, `--yes` skips the question, and
without a terminal nothing is trusted unless `--yes` is given. The
dashboard gets the same two steps as API routes.
Nothing is cleared any more: a leftover entry only matches a hook with
the same event, matcher and handler at that position, which is the hook
the user already approved. That removes codex-trust.json.
The app-server is started without CODEX_HOME for the default home.
Codex resolves the symlinks of CODEX_HOME but not of ~/.codex, so a
symlinked default home got a trust key the user's own Codex never looks
up.
A home whose write fails no longer stops the other homes, and the error
names which were recorded. A preview releases the hooks operation lock
before it waits on Codex, so a slow Codex does not fail other hooks
operations.
Refs #828
* feat(ui): trust Codex hooks from the Hooks page
The dashboard could sync Codex hooks but left them untrusted, so Codex
skipped them until the user ran the CLI or approved each one in Codex.
The Sync box now offers "Trust Codex hooks" in the global scope when a
hook is bound to a Codex target. The dialog shows each hook that needs
trust with its full command and records trust for exactly that list; a
change since the list was shown is refused. The button is hidden while
changes are pending, because trust covers the hooks on disk and the next
sync would invalidate it.
Refs #828
* test(ui): cover the Codex trust dialog's refused, empty and disabled states
Only the happy path was tested, so a regression in the states where the
dialog must not offer a write would have passed. The docs sentence on
several Codex homes now says what is isolated: a failed write, not a
home that cannot be listed.
Refs #828
* refactor(hooks): split the trust prompt and output rendering out of the handlers
hooks_handlers.go had grown past 500 lines and mixed orchestration with
the confirmation prompt and every print function, which the CLI layering
rule asks to keep apart. The code is moved unchanged: the prompt goes to
hooks_prompt.go and the printing to hooks_render.go.
* fix(hooks): leave out a Codex home that cannot be listed instead of stopping
With several Codex homes, one home Codex could not list aborted the whole
trust run, so a broken account home kept every other home untrusted.
A home that fails to list is now reported and left out, and the other
homes are previewed and trusted as usual. The CLI warns before the
question and exits with an error that names the home; the dashboard
dialog shows the same note. When no home can be listed the preview still
fails.
Codex answers a home it cannot load, such as one with an invalid
config.toml, with a successful reply that has no hooks and the reason in
`errors`. That was read as a home without hooks and passed silently. It
is now a failed listing that carries Codex's own message.
Refs #828
* fix(hooks): check the reviewed Codex hooks per home when recording trust
The revision was one digest over every home's hooks. When a home was
listed in the preview but failed to list again at the write, its hooks
dropped out of the digest, so the write was refused as stale: the homes
the user had just reviewed stayed untrusted and the real listing error
was hidden behind "changed since they were listed".
The revision now has one part per home. A home is refused only when its
own hooks changed; a home that cannot be listed any more is reported and
the reviewed homes are still trusted.
Refs #828
* chore: release as 0.30.10
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.10
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Willie <egg358358@gmail.com>
Without file-link privilege (Windows without Developer Mode) merge mode
copies agents and tracks the copies it wrote. A file a tool already had
with the same bytes as the source was not tracked, so it was kept, and
--force kept it too: the identical-content check ran before the force
check. init's "kept local agents: X (sync agents --force replaces them)"
then named a file --force could never take over, on every run.
With --force the file is now recorded as skillshare's, so later syncs
update it. Without --force nothing changes.
Also: the five-name cap written twice is one helper, sync.ListNames,
and doctor.md says when a recorded broken link is reported as a broken
symlink (the behavior from #942).
init syncs agents quietly, and an agent file a tool already had under an
agent's name was kept without a word: init said "Synced" while the tool
went on loading its own file. A plain sync shows this only as a count.
The quiet agent run now returns a line per tool that names the kept
files and the command that replaces them, and init prints it with the
skill warnings. In symlink mode what is kept is the whole agents folder,
so the line says that instead.
Closes#938
Three previews disagreed with what sync does to a link no skill or
agent maps to.
The agent diff, in the CLI and the dashboard, listed every orphan link
as a removal. Agent sync prunes a link only in merge mode, and only when
it is broken or points into the source, so a live link to another
location was listed forever. Both diffs now ask the function prune uses.
The CLI diff listed no orphan links at all for merge-mode skills, so a
skill removed from the source showed nothing until sync pruned its
link. It now lists the links sync.OrphanLink says prune removes.
doctor called a broken link "did not create, kept" whenever OwnsLink was
false. Prune also removes a broken link under a name the manifest
records in any form once no skill maps to it, so doctor told the user to
delete by hand a link that sync removes. It now reports those as broken
and suggests sync. An empty source counts as "every entry is an orphan";
only a failed discovery turns the check off.
Closes#939Closes#940Closes#941
The Sync page predicted which orphan links sync would remove with its
own copy of prune's rule. The copy had already drifted once (#914), and
it still disagreed in two cases: prune treats a link it cannot follow,
such as a loop, as broken, while the page only counted a missing
destination; and prune keeps a link whose target it cannot read.
The decision now lives in sync.OrphanLink. Prune and the dashboard diff
both call it, so a later change to the rule reaches both. Prune's
results, warnings and dry-run text are unchanged. LinksIntoSource, added
for the dashboard's copy, is no longer needed and is removed.
* fix(sync): never delete or re-point entries skillshare did not create
On Windows, a plain `init` followed by `sync` deleted things in
~/.claude/skills that skillshare never created, with no backup and no
prompt. It also re-pointed another tool's junction. Seen in a sandbox
run of v0.30.7:
- prune removed real folders whose names only look like skillshare's
flat naming (team__shared, _drafts), via the name heuristic
- prune removed a broken link that another tool or the user made
- merge sync deleted and re-created a same-name link that pointed into
another manager's store
- init's import deleted original folders that matched the source
byte for byte
The manifest already records what skillshare made, so use it:
- prune keeps a look-alike folder that is not in the manifest and warns
once per sync; --force still removes it
- prune removes a broken external link only if the manifest records it
(e.g. after the source moved); otherwise it keeps the link and warns
- merge sync re-points a link only if the manifest records it or it
already points into the source; otherwise it reports the entry as
kept local, as it already does for a real folder; --force replaces it
- init's import moves identical copies to the trash under
replaced-by-init/<target>/ instead of deleting them
Tests: ownership_test.go adds regression tests that use createLink, so
they run on Windows without Developer Mode (junctions). The 4 keep
tests fail without this change. TestSyncTargetMerge_FixesBrokenLink now
records the link in the manifest first, since a same-name link that
skillshare did not make is no longer re-pointed. Existing tests in
internal/sync, internal/trash and cmd/skillshare show the same failures
on a Windows host with and without the change (symlink privilege). The
devcontainer suite has not been run.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: say what sync and init keep when skillshare did not create it
The previous commit makes sync and init leave alone entries skillshare
did not create. Update the pages that describe that behaviour:
- sync-modes: merge mode keeps a same-name link from another tool and
reports it as local; orphan cleanup keeps folders that only look like
skillshare's flat names, and broken links outside the source that the
manifest does not record. sync --force still removes them.
- init: identical folders replaced with links during the first sync go
to the trash first (replaced-by-init/<tool>/, cleaned after 7 days).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* test(sourcefs): drop the raw-write allowance replaceIdenticalCopies no longer needs
replaceIdenticalCopies now moves an identical copy to the trash instead
of calling os.RemoveAll, so TestRawWriteRatchet reports its allowance as
stale.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(sync): apply the ownership rule at every consumer
Review of the first commit found places that still did, or predicted,
the old behaviour. One rule now decides whether a link is skillshare's:
Manifest.OwnsLink (the manifest records a link there, or it points into
the source). It compares canonical paths, so a source reached through an
alias and a relative project link still count as skillshare's.
- copy mode kept re-pointing: it removed any same-name link and wrote a
copy. It now keeps a link it does not own, like merge mode.
- the dashboard diff predicted a prune for a folder that is only named
like skillshare's, and an update for another tool's link. It now
reports them as local and kept. The orphan-link prediction uses the
same rule as prune.
- `diff` reported a target as in sync while sync printed "kept local"
for another tool's link. It lists the link as a local override.
- doctor reported a broken link skillshare did not create as an error
and suggested `skillshare sync`, which now keeps it. It is a warning
with its own row, and `broken_symlinks` is `warning` in --json.
- `trash restore` put a folder init had replaced into the source as a
new nested skill. Restore refuses entries under replaced-by-init/ and
names the trash folder to copy from.
- init reported a folder it could not move to the trash as one that
differs from the source, and dropped the error. It is reported
separately, with the error.
- the PruneOptions.ManagedOnly comment still said broken external links
are skipped; manifest-recorded ones are removed.
Tests cover the states the review listed: a source behind an alias, a
relative project link, ManagedOnly, standard naming, dry run with
--force, and a recorded copy the user replaced with a link.
TestSync_Pruning_RemovesBrokenExternalSymlinks passed without testing
anything, because FileExists follows links; it is now two tests that
use Lstat, one per owner.
Agent merge is unchanged: agents have no link manifest.
* fix(diff): list another tool's link as kept in copy mode too
Copy mode now keeps a same-name link skillshare did not create, but both
diffs read the entry with os.Stat. A broken link showed as a skill to
add on every run, and a live one as a plain local copy, while sync kept
both and said "kept local".
`diff` and the dashboard diff check the link first and report it the way
merge mode does: a local override, kept until --force.
* test(sync): make the aliased-source link while its folder exists
TestSyncMergeRepointsUnrecordedLinkIntoAliasedSource failed on Windows:
it linked straight to a missing folder, and a junction cannot be made
to one. It now links first and removes the folder after, like the other
broken-link tests in this file.
* fix(sync): compare a broken link by where it would point
linksIntoSource resolved both paths with EvalSymlinks, which gives up on
a path that does not exist. A broken link is exactly that, so a link
into a source reached through an alias (a symlinked config folder, or a
short 8.3 path on Windows) compared an unresolved path with a resolved
one and was taken for another tool's link. Sync then kept it instead of
repairing or pruning it.
It now uses sourcewalk.Canonical, which resolves the nearest folder that
exists and keeps the missing tail. The test covers both spellings: the
alias in the link, and the alias in the configured source.
* fix(init): report what the first sync kept, and match prune in the diff
Two previews said less, or more, than sync does.
init ran its first sync quietly and printed only "Synced". Sync now keeps
a link another tool put on a skill's name, a folder that is only named
like skillshare's, and a broken link it did not create, so the skill was
reported as synced while the tool still loaded the other copy. firstSync
returns the warnings a plain sync prints, and init shows them. They
already name the folders that differ from the source, so the separate
list of those is gone.
The dashboard diff counted an orphan link as a removal whenever the
manifest recorded it. Prune keeps a recorded link that still resolves
outside the source (the source moved and the old checkout stayed), so
the Sync page showed a removal that never happened. The diff now uses
prune's own rule: a link into the source goes when broken or recorded;
any other link only when broken and recorded.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Willie <egg358358@gmail.com>
* fix(ui): pick nothing by default when taking over hooks from targets
The hooks import dialog is also where a hook is edited or removed in its
target file without importing it, but it opened with every hook ticked,
so managing removals could import the rest by accident. It now opens
with nothing selected, and its entry points are named for what they
show ("Hooks in targets", "Not managed yet") instead of "Import".
The review step stacked three scroll areas (dialog body, file list,
diff) and listed each removed hook three times. The dialog body is now
the only thing that scrolls, hook names are listed once, a file card
shows a count per action, and its diff opens on request. The other hook
previews share the component: their diffs still start open but lose the
inner scroll and gain the same toggle.
Adding or editing a hook now uses the same command cards as editing one
in a target: collapsible, with a multi-line editor that can be expanded.
A collapsed card with a missing field is marked. The variable buttons
append to the command there instead of inserting at the cursor.
A missing OpenCode CLI showed the raw exec error when reading its hooks;
it now says the command was not found and what to do.
* fix(ui): explain a missing OpenCode CLI in hook plan warnings
The sync preview, Sync page and target hooks views show the same
failure as a plan warning, wrapped as "target X: detect OpenCode API
...; its hook bindings are skipped". That form still put the raw exec
error in parentheses. It now says the command was not found, that the
bindings are skipped, and what to do. Other detection failures keep
the existing message with the detail.
* fix(ui): fetch each repository once when the dashboard updates skills
Updating many skills from the Updates tab cloned the repository once per
skill and reinstalled every one, so 31 skills from 8 repositories took over
a minute where `skillshare update --all` takes 16 seconds, and unchanged
skills were reported as updated.
The update stream and the update-all endpoint now group the request's
skills by repository and branch and go through install.UpdateSkillsFromRepo,
as the CLI does. A skill that already matches upstream is left alone and
reported as up to date; the Updates tab shows and counts it that way.
Results still arrive in request order, which the dashboard relies on.
Updating a single skill and switching its branch still reinstall. Those
paths now also pass the configured parse options to the installer.
* fix(ui): keep one thing moving while an update runs
An update showed a spinner in the status card, a progress bar, a spinner
on the active row and a moving line under it, all at once. The bar also
sat empty while a repository was fetched, and was removed in the same
render as the last result, so it never reached the end.
The bar is now one shared component. A faint runner shows work before
the first item finishes, the fill moves with a transform, and when the
run ends it reaches the end, holds, then fades and gives its space back.
The status card icon stays still and ends with a check that draws
itself. The active row is marked by a light sweeping its status text
instead of a spinner and a line. Backup, install from config, the plugin
update dialog and pending Doctor checks follow the same rule.
* fix(ui): fetch each repository once when the dashboard updates skills
Updating many skills from the Updates tab cloned the repository once per
skill and reinstalled every one, so 31 skills from 8 repositories took over
a minute where `skillshare update --all` takes 16 seconds, and unchanged
skills were reported as updated.
The update stream and the update-all endpoint now group the request's
skills by repository and branch and go through install.UpdateSkillsFromRepo,
as the CLI does. A skill that already matches upstream is left alone and
reported as up to date; the Updates tab shows and counts it that way.
Results still arrive in request order, which the dashboard relies on.
Updating a single skill and switching its branch still reinstall. Those
paths now also pass the configured parse options to the installer.
* fix(ui): keep checkouts and recorded sources when updates share a fetch
Grouping a dashboard update by repository sent every skill through the
discovery installer. A root skill kept as a Git checkout was replaced by
a plain copy, losing its repository, and an updated skill had its source
recorded in the repository's canonical spelling, which a project
declaration written with another spelling no longer matches.
A checkout now updates on its own by pulling, as before, and an updated
skill keeps the source its record had, as updating one skill does.
* chore(main): release 0.30.9
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.9 for users
The generated entry listed commit subjects. Rewrite it as what changed
for a user, with the symptom each fix removes, and keep the website
copy identical.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The Latest callout still named 0.30.7. Point it at the hooks import
dialog change that 0.30.9 ships, in every translated README, and add
the reporters of #921 and #922 to the contributors.
Choosing "No limit" for a skill, a folder or a selection still showed
"… now available in All": the toasts put the old "All" label into the
"available in {target}" sentence. That is the wording #925 found
misleading, and it no longer matches the option's name.
Give the no-limit case its own sentence in each of the three toasts
and drop the "All" label nothing else uses.
* fix(ui): count symlink-mode targets in the Skills list
A symlink-mode target links the whole source folder, so every skill is
live there. The skill detail page and the Sync page count it, but the
Skills list read only `synced` matrix entries: the Targets column, the
tree pane and the target filter left such a target out, and the Agents
page reported a symlink-mode agent target as not supporting agents.
A skill whose targets all had skills switched off was labelled "No
agent targets", wording meant for agents. It now reads "Skills off".
Nothing else reaches that label any more, so the key is removed.
The list now applies receivesSkill, the same rule as the other pages.
Closes#926
* fix(ui): rename the "All" target option to "No limit"
The option clears a skill's own `targets:` field. Labelled "All", it
read as "synced to every target", so a skill showing "All" next to a
single target icon looked like a bug (#925). "No limit" says what the
field does and pairs with the existing "Limited" tag.
Closes#925
The sync matrix reports a target as `na` both when it is in symlink
mode and when skills are switched off for it. The skill detail page
read every `na` as symlink mode, so a skills-off target showed
"Symlink mode, filters do not apply" with its switch on and counted
toward "4 of 4", although nothing syncs there. Next to a Skills list
that shows only the targets the skill reaches, the two pages
contradicted each other (#925).
Use receivesSkill, the rule the Sync page already applies, so only a
symlinked folder counts as carrying the skill, and label the other
case "Skills off".
* feat(hooks): browse, edit and remove unmanaged hooks in the import dialog
The import dialog listed every target's hooks in one long scroll of
full commands, so it was hard to read and hard to tell which target a
row belonged to. It also offered no way to change a hook without first
handing it to skillshare.
The dialog now shows one target at a time from a rail, with two-line
rows that open to the full commands. A hook that lives as an event in a
target's settings file can be edited or removed in place: the change
stays pending, a review step shows the file diff, and only then is the
file written, with a backup that restores it. The hook stays unmanaged.
The write is a new operation in internal/hooks (PreviewNativeEdits and
ApplyNativeEdits) that addresses elements by content, refuses anything
a ledger record holds, and reuses the existing backup and journal path.
Whole-file hooks, Copilot files and Antigravity blocks still have to be
imported first.
* fix(hooks): keep repeated restores and retries from writing a hook twice
Two ways an unmanaged hook could end up in a target file twice:
Restoring the backup of a removal a second time appended the hook
again. An unmanaged hook has no ledger record, so nothing marked the
backup as restored. PreviewRestore now reports a conflict when the
removed hook is already in the file.
When the dialog's native write succeeded and a later import failed, the
retry compared each pending change with the row it was made in. An edit
that moves or adds a command under another event comes back as other
rows, so the change stayed pending and was written again, and the new
row was picked for import. The dialog now drops every change once the
write went through (or reports files it already applied), and keeps
only the rows picked before as imports for the targets it wrote.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(hooks): tell a restored hook from a surviving twin, keep unwritten edits
The check that refuses a second restore of a removed unmanaged hook
looked for any unmanaged hook with the same content. When one of two
identical hooks was removed, the survivor made the first restore look
done. A removal that shifts later hooks is stored as an update plus a
removal, which the check did not cover, and a restored hook that was
imported afterwards no longer counted, so those backups could still
restore twice. Every change to an unmanaged hook now records how many
identical hooks the write left, and a restore is refused only when the
file holds more than that.
When a native write failed after its first file, the dialog dropped
every pending change, including those of files the write never reached.
The failure response now lists the applied files in error_params, and
the dialog drops only the changes of those files. Pasted candidates are
no longer unpicked by a write to the target they were pasted for.
* fix(ui): show a hook row's edit and remove actions once
An open row in the import dialog showed the pencil and trash icons next
to the labelled Edit and Remove buttons below, which do the same thing.
The icons now hide while the row is open; their space is kept so the
chevron stays where it was clicked.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(hooks): count surviving twins for every backup, not only native edits
Only the native edit preview recorded how many identical hooks a write
left, so the backup a restore writes had no count. Undoing a restore
through Backups was then refused whenever a hook with the same content
was still in the file. The count now happens where every backup is
written.
* fix(ui): keep the row icons as the only edit and remove actions
The labelled Edit and Remove buttons under an open row repeated the
icons and stood out too much, so they are gone and the icons stay
visible on open rows again. Each icon now has a tooltip that says what
it does.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(ui): put the import dialog's hooks on one card, with fewer lines and fills
The dialog mixed a grey rail, a grey footer, grey expanded rows and a
divider around every region, and the editor stacked its own Cancel and
Done above the dialog's. It read as cluttered, and a long JSON line
pushed the editor's controls out of the dialog.
The dialog now sits on the page background with the hook list, or the
editor, as one card. Rows are separated only by the list separator, the
row icons are neutral until hovered, and code is the only sunken fill.
One row is open at a time, and a single command no longer repeats its
event as a heading.
While a hook is edited, the dialog's footer holds the editor's actions,
so there is one row of buttons and Cancel returns to the list instead
of closing the dialog with the draft. Commands are sections of the card
and wrap instead of scrolling sideways. The dialog is larger.
The hint is one line, the edit note moved to the footer, and the name
field is labelled by where the name is used.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(ui): give the import review step the same card-on-ground look
The review step still had the white body, the grey footer and the
bordered summary box, so it looked like a different dialog from the
list it follows. It now sits on the page background with the summary
as one card, and the removal tile is neutral with only its icon in the
danger colour.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
Windows has no sh on PATH, so every panel exec failed with "program not
found". A default Git for Windows install puts only Git\cmd on PATH, so
when sh cannot start the panel asks `git --exec-path` for the Git root
and uses its bin/sh.exe, which sets up the MSYS PATH itself. The shell
found is kept per machine, because a space's machine can run a
different OS than the window.
Under that sh, jobs printed their temp folder as /tmp/..., which Herdr's
native readTextFile cannot open, so every job waited out its 15 minutes.
READY now prints the cygpath -m form (C:/...) when cygpath exists; MSYS
sh accepts it too, and other platforms are unchanged.
Closes#922
prompt-injection-1 kept reporting ordinary source lines as CRITICAL
prompt overrides: `root: Path = Path(".")` (#921), docstring arguments
such as `root: Repository root containing the manifests.`, and typed
parameters with a name default. #376 and #750 each added value shapes
to the exclude. Measured on 5,573 real Python files and 33,006 Markdown
and config files, widening the exclude again cleared no line, and a
docstring entry cannot be told from prose by any value pattern.
In a source file a lowercase label word is a parameter, field or
docstring entry, so the built-in rule now matches only uppercase labels
there. The file extension decides, never a shebang, so a text file
cannot switch the check off. Markdown, text, config and extensionless
files, and Markdown code fences, keep the case-insensitive match. A
custom regex under the same ID is used as written.
This reverses the earlier choice that a lowercase `system: "..."` in a
non-Markdown source file stays CRITICAL.
Closes#921
When Agents hold different definitions of one server, importing one
Agent's version was refused with "unresolved conflicts prevented
adoption", because any conflict in the plan blocked it, including
another Agent's. The source was saved anyway, so the Agents that had
matched the old definition now conflicted, and importing from them
flipped the source back. Replace with source sent one resolution at a
time, so with two conflicts the plan stayed blocked and the dialog
could never apply.
Gate adoption only on the resolved entries' own conflicts, in the API
save and in the interactive CLI import. Replace with source now settles
every conflict of that server at once. After a conflict import, a
translated hint names the Agents in the same scope that still need
Replace with source, and the remaining adoption error is translated.
The Git and CLI groups listed command names on one line with no
summaries, so finding the command for a task meant opening each one's
help. Give them a row and summary like every other group.
Python credential scans can produce a HIGH comment before a CRITICAL
code finding for the same rule. Keeping the first descriptor score hides
the later severity. Promote the shared descriptor while retaining each
result's level and the first-seen rule index.
* fix(opencode): preserve v2 directory packages
Stage the reviewed issue 913 source for isolated fork validation. Preserve
package directories and manifests without executing managed packages or
installing their dependencies, and include receipt and localized UI fixes.
Reviewed local source: 15ac88e2f266571b8a6dc8d777302db0f4dcae44
Exact source tree: 45ebabfe2b
Static checks and independent inspection completed. Go, integration,
dashboard, rendering, and hosted runtime validation remain pending.
This fork staging commit is not an upstream publication or merge.
* test(opencode): align schema and snapshot assertions
Check the version-aware binding schema and verify native unregister retains the unchanged managed snapshot.
* fix(opencode): resolve Windows npm native launchers
Probe recognized native Opencode executables without invoking a batch shell; exercise the default version probe on hosted Windows.
* test(opencode): normalize Windows fixture line endings
Avoid doubling carriage returns when Git checks out the npm fixture with CRLF.
* fix(opencode): keep an undetected OpenCode version from blocking other agents
Review of the v2 directory package change found that one failed
`opencode --version` probe failed the whole hooks plan, so a machine
without the binary (a second machine sharing the config, CI, a
devcontainer) could no longer sync hooks to any agent, and doctor and
the dashboard preview failed with it.
Hooks:
- A probe that fails or reports an unknown major now skips only the
OpenCode bindings with one warning per target. Outputs already owned
there are parked, so they are neither rewritten nor removed while the
layout is unknown. The probe runs once per plan, list and import.
- A `package` binding on OpenCode v1 is skipped with a warning instead
of failing the plan.
- The v2 dependency warning is reported once, and only when a package
file is written, so a synced hook no longer keeps doctor yellow.
- `hooks import` reports an unreadable file such as a symlink as that
package's problem; other packages and flat files stay importable.
The package validation problem is reported once instead of twice.
- Directories under `plugins/` are listed as unmanaged only on v2.
Plugins:
- The inventory leaves `plugins/skillshare-NAME` registrations to
hooks, so a synced v2 hook is not offered as an importable plugin.
Dashboard: the new warnings are translated in every locale, a
`hook NAME:` prefix no longer defeats translation, the native preview
translates its per-file error, and the YAML editor documents `package`.
Docs: the English pages and the built-in skill describe the behavior
above; the ja, ko, zh-Hans and zh-Hant pages now carry the same
content as the English ones. The runbook drives the CLI with mdproof
assertions instead of prose expectations.
Refs #913.
---------
Co-authored-by: Willie <egg358358@gmail.com>
* chore(main): release 0.30.8
* chore(release): synchronize release metadata
* docs(changelog): rewrite the 0.30.8 entry for users
The generated entry listed commit subjects. Readers need what changed for
them and what to do: the MCP directory reads are a new capability, the
tracked-repository fixes change what uninstall and unlink remove, and the
theme fix needs the matching desktop app update.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Since #880, the Dashboard lists a tracked repository that is recorded in
metadata but not cloned on this machine, marks it "No checkout on this
machine", and its Uninstall removes only the record and audit acceptances.
The Dashboard row in the ui reference still described only checkout
uninstalls, so readers could expect the repo to move to trash.
Follow-up to #905.
The conformance script builds and serves skillshare and runs npm ci, which
the repository only allows inside a container, but nothing stopped it from
running on the host. It now refuses outside a container, with the same check
scripts/hooks/git-e2e.sh uses. Nothing referred to the script either, so the
testing topic now says when and how to run it.
The translated mcp reference pages left out the example URI the English page
gives for a skill root. All four now carry it.
The streaming UTF-8 check in the package loader was only exercised with a
rune split one byte before the read boundary. Two fixtures in the existing
directory test add the 2+2 and 3+1 splits, so a mistake in the carried-over
bytes shows up as a wrong MIME type.
* feat(mcp): support Skills directory reads and metadata listing
Expose accepted skill directories and SKILL.md metadata so MCP hosts can
browse served packages without guessing manifest filenames. Reuse catalog
selection and refresh boundaries, including empty directories and stable
pagination, and normalize strict frontmatter for YAML 1.2 Core readback.
Add regressions and a pinned official conformance runner, and update the
runbook and MCP references to describe the browsing contract.
Refs #895
* fix(mcp): preserve supporting file MIME types in directory listings
Record UTF-8 classification from the same bounded bytes used for package
digests so directory metadata agrees with resource reads for extensionless
and unknown-extension text. Reuse the existing bounded reader without
adding listing-time payload reads or changing package limits.
Share pagination with skills/list, trust the SDK's typed request boundary,
and repair the pagination regression to detect stale catalog snapshots.
Refs #895
* fix(mcp): stream supporting file metadata inspection
Buffering supporting files during catalog refresh allocated with asset size.
Restore one bounded stream for digest, size and UTF-8 classification, retaining
at most three incomplete rune bytes and consuming invalid text through EOF.
Preserve the existing same-file checks, package caps and SKILL.md byte reader.
Keep real package-load benchmarks and strengthen the existing MIME fixtures
for split runes and bytes after invalid sequences. Use one first-match sed
command for the conformance URL without a truncated pipeline under pipefail.
Scoped packages, focused race tests, vet, shell syntax/shellcheck and all 45
pinned official checks pass. Allocation stays near 48 KB for 64 KiB and 8 MiB
assets; multibyte UTF-8 validation still costs CPU versus digest-only loading.
* test(mcp): consolidate directory and frontmatter coverage
Check every directory continuation URI so a duplicated middle entry cannot
hide a missing resource. Keep the existing before/after-cursor refresh cases.
Merge nested-skill acceptance fixtures in the catalog owner, preserving all
skill-count, skip-warning and directory assertions across configured and
targetless cases. Move directory capability coverage to initialization and
merge scalar, alias and rejection cases under the existing parser test.
Give cached-page benchmark skills names that match their URI directories.
Narrow tests, benchmark smoke and vet pass; duplicate-result and stale-catalog
mutations both fail, then restored source passes. Production is unchanged.
The desktop app shows the dashboard in an iframe and passes its theme as
?theme=, which holds one value: it cannot ask for Dark + Clean or Playful
dark. Where the iframe's localStorage is not kept (WebKitGTK on Linux), the
dashboard then started with another theme, flashed it, and reported it to
the app as if the user had picked it (runkids/skillshare-app#128).
?mode= and ?style= now name one axis each and win over ?theme=, in both the
pre-paint script and ThemeContext, through one parser. The dashboard also
posts theme-init to its parent when a page starts, before the first
theme-change reports, so the app can tell a starting theme from a user's
choice even when the dashboard reloads itself.
The index and the draft builder read a skill's tags with different readers,
so the same SKILL.md could publish different tags depending on the path:
- The index accepted only the comma form (tags: git, workflow). A YAML list
became "[git" and "review]", and a block list produced nothing.
- Drafts accepted only a YAML list, so the documented comma form produced no
tags, and metadata.tags replaced the root field. After #901 the index
ignores metadata, which made the two disagree there as well.
Both now call readSkillTags. It reads the root field only, in either form:
a list comes from the decoded frontmatter, and the comma form from the
existing line scan. The scan also unwraps a one-line list, so a skill whose
frontmatter YAML rejects on another line (for example an unquoted colon in
the description) no longer publishes bracketed fragments.
Tags under metadata are custom data and are not read by either path. The
skill format page says so in all five locales.
Follow-up to #901.
IsRootFrontmatterLine took the caller's trimmed line only to test for blank
and comment lines, and its callers disagreed on how they trimmed it
(ParseSkillName trimmed spaces and tabs on the left, the rest trimmed all
whitespace). The helper now trims the raw line itself, so there is one
definition of a blank line and one argument fewer to get wrong.
Two tests added in #901 covered behaviour that change did not touch. The
ParseFrontmatterFields row is removed, and the ParseFrontmatterMap test is
reduced to the one case that guards what the skill format page promises:
nested metadata mappings and lists are kept.
Docs: the skill format page now recommends metadata for custom fields, but
the "Version tracking" example in creating-skills still showed top-level
version and author. It now matches. The sentence saying sync preserves
existing last_edited values is shortened, because skillshare has no such
field and the wording suggested it does. Both edits are applied to en, ja,
ko, zh-Hans and zh-Hant.
* fix(frontmatter): keep nested metadata out of skill identity
Preserve root indentation in the tolerant identity readers so nested name
and description fields cannot shadow a skill or create audit claims. Keep
each reader's locator, scalar conversion and streaming policies intact.
Prove existing structured provenance preservation and the namespace fix
with regressions, bounded fuzzing, and global/project CLI integration.
Document nested metadata and native-client compatibility in all format
page locales.
Fixes#894
* refactor(frontmatter): share root-line indentation checks
Use one root-line predicate for the tolerant identity readers and
ParseSkillName so their metadata namespace boundary has one owner.
Keep each caller's whitespace policy, locator, scalar handling and
early-stop behavior intact.
Retain the existing namespace regressions, fuzz invariant and CLI flow
coverage without adding a duplicate helper test harness.
* fix(hub): keep nested metadata out of index tags
Apply the shared root-line predicate to the hub index scalar tag reader so
custom metadata tags cannot replace root tags or create absent root tags.
Extend the existing namespace table rows to assert exact index tags while
preserving the separate structured-list metadata precedence policy.
Uninstalling the _team checkout matched every tracked entry grouped as
"team", so a repo installed with --into team (team/_b) lost its record
and audit acceptances too. Since #880 keeps declarations that have no
checkout on this machine, reconcile could no longer restore that record,
and the next push removed it on every machine; only trash restore of
_team brought it back.
#880 already excluded _-prefixed repo directories from the legacy match
for unlink and declaration-only removal. Move that guard into
inLegacyRepoGroup so checkout uninstall and its trash copy follow the
same rule.
Fixes#898
TestDoctor_JSON_StreamDefersPluginCheck required the pending plugins
row to follow hooks directly. Git status also runs in the background
in a streamed doctor and is recorded at whichever check comes next,
so on a fast runner its result can land between hooks and plugins,
and the test failed on ubuntu CI (seen on #880). The order the test
guards is unrelated to Git, so leave git_status out of the list.