2469 Commits
Author SHA1 Message Date
Willie 45d28e601b Merge pull request #394 from runkids/release-please--branches--main
chore(main): release 0.24.5
v0.24.5
2026-10-05 01:29:39 +08:00
Willie d3e42a0e9b Merge branch 'main' into release-please--branches--main 2026-10-05 01:23:49 +08:00
Willie 38a6446e64 docs(changelog): write the 0.24.5 notes for users
Release Please listed every commit in the range, with each pull
request's merge commit repeating its fix. The entry now says what
changed for users: Pi package versions and npm update checks, the Sync
box that puts failures first, status no longer reporting drift after a
complete agent sync, Codex plugins with a portable manifest updating
again, .skillignore.local overrides being reported, and the smaller
dashboard fixes, with commands to try.
2026-10-05 01:18:34 +08:00
Willie 4a7d2ab414 Merge pull request #401 from runkids/runkids/release-0.24.5-docs
docs: bring translations and status up to date for 0.24.5
2026-10-05 01:17:22 +08:00
Willie 751d0b50fa docs: bring translations and status up to date for 0.24.5
Release prep for 0.24.5 found three places where the docs no longer
matched what the pending range changed:

- The Codex portable-manifest rule (Codex installs from a root
  plugin.json when a package has both manifests, so Skillshare expects
  its version, or 1.0.0) was only in the English plugin reference.
- The .skillignore.local behavior (a pattern without / matches at any
  depth, the dashboard shows the .local rules in Settings > Files and
  reports a toggle they override as failed, and GET /api/skillignore
  returns the .local file) was only in the English filtering and ui
  references.
- The status reference did not say that the agents column counts only
  the agents a target syncs, after .agentignore, the target's
  include/exclude and each agent's targets frontmatter.

The ja, ko, zh-Hans and zh-Hant pages now carry the first two, and every
language carries the third. The Latest callout in README.md and its
translations now describes 0.24.5, which includes a feature.
2026-10-05 01:13:15 +08:00
github-actions[bot] 77bd085d3a chore(release): synchronize release metadata 2026-10-04 16:58:56 +00:00
github-actions[bot] 764dfa261a chore(main): release 0.24.5 2026-10-04 16:58:53 +00:00
Willie c9e1566287 Merge pull request #400 from runkids/runkids/plugin-sync-grouping
feat(plugin): check Pi npm packages for updates and show their versions
2026-10-05 00:58:19 +08:00
Willie 9ea4d655df fix(ui): prefer the installed version for every Pi package
Codex review on #400: the previous fix preferred Pi's installed version
only for npm packages. Pi reads the package.json of every installed
package, git and local ones too, and plugin import records the version it
saw, which a later pi update does not rewrite. An imported git package
moved from 1.0.0 to 1.1.0 kept showing 1.0.0. On a Pi target the page now
prefers what Pi reports for any package, and falls back to the recorded
version.
2026-10-05 00:52:26 +08:00
Willie 224a6bc23c Merge branch 'main' into runkids/plugin-sync-grouping 2026-10-05 00:49:05 +08:00
Willie ff618b6034 fix(ui): show the version Pi installed, and clear an update that was already done
Codex review on #400:

- Now that Pi reports an installed npm package's version, plugin import
  records it in config, and nothing rewrites it after a pi update. The
  Plugins page preferred that recorded version, so an imported package
  kept showing its import-time version. For an npm package the page now
  prefers what Pi reports installed, and falls back to the recorded one.

- When the package reached the checked version before the update ran,
  the update preview had a noop change and the apply an unchanged
  outcome, but only update changes took an Agent off the checked list, so
  the stale old -> new tag and Update button stayed until another check.
  A noop with an outcome that is not failed now clears it too.
2026-10-05 00:44:21 +08:00
Willie 116feb6d16 fix(plugin): ask npm which registry it uses, and keep updates that never ran
Codex review on #400:

- The private-registry check read npm's config by hand, and each round
  found another place npm reads it from: the lowercase environment, the
  global npmrc, and now a globalconfig or prefix set in the user .npmrc.
  Rather than chase npm's rules, the check now asks npm itself:
  `npm config get registry @scope:registry` in the folder Pi runs npm in.
  Any registry other than npmjs, or npm not answering, leaves the package
  to Pi. The hand-written .npmrc reading is gone.

