The conflict notice placed its action buttons beside the sentence. With
a project target the "Edit app@claude's project" label is long, so two
buttons squeezed the sentence into a narrow column of short lines. Put
the actions on a row under the sentence, indented like the comparison
table, so the sentence uses the full width.
The hint under a folder conflict linked every target it named to its
target page, but a project target's settings can only be changed from
its project. Link those names to the project editor, as the button
above already does, and drop "on the target page" from the sentence so
it no longer points at the wrong place.
Refs #612
The Sync page offered "Stop syncing skills" for every target a folder
conflict asked to stop. For a project target that button opened the
skills-off dialog, whose preview and update calls the server refuses
with 400 because project targets are configured through their project.
Link those targets to their project's editor instead, and say so in the
doctor docs.
Fixes#612
The Agents Updates tab updates through /api/update/stream, which resolved
every name against the skills source, so agent updates failed there. The
agent detail page names a tracked repo by its folder, which updateAgent
did not resolve, so updating an agent inside a repo failed with "agent not
found".
The stream now takes a kind and routes agent names to updateAgent, which
also resolves an agent repo folder under the agents source. The tab sends
its kind to the stream and to Prune, and matches update results by kind and
by the agent's path, so a nested agent is marked up to date after it
updates.
Closes#600
* fix(plugins): honor native OMP marketplace builds
Resolve OMP entries from their native marketplace when present and inspect package.json extension-only plugins. Keep target-specific source paths, marketplace identities and components so Claude adoption and hybrid manifests remain valid.\n\nShow separate builds in text discovery without changing logical JSON selection, and cover native precedence, invalid catalogs, manifestless and hybrid packages, global/project materialization and CLI output with regression tests. Update the plugin docs and existing translations.\n\nFixes #587
* fix(plugins): preserve native build metadata across consumers
Keep OMP catalog versions in target discovery metadata and materialized marketplace entries so previews, cache guards, and native installs use the same version, including legacy catalog fallback. Cover catalog versions that differ from package manifests.
Show each dashboard discovery target's own version, components, and source path instead of presenting a merged candidate as one build.
* fix(plugins): avoid ambiguous shared build versions
Derive candidate versions from agreement across supported targets and recompute after catalog overrides. No-Agent records and lists no longer inherit an arbitrary native build version; equal versions remain available and unknown versions stay unknown.
Keep Cursor and Antigravity inventory target-specific when manifests disagree. Cover no-Agent preview and persistence, equal and unknown versions, catalog overrides, and mixed-manifest local inventories. Align English and translated plugin references.
* fix(plugins): accept Pi extension manifests for OMP catalogs
Reuse the existing OMP extension detector instead of requiring an OMP-specific manifest key. Native OMP accepts Pi extension manifests too, so the extra gate rejected supported native catalog entries.
Cover Pi-only discovery with scoped package names and global/project materialization. Align the English plugin references and all existing translations.
After a release changed the guidance text, outdated agents showed an
unchecked box in "Connect to agents", so updating looked like it
required disconnecting and reconnecting. An "Update to latest" button
now opens the same review with every outdated agent preselected and
its mode kept. Hand-edited blocks are "modified", not "outdated", so
they are never preselected and the backend still refuses to overwrite
them.
A pull with dozens of conflicting files meant clicking "Keep this
version" once per file. Two buttons now set every file to the same
side; individual files can still be switched afterwards.
* feat(hooks): read hook code and scripts from files next to the config
Code Agent extensions and command scripts lived as strings in
config.yaml, so a longer Pi extension or shell script was edited inside
a YAML block scalar with no editor support, and nothing type-checked or
linted it. A breaking change in an Agent's extension API went unnoticed
because the generated file is not part of any tsconfig.
A binding now takes `codeFile: path` instead of `code`, and a `files`
value may be `{from: path}` instead of the contents. Paths resolve
against the folder of the config that holds the entry and are read
every time the config is read, so the regular typecheck or shellcheck
can cover the real source. The revision and drift checks use the
resolved contents, so a file edited after a preview fails the apply as
stale.
Saving keeps the references: enable/disable, `hooks edit` and the
dashboard write `codeFile` and `{from}` back instead of inlining the
contents. JSON carries the contents plus `codeFile`/`filesFrom`, and an
entry echoed back with both must match the file, so an edit is refused
rather than silently dropped. Paths must stay inside the config folder
without symlinks, so a cloned project cannot pull in files from
elsewhere. References are taken from the YAML tree before one strict
decode, which keeps unknown-field checks and anchors shared across
bindings working.
Closes#585
* fix(hooks): refuse an emptied file sent with its reference
An empty files value stood for "contents not sent", so a file cleared in
the dashboard's Git YAML editor while its filesFrom reference stayed was
treated as unsent: the file was read again from disk and the save
reported success with the user's edit discarded.
A value read from {from: path} now keeps a dedicated mark until it is
resolved, so an empty value is compared with the file like any other
contents and refused when they differ. Code keeps using empty as unsent,
since a code binding can never be empty.
* fix(hooks): render referenced files as they are on disk
RenderNative rendered the contents the caller sent. The dashboard sends
the entry it loaded, so after a referenced file changed, View
configuration still showed the old contents while describing them as
what sync would write.
Render now drops sent contents for codeFile and {from} references and
reads every reference again, like preview and save. Draft, render and
config decoding are the only paths that take an entry, and all three now
resolve references.
* fix(hooks): accept file references in JSON entries and anchored values
Two inputs that config.yaml accepts failed to load elsewhere.
A `{from}` value carrying its own YAML anchor, aliased from another
binding, lost its anchor because the value node was replaced instead of
rewritten, so the alias no longer resolved. The node is now rewritten in
place with its anchor kept.
An entry JSON file (`hooks add|edit --file x.json`) could not write a
files value as `{"from": path}`, because JSON decoded straight into
string contents. Binding now decodes JSON files values as contents or a
reference, strictly, like YAML, so both entry formats and the Web API
take the same shapes.
* feat(mcp): write per-Agent native fields from the source
Some MCP settings have no portable form, such as Codex's
default_tools_approval_mode or Claude Code's per-server timeout. Sync
kept them only while an entry survived, so a recreated entry (for
example after a rename) lost them, and every machine needed them added
by hand again.
A server's `options` now holds these fields per Agent, and sync writes
them as given. The field ledger that piOptions used is extended to
every Agent, so sync removes an option it wrote once the source drops
it, and reports a conflict when the Agent changed it since.
Options are refused when they could break the entry or leak a secret:
fields Skillshare writes (including portable names some Agents rename),
values a native format cannot write back (null, arrays of tables),
options.pi (piOptions covers Pi), disabled entries, and credentials as
plain text, since the Agent's file may be committed.
The dashboard has no editor for options yet but keeps them on save.
Refs: #578
* fix(mcp): close gaps in per-Agent options found in review
- A credential option passed if it merely contained "${", so text around
a reference, or another Agent's syntax, was written out as plain text.
It must now be a whole-value reference in the Agent's own syntax, and
Codex and Antigravity options, which read no references, cannot hold one.
- The Kilo Code project check looked only at portable env references, so
an {env:VAR} in options reached a project file Kilo refuses to load.
- A replace resolution left the dropped-option conflict in place, so the
plan stayed blocked; replace now lets the source win and prunes those
fields.
- Adopting an entry that already matched skipped writing its options until
a later sync; the takeover now writes them.
* fix(mcp): refuse numeric credentials and constrain option values in the schema
- YAML reads an unquoted secret such as clientSecret: 123456 as a number,
which the credential check skipped, so sync wrote it out as plain text.
A mapping under a sensitive name such as credentials also hid its
plainly named fields. Sensitivity now carries down through mappings and
lists, and a number under a sensitive name is refused.
- The schema allowed any value inside an Agent's options, so editors
accepted null or nested lists that LoadSource then rejects. A recursive
optionValue definition now matches the runtime rules.
* feat(ui): edit other Agents' MCP options in the server dialog
The dialog only carried options through unchanged, so setting a field
such as Codex default_tools_approval_mode or Claude Code timeout still
meant editing mcp.yaml by hand. One Agent picker with a JSON editor keeps
the dialog short however many Agents are ticked; ticked Agents come first,
and an unticked Agent that still has settings stays listed so they can be
cleared. Anything but a JSON object blocks saving; the server checks the
fields themselves.
* fix(ui): offer every Agent in the options picker and document the editor
- The picker listed targets from the order, which includes accounts, so a
ticked account produced an options key the server refuses, and the
Agent the account writes to was not offered. Options are keyed by Agent,
so every Agent but Pi is offered, ticked ones first.
- An unticked Agent left the list as soon as its text was emptied, so its
settings could not be cleared and retyped.
- The editor was hidden on the Skillshare tab although its server takes
options too, and hidden invalid text could block Save there.
- The docs still said the dashboard had no options editor.
* fix(ui): open the options editor on a ticked account's Agent
The picker ranked Agents by the ticked targets, which hold account names,
so a server reaching only codex-work opened the Claude editor and what was
typed there was saved under options.claude. The MCP page now provides
each account's Agent, and the ranking uses it.
The retype test now asserts the saved options rather than the editor
staying visible.
* fix(ui): show the server's refusals of Agent options in the dashboard language
The dialog leaves field rules to the server, but its refusals (a field
Skillshare writes, a plain-text credential, a credential in an Agent that
reads no references, an unsupported value) reached the dialog in English.
describeError now maps each to a translated message naming the Agent and
field. The other option errors cannot come from the dialog: it offers no
Pi, no non-Agent key, and no options on an off switch.
* feat(mcp): write per-Agent native fields from the source
Some MCP settings have no portable form, such as Codex's
default_tools_approval_mode or Claude Code's per-server timeout. Sync
kept them only while an entry survived, so a recreated entry (for
example after a rename) lost them, and every machine needed them added
by hand again.
A server's `options` now holds these fields per Agent, and sync writes
them as given. The field ledger that piOptions used is extended to
every Agent, so sync removes an option it wrote once the source drops
it, and reports a conflict when the Agent changed it since.
Options are refused when they could break the entry or leak a secret:
fields Skillshare writes (including portable names some Agents rename),
values a native format cannot write back (null, arrays of tables),
options.pi (piOptions covers Pi), disabled entries, and credentials as
plain text, since the Agent's file may be committed.
The dashboard has no editor for options yet but keeps them on save.
Refs: #578
* fix(mcp): close gaps in per-Agent options found in review
- A credential option passed if it merely contained "${", so text around
a reference, or another Agent's syntax, was written out as plain text.
It must now be a whole-value reference in the Agent's own syntax, and
Codex and Antigravity options, which read no references, cannot hold one.
- The Kilo Code project check looked only at portable env references, so
an {env:VAR} in options reached a project file Kilo refuses to load.
- A replace resolution left the dropped-option conflict in place, so the
plan stayed blocked; replace now lets the source win and prunes those
fields.
- Adopting an entry that already matched skipped writing its options until
a later sync; the takeover now writes them.
* fix(mcp): refuse numeric credentials and constrain option values in the schema
- YAML reads an unquoted secret such as clientSecret: 123456 as a number,
which the credential check skipped, so sync wrote it out as plain text.
A mapping under a sensitive name such as credentials also hid its
plainly named fields. Sensitivity now carries down through mappings and
lists, and a number under a sensitive name is refused.
- The schema allowed any value inside an Agent's options, so editors
accepted null or nested lists that LoadSource then rejects. A recursive
optionValue definition now matches the runtime rules.
* docs(mcp): name every Agent whose options cannot hold a credential
The docs named only Codex and Antigravity, but Claude Desktop, Goose,
Junie, LM Studio and Warp read no environment references there either,
so a source such as options.goose.apiKey: "${GOOSE_KEY}" looked valid
while LoadSource refused it.
AgentIcon had no entry for git, so places that show a Git source fell
back to the generic icon. The logo comes from Simple Icons (CC0); the
Git Logo itself is by Jason Long under CC BY 3.0, credited next to the
import.
* feat(mcp): pin tool definitions in mcp check --live and warn when they change
An Agent reads a server's tool names and descriptions as instructions,
and a server can change them after the user reviewed it (a "rug pull").
The MCP spec 2026-07-28 local-server security guide notes the protocol
does nothing about this and advises clients that re-prompt on a changed
definition; most clients do not.
`mcp check --live` now records one SHA-256 per tool over name,
description and inputSchema the first time a server answers, in
mcp/tool-pins.json of the state directory, keyed by scope and server.
Later probes report a changed or new tool as a `tool-change` warning and
a removed one as info, until `--accept-tools` (only with --live) records
the current definitions. Without --live the pins are never read or
written. An unreadable pin file is never rewritten, since it may hold
other servers' pins. The dashboard words both warnings in every locale.
* fix(mcp): keep schema numbers exact, name the scope to accept in, and log acceptance
Codex review on #560:
- Tool definitions were decoded through float64 before hashing, so a
schema bound changed from 9007199254740992 to 9007199254740993 hashed
the same and raised no warning. Numbers now keep their literal text.
- The suggested accept command left out -g/-p; run from inside a project
after a global check, it would accept the project's server instead.
It now names the scope of the check that warned.
- Accepting changed tool definitions approves a possible rug pull, but
left no record. --accept-tools now writes an operations log entry with
the servers it accepted.
* fix(mcp): log a tool acceptance only when its baseline was saved
Codex review on #560: when comparing succeeded but writing tool-pins.json
failed (lock held, state directory unwritable), the report kept its
"accepted" finding, so the operations log listed the server as accepted
with status ok although its old pins remained. Such a server is now
logged under `failed` and the entry's status is error.
* fix(mcp): log first pins as accepted and report errors in the accept entry
Codex review on #560:
- A check that accepted one server but found an error on another still
logged status ok, while the command itself exited 1. A server with an
error is now listed under `failed` and the entry's status is error.
- --accept-tools on a server's first probe records its baseline, but the
finding says "pinned", so the entry listed nothing as accepted. A first
pin counts as accepted now.
* chore(release): request version 0.25.11
The MCP pin checks (#559, #560) and the backup staging fix (#558) ship
as 0.25.11 instead of the computed 0.26.0, per maintainer decision.
Release-As: 0.25.11
* feat(mcp): warn when a local server runs an unpinned package or image
An entry such as `npx -y some-mcp` fetches whatever the registry serves
at every Agent start, so a compromised release reaches the machine on the
next launch without anyone noticing. The MCP local-server security guide
(spec 2026-07-28) names version pinning as a baseline and points out
that a container tag can move while a digest cannot.
`mcp check` now adds a `pin` finding from command and args alone, with no
network: npx, uvx and `pipx run` with no version or `latest`, and
`docker`/`podman run` with no tag or `latest`, are warnings; an image
pinned by tag but not by `@sha256:` digest is info. Value-taking run
flags are skipped so hardened lines such as `--cap-drop ALL` are not read
as the image. Warnings keep the exit code at 0, as before.
* fix(mcp): check every npx package, word pin warnings in the dashboard, document them in doctor
Codex review on #559:
- npx accepts --package more than once and fetches each one, but the pin
check stopped at the first, so `npx --package=lodash@4.17.21
--package=cowsay cowsay` passed although cowsay is unpinned. Every
--package/-p value is now checked.
- The dashboard words env, command and dns findings in the viewer's
language but showed the new pin warning in English. It now has its own
sentence for an unversioned package and for an untagged image in every
locale. The dashboard hides info findings, so the digest note needs none.
- doctor promotes check warnings, so an unpinned launcher now shows there;
its docs list the pin check.
The mcp check runbook gains a step for the pin check.
* fix(mcp): check uvx --with packages and ignore environment markers in pins
Codex review on #559:
- uvx --with (-w) installs each named package beside the tool, so an
unpinned one moves just like an unpinned tool, but the pin check
skipped it as a flag value. Every --with requirement is now checked
next to the --from or command package.
- In `--from 'mcp-server; python_version == "3.12"'` the == belongs to
the environment marker, not to the package, yet it read as a pinned
version. Only the requirement before ';' is inspected now.
* fix(mcp): treat only exact versions as pins, and pin the docs' own examples
Codex review on #559:
- npm resolves a dist-tag (`@next`) or a range (`@^1.2.3`) to whatever
release matches at launch, yet any selector but `latest` passed as
pinned. An npx package is pinned now only by an exact semver version,
the rule Pi bindings already use.
- `==1.*` is a prefix match in Python version specifiers, so
`uvx --from 'mcp-server==1.*'` can pick up a new 1.x release; it is no
longer read as a pin.
- The Context7, Playwright and filesystem examples in the docs and the
built-in skill launched unpinned packages, so copying them produced the
new warning at once. They now name the current registry version.
* fix(backup): reclaim abandoned staging directories safely
Interrupted backup copies leave hidden .snapshot-* directories that retention cleanup never discovers. Hold a shared process lock during copies and use an exclusive cleanup lock to reclaim orphaned staging without deleting active work.
Share retention planning with non-mutating dry runs, report busy manual cleanup in the CLI and API, and align dashboard messages and translated docs. Cover process interruption and automatic cleanup with regression tests and an executable E2E runbook.
Closes#556
* fix(backup): address staging cleanup review findings
Keep cleanup reachable for staging-only dashboard backups and disclose abandoned incomplete directory deletion in every confirmation locale. Cover the empty-state confirmation with a regression test.
Read staging entries before a read-only lock probe so first-use dry runs cannot count a newly active writer. Refresh entries only under the acquired lock and classify both backup-root reads in the filesystem guard.
* fix(backup): align cleanup guides and doctor status
Disclose abandoned incomplete directory removal in backup help, completion descriptions, and the daily backup guide with all four translations. Add help and completion regressions so these consumers stay aligned with cleanup.
Keep the doctor Backups row visible when only the persistent lock remains after cleanup, preserving the existing JSON check and covering the lock-only state.
* fix(backup): complete cleanup documentation disclosure
Cleanup reclaims abandoned incomplete directories regardless of retention, so retention-only summaries understated the action. Align the backup synopsis, option table and previews, related workflow guides, built-in reference and all four website translations. Scope the retention defaults to completed snapshots.
* feat(mcp): open an Agent's MCP config folder, and project files, from the dashboard
A user who wants their own editor (Notepad++ on Windows) found setting
both PATH and $EDITOR too much just to open a config file, and could not
find any entry point for the MCP files of an mcp.projects root (#538).
Each Agent row on the MCP page now also has Open folder, which opens the
folder holding the file in the file manager, so any program can open it
from there. Before the Agent has written its file, it opens the closest
folder that exists. The project MCP tab gets the same Agents list for
that project's files. The open endpoint resolves project paths from the
config, as it does global ones, so a request still cannot name another
file, and folder and file opens keep the same-machine and headless
guards. The file manager launch is shared with the extensions folder.
* fix(mcp): keep a project's existing Agent files listed for remote viewers
Codex review: the project MCP tab built its Agents list from the
project's targets plus the files this viewer could open. A viewer on a
LAN address or behind a proxy can open none, so an existing file of an
Agent outside the project's targets dropped off the list, although the
docs say it shows with its path and only the open buttons go.
The list now returns which files exist apart from whether this viewer
may open them, and the page shows the open buttons only when local.
* fix(mcp): list the Agents a project's own servers write to in its file rail
Codex review: a server that exists only in one project can pick Agents
outside the project's targets, and sync writes their project files, but
the project tab listed only the project's targets and files that already
existed. Before the first sync such an Agent had no row, so its path
could not be copied and its folder could not be opened.
The list now also takes the targets of the project's own servers. Global
servers reach a project only through its targets, so they add nothing.
The rule lives in mcpView as projectFileTargets, with a unit test.
* feat(mcp): open an Agent's MCP config file from the dashboard
Users asked to jump from the MCP page straight into a client's config
file, such as opencode.json or .cursor/mcp.json, instead of copying the
path and opening it by hand (#538).
The open uses the same editor chain as a skill's Open in editor, so the
dashboard opens files one way. The endpoint takes a target, not a path,
and only opens a file the MCP page already lists. It answers only
requests from the machine running the dashboard, because the editor
starts on that machine. The list now reports which files exist, so the
button is hidden for a client detected before it has a file.
* fix(mcp): hide Open in editor where the server would refuse it
Codex review: the dashboard can be opened through a LAN IP, but the
open endpoint answers only loopback requests, so the button showed and
every click returned 403, while the docs promised it would open.
The list now reports `openable` instead of `existing`: the files that
exist, and only when the request comes from the dashboard's machine. A
viewer elsewhere does not see the button, and the docs say where it
appears.
* fix(mcp): don't treat a reverse proxy's viewers as local for Open in editor
Codex review: the documented Nginx and Caddy setups connect from
127.0.0.1, so the loopback socket check let any browser behind the proxy
see the button and launch editors on the server.
The browser now counts as local only when the socket and the Host it
used are both loopback and no proxy forwarding header is present. Both
documented proxies keep the browser's Host and add X-Real-IP or
X-Forwarded-For, so their viewers no longer qualify.
Pi 1.2.0 (earendil-works/pi#10765) runs normalizePath on resource-filter
patterns before matching, so `~`, `~/`, `file://` and, on Windows, `~\`
and Git Bash/MSYS/Cygwin/WSL drive paths now match files that older Pi
never matched. Skillshare supports Pi 0.99.2 and later without knowing
which one evaluates the rules, so it reported a definite selection that
could be wrong and let the write guard reason from it. Such rules now
evaluate as unknown, and the dashboard names the rule instead of a
generic message.
Exact rules also missed Pi's normalizeExactPattern in every version: a
leading ".\" is dropped on all platforms and backslashes become slashes
on Windows. Skillshare only dropped "./", so `-.\extensions\a.ts`
looked unmatched and produced a duplicate missing row.
* fix(plugin): accept OMP 18.6.1 and later instead of exactly 18.6.1
The OMP adapter pinned the native version to exactly 18.6.1, so every
newer release was refused: the dashboard reported "Installation requires
OMP 18.6.1" for a user on 18.8.7, and removal and standalone extension
selection were blocked the same way.
The sources the adapter depends on (marketplace cache/manager/types,
plugin-cli output, the project anchor in discovery/helpers.ts, extension
loading and the pi-natives file lock) are unchanged from v18.6.1 through
v18.10.2, so the pin is now a minimum. The install, removal and selection
gates share one check built on the existing plainVersion helper;
unparsable, prerelease and older versions stay blocked.
Messages, all dashboard locales, the plugin reference docs and the
built-in skill now state 18.6.1+. A test keeps the English guidance text
in en.json equal to the Go strings the dashboard matches on.
* fix(docs): record the OMP 18.6.1+ boundary in the cache safety report
The safety report still said installation is allowed only for OMP 18.6.1
and that an unknown version blocks it, which no longer matches the gate.
It now states the minimum, which versions stay blocked, and the source
comparison and native 18.8.7 run that justify replacing the pin. The two
OMP runbooks no longer require exactly 18.6.1.
Keep plugin names on their own line and let agent labels and version changes wrap. Reserve space for update status so batches with many agents remain readable.
* fix(mcp): turn off a global server in OpenCode 2 projects
OpenCode 2 replaces a global server with the project entry of the same
name, and silently drops an entry without its type and command or url.
The project switch Skillshare wrote, {"enabled": false}, therefore left
the server on in OpenCode 2, while OpenCode 1 merged it by field.
Checked against OpenCode 2.0.27 and 1.19.0: OpenCode 2 still reads the
flat mcp.<name> shape and turns enabled: false into disabled: true, and
both read an entry with type and command or url. So no version detection
is needed. When the global config under mcp.projects defines the server,
the OpenCode switch now carries its type and executable, or its url
without the query, next to enabled: false. Args, env, headers and the
query stay out of a project file that may be committed, as the Pi switch
once did. A switch that already carries the endpoint keeps it when the
global server later leaves the config, unless it was edited since sync.
In project mode, or when the global config lacks the server, only the
bare switch can be written; the plan now says OpenCode 2 ignores it, in
the CLI and the dashboard.
Import also reads OpenCode 2's mcp.servers section, which its own
`mcp add` writes, instead of reporting it as one broken server.
Refs #538
* fix(mcp): keep secrets in a URL path out of the OpenCode switch
The OpenCode switch dropped only the query of the global server's URL.
Some MCP services put the key in the path instead, and an absolute
executable path names the user's home directory; both then reached a
project file that may be committed. A disabled server never starts, and
OpenCode 2 accepts any type with a command or url, so the switch now
carries only the executable's name or the URL's scheme and host.
Refs #538
* fix(mcp): skip OpenCode 2's timeout defaults when importing
OpenCode 2 keeps server defaults in mcp.timeout next to mcp.servers, so
import listed timeout as a broken server. It is dropped only together
with a recognized servers section, where it cannot be a v1 server.
Refs #538
* fix(mcp): read an empty OpenCode 2 servers section
An empty mcp.servers object was not recognized as OpenCode 2's section,
so import listed servers and timeout as broken servers instead of
finding no entries. The dashboard help for disabled also still said only
the switch is written, which is no longer true for opencode.
Refs #538
* fix(mcp): keep an OpenCode endpoint switch next to its own fields
The kept switch was matched by the whole native entry, so a field only
OpenCode reads, such as a per-server timeout, made the next sync drop the
type and command or url once the global server left the config, and
OpenCode 2 then ignored the switch. Match the fields Skillshare manages.
Refs #538
* fix(mcp): show the OpenCode endpoint switch in the dashboard preview
The dashboard renders a project's server alone, so the preview never saw
the same-named global server and showed the bare switch that OpenCode 2
ignores, while sync wrote the switch with the endpoint. Resolve the
global server the way sync does.
Refs #538
* fix(plugin): read OpenCode 2's version output
OpenCode 2 prints "opencode v2.0.27" for --version, while OpenCode 1
prints only "1.19.0". The adapter trimmed a leading "v" only, so plugin
sync to OpenCode 2 failed as an unrecognized version and imported
updates were skipped as if OpenCode 1 had no update command. Read the
last field, and decide the update check with the same parser.
Refs #538
* feat(memory): add host-owned review and verification workflows
Share scoped memory tools between Dashboard and Memory, and route retrospective and Dreaming requests through the built-in skill. Keep agent execution in the host, require approval for reviewed edits, and preserve versioned CLI write safeguards.
Confirm scope before exposing prompts and include the resolved root in recent memory responses. Update provenance guidance and localized documentation, with regressions for unavailable scope and protected review prompts.
* fix(memory): distinguish trial copy controls for screen readers
Include the localized step title in each trial copy control accessible name while keeping the short visible label. Update the existing clipboard test selector for the distinct names; no new test or local test rerun was requested for this label-only fix.
* fix(memory): point connection hints to the trial tools
Replace stale verification-prompt directions in all eleven locales with the current Memory tools and Try across sessions labels. Interpolate the existing localized labels so future naming changes remain aligned.
No new tests or local test reruns for this copy-only correction, as requested by the maintainer.
* feat(ui): surface existing shared memory on the dashboard
Make shared notes visible through recent updates and direct links, with file timestamps and an introductory state for untouched starters. Keep the dashboard quiet until memory is configured, and preserve access to existing notes when starter files are missing.
* fix(memory): bound dashboard reads and remember preview expansion
Count vault entries from metadata and read at most the two starters and four recent candidates instead of hashing the full vault on dashboard load. Keep incomplete starter states accessible and refresh the overview after source and instruction changes. Remember preview expansion in browser storage and raise the collapsed height to 360px.
Updating several plugins from the dashboard was slow: each plugin took a
preview and an apply round trip, apply previewed again, every plugin cloned
its source on its own, and config reloaded after each one.
The dashboard now sends the picks to POST /api/plugins/update/stream. The
server holds the plugin lock once, previews each plugin once and applies that
plan, lets plugins from one source share a single read of it, and reloads
config once at the end. POST /api/plugins/update/stop lets the plugin under
way finish and starts no other; a closed page does not cut an install short.
The check-to-update safety moves to the server: an Agent whose source moved
since the check, or that no check showed, installs nothing. npm packages in
Pi are exempt, since Pi installs whatever npm names latest; the old
client-side comparison flagged them as moved on every update.
The update dialog follows the Skills update page, shows per-Agent old -> new
versions, fails rows a broken stream never finished, and lists every plugin
with its Agent and version when all are current.
Release-As: 0.25.6
A successful source update does not always require a target sync: existing symlinks already expose the updated content. Recheck the per-kind diff before offering Sync Now, refresh it when resources change, and report check failures without claiming targets are current.
Cover stale previews and post-sync dismissal with regression tests, and align the dashboard, workflow, source/target, and built-in skill documentation across locales.
Prefixed naming rewrites name: in every copy to the entry name, so the
target folder and name: always agree. Requiring name: to equal the source
folder only skipped skills it could sync: a tracked repo that is itself a
skill lives in _<repo>, so its root SKILL.md could never pass.
Only standard naming now requires the match; name format rules still
apply to both. Sync lists the skills named this way, so a user looking
for _ooux in the target finds ooux.
The dashboard's skipped-skills hint always blamed folders that end in the
same name, even when skills were skipped for their name. The diff API now
reports naming skips apart from collisions and the hint names the cause.
Refs #530
* feat(ui): check plugin updates on load and update them in one batch
Updating plugins took four steps each: press Check updates, press Update
on one row, review a second preview, apply, then check again because the
list did not know the update had happened. Six plugins meant six rounds.
The page now checks once in the background when it opens, so rows show
their new version without a click. The header's Check updates button
becomes "Update N" when something is behind and opens one dialog: every
plugin with an update is ticked, a plugin on several Agents is one row
whose Agents can be left out, and imported installs Skillshare cannot
update sit apart. One button runs them in turn through the existing
preview and apply, so no new API is needed. Progress, results, errors
and per-Agent retry stay in the same dialog, and the applied results
update the page state, so nothing has to be checked again.
The count and the dialog both come from what is still behind after the
last check, limited to Agents that can be updated from here, so a
partial batch is not offered again and Agents with check but no update
(OMP, Antigravity CLI, Grok) do not inflate the count.
* fix(ui): keep batch plugin updates to what the user reviewed
Codex review of #527 found four ways the batch update could act on
something other than what the dialog showed:
- A source that moved between the background check and the click was
installed straight from the fresh preview, so a newer version or new
components went in unreviewed. The batch now compares each fresh plan
with the version and commit the check showed, applies nothing when
they differ, says so on the row, and runs a quiet check so the next
dialog shows the new version for review.
- A retry of the failed Agents that failed again lost that subset, so a
third try re-sent Agents that had already updated. A failed row now
always keeps the Agents it failed on.
- An update the server skipped (its marketplace gone, say) counted as
done: the row said updated and the plugin left the update count.
Skipped outcomes now keep the Agent pending and show as skipped.
- A plugin removed after the check stayed in the update count and
failed with "not found" when picked. Pending updates now drop any
plugin or Agent binding the inventory no longer has.
* fix(ui): show a manual check's result and each Agent's own version move
Codex's second review of #527 found two gaps:
- A check the user pressed that found nothing to update from here (only
imported installs, or everything current) opened nothing, so the
"update inside the Agent" guidance and the up-to-date result never
showed. The check now reports whether it came back, and a check the
user asked for opens the dialog; the background check on load stays
quiet.
- A plugin on several Agents showed one version move built from the
first Agent's installed version and the first new version found, which
can mix Agents that come from different sources. The row now shows one
move only when every Agent makes the same one, and each Agent's own
move otherwise.
* fix(plugin): carry the source digest on a check so a batch update can tell it moved
Codex's third review of #527: a local-directory plugin has no commit,
so when its files changed again after the check while the manifest
version stayed the same, the batch's version and commit comparison
passed and the fresh preview was applied without the user seeing it.
The check copied the installed binding, so its digest was the one
already installed, not the source's. It now sets the discovered digest
alongside the version and commit, as the update preview already does.
The dashboard keeps that digest with each update it found and refuses
to apply when the fresh preview's digest differs, marking the row as
changed since the check. An npm package has no digest and is unaffected.
* fix(ui): list blocked check results and drop unticked Agents from the batch
Codex's fourth review of #527:
- A check can mark an Agent blocked when the updated source no longer
offers a compatible plugin for it. The update dialog listed only
updatable, native-check and up-to-date results, so it hid the block
and could say everything was current. Blocked results now get their
own section with the reason, and the empty state says nothing can be
updated from here rather than that everything is up to date.
- An Agent unticked after the check stayed in the pending updates;
picking it produced a no-op that the batch reported as updated.
Pending updates now skip bindings with sync off, as the row's own
behind count already does.
* fix(ui): count partly skipped plugins as updated and surface a failed re-check
Codex's fifth review of #527:
- When one Agent of a plugin updated and another came back skipped, the
row was marked skipped, the summary counted no update, and the Agent
that did update was not shown. A row now names which Agents updated
and which were skipped, and the summary counts any plugin with an
updated Agent.
- After a source moved since the check, the follow-up check ran quietly,
so if it failed the stale update stayed offered and every retry hit
the same skip. The moved plugin now leaves the found updates, and the
follow-up check reports its failure like any check the user started.
Add a Move dialog with entry points in the selection bar, the skill and
folder menus, the tree pane and the detail page. It previews the move
with a dry run, blocks a whole-folder move when any item is refused,
offers Move anyway only for a name collision and Sync now on the
result, and animates the new-folder step and dialog transitions.
Refs #510
* feat(ui): pick an existing folder when installing into a folder
The "Into folder" field in the install dialog was free text, so users
mistyped paths or could not see which folders already exist. Replace it
with a picker listing the source root, every existing folder, and a
"New folder..." entry that reveals an input validated like
validate.IntoPath. The `into` value sent to the API is unchanged, so no
backend change is needed.
Existing folders are derived client-side from the resource list and
exclude tracked repos, followed source links, folders that are skills
and names the server would reject. FolderPicker takes a disabledFolder
prop so a later move dialog can reuse it.
Refs #510
* fix(ui): block install while the picked folder is not a usable path
Two paths let an unusable `into` through:
- Choosing "New folder..." cleared the value but still counted as
valid, so install silently went to the source root. The picker now
reports validity with each change and an empty new folder is invalid.
- Validity was ignored once Advanced was collapsed, and the server does
not run IntoPath on install, so a bad path could still be installed.
The dialog now keeps the picker's validity regardless of the panel.
* feat(ui): make new folder a step in the folder picker
Typing a new folder path inline gave no sense of where it would land or
what the skill's link would be called. Align the picker with the
approved design:
- Picker rows show a folder icon, the path in monospace, and how many
skills are under it; "New folder..." sits below a separator.
- "New folder..." opens a step in the dialog with a parent folder,
a name, and a result box with the folder path and the link name
(path with / as __ in front of the skill name). Using it returns
to the picker with the new path selected and tagged as new.
- A caption under the picker says where the skill installs and what
its link is called, using the skill name from the source when known.
- Escape and the back arrow in the step return to the picker instead
of closing the install dialog.
The `into` sent to the API is still a plain path. FolderPicker takes
disabledPaths (a folder and everything below it) for the move dialog.
Refs #510
Invalidate instruction queries when targets change or config.yaml is saved so AGENTS.md target lists and instruction paths do not remain cached until reload or expiry.
* fix(sync): replace copy-mode copies with links when switching back to merge
Switching a target from copy back to merge left every copy whose entry name
did not change as a real folder. Merge sync treated it as the user's own
folder, so status and doctor kept saying "run skillshare sync" while sync
changed nothing, and only `sync --force` turned it into a link.
Copy mode already replaces merge-mode links with copies on its own, so merge
sync now replaces a folder the manifest records with a checksum (a copy-mode
copy) with a link, without --force. Folders the manifest does not record, or
records as a link, stay untouched. The pre-sync target backup is unchanged.
The CLI and dashboard diffs name these entries as copies sync replaces
instead of suggesting --force, and the sync-modes docs describe the switch.
* fix(sync): keep copy-mode copies the user edited when switching to merge
The first version replaced any folder the manifest recorded as a copy-mode
copy. The manifest checksum is only a record, so a copy edited since copy
mode made it was deleted too, and `sync --json` and project-mode dashboard
sync take no pre-sync backup to restore it from.
Replace the folder only while it still hashes to the recorded checksum
(Manifest.OwnsCopy). An edited copy is kept and `sync --force` still
replaces it; diff keeps suggesting --force for it. A copy whose name: was
rewritten by prefixed naming, or that was made with custom ignore patterns,
no longer hashes to the source checksum and is kept the same way.
* fix(ui): say a copy-mode copy in a merge target is replaced by a link
The Sync page picks a row's text from the diff item's action alone. The
copy-mode copy that merge sync now replaces comes from the server as an
update, which the page worded as "Link is broken or points elsewhere. Will
be relinked" even though no link exists yet.
Match the server's reason and show "Copy made by copy mode. Will be replaced
by a link" instead, in all eleven dashboard languages.
* docs(sync): say only unedited copy-mode copies are replaced on merge sync
The sync-modes paragraph promised that copies copy mode made are replaced
with links without --force. Merge sync keeps a copy that no longer hashes to
the checksum copy mode recorded, so an edited copy, or one whose name: copy
mode rewrote for prefixed naming, still needs --force.
State the three cases in sync-modes and qualify the diff Modified and Local
override labels, in English and the ja, ko, zh-Hans and zh-Hant copies.
* fix(sync): keep the copy until its replacement link exists
Replacing a copy-mode copy removed the folder first and then created the
link. If creating the link failed (no symlink or junction rights on a
Windows or network filesystem), sync returned an error with the skill gone
from the target. This path now also runs on a plain sync, not only on
--force.
Park the folder beside the entry, create the link, then delete the parked
folder; on failure the folder is moved back. A parked folder left by a run
that died mid-way may be the only copy, so the next sync stops with a message
instead of deleting it. The manifest also forgets the copy-mode mtime and
naming records of an entry that is now a link.
* test(sourcefs): register replaceWithLink's target writes in the raw-write ratchet
The previous commit moved the merge-mode folder replacement into
replaceWithLink, which the ratchet reports as new raw os calls and the old
os.RemoveAll allowance as stale. All of them act on the sync target, not the
skills source, like the neighbouring entries.
* fix(sync): bound the parked copy's name and document the naming exception
The folder parked while a link is created was named after the entry, so an
entry near the 255-byte filename limit (a long flattened nested skill)
could not be moved aside and its replacement failed. The parked name is now
a fixed-length hash of the entry name.
sync-modes also says what happens when `target_naming` changes in the same
sync: the copy gets a new entry name and the prune pass removes it as an
orphan whether or not it was edited, as it did before this change.
* fix(sync): close gaps found while simulating the prefixed naming switch
Simulating the #497 reporter's switch from merge + flat to copy + prefixed
turned up four problems:
- `target X --mode copy --target-naming prefixed` applied only --mode, since
the setter dispatch returned after the first flag. Both flags given
together now check the final pair, then apply in an order that keeps the
saved pair valid (copy mode first, any other mode last).
- Skipped skills were only counted, so a prefixed name over 64 characters
vanished with "1 skill(s) skipped". Sync now names the first five with
their reason; the cap keeps huge sources from flooding the output.
- In copy mode a merge-mode link to the skill was not a managed entry, so
when a local folder held the new name the old link was pruned and the
skill left the target, contrary to the documented "old managed entry is
preserved". Copy mode now migrates such links like managed copies.
- PATCH /api/targets validated the mode/naming pair against the current
skills state, so disabling skills while changing mode was rejected. It now
checks the state the request leaves the target in.
* docs(target): drop stray space in the Japanese mode+naming sentence
* fix(diff): save paired target settings once and report kept legacy entries
- `target X --mode M --target-naming N` ran the two setters, each saving
the config, so a failed second save left half the change behind (Codex
on #504). Both fields are now set and saved once, after the final pair
is checked.
- When a local folder holds the name a skill's naming now gives it, sync
keeps the skill under its old entry and leaves the folder alone, even
with --force. diff still called the folder a "local copy" and suggested
`sync --force`, which does nothing for it. CLI and Web API diff, copy
and merge mode, now report the folder and the entry the skill stays at.
* fix(sync): migrate only links the manifest records as merge-made
Copy mode treated any link to the skill's source at an old naming's name as
the entry merge mode left behind, so a user's own link was renamed and
replaced with a copy (Codex on #504). A link now migrates only when the
manifest records it as "symlink", which merge mode writes for links it makes;
other links stay as the user left them. The value is now a named constant.
* fix(diff): mark kept legacy entries as unaffected by force
Two problems Codex found on #504:
- The Web API diff sent a local folder on a skill's new name as a "skip",
which the dashboard shows as an edited entry that Force replaces. Sync
keeps that folder and the legacy entry even with force, so the preview
promised a change that never happens. It is now its own "kept" action,
shown with its reason and not counted.
- `target X --mode M --target-naming N` printed the target's own naming as
the old value, so a target inheriting standard or prefixed showed
"flat -> ...". It now prints the naming the target had in effect.
* fix(diff): keep kept-name conflicts out of the sync count
Two problems Codex found on #504:
- A local folder on a skill's new name counted toward "N to sync" and
fell through to the plain `skillshare sync` hint, though sync changes
nothing there until the folder is renamed or removed. Such rows now
carry a kept flag, count as neither sync nor local, and print their own
hint; a target whose only row is kept still shows that row.
- The dashboard grouped targets by row name and icon only, so two targets
keeping the same skill at different old entries merged and showed one
target's old location for both. The row detail is now part of the key.
* fix(diff): do not list a kept local folder's files as deletions
A kept row (a local folder on a skill's new name) still pointed at that
folder, so `diff --stat` and `--patch` listed each of its files as removed,
though sync never touches the folder (Codex on #504). Kept rows no longer
point at a target directory, so no file-level diff is built for them in the
CLI or the TUI.
* fix(diff): report kept skills consistently in every diff view
An exhaustive review of the kept-row change (prompted by two Codex findings
on #504) found the same gap in several places:
- A target whose only rows were kept was summarized as "in sync", and mixed
summaries left it out of every count. Such targets now count as "N kept
under old name" with a warning mark, and the scan progress counts them.
- Plain output and the TUI hid where the skill stays; rows now read
"name (stays at old-name)". The TUI also lacked the kept Next hint and
called kept-only targets "differs"; it now matches the plain output.
- `diff --json` emitted kept rows as "remove", indistinguishable from
local-only folders; it now emits "kept", as the Web API does. The diff
docs' JSON example also showed actions the CLI never emits.
- Renamed rows whose old entry is a merge-made link showed a bogus file
stat, because the link was walked as a file; a link now stands for the
folder it points to.
- A dry-run migration printed "Would copy" to the old path; it now names
the new one.
* fix(sync): stop reporting kept folders and skipped skills as pending work (#509)
Three reports told users to do something sync cannot do, or hid what it
did:
- Copy and merge sync kept a folder the user made on a skill's name but
counted it as "up to date" with no hint. Sync now counts it as local and
adds one capped line per target naming the folders and saying that
`sync --force` replaces them. The line is added in SyncSkillTarget, so
the dashboard gets it too.
- status and doctor counted skills that sync skips on purpose (invalid
names under standard or prefixed naming, name collisions) as "not
synced — run skillshare sync". Running sync can never add them, so the
advice looped. They now compare against the skills sync places.
- diff marked a target whose only items were local-only folders as "to
sync" and `synced: false`. Those items are still listed, but they no
longer make the target pending.
* fix(target): apply every setting flag, require flag values, report no-ops as unchanged (#507)
* fix(target): apply every setting flag, require flag values, report no-ops as unchanged
`skillshare target <name>` dispatched --mode, --agent-mode and
--target-naming through an if-chain that returned after the first match,
so `--agent-mode copy --target-naming prefixed` applied one setting and
silently dropped the other. Filters, --skills and --dry-run had the same
early-return problem.
- Check --mode, --agent-mode and --target-naming as a whole and save
once, in global and project mode (one targetSettingsUpdate replaces six
per-flag functions).
- Reject --mode/--agent-mode/--target-naming combined with filters or
--skills, and --dry-run without --skills, instead of dropping them.
- A value flag followed by another flag (or an empty string) now reports
"<flag> requires a value"; `--target-naming -p` used to report an
invalid naming '-p'.
- A value the target already has is reported as unchanged and the config
is not rewritten.
* fix(target): leave the skills pair alone on agents-only changes
A target with skills off may keep target_naming prefixed with a merge
mode it cannot sync; validateGlobalTarget and validateProjectTarget only
check that pair for enabled skills. The combined settings update ran the
pair check for every setting, so `target claude --agent-mode copy` was
refused on such a target although the old agent-mode handler never looked
at skills settings. Check the pair only when --mode or --target-naming is
given.
* docs(target): show combined settings in --help and the built-in skill
The combined --mode/--agent-mode/--target-naming form is now the way to
move a target to copy + prefixed in one step, but neither the help
examples nor the built-in skill's target reference showed it.
* fix(frontmatter): read and rewrite SKILL.md that starts with a UTF-8 BOM
Windows editors such as Notepad write a BOM before the opening ---. The
lenient readers (ParseSkillName, ParseFrontmatterField/Fields/List, ReadSkillBody)
did not skip it, so under target_naming standard/prefixed the skill had no
readable name and was silently skipped. Strip the BOM in the shared frontmatter
locator and the line scanner, and in the hub, search, audit and sync/context
readers that split lines themselves (utils.TrimBOM).
The writers kept working on the unstripped text, so SetFrontmatterValue
prepended a second block and ToggleFrontmatterFlag/RewriteFrontmatterList
could leave a BOM in the middle of the file. They now split the BOM off and
put it back in front, rewriting only the name value (or flag/list) as before.
* fix(frontmatter): cover the dashboard parser and stop auditing a leading BOM
A consumer sweep after the first BOM commit found two more places that
mishandled a SKILL.md written by Notepad:
- audit reported the leading BOM as a HIGH hidden-unicode finding (U+FEFF is
in the zero-width rule), so every such skill showed a risk score. A BOM at
the very start of a file is its encoding mark and hides nothing; one past
the start is still reported.
- the dashboard's parseSkillMarkdown saw no frontmatter, so the skill editor
would treat the whole file as body and write a second block on save.
The audit-engine page and its four translations note the exemption.
* fix(ui): keep the BOM when the skill editor saves a SKILL.md
parseSkillMarkdown dropped the BOM so the editor could see the frontmatter,
but SkillEditor writes the composed text back through PUT .../content, so every
dashboard edit silently removed the marker from a Notepad-written file. The
parse result now carries the BOM and composeSkillMarkdown puts it back in front,
matching the Go rewrite paths.
The command reference, both schemas and the dashboard field help still
said skills target naming is ignored in symlink mode, while prefixed is
refused there.
The aria-label branch special-cased string labels, but lucide icons are
aria-hidden, so an icon-only button already takes its accessible name
from title and a text label wins over it; the attribute was redundant.
A disabled segment also still brightened on hover, so the hover rule now
skips disabled segments. In TargetDetailPage the mode reset and the
naming options move out of one-line expressions so they read at a glance.
Hiding prefixed unless the draft mode was copy made the option hard to
discover, and a user who left copy mode with prefixed drafted kept a
naming the server would reject on save. Following the approved design,
the naming control now always lists flat, standard and prefixed;
prefixed is a disabled segment with a "Needs copy mode" tooltip and an
info line saying why. Leaving copy mode resets a drafted prefixed back
to the saved naming (or flat when prefixed was saved), and a pending tag
marks an unsaved naming change.
SegmentedControl gains a per-option disabled flag. Its title no longer
replaces a text label's accessible name, so the disabled segment is
still announced as "prefixed"; icon-only options keep title as name.
Codex review on #499: when two targets on one skills folder agreed on
mode and naming but had different include/exclude, the target page showed
no note, so it looked settled while the Sync page still reported the
conflict and each sync kept pruning the other's entries. Compare the
draft filters with every target sharing the folder (outside symlink mode,
which ignores them) and offer to copy the other target's filters.
Changing sync mode or naming on a target whose skills folder another
target also writes silently set up the conflict that the Sync page only
reported after saving. The target page now compares the draft with each
sharing target and, under the control that causes it, says the other
target's value and offers "Use <value> like <target>". Nothing shows when
both resolve to symlink or the draft matches. The symlink mode copy now
also says naming does not apply there.
The notice said two targets sync into one folder "with different
settings" but not which ones, so users could not tell what to change
(mode, naming or filters) to keep both. Under the existing sentence and
stop buttons it now lists only the settings that differ as a small grid,
keep target first, with a link to the target page to change them.
Symlink targets show n/a for naming and filters, matching the server rule
that those settings do not apply there. The names-as-links sentence is
shared with the target page's reader notes.
The target page needs to know which other targets write to the same
skills folder to warn when an unsaved mode or naming change would make
their syncs undo each other. Re-implementing the server's folder
normalisation (home expansion, path cleaning) in TypeScript would drift
from config.SkillsFolderConflicts, so the targets API now returns
skillsSharedWith, built from the same skillsFolder helper.
The new naming has to be choosable wherever naming already is: target
--target-naming, the target list TUI, the dashboard target page, shell
completions and the config schemas. Each setter checks the copy-only rule
before saving, for a naming change and for a mode change on a prefixed
target, so an invalid pair never reaches the config file and only surfaces
later as a failed sync.
Two targets writing one skills folder with different target_naming or
mode undo each other on every sync (flat links vs standard names, merge
vs copy), but only include/exclude were compared, so sync and doctor
fell back to the generic shared-path hint.
Compare the effective mode and target naming too, so an unset value
equals the default it resolves to. The global default mode is not
carried on the target, so SkillsFolderConflicts takes it from its three
callers. The warning now says "different settings" instead of "different
filters".
Fixes#498
The skills toolbar sat about 60px under the tabs because its zero-height
stuck marker took its own flex gap. It now sits 16px from the tabs and the
list, and the marker keeps its old distance so the stuck state flips at the
same scroll position as before.
The hub header was a bare sticky div that pinned flush against the list.
It now uses the shared stuck bar, so it gets padding and a bottom line
once pinned while its resting layout stays the same.
Most .test.tsx files asserted layout, icons, collapse state, remembered
widths, toasts, focus or shown text. They broke on harmless UI changes
and missed real regressions, which screenshots catch better.
Keep rendered tests for write/delete payloads, confirmations before
destructive actions, drafts kept after errors, stale-version refusal and
sanitizing; logic stays tested in plain .ts modules.
Add target and the Edit target dialog each implemented the field rules
(an extension forces copy, symlink turns flatten off), and they had
drifted: the dialog kept flatten on through a switch to symlink and
back. applyDraftChange now holds the rules and both use it, so the
dialog clears flatten on symlink exactly like Add target.
Refs #490
Every submenu trigger closed whichever submenu was open when its 180ms
leave timer fired. Moving from Mode to Flatten and back let Flatten's late
timer close Mode's submenu a moment after it opened. A trigger's timer now
closes only its own submenu.
A directory extra used to sync every file to every target, so a tool that
only wanted a few docs got the whole folder. Each target can now set
gitignore-style include/exclude patterns, matched on the path inside the
source. Merge targets prune links to files that stop matching; copy targets
keep earlier copies, since nothing records which copied files are ours.
Filters are rejected for symlink mode and single-file extras, and sync warns
when an include matches nothing.
The dashboard previously forced users to delete and re-add a target or an
extra to change it. Edit target now changes the folder, file name, mode,
flatten and filters with a live preview; Edit extra renames an extra or
points it at another source folder. A moved target or source drops the
links left at the old place and syncs right away.
CLI: --include/--exclude on extras init, and --add-include, --add-exclude,
--remove-include, --remove-exclude on extras <name>.
Refs #435
The pull response copied only the sync's warnings, so with unmatched
include filters moved to their own field, the Git Sync page stopped saying
that a filter selected nothing after its automatic sync. The pull response
now carries them and the page shows the same notice as the Sync page.
The project sync dialog and the sync preview modal show only the response's
warnings. With unmatched include filters moved to their own field, a sync
from those dialogs no longer said that a filter selected nothing. Both now
render the same notice as the Sync page.
Two global targets with the same unmatched filter were merged into one
notice whose Edit filter link opened only the first target, leaving the
other unfixed. Only a project's targets share a filter, so other targets
now keep their own notice and link.
A target whose includes were an unmatched pattern plus a blank entry was
not marked as getting no skills, because the check counted the raw list
while filtering drops blanks. It now counts the effective patterns.