Commit Graph
3043 Commits
Author SHA1 Message Date
Willie 2e22257520 fix(check): report failed update checks as failures (#643)
Return nonzero exit status for failed skill and agent checks while preserving JSON results. Propagate agent remote errors and prioritize dashboard check failures over the up-to-date summary.

Add regression coverage and document exit status in all command reference locales. Related to runkids/skillshare-app#85.
2026-10-26 01:20:22 +08:00
Willie 562e7371fa fix(ui): prevent update action overlap and support mobile navigation (#642)
Keep local-edit statuses wide enough so they do not collide with update actions. Wrap update rows on narrow screens and show row actions on touch devices.\n\nReuse the shared dialog for mobile navigation, close it before blocked or successful keyboard navigation, and keep the language picker and tour within the visible mobile UI. Include locale labels, responsive layout documentation, and tour-step regression coverage.\n\nFixes #638.
2026-10-26 00:45:34 +08:00
Willie 6ea5b91843 test(server): cover selected global config in dashboard log handlers
The handler test used the default test config directory, so it passed
without the oplog routing fix. Select a config in a folder named
skillshare so list, stats and clear prove they use the state-dir log.

Refs #609
2026-10-25 22:57:04 +08:00
Rusty ShacklefordandClaude Opus 5.5 61eedffe1e fix(oplog): keep selected global config logs in the state dir (#609)
SKILLSHARE_CONFIG can select a global config in a directory named
skillshare or .skillshare. Treating it as a project config puts logs and
a .gitignore beside the shared config and labels global logs as project logs.

Exclude selected and read-only global config paths from project routing.
Share the check with the log command so readers and writers agree.
Run the legacy config regression explicitly in Windows CI so it is exercised
without enabling unrelated tests that still need Windows fixes.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 22:55:36 +08:00
Willie 3cb1fa4984 test(plugins): require JSON flag in native lifecycle inventory
Match the complete plugin list --json command so dropping the JSON flag no longer passes the native lifecycle test.
2026-10-25 22:32:33 +08:00
Krishnaswamy Subramanian fad3305060 fix(plugins): support native JSON array for Antigravity CLI inventory (#640)
Pass --json to agy plugin list and parse the top-level JSON array returned by the Antigravity CLI. Keep fallback handling for empty text output and legacy wrapped envelopes.

Closes #639
2026-10-25 22:27:49 +08:00
github-actions[bot]andWillie a5477ebe6b chore(main): release 0.26.4 (#618)
* chore(main): release 0.26.4

* chore(release): synchronize release metadata

* docs(changelog): describe 0.26.4 for users

The generated entry lists commit subjects; users need to know what each change does for them and how to use it.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
v0.26.4
2026-10-24 23:43:29 +08:00
Willie 997d76eda7 docs: prepare v0.26.4 release overview
Refresh the localized Latest callouts for 0.26.4 and credit trojanwk for the list proposals and the jsdom test fix.
2026-10-24 23:28:48 +08:00
Willie f3d23ccb0c feat(ui): draw skill trees as curved branches and animate folding
Nested packages sat in a grey inset panel and the folder tree drew one
straight line per level, so neither showed which row a child hangs from.
Both now use one faint spine under the parent with a rounded elbow into
each child that stops short of its checkbox or icon, in an opaque colour
so overlapping strokes leave no darker seam.

Opening and closing a package or folder now grows and shrinks instead of
jumping; collapsed content is inert while it shrinks, and reduced motion
turns the animation off. Nested row actions line up with top-level rows,
and a selected folder's block keeps straight sides.
2026-10-24 23:24:08 +08:00
Willie a96c5e55f2 fix(ui): warn that uninstalling a package removes its nested skills (#636)
* fix(ui): warn that uninstalling a package removes its nested skills

Uninstalling a skill moves its whole folder to the trash, so the skills
nested inside it go too, but the confirmation listed only the one skill.
It now counts them in the title, marks the package row and adds a note.

Selecting a package together with its nested skills (select all does this)
also sent every name to the server, which trashed the package first and
then failed on each child whose folder was already gone. The dialog now
sends only the outermost selected skills.

The success toast uses the same count as the title; it reported the
server's per-name count, which read as fewer removals than confirmed.

* fix(ui): keep nested skills of a linked folder root in uninstall

A linked folder whose root is itself a skill can only be unlinked, so the
server refuses to trash it. Collapsing the selection to that root dropped
its selected children from the request and none of them were removed.
A linked root no longer counts as holding its children: they are sent on
their own and the root row does not claim to remove them.
2026-10-24 22:08:23 +08:00
Willie 1a79971df4 feat(ui): show skill descriptions in the list and redesign package rows (#635)
* feat(ui): show skill descriptions in the list and let expand all open packages

Reviewing a large library meant opening each detail page just to read
what a skill does (#627, proposal in #631). The resources list response
now carries each skill's and agent's frontmatter description, read in
the same pass as manual-only, and the list shows it truncated under the
name with the full text on hover.

The read now decodes the frontmatter once for both fields. An unquoted
": " in a description is invalid YAML, so a failed decode falls back to
the line scanner instead of dropping the description and manual-only.
Editing a skill refreshes the list too, so the new description shows
right away.

Expand all / Collapse all also opens and closes nested-skill packages
from #624; before, it only touched source and folder groups.

Closes #627

* feat(ui): redesign list packages as an inset panel with a description switch

The chevron-in-a-column nesting read as a second, unrelated table and gave
no room for the descriptions #627 asks for. A count pill after the package
name now opens its skills in one quiet inset panel, with deeper packages
indented under a faint guide, so the hierarchy stays readable at any depth.

The rest closes the gaps left against #627: a Show > Descriptions switch
keeps the compact list one click away, keyboard focus reveals the full
description, a search opens only the packages holding a match without
overwriting what the user left open, and the selection bar says how many
selected items are out of view. Only the name opens the detail page, since
whole-row clicks were easy to trigger by accident once rows held more text.

* fix(ui): keep linked-folder matches when searching a folder group

Searching while grouped by folder took package ancestors only from skills
whose folderOf matched the group key, but groupByFolder keys a linked
folder's skills by the link name. Every skill in a linked folder fell out
of its own group, so the header counted a match and drew no row. The
ancestor pool is now each folder group's unfiltered skills, keyed by
groupByFolder itself, which always contains the group's matches.

* fix(ui): keep the .ss-r .nm.m rule the design token export reads

Merging it into :is(.ss-r, .ss-nr) .nm.m removed the exact selector that
scripts/design/tokens.py looks up for the row name type scale, so the
design token tests failed in CI.
2026-10-24 21:43:12 +08:00
Willie a65414fa2f feat(ui): nest skill packages under their parent in the list view
A package that ships its own SKILL.md plus nested skills used to list
every child as a peer, so one large package could fill the page and hide
which skills belong together (#624, proposal in #625).

The list view now puts each skill under the nearest skill whose folder
holds it, within its current group. Packages start collapsed with a
nested count, a search opens them so matches stay visible, and paging
counts top-level rows so a package is never split across pages.
Selection, select-all and bulk actions still work per skill.

Closes #624
2026-10-24 18:37:08 +08:00
trojanwk fafbe957d4 docs(proposals): show skill descriptions in the installed list (#631)
Record the independently requested local use case from #627 for maintainer discussion. Keep adoption optional and leave runtime behavior and the hierarchy-first scope unchanged.
2026-10-24 18:27:21 +08:00
trojanwk 017dfab88f docs(proposals): organize large skill lists with expandable package rows (#625)
* docs(proposals): describe expandable skill package rows

Large skill libraries flatten package roots and nested skills into peers. Propose path-based list hierarchy and outline optional list context controls while preserving install and sync semantics.

* docs(proposals): narrow skill hierarchy to maintainer feedback

Keep the first implementation focused on real directory ancestry, defer other list ideas, and define root-entry pagination so expanding a package does not split its children across pages. Prefix the proposal filename with its tracking issue.
2026-10-24 18:24:37 +08:00
Willie abc47a344d test(integration): drop EvalSymlinks workarounds made redundant by #610
NewSandbox now resolves its root, so these tests no longer need to
canonicalize macOS /var temp paths themselves. The leftovers were no-ops
that suggested the sandbox could still hand out symlinked paths.
2026-10-24 18:00:12 +08:00
Rusty ShacklefordandClaude Opus 5.5 51cecbeab4 test(testutil): align sandbox paths with symlinked temp dirs (#610)
On macOS, TMPDIR sits under /var, a symlink to /private/var. Sandbox
paths kept the unresolved form while the CLI reports canonical paths,
so tests needed per-case EvalSymlinks workarounds. NewSandbox now
resolves its root once.

RunCLIInDir and RunCLIInDirWithInput pass an explicit Env, so os/exec
does not set PWD and the child inherits the test process's PWD. The CLI
then falls back to getcwd and reports the canonical path even when
invoked through a symlinked directory, unlike a real shell. Set PWD to
the requested dir so the helper matches shell behavior.

The affected integration tests now create explicit symlink aliases so
they keep covering aliased working directories and config paths.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-24 17:58:31 +08:00
trojanwk e5e2e2c0f3 fix(ui): restore jsdom storage in Node 26 test workers (#626)
Node exposes native localStorage without usable storage when no backing file is configured. Disable native Web Storage for test workers only when the runtime exposes it, allowing jsdom to populate browser storage and preserving Node 24 behavior.
2026-10-24 17:55:18 +08:00
Willie 2d196c286b feat(check): show what changed in a skill since install (#623)
* feat(check): show what changed in a skill since install

#622 made a hand-edited skill visible as modified and kept update from
overwriting it, but there was still no way to see the edits before
deciding to keep or discard them (#621).

LocalChanges compares the skill's files with the hashes recorded at
install, fetches the source at the recorded commit only when a recorded
file changed, and diffs each file against it, so the diff shows the
user's edits even after upstream moves on. A skill without a recorded
commit is refused rather than diffed against HEAD, which would show
upstream changes as the user's.

It backs `check <name> --diff`, GET /api/resources/{name}/local-changes,
and the dashboard: the Modified locally dialog on the skill page lists
the diffs, and the Updates tab links a modified skill to it. update's
skip hints now point at --diff. The route looks up the exact record and
refuses non-local names, so a nested or ../ path cannot borrow a
top-level skill's record or read outside the source. The file diff
helper moved to textdiff so the CLI and server share it.

* fix(install): diff local changes against the full installed commit

entry.Version holds the short SHA from `rev-parse --short`. A targeted
fetch needs the full SHA, so checkoutCommit fell back to fetching every
branch and tag with --unshallow: viewing one edited skill could download
the repository's whole history, and fail when the commit is only
reachable by its full SHA.

Use entry.Commit, the full SHA install records, when it is the same
commit as Version; a Commit left from an older install, or a legacy
record without one, falls back to Version.

* test(install): keep checkout line endings when editing in LocalChanges test

On Windows git checks the installed copy out with CRLF, so overwriting
SKILL.md with LF content made every line differ and the expected diff
failed. Edit the installed file in place, as an editor would, and compare
the diff without carriage returns.
2026-10-24 17:32:34 +08:00
Willie 7a7cceefab feat(update): flag and protect skills edited since install (#622)
* feat(update): flag and protect skills edited since install

A skill installed from a repository and then edited by hand looked
exactly like an untouched one: check said up to date, and update either
reported it current or silently reinstalled it over the edit (#621).

Install already records each file's hash, so check now compares a
remote skill's files with those hashes and reports "modified", and
update skips such a skill until --force (CLI single, --all/--group,
dashboard). --force, the dashboard's Force Retry on the skipped row, or
the confirmation on the skill page discards the edit and reinstalls.

Two hash paths had to be made reliable for this to be trusted: the
dashboard's folder-wide target edit refreshed hashes by basename, so a
nested skill looked edited after skillshare's own change, and a skill
whose files cannot be hashed now counts as modified instead of being
overwritten.

* fix(server): keep earlier local edits when a target change rewrites SKILL.md

Changing a skill's targets in the dashboard rewrites its SKILL.md, and
both the folder-wide and the single-skill handler then re-hashed the
whole directory as the new baseline. An edit the user had already made
to any file in the skill was absorbed into that baseline, so the skill
stopped counting as modified and the next update overwrote the edit
without --force.

Both handlers now move only SKILL.md's recorded hash, and only when the
file still matched it before the rewrite. skillshare's own target edit
no longer reads as a local change, and an earlier edit still does. The
whole-directory refresh helpers lost their last callers and are removed.
2026-10-24 16:33:37 +08:00
Willie e441b57f0e fix(ui): offer a tracked repo's Update only when a check finds it behind (#619)
* fix(ui): offer a tracked repo's Update only when a check finds it behind

The Dashboard showed Update on every tracked repo, so a clean repo looked
like it had an update. Clicking it only reported "already up to date" and
the button stayed, which read as an update that would not apply.

The last update check is now kept in the shared query cache, the repo row
shows Update only for a repo that check found behind, and a pull that
succeeds drops the repo from that result so the Update button and the
Needs attention row both clear.

* fix(ui): drop the Dashboard update check when the Dashboard unmounts

Moving the check into the shared query cache kept it for the cache's
10-minute gcTime. An update made elsewhere (the Skills Updates tab, a
single skill update, the CLI) never corrected it, so returning to the
Dashboard still showed the repo behind in Needs attention and offered its
Update button. The old component state was discarded on navigation;
removing the query on unmount restores that for every update path at once.
2026-10-24 02:15:24 +08:00
Willie 265f518cc4 fix(version): refetch the skill version when a newer CLI release is cached (#620)
The skill and CLI version checks keep separate 24-hour caches. The CLI
check refetches once the installed version catches up with its cache, but
the skill check did not, so right after a release the dashboard, status
and doctor could offer the CLI update while calling the built-in skill up
to date. Both ship in the same release, so a cached CLI release newer than
the cached skill version now means the skill cache predates the release.
2026-10-24 02:07:06 +08:00
Willie 5ba626696e fix(ui): center single-line rows in the plugin update dialog
Rows align to the top so multi-Agent rows stack from there, which left a one-line row's name and version above the centre of its icon and checkbox.
2026-10-23 21:38:57 +08:00
Willie 8e43cc5ce6 feat(ui): import several installed plugins at once
Importing one plugin per click closed the dialog each time, so the user
had to reopen it and scroll back to the next row. Ticked rows are now
imported in turn while the dialog stays open, and a blocked or failed row
stays ticked for a retry. Installs with resource filters still go through
the single reviewed import, because their preserved native fields need to
be seen first.

Release-As: 0.26.4
2026-10-23 20:52:10 +08:00
github-actions[bot]andWillie 876d9a1d10 chore(main): release 0.26.3 (#607)
* chore(main): release 0.26.3

* chore(release): synchronize release metadata

* docs(release): polish v0.26.3 changelog

Describe OpenCode accounts and install naming behavior with user-facing examples, and consolidate dashboard and dependency fixes.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
v0.26.3
2026-10-23 20:23:33 +08:00
Willie a39a565074 docs: prepare v0.26.3 release overview
Refresh localized release callouts, credit contributors, and update Star History links with theme-aware charts.
2026-10-23 20:17:19 +08:00
Willie 330114bd6a fix(install): use frontmatter names for generic skill directories (#617)
* fix(install): use frontmatter names for generic skill directories

Resolve meaningful defaults for generic containers while preserving explicit names, tracked paths, existing update destinations, and directory-based source selection. Fall back on unsafe or colliding names to prevent overwrites.

Cover global and project installs, local and Git sources, naming overrides, tracked reports, collision safety, and updates. Closes #616.

* fix(install): preserve names during source-based updates

Resolve source-based updates against existing metadata before choosing destinations. Reject ambiguous or colliding update targets before writes, and reserve case-insensitive discovery names across filesystems.

Add global/project regressions for local and Git source updates, legacy destinations, grouping, and upstream-added collisions.

* fix(install): retain update ownership and selection checks

Only allow a metadata-verified same-source update to bypass destination conflicts. Reject occupied fallback destinations for both local and Git sources unless overwrite is explicitly forced.

Resolve destinations after skill selection so unrelated conflicts do not block filtered updates. Cover cross-source and unmanaged destinations, selected/excluded updates, and collision aborts in global and project modes.
2026-10-23 20:04:45 +08:00
Rusty Shackleford 107d1b2fe0 fix(website): approve dependency build scripts for pnpm 12 (#615)
pnpm 12 fails install when a dependency's build script hasn't been
approved. The pnpm 12.6.0 bump recorded ui's approvals but not the
website's, so devcontainer setup stops at the website install with
ERR_PNPM_IGNORED_BUILDS. Allow @swc/core's native setup and skip the
core-js postinstall banners.
2026-10-23 18:10:57 +08:00
Willie 2c724c4e51 fix(ui): put folder-conflict actions on their own row (#613)
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.
2026-10-23 14:29:43 +08:00
Willie dea01b1b8d fix(ui): link project targets in the folder-conflict hint to their project
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
2026-10-23 14:17:47 +08:00
Willie 9dcd8d6e63 fix(ui): send project-target folder conflicts to the project editor
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
2026-10-23 14:14:41 +08:00
Rusty Shackleford d23a44aec9 refactor(projects): share safe dashboard and CLI operations (#602) 2026-10-23 02:07:54 +08:00
Rusty ShacklefordandWillie 4f61689542 docs(proposals): define global project CLI scope (#592)
Co-authored-by: Willie <egg358358@gmail.com>
2026-10-23 01:04:42 +08:00
Adrian Love b7cffce14b fix(deps): update vulnerable Go dependencies (#608)
Replace advisory-matching module versions and their required transitive
versions. Keep application source and test assertions unchanged.

Local candidate build, vet and vulnerability scans pass; retained upstream
and custom UI packaging failures are disclosed in the pull request.
2026-10-22 23:27:05 +08:00
Krishnaswamy SubramanianandWillie dabe06a297 feat(targets): support OpenCode config directory accounts (#594)
* feat(targets): support OpenCode config directory accounts

OpenCode v2 introduces support for custom configuration directories
via OPENCODE_CONFIG_DIR, storing opencode.json and agent directories.

Previously, skillshare rejected OpenCode accounts configured with a
custom config directory because OpenCode was missing config_dir and
was excluded from accountAgents in hooks and MCP services.

- Define default config_dir (~/.config/opencode) in targets.yaml
- Add OpenCode to account agents and register OPENCODE_CONFIG_DIR
  across hooks and MCP service handlers
- Route OpenCode account MCP configuration to opencode.json inside
  the account config directory

Resolves #593.

* fix(targets): add OpenCode to schemas, completions and docs

Add opencode to the targetConfig.agent enum and config_dir description
in schemas/config.schema.json so configurations containing OpenCode
account targets pass schema validation.

Include opencode in the target --agent completion scripts for Bash,
Zsh, Fish, PowerShell, and Nushell.

Update website documentation and built-in skill references to describe
OpenCode accounts and OPENCODE_CONFIG_DIR management alongside other
account agents.

* fix(targets): support plugin accounts and overlap

Add OpenCode account recognition and OPENCODE_CONFIG_DIR resolution to
the plugin service so plugin sync works for OpenCode account targets.

Introduce TargetScanPaths to resolve cross-runtime scan paths using
TargetConfig.Agent for account targets while retaining the account's
own primary directory. Update path overlap detection, doctor checks,
and LeakedSkills to warn about leaked skills for account targets.

Update localized docs (zh-Hans, zh-Hant, ja, ko) and plugin references
to document OpenCode account targets and OPENCODE_CONFIG_DIR. Update
the available targets handler test to expect OpenCode's configDir.

* fix(targets): isolate OpenCode accounts and scan paths

Reject OPENCODE_CONFIG overrides when operating on OpenCode accounts
and clear OPENCODE_CONFIG in the account execution environment so
plugin operations target the account directory.

In TargetScanPaths, remap config-root paths to the account directory
while preserving external scan paths like Codex's ~/.agents/skills.

* fix(plugins): use account target in OpenCode update probe

Pass c.Target instead of a hardcoded "opencode" when probing whether
OpenCode supports plugin updates, ensuring account-configured CLI
binaries and account environment variables are used during preview.

* test(mcp): isolate XDG_CONFIG_HOME in account test service

Isolate XDG_CONFIG_HOME to the temporary test directory in
agentAccountService to prevent runner environment variables from leaking
into TestAccountEnvOverrideDoesNotPruneDefaultHome when testing OpenCode
account shell overrides.

---------

Co-authored-by: Willie <egg358358@gmail.com>
2026-10-22 21:50:06 +08:00
Willie 0122ff0264 chore(release): request 0.26.3
Request the next release version through Release Please.

Release-As: 0.26.3
2026-10-22 21:29:52 +08:00
Willie 835c8b3d72 docs(changelog): describe the Go 1.26.10 security fix for users (#606)
The generated entry repeated the commit title. Say what the CVE changes
for users, which releases lacked the fix, and which requests it covers.
2026-10-22 14:54:58 +08:00
github-actions[bot] ce4aafdb89 chore(main): release 0.26.2 (#605)
* chore(main): release 0.26.2

* chore(release): synchronize release metadata

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
v0.26.2
2026-10-22 13:45:03 +08:00
Willie 13330867ce fix(security): bump Go to 1.26.10 for CVE-2026-111943 (#604)
Go 1.26.10 and 1.27.3 make crypto/x509 reject chains that pass through
the compromised eMudhra intermediate CAs. Go 1.25 has no backport, so
binaries built from go.mod 1.25.5 would still trust forged certificates
from those intermediates on systems whose trust store has not been
updated. skillshare makes HTTPS requests for upgrade, update checks,
search and registry lookups, so release binaries need the fix.

Move go.mod, mise.toml, the three Docker images and the sandbox docs to
1.26.10. CI and release builds follow go.mod through go-version-file.
2026-10-22 13:34:41 +08:00
github-actions[bot]andWillie 02d8dfffa0 chore(main): release 0.26.1 (#597)
* chore(main): release 0.26.1

* chore(release): synchronize release metadata

* docs(changelog): describe 0.26.1 for users

Replace the generated entry with user-facing notes so the release body
explains what changed in the dashboard and in the tracking guidance.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
v0.26.1
2026-10-22 02:22:28 +08:00
Willie 2bba224cdf fix(ui): update agents from the Updates tab and repo detail page (#601)
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
2026-10-22 00:39:12 +08:00
Willie 7b952c02a9 fix(update): honor accepted findings in dashboard tracked updates (#599)
* fix(update): honor accepted findings in dashboard tracked updates

The dashboard ignored findings accepted through the CLI, so a tracked repo
that `update --force` let through was blocked again on the next dashboard
update, and every dashboard Force Retry had to be repeated. Regular skill
updates in the dashboard already honored and recorded acceptances, so only
tracked repos differed.

Tracked-repo updates now always honor accepted findings and record the ones
an override lets through, for both callers. The opt-in option and the
AuditGate flag it fed are removed, since no caller turns them off.

Dashboard agent tracked repos passed an empty source dir, so a nested repo
kept acceptances in its group folder under a different key than the CLI.
They now pass the agents source, as the CLI does.

* fix(update): reload the agents store after agent repo refresh

Dashboard agent tracked repos now refresh metadata in the agents source,
but a metadata change reloaded the skills store, leaving the agents store
as it was until the next request. Reload the store that matches the source.

Every caller of update.TrackedRepo now passes a source dir, so the
empty-dir guard and its doc no longer describe a supported mode. The new
agent test reuses the tracked fixture instead of rebuilding it.
2026-10-21 23:28:16 +08:00
star-nebula e10304eb81 test(theme): enable Windows CI coverage (#589)
Correct Unix-only resolution expectations on Windows and pin terminal and renderer state so the package is deterministic. Add theme to the Windows test job to catch future platform regressions. Related to #344.
2026-10-21 23:08:20 +08:00
Willie 5c59de8847 docs(skill): restore plugin guardrails trimmed in #596
Trimming the plugin section dropped the instructions to run only the
requested operation and to read plugins.md before applying changes, so
agents lost the cue to stop at what the user asked for.

The tracking docs fix (#596) and this follow-up ship as 0.26.1.

Release-As: 0.26.1
2026-10-21 22:42:23 +08:00
Rusty Shackleford b69b3584d3 docs: clarify upstream skill and plugin tracking (#596)
* docs: clarify upstream skill and plugin tracking

The built-in skill recommends --track --all, which install rejects. Show valid scoped workflows for following upstream collections and native plugins, distinguish update from sync, and explain selection flags before users hit their conflicts.

* docs: clarify default-branch and retained-ref boundaries

Qualify default-branch guidance for unpinned sources so update examples do not imply that an existing ref is cleared. Clarify mixed resource collections and filter modes alongside the workflow.

* docs: address tracking workflow review feedback

Remove rejected tracking/selection combinations from enterprise recipes in all five languages, document incompatible flags in the install tables, and state the selection errors explicitly. Keep the built-in skill concise by routing detailed upstream workflows to its references.
2026-10-21 22:40:31 +08:00
github-actions[bot]andWillie 7ca59a023f chore(main): release 0.26.0 (#581)
* chore(main): release 0.26.0

* chore(release): synchronize release metadata

* docs(changelog): clarify 0.26.0 release changes

Describe MCP options, Executor serving, hook file references, native OMP builds, and dashboard shortcuts from the user's perspective. Include the shared-token editing warning and keep the website changelog synchronized.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
v0.26.0
2026-10-20 14:20:56 +08:00
Willie d28408f86e docs: prepare documentation for 0.26.0
Update the release highlights in every README and fill the missing hooks, pull conflict, and memory guidance translations before reviewing the Release PR.
2026-10-20 13:48:53 +08:00
Willie 829cbb176d fix(plugins): honor native OMP marketplace builds (#588)
* 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.
2026-10-20 12:22:05 +08:00
Willie 364af36391 feat(ui): update outdated memory guidance in one step
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.
2026-10-20 00:23:42 +08:00
Willie a2112ff681 feat(ui): keep all local or all remote in the pull conflict dialog
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.
2026-10-19 23:21:54 +08:00
Willie f6e7265414 feat(hooks): read hook code and scripts from files next to the config (#586)
* 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.
2026-10-19 22:48:00 +08:00