- When an apply stopped before any Agent ran, such as on a stale preview,
  the result had no outcomes, and the page took every planned update off
  its list, hiding the row's Update action. Only an Agent the result
  reports done comes off now.
2026-10-05 00:32:56 +08:00
Willie be661c593f fix(plugin): keep row updates without a new version, read npm's global config, keep odd manifests
Codex review on #400:

- The Plugins page kept only one version per plugin from a check, and
  only when the change had one, then hid the row's Update button when an
  Agent already had that version. A source plugin whose content changed
  without a version bump, or whose manifest has no version, so lost its
  Update action once the check dialog closed. The page now keeps what the
  check found per plugin and Agent, with or without a version, and an
  applied update takes those Agents off; the version only shows what the
  update brings.

- The private-registry check did not read npm's global config, so a
  registry set only in $PREFIX/etc/npmrc still sent the package name to
  npmjs. It now reads the file npm_config_globalconfig names, else
  $PREFIX/etc/npmrc with the prefix from the environment or the npm on
  PATH, and leaves the package to Pi when it can't tell where that file
  is.

- Reading the package version made a package.json whose version is not a
  string fail to decode as a whole, which dropped its pi manifest and the
  extensions it declares. The version is decoded on its own now, so an
  odd one is only skipped.
2026-10-05 00:22:30 +08:00
Willie 091c39262b docs: prefer shared devcontainer with isolated task state
Use ssenv and explicit worktree and binary paths for parallel CLI verification. Reserve temporary containers for mount or runtime isolation needs and avoid duplicating unnecessary frontend dependencies and Go build caches.
2026-10-05 00:12:38 +08:00
Willie c5571a8cae fix(plugin): leave npm ranges and tags to Pi, and read a lowercase userconfig
Codex review on #400:

- A package added with a range such as npm:demo@^1.2.0 was compared with
  npm's unrestricted latest. With latest at 2.0.0 and the newest matching
  release at 1.9.0, check kept offering 2.0.0, which Pi never installs
  because it keeps the configured range. Only a package added without a
  version follows latest now; one with a range or a tag is left to Pi, as
  a pinned one already was.

- The private-registry check read the user .npmrc path only from
  NPM_CONFIG_USERCONFIG. npm reads its environment case-insensitively, so
  a lowercase npm_config_userconfig pointing at an .npmrc with a private
  registry was ignored, and the package name went to npmjs. Both
  spellings are read now.

The plugin reference, its translations and the built-in skill say which
packages the check leaves to Pi.
2026-10-05 00:12:29 +08:00
Willie cc249c1498 fix(plugin): leave private npm registries to Pi, and keep updates for Agents still behind
Codex review on #400:

- The update check asked the public npm registry about every unpinned Pi
  package, even when the environment or an .npmrc sends the package, or
  its scope, to another registry. A public package with the same name
  could then hide a real update or offer an unrelated version. The check
  now reads the npm registry settings for the package and its scope from
  the environment, Pi's npm folder and the user .npmrc, and falls back to
  checking in Pi when any of them names another registry.

- The row's Update button disappeared as soon as any Agent had the
  version the check found, so with one Pi target behind and another up to
  date, the one behind lost it. The row now compares each selected Agent
  with that version on its own, and updates only the ones behind.
2026-10-05 00:05:07 +08:00
Willie 0f2ce354fc feat(plugin): check Pi npm packages for updates and show their versions
The Plugins page listed every binding a run touched, one row each, so a
single failure sat among a dozen "unchanged" rows, and the preview did
the same. Failures now come first, Agents that ended the same way share
a row, and what stayed the same folds into one Unchanged line that opens
to one row per plugin, with Pi packages apart. Logos stay only on the
rows that need a look.

