Disabling a skill only checked that its path was written to .skillignore.
A "!" rule in .skillignore.local is applied after that file, and an
unanchored one such as "!feature-radar" re-includes every path segment with
that name, so the skill stayed enabled while the dashboard reported success.
The dashboard also never showed the .local file, so nothing explained why.
Single and batch toggles now re-discover after writing and report an item
that did not reach the requested state as failed, naming the overriding
file; the batch toast shows the first failure's reason. GET /api/skillignore
and /api/agentignore return the .local file, and Settings > Files shows its
rules above the editor.
Add multi-select mode to the Resources page so users can enable or
disable many skills or agents at once (issue #203), instead of toggling
each one individually.
- New POST /api/resources/batch/toggle endpoint (skills + agents) backed
by the shared .skillignore/.agentignore, returning per-item results and
an updated/unchanged/failed summary
- Selection mode across grid, tree, and table views with a unified
checkbox, folder-level tri-state select-all in the tree, a bottom
action bar (Enable applies immediately, Disable confirms first), and
optimistic updates
- i18n keys for all 11 locales