An npm package in Pi recorded no version and no source, so it showed no
version and Check updates could only say to check in Pi. The installed
package.json now gives its version, on the Plugins page and in a Pi
target's Extensions tab, and check compares that version with npm's
latest. A newer version gets an Update button on the row and in the
check's result; it updates that one package with pi update <source>,
not pi update --extensions, which would also update packages the
preview never listed. update leaves a package already at npm's latest
alone, and records no version, so the dashboard keeps reading what Pi
installed. The two check messages that were English in every locale now
have keys.

Release-As: 0.24.5
2026-10-04 23:55:11 +08:00
Willie 43b857b2e8 Merge pull request #399 from runkids/runkids/pi-managed-plugin-grouping
fix(ui): keep Skillshare-installed Pi plugins out of Pi packages
2026-10-04 23:22:23 +08:00
Willie eb58dec1f0 fix(plugin): keep the global owner of a Pi project override
Codex review on #399: switching an extension of a global package in a
project writes a project override, which the project view reads in its
project-entry loop. In project mode that loop looked only at the
project's config, so the override lost the global plugin's name.

A project entry now falls back to the global config's owners when the
project config has none.
2026-10-04 23:14:07 +08:00
Willie 56b4f79ac4 fix(plugin): find global owners of inherited Pi packages in project mode
Codex review on #399: a dashboard started in project mode gives the
plugin service the project's config, so a global Pi package that
Skillshare installed, inherited by the project, found no owner and its
card fell back to the state path again. The earlier test kept
ConfigPath on the global config and missed this.

The service now takes the global config path in project mode, and the
project view looks up inherited global entries there.
2026-10-04 23:08:33 +08:00
Willie a510d2a089 fix(plugin): name the managed plugin of a Pi entry with a problem
Codex review on #399: an entry with a readable source but a value
Skillshare can't edit, such as "extensions": null, returned early in
both the global and project views before ManagedBy was set. Its card
then fell back to the plugin's local state path again.

The lookup now runs for every entry whose source can be read, before
the early return.
2026-10-04 23:02:03 +08:00
Willie a62b140b15 fix(ui): leave managed plugins out of the Import dialog
The Import dialog listed everything an Agent reports as installed,
including what Skillshare itself installed there (a Pi plugin shows up
as its state path) and what was already imported. Importing either one
again changes nothing, and the path does not say which plugin it is.

Each Agent's list now skips entries whose ID a package already binds to
that Agent, counts only what is left, and says when everything there is
already managed.
2026-10-04 22:59:14 +08:00
Willie c31dffc450 fix(plugin): name Skillshare-installed packages in Pi project views
Codex review on #399: piProjectState never set ManagedBy, unlike
piGlobalState. A project's Extensions tab (<project>@pi, or pi in
project mode) therefore titled a plugin Skillshare installed by its
state path and dropped the "Managed by Skillshare" tag, for both the
project's own entries and the global entries it inherits.

The lookup by source, then by resolved local path, moves into
piManagedBy and runs for every package of both views.
2026-10-04 22:56:12 +08:00
Willie f0e3ee22b3 test(plugin): keep Codex finder tests off the machine's own installs
The macOS finder tests stub PATH, but the candidate list still checked
/opt/homebrew/bin/codex, /usr/local/bin/codex and /Applications on the
real filesystem. In the devcontainer /usr/local/bin/codex exists, so it
won over the app bundle each test set up and make check failed there.

The finder now joins those absolute paths onto a root field, "" on a
real machine, and the tests point it at an empty temp dir.
2026-10-04 22:56:12 +08:00
Willie 4a2ff0dcde fix(ui): keep Skillshare-installed Pi plugins out of Pi packages
A plugin Skillshare installs from a Git source and binds only to Pi
landed in the "Pi packages" list, which is meant for packages Pi
installs itself (npm:/git: identifiers with no recorded source). The
list now also requires that neither the package nor any binding has a
source, so such plugins stay under "Managed by Skillshare".

The Pi target's Extensions tab titled those same plugins by their
local state path (local:.../skillshare-<hash>/content), which does not
say which plugin it is. The server already returns the plugin name as
managedBy; use it as the card title, keeping the path in the tooltip
and details.
2026-10-04 22:50:10 +08:00
Willie 9f39b2458e Merge pull request #397 from runkids/runkids/395-status-agent-filters
fix(status): expect only the agents a target would sync
2026-10-04 22:33:57 +08:00
Willie b8a39f373a Merge pull request #396 from runkids/runkids/codex-portable-manifest-version
fix(plugin): expect the version Codex reads from a portable manifest
2026-10-04 22:33:39 +08:00
Willie 27cece3f24 Merge pull request #398 from runkids/runkids/wiki-track-codex-review
docs(wiki): follow Codex's first review right after opening a PR
2026-10-04 22:29:11 +08:00
Willie 640e853c99 fix(status): count only links for agents the target expects
countAgentLinksAndBroken counted every healthy .md link in the target,
so a leftover link for an agent the target no longer syncs could stand
in for a missing expected one and hide drift. status and doctor now
count a link as linked only when its name is an expected agent; broken
links are still reported regardless of name.

Refs #395, Codex review on #397.
2026-10-04 22:28:35 +08:00
Willie f5a2470276 fix(plugin): keep the Codex logo under a portable manifest
Adopting the portable root plugin.json replaced the whole Codex target
info, dropping the interface.logo read from .codex-plugin/plugin.json.
Codex still overlays that native manifest, and the portable one rarely
names a logo, so the add/list UI fell back to a generic icon.

Refs Codex review on #396.
2026-10-04 22:24:12 +08:00
Willie 47a98b81ff fix(status): expect only the agents a target would sync
status counted every discovered agent against each target, while sync
agents writes only the agents left after .agentignore, the target's
include/exclude and the frontmatter targets field. A target that leaves
some agents out was reported as N/M with drift after a complete sync,
in the table and in --json, in global and project mode. doctor and the
dashboard already filtered per target.

status now applies the same three filters before counting and expecting.
The table reports an invalid include/exclude as an error, like it does
for skills; --json falls back to the active agents.

Refs #395
2026-10-04 22:21:00 +08:00
Willie ad7a518420 docs(wiki): follow Codex's first review right after opening a PR
The polling instructions read as applying only after an `@codex review`
comment, so an agent could open a pull request and hand Codex's initial
findings back to the user instead of following them up itself.
2026-10-04 22:19:22 +08:00
Willie 04c4c95cba fix(plugin): keep version check for versionless portable manifests
A portable root plugin.json without a version left the Codex binding's
version empty, which skips the post-update version check, so an update
could advance the snapshot while Codex still ran an older copy. Codex
reports 1.0.0 for such a manifest, so expect that instead.

Refs Codex review on #396.
2026-10-04 22:18:57 +08:00
Willie 021e0037b6 fix(plugin): expect the version Codex reads from a portable manifest
Codex 0.159 installs from a portable root plugin.json (agent-plugins.org
schema) ahead of .codex-plugin/plugin.json, and reports 1.0.0 when that
manifest has no version. Skillshare preferred .codex-plugin/plugin.json,
so updating a package that ships both (ponytail 4.10.3) failed with
"native update returned version 1.0.0; expected 4.10.3" on every sync.
2026-10-04 22:14:28 +08:00
Willie a265155844 Merge pull request #392 from runkids/runkids/391-extension-agent-status
fix(status): count extension-converted agents as synced
2026-10-04 20:12:07 +08:00
Willie c43bb763f9 fix(status): count one extension output per agent
Two agents that flatten to the same name matched the same manifest entry
and were both counted, so status could report 2/2 with one output on
disk. Each manifest key now satisfies one agent.

Refs Codex review on #392.
2026-10-04 20:01:51 +08:00
Willie aca1438fb5 Merge remote-tracking branch 'origin/runkids/391-extension-agent-status' into runkids/391-extension-agent-status 2026-10-04 19:49:55 +08:00
Willie 51a3be1ca6 fix(status): report drift when an extension agent's source changed
Counting an extension output as synced from its output hash alone missed
the common case: the user edits the agent in the source and runs status
to see whether a sync is due. The output still matched the manifest, so
status, doctor and the dashboard reported no drift although the next
sync would regenerate it.

Sync now records a SHA-256 of the source each output was converted from
in the manifest (sources), and status counts an output only when both
the output and that fingerprint are current. Outputs recorded by earlier
releases have no fingerprint and count as current until the next sync
records one, so upgrading does not show the 0/N the report was about.

Refs #391, Codex review on #392.
2026-10-04 19:49:29 +08:00
Willie d589e4f92f Merge branch 'main' into runkids/391-extension-agent-status 2026-10-04 19:46:28 +08:00
Willie d8c1437234 Merge pull request #393 from runkids/runkids/ignore-local-feedback
fix(server): report toggles that .local ignore rules override
2026-10-04 19:46:02 +08:00
Willie af7654712c fix(server): log a disable that a .local rule overrides
When a "!" rule in .skillignore.local overrode a single disable, the handler
returned 409 before its only ops log call, although AddPattern had already
written the pattern to .skillignore. The shared file changed with no trace in
the log. Log the attempt with status "error" and the reason before returning.
2026-10-04 19:40:44 +08:00
Willie d4c2f6e9a0 fix(server): report toggles that .local ignore rules override
Disabling a skill only checked that its path was written to .skillignore.
A "!" rule in .skillignore.local is applied after that file, and an
unanchored one such as "!feature-radar" re-includes every path segment with
that name, so the skill stayed enabled while the dashboard reported success.
The dashboard also never showed the .local file, so nothing explained why.

Single and batch toggles now re-discover after writing and report an item
that did not reach the requested state as failed, naming the overriding
file; the batch toast shows the first failure's reason. GET /api/skillignore
and /api/agentignore return the .local file, and Settings > Files shows its
rules above the editor.
2026-10-04 19:34:24 +08:00
Willie 6cc10220be fix(ui): make the mixed folder switch read as partly on
The tree pane's folder switch showed a partial state by only centering the
knob on the off-colored track. On a 34px track that looked like a stuck or
broken off switch. Give the mixed state a half-tone track and a dash in the
knob, the way an indeterminate checkbox reads.
2026-10-04 19:34:24 +08:00
Willie f403ea5a6f fix(status): count extension-converted agents as synced
An agent target with an extension writes each agent under output_ext
(reviewer.toml) with transformed content, and the manifest tracks that
output name. status, doctor and the dashboard's Sync tab counted synced
agents by looking for the source name and comparing with the source
content, so every converted agent was missing: status showed 0/N with
drift, doctor said the same, and the Sync tab kept them pending after a
successful sync.

For an extension target, count an agent as synced when the manifest
tracks an output with the same stem and that file still matches its
recorded hash. Matching by stem avoids loading the extension spec in
status paths. doctor keeps reporting leftover broken links for these
targets.

Refs #391
2026-10-04 19:33:50 +08:00
Willie 7ed49191a9 Merge pull request #388 from runkids/release-please--branches--main
chore(main): release 0.24.4
v0.24.4
2026-10-04 18:28:20 +08:00
Willie 534ae9793c docs(changelog): describe 0.24.4 from the user side
Replace the generated commit list with what each fix changes for the user, with the command that applies it.
2026-10-04 18:22:09 +08:00
github-actions[bot] 0e23aa7e06 chore(release): synchronize release metadata 2026-10-04 09:30:54 +00:00
github-actions[bot] 7d8b69deb4 chore(main): release 0.24.4 2026-10-04 09:30:51 +00:00
Willie b58d510ec6 Merge pull request #389 from runkids/runkids/skip-target-dotdirs-in-source
fix(sync): skip nested target dotdirs when discovering source skills
2026-10-04 17:30:27 +08:00
Willie 881d08e52e fix(sync): skip nested target dotdirs when discovering source skills
Installing a repo whose root is a skill copies the whole repo into the
source, including any .claude/skills/ the author keeps for their own
development. Install discovery already skips target dotdirs, but the
source walk used by sync, check, and the dashboard only skipped .git,
so those dev-only skills surfaced as nested skills and were synced to
every target.

Share the skip set through sourcewalk and apply it in both source
walks. Only dotdirs nested below the source root are skipped: host-style
paths directly under the root (.cursor/skills/*) stay visible because
they drive target inference.
2026-10-04 17:11:53 +08:00