* feat: add Nix flake and stop self-upgrade of Nix-store installs
Add flake.nix with packages, overlays.default, checks and a formatter,
building nix/package.nix with the unit tests in the Nix sandbox. The
version comes from the Release Please manifest, so releases need no Nix
edit. A Nix workflow runs `nix flake check` on non-docs changes.
`skillshare upgrade` now detects binaries under /nix/store/ and prints
`nix profile upgrade skillshare` instead of replacing a read-only store
path; update notices and doctor suggest the same command.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix(upgrade): give Nix installs the right update path everywhere
The first flake commit sent every /nix/store binary to `nix profile
upgrade`, failed a plain `skillshare upgrade` with exit 1 even when the
CLI was current, and left the dashboard with a generic 500.
- Tell `nix profile` installs (the profile manifest lists the store path)
from NixOS, Home Manager and overlay installs, which are told to update
their configuration and rebuild. Detection lives in one helper shared by
the update notice, doctor, upgrade and the dashboard.
- `upgrade` on Nix reports "already up to date" or prints the hint and
exits 0; the built-in skill still updates.
- The dashboard runs the upgrade so the skill updates, then answers
409 `upgrade.nix` with the command when a newer CLI waits on Nix. The
UI shows localized text for it in all 11 locales.
- Installs skip the unit tests; the flake's checks enable them. postPatch
lowers only the go directive's patch version and fails evaluation with
a clear message when go.mod needs a newer Go minor. CI also builds the
package on macOS.
- Docs, translations, the built-in skill reference and the release topic
describe the new behaviour.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Replace the separate audit and install proposal PRs with one selection
list: an index table, a one-line summary and decision per item, and the
full original proposal under each item.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
fakePiNpm is the Run fake for every target in a test Service, and it
rewrote Pi's settings.json after any command other than --version and
--help. Inventory queries all targets concurrently, so another target's
read-only CLI call could truncate the file while the pi host read it.
The pi host then saw no packages, and
TestPluginHostStateProducerLegacyProjection/local failed with "local
proof rejected". It failed three times on the v0.28.3 release run and
on PR #745.
Only install and remove change Pi settings, so only they write now.
* test(plugins): replace OMP ownership property tests with table tests
#758 added Hegel property tests for ompPreviewRuntime, which pulled in
hegel.dev/go/hegel and an alpha pseudo-version of ebitengine/purego as
the repo's only property-testing dependency. The logic under test is a
few booleans and a module name, so explicit cases cover it, and a plain
test runs on every platform instead of the ones Hegel bundles an engine
for.
The table keeps each dimension the properties drew: present or absent
link, exact or other path, same or other target, relative target,
scoped module names, linked ancestors at several depths, and a link
replaced by a directory or a file. It adds the no-proof case.
* test(plugins): name linked-ancestor subtests by depth
A subtest named nested/pkg contains a slash, so go test -run could not select it exactly.
A returning machine can retain an old runtime link after shared plugin intent changes source. Review its verified scoped cleanup together with replacement, then remove the old link before installing the new source while retaining shared cache and settings.
Preserve the original recipe identity when cleanup of a pending-only installation fails, so retries still reconcile the replacement. Add filesystem-backed regressions, Hegel ownership properties and a two-machine native CLI runbook.
Since v0.19.12 the docs say a project's skills/.metadata.json is
gitignored, but no code ever wrote that rule, so `git add .skillshare`
picked it up (#759). The file records this machine's installs (hashes,
timestamps) for folders that are themselves ignored; teammates already
share config.yaml and skills.lock.json, so committing it only adds noise
and merge conflicts.
ReconcileProjectSkills runs after every project install (CLI, search,
dashboard, move, trash), so it now adds the rule for the skills and
agents sources, at the path ProjectGitignoreTarget computes. Projects
initialized earlier and custom sources get it on their next install.
AdoptMovedProjectSkills is untouched, so `sync -p` still leaves
.gitignore alone (#547). Global mode keeps committing its metadata.
The docs that list the project .gitignore contents now name the
metadata files, and project-skills explains the one-time
`git rm --cached` for projects that already committed it.
Closes#759
* docs(audit): add optional skill review playbook
Give users a repeatable way to assess untrusted skills and their requested permissions before deciding whether to install them.
* docs(install): translate optional review playbook example
Keep translated install references aligned with the English example so readers can find the optional playbook before installing untrusted skills.
* docs(audit): align review playbook with audit exit codes
PR #686 now distinguishes execution errors from blocking findings. Describe the merged 0/1/2 exit contract while retaining the caveat for older releases and requiring report and coverage checks.
* docs(skill): move audit review procedure into built-in skill
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Willie <egg358358@gmail.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
prompt-injection-1 reported a JS `ignore: ['**/*.test.vue']` option and a
Python `root: Path, lang_filter: set[str] | None = None` parameter as
CRITICAL prompt overrides, which blocked `update --all` for vuejs-ai and
dotnet skills. The #376 exclusion only covered scalars, root paths and
ignore objects.
The exclude now also accepts an inline ignore array of quoted items
without spaces, and a typed root parameter whose types are capitalized or
builtin names, followed only by further `name: Type` parameters. Both are
limited to the key whose real configs use them, so `admin: Execute`,
`system: Path, Ignore` and comma-joined word lists stay CRITICAL.
Closes#749
anti-refusal-0 allowed up to 60 characters between "regardless of",
"despite" or "even if" and the policy noun, so a line that only names
security policies as a topic matched at HIGH, such as "Always answer,
even if the question mentions security policies." Require the policy
noun to follow the qualifier, with at most one determiner between them.
Every override form from #711 still matches.
Release-As: 0.28.3
* feat(audit): detect narrow prose risk directives
* fix(audit): honor link confidence and narrow refusal rule
Apply configured confidence to Markdown link findings and require safety-related evidence in anti-refusal directives to avoid ordinary compliance false positives.
* fix(audit): address prose and confidence review feedback
Narrow prose matches, preserve overrides when enabling rules, and expose effective confidence to rule consumers. Expand Markdown coverage and synchronize the audit guidance.
* fix(audit): retain scheduled payload detection
Keep detecting directives that schedule a payload while excluding ordinary payload processor terminology.
* fix(audit): preserve prose detection recall
Recognize concise disclosure and safety override directives while retaining benign exclusions. Share the confidence default and cover replacement overlays.
* fix(audit): detect quantified refusal directives
Retain detection when a directive refers to any or every user request while preserving benign security discussion.
* fix(audit): distinguish execution errors from findings
Return a separate exit code for audit errors so CI can tell an incomplete scan from a threshold finding. Preserve partial reports and give scan errors precedence when both occur.
* fix(audit): keep list and abort exit codes consistent
Preserve audit execution-error classification when list delegates to audit, so both global and project actions exit 2. Treat declining a large scan as a clean cancellation before any scanning or error logging.
Cover both paths with real terminal regressions and keep the documented exit-code contract aligned across translations.
Every /api/ request reloads config under the write lock of s.mu. The
Plugins page's inventory (Agent CLIs) and update check (network) held
the read lock for their whole run, and Go's RWMutex makes later readers
queue behind a waiting writer. Switching pages or reloading while a
check ran froze the whole dashboard until the check finished.
Build each service under the read lock and release it before the slow
work: plugin list, discover and preview; Pi extensions view and
preview, which run the Pi CLI; and MCP check, which looks up hosts and
probes servers live. Writes still take the write lock, and apply paths
still compare revisions, so a read that races a write is refused at
apply time rather than applied.
Finder writes .DS_Store into any folder it opens, and Explorer writes
Thumbs.db and desktop.ini. These counted as skill content, so opening an
installed skill in a file manager made check report it as modified, hid
update_available, and made update skip it unless run with --force, which
also lowers the audit threshold.
Skip them when hashing a skill, drop hashes earlier versions recorded for
them (from .metadata.json and from legacy sidecar migration), and keep
audit integrity from reporting them. Their content is still audited.
Closes#743
Vulnerabilities could only be reported in public issues, which exposes
exploit details before a fix. Point reporters to GitHub's private
advisory form, now enabled for the repository.
The project MCP tab now shows which Agents load an enabled global server
(cc4c9e43), but the reference only described the logos on servers that
are off. Document both before 0.28.2 ships.
Adding a server a user already set up in another project meant typing it
in again. The project MCP tab's Add server dialog now has a "From another
project" tab that fills the form from a server another mcp.projects root
has. The copy leaves out that project's targets, so it follows this
project's Agents. Off switches are not offered.
Closes#678
A project's MCP tab only showed Agent logos for a global server that was
turned off, so an enabled row gave no hint of where the server loads.
Enabled rows now show the Agents the global server is written to; a row
overridden by a project server of the same name shows none.
Closes#677
* fix(trash): keep install metadata when restoring from the trash
Uninstall pruned a skill's, tracked repo's or agent's entry from the
central .metadata.json, and only the files went to the trash, so a
restore brought back a remote install as a local one: update and check
no longer knew its source (#679).
Uninstall now saves the entries it prunes, with their audit acceptances
and target overrides, beside the trash entry, re-keyed to the trash
name so they match where restore puts the item. uninstall.Restore and
RestoreAgent merge them back after the files return, and every restore
path (CLI, trash TUI, dashboard) goes through them; the dashboard
passes its cached store so it does not go stale. The saved copy is
taken with the same rule RemoveByNames uses and copies each entry, so
legacy repo-group entries are kept and re-keying never touches the
live store.
In project mode uninstall also drops the skill's .gitignore rule and
lock pin, so a skill restore reconciles the project skills afterwards.
trash.Delete removes an entry with its saved metadata, and replaces the
direct RemoveAll calls in delete, empty and the 7-day cleanup. Items
trashed before this change have no saved metadata and still restore as
local.
* fix(trash): keep live records of another path when restoring metadata
A legacy store keys a grouped skill by its basename, so the saved copy of
frontend/foo was keyed "foo". If a different skill was installed as
root-level foo while frontend/foo sat in the trash, restoring it replaced
the root skill's record and lost its source.
Extract now writes full source-relative keys (legacy repo-group entries
keep theirs, since their Group is not their path), and Merge keeps a live
entry whose key names a different path instead of overwriting it. Merge
is shared by skill and agent restore, so both are covered.
#660 removed "Sync selection saved..." and its translation key, but
outcomeText.test.ts still expected it to localize, so the dashboard
suite failed on main. CI does not run vitest, which let it through.
#660 stopped filtering plugin changes and results by message, so rows
with no message now reach the join. Two such rows joined to a blank
note, which hid the "Blocked" fallback and showed an empty note under
a skipped or running plugin.
* feat(mcp): allow plain HTTP on trusted private networks
Containerized MCP gateways need to reach a skills server directly on a private network without adding a TLS terminator. Add an explicit flag and matching serve config opt-in, retain bearer authentication and the secure default, and warn when plaintext transport is enabled.
* fix(mcp): require explicit HTTP transport opt-in
Keep insecure HTTP opt-in in the container command so repository configuration cannot enable it. Reject the flag without HTTP, align translated examples, and cover startup warnings and authentication in the runbook and transport tests.
* fix(plugins): separate shared intent from machine-local receipts
Shared configs currently carry native paths, reviewed snapshots and pending
failures, so one host can publish local progress over another host's target
selection. Persist versioned declarations separately from local applied and
pending receipts, and reconcile reviewed installs, imports and cleanup against
this machine's native inventory without rewriting intent during sync/update.
Keep snapshot names and adapter safeguards, move the operation lock locally,
validate legacy adoption with local evidence, and invalidate approval on local
state or native-context changes. Preserve source recipes after native adoption,
require local import for absent native-only targets, and document the shared
writer upgrade boundary in schemas and translated references.
Cover two-host behavior, generated legacy fixtures, failure/recovery, stale
intent, cleanup, npm recipes and the existing CLI/API/UI consumers with focused
resource-capped tests. Fixes#651.
* fix(plugins): preserve intent and ownership across host transitions
Repeat-add must retain shared target selection, and update previews must resolve
the requested ref before reviewing fresh or replacement installs. Keep disabled
targets on the uninstall path and reject refs unsupported by native-only/npm
intent before they can produce invalid shared declarations.
Block changed-context add/import before Pi registration preparation so a new
account cannot overwrite the old receipt. Preserve unresolved legacy bindings
as passive private proof candidates before rewriting shared YAML, retaining
original intent/store for later verified adoption and cleanup. Never compose
these hints as executable state, and persist their explicit resolution.
Cover the five review classes, native/private failure boundaries, requested-ref
retry, and original-context hint proofs with isolated focused regressions.
Keep local format v1 and baseline account validation unchanged. Refs #651.
* fix(plugins): allow receipt-only orphan cleanup to complete
An installation already removed on this host can retain a local receipt when
another host removes or replaces shared intent. Sync correctly plans forget,
but native command verification rejects that metadata-only action and blocks
all targets before the receipt can be cleared.
Exclude forget from native command verification while retaining host inventory
checks and OMP scoped cleanup preparation. The existing completion path then
persists receipt deletion, including pending work and passive legacy hints.
Cover the cross-host disable/re-enable/remove walk, five native adapters,
failed work with a legacy hint, and absent source replacement alongside a
healthy target. Assert Apply completion, unchanged shared bytes/mtime, and a
quiet second sync. Refs #651.
* fix(plugin): reconcile ref intent across inventory consumers
Validate explicit ref changes before disabled targets can save them and reuse
one reviewed discovery throughout a preview. Surface shared ref changes as local
reconciliation work while preserving the applied native identity and receipts.
Reuse scoped legacy proofs for Pi extension ownership and make full inventory
the dashboard's authoritative package/host pair. Cover invalid and replacement
refs, read-only ownership, and shared-state properties without new persisted
state or dependencies.
* test(plugin): repair and consolidate host-state fixtures
Create source intent and a pending imported Claude update through supported
operations so direct and batch updates exercise the intended fixture. Keep the
marketplace-loss case locally owned before testing its skipped reinstall.
Consolidate cross-host repeat-add and requested-ref replacement/orphan retries
at their existing owners, retaining failure recovery and shared-byte checks.
Trim duplicate HTTP and translated-text assertions from consumer tests.
* fix(plugin): reconcile legacy snapshot reads and native imports
Resolve legacy snapshot ownership through existing scoped proofs before listing,
reading or discovering cached source files. Keep adoption read-only and limit
proof work to the requested package and targets; current receipts need no CLI.
Only preserve reviewed source metadata on reimport when intent remains source
managed. Native-only intent must not resurrect an older Git source after a
same-ID local import. Retain identity mismatch and reviewed-source safeguards.
Remove the unused source-folding helper left by the old shared runtime writer.
* Preserve reviewed package versions locally
* Fix reviewed package version lifecycle
* fix(plugin): report missing local imports in doctor
Show the local-import instruction instead of claiming a skipped imported
plugin is healthy. Preserve the missing-CLI warning and shared config bytes.
Keep fixture native settings inside scratch XDG directories and serialize
the fake CLI calls used by concurrent inventories. Update assertions to
separate shared declarations from local versions and native IDs, and align
the raw-write audit with private plugin state and operation locks.
* test(plugin): use declarations for doctor source fixture
The missing-CLI case has no native ID, so encode it with the version 2
declaration schema. Keep the native-only import case in legacy syntax.
* fix(plugin): install shared sources from reviewed snapshots
When a source target is already declared, first sync must install its
reviewed local snapshot even if the native client has a package from the
same marketplace. Keep explicit add adoption and native-only import intact.
Extend the existing two-host adoption check to cover an independent native
installation on the second host and verify a quiet subsequent sync.
* fix(plugin): preserve reviewed retries and native collision boundaries
Retry a pending source update through the existing reviewed update path,
so a rolled-back native failure cannot clear progress at the old snapshot.
Record default-source versions for add, sync, and update while retaining
the recipe fingerprint and generic-version checks for target overrides.
Keep explicit native adoption, but block shared Claude sources when an
independent same-name native plugin could shadow their hooks. Extract the
existing adoption decision so the preview function becomes smaller.
* test(plugin): respect OMP update safety in version control
Check generic and target versions during review, then confirm the existing
OMP upgrade guard preserves the installed and default-source versions.
* fix(plugin): declare first local native imports explicitly
A first local import into a shared source target now changes that target
to native-only intent while preserving its sync selection. Verified source
reimports retain their reviewed source and the preview discloses conversion.
Cover the explicit import, local sync, and other-host cleanup flow, and
remove the unconsumed internal observation assertion from the OMP test.
* docs(plugin): explain first local import intent changes
Describe the shared native-only target conversion and its effect on other
machines, while distinguishing verified source reimports.
* fix(plugin): verify checked sources before native reinstalls
A checked update that becomes an install after native removal must still
match the source digest the user approved. Reject moved or unchecked
sources before native work, and allow a stable approved reinstall.
Clear completed reinstalls from dashboard update availability while keeping
failed targets available for retry. Cover both native presence states in
the existing checked-update tests and the dashboard outcome rule.
* fix(plugin): guard replacement before cleanup
* fix(plugin): refresh discovery for each manager action
A later Add action must review the current source even when the manager
previously observed that source. Keep discovery sharing across one action
while ending its cache before the next wizard invocation.
Exercise a fresh source version after an earlier Add preview without TTY
input or native writes, using an unavailable client to stop at review.
* test(plugin): cover desired checks and final update outcomes
Consolidate checked batch approval and dashboard completion tests while
retaining removed-native, digest, version and approval controls. Reproduce
stale shared recipes and failed or unfinished replacement installs.
* test(plugin): make stale source discovery observable
Remove the old repository before native-only and npm desired checks so
those existing cases cannot pass by reading the applied source.
* fix(plugin): check desired source and final outcome
* test(plugin): bind checked updates to the observed recipe
Reproduce a shared candidate change with equal version, commit and digest,
and preserve a freshly checked replacement whose native ID differs. Use
actual check observations in approval and native update controls, reject
missing source identity, and verify the UI carries the observation through.
* fix(plugin): bind checked update to source recipe
* fix(ui): classify npm recipes as Pi packages
* fix(plugin): retain legacy removal intent during migration
Omit pending removals from shared declarations while retaining original local ownership proof so sync retries cleanup.
Verification: focused regression passed in an isolated Linux Codex container, not the devcontainer (GOMAXPROCS=4, -p=4).
* fix(plugin): keep imports local to an existing shared recipe
Adopt a native installation into its local receipt without converting the shared source target or removing other machines installations.
Verification: focused import regressions passed in an isolated Linux Codex container, not the devcontainer (GOMAXPROCS=4, -p=4).
* fix(plugin): capture legacy evidence on first read
Persist passive hints before another machine writes v2 and save verified adoption on reads. Apply reuses preview receipts instead of querying every legacy binding again. Document the per-machine pre-migration read.
Verification: migration regressions passed in isolated Linux Codex container runs, not the devcontainer (GOMAXPROCS=4, -p=4).
* fix(plugin): target named declarations in interactive imports
Offer unresolved package names in dashboard and TUI imports and pass the selected name in single and batch requests. Drop display-only rendered assertions.
Verification: 47 UI tests passed with at most four workers in an isolated Linux Codex container, not the devcontainer.
* fix(plugin): localize shared intent plan guidance
Add message keys for local imports, account changes, cleanup and native collisions across all dashboard locales. Localized guidance contains no CLI flags.
Verification: failing localization regression now passes in an isolated Linux Codex container, not the devcontainer (GOMAXPROCS=4, -p=4).
* refactor(plugin): reuse preview inventory and guard apply boundaries
Capture hints on first load without persisting in-memory adoption during preview, keeping approval revisions stable. Apply reuses preview inventory. Reuse accountEnv and guard applyChange plus native write boundaries without inspecting argv.
Verification: migration, receipt, account and sync regressions passed in an isolated Linux Codex container, not the devcontainer (GOMAXPROCS=4, -p=4).
* test(plugin): organize host state coverage around lifecycle scenarios
Group migration, ref drift, account context and cleanup tests behind shared host fixtures and public Preview/Apply assertions. Cover Codex, Cursor, Antigravity and project scopes; add second-machine doctor coverage and the two-machine runbook. Consolidate package-version tests and remove the unused private-record fixture.
Verification: focused plugin regressions passed in an isolated Linux Codex container, not the devcontainer (GOMAXPROCS=4, -p=4).
* docs(plugin): explain local imports and per-machine migration
Document local receipts, per-machine review and commit pinning, config-path state identity and the required legacy read on every machine. Align sharing, doctor, troubleshooting, file-layout and four translated plugin references; restore schema editing guidance.
Verification: context-router check passed. Runtime verification uses an isolated Linux Codex container, not the devcontainer.
* refactor(plugin): separate unrelated review scope
Move project OMP configuration, plugin list ordering, and npm Pi classification to independent local branches based on upstream/main. Keep the shared intent change focused and cover named import selection in the pure flow helper.
The three local branches have passing builds in a Linux Codex container, not the devcontainer, with isolated test homes and capped parallelism.
* perf(plugin): avoid recapturing v2 state on reads
Only compare and persist passive migration hints when legacy bindings exist. Native v2 reads need no state serialization for migration.
Verification: pending removal and first-read/import regressions passed in a Linux Codex container, not the devcontainer, with isolated HOME/XDG/TMPDIR and GOMAXPROCS=4 GOFLAGS=-p=4.
* docs(plugin): clarify native marketplace repair after import
A local import receipt is not a reviewed reinstall source. Correct the remaining troubleshooting instruction and its four translations to require native-client repair, and align the nearby code comment.
Validation: checked against prepareChange, context-router check and git diff --check passed. Verification for this review ran in a Linux Codex container, not the devcontainer.
* fix(plugins): preserve local ownership across shared intent changes
Retain completed legacy migration markers so unchanged v1 YAML cannot
uninstall a later manual reinstall. Serialize read-side hint persistence
with native operations and keep local imports when shared recipes change.
Require explicit dashboard import names and validate recipe identities.
Correct schema descriptions, messages, CLI ref status, translated migration
guidance and runbooks. Add failing-first Preview/Apply regressions and a
real two-ssenv CLI lifecycle script.
* fix(plugins): preserve migration history and show retained import guidance
Mark existing legacy hints and receipts as captured before cleanup so state
from the previous serializer cannot re-adopt a later manual installation.
Keep recipe-change guidance in unchanged sync outcomes and visible dashboard
rows, and resolve nested OpenCode entries through their package manifest.
Cover public migration, ref, account, import and message contracts across
adapters. Correct the real two-host Cursor assertions, explicit dashboard
selection flow, and remaining localized guidance.
* fix(plugins): retain explicit OpenCode entry during import matching
Standalone OpenCode packages can rely on a reviewed explicit entry rather
than an SDK dependency. Preserve that entry when reading native package
identity so matching nested imports remain supported.
* fix(plugins): preserve migrated imports and verify native entry identity
Recognize older native-only receipts by their existing declaration
fingerprint so remote source recipe edits cannot replace migrated imports.
Keep managed npm receipts distinct through their source fingerprints.
Only borrow an ancestor OpenCode package identity when its resolved entry
is the actual registered file. Retain nested and explicit entry support.
Add public two-host migration and mismatching-entry regressions.
* fix(plugins): retain imported ownership through repeated adds
Persist inferred imported ownership when a matching add refreshes the
receipt intent, so later shared recipe changes still preserve local
native installations. Keep the legacy replacement regression aligned
with that ownership contract while retaining removed-intent cleanup.
Reject missing or unstatable absolute OpenCode entries before identity
matching rather than falling back to the file name. Cover both paths
through public Preview and Apply regressions.
* test(plugins): isolate OpenCode adapter fixtures from host config
Keep native registration fixtures inside their fake agent home by setting
XDG_CONFIG_HOME and clearing inherited OpenCode overrides. Ambient config
writes can otherwise leak into config-discovery tests in other packages.
Cover the XDG, file, directory and inline override cases with temporary
config sentinels, while retaining the existing MCP listing expectation.
* fix(plugin): let local imports return to the shared source
Add a local unimport action that removes only this machine’s installation and receipt while preserving the shared source declaration. Keep retained-import guidance visible across matching adds, list, doctor and dashboard consumers.
Avoid idle OMP guidance and unchanged legacy-read locks, preserve localized errors, keep import identity checks offline, and normalize OpenCode drive URLs. Cover the A/B transition and align translations, runbooks and environment cleanup.
* fix(plugin): complete unimport validation and guidance
Reject missing targets before planning local unimports and share per-target eligibility with the wizard. Make native uninstall effects explicit in help and translated docs, preserve structured update guidance, and cover error paths and shell completion.
walkEntries replaced its root with the resolved path before calling
Walk and WalkDir, so the follow tests never exercised Walk's own root
resolution on aliased temp dirs such as macOS /var. Resolve only the
base used for relative labels.
Windows temporary paths can use a spelling that differs from the path returned by filepath.EvalSymlinks. Canonicalize test roots before relativizing callback paths and restore internal/sourcewalk to the windows-test allow-list.
The result rows centered the icon against a multi-line body, so it
floated mid-row. Top-align it like the selection list and keep the
status and retry button centered.
The built-in skill said that omitting --source-ref on update does not
unpin a package, but not how to unpin one. It also did not say that a
remote source is read only at its repository root, so agents facing a
plugin kept in a subdirectory fell back to cloning a release tag and
stayed pinned.
Document that updating with --source-ref BRANCH stores the branch and
follows its latest commit, and that a subdirectory plugin with no root
marketplace is added from a local clone of the default branch, pulled
before check or update.
The agy CLI keeps its MCP servers in the file the antigravity client
writes, and plugins and hooks already call it antigravity-cli, but
mcp --target and --from rejected that name. Map agy and
antigravity-cli to antigravity when the flags are parsed, so the
source still stores one client name.
Document the aliases in the MCP command reference, its four
translations and the built-in skill reference.
Closes#669
* chore(main): release 0.28.0
* chore(release): synchronize release metadata
* docs(changelog): rewrite 0.28.0 entry for users
The generated entry listed raw commit subjects, including a docs commit
and an internal skill fix that users never see. Describe each feature
and fix by its visible behavior, with examples and credits, and keep
the website copy in sync.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The pending release ships agent-specific skill variants and plugin
update --all, so it is a minor release rather than the 0.27.1 that an
earlier footer requested. Refresh the Latest callouts in every README,
and translate the checkout update serialization note from #666, which
only landed in the English update page.
Release-As: 0.28.0
Tracked repos are shallow blob:none partial clones, so they lack the
blobs of intermediate commits. Since git 2.45.1, a local upload-pack
refuses to lazy-fetch missing objects, so both the candidate clone and
the publish fetch back into the checkout failed with "fetch-pack:
invalid index-pack output" once more than one upstream commit arrived.
Re-enable lazy fetching only for these two local transports, whose
source is our own checkout, and pass origin's auth env so private
repos can supply the blobs. Fetched blobs are hash-addressed, so the
published tree still matches the audited revision.
Closes#667
Pick up the upstream fix to Markdown link parsing: link reference
definitions now require a bare destination, and quotes that contain
nested lists are measured against the list opened inside them. The
existing docs pass check unchanged.
The testing topic was 8 bytes under its 16 KB cap, so any edit would
fail the router check. Move the E2E runbook, quality checklist and
Windows verification sections verbatim into a new e2e-runbooks topic
instead of raising the cap.
Also upgrade scripts/ai-context.py to 0.2.0, which adds link checking,
skipDirs and glob-based unrouted exceptions; the existing docs pass.
* docs(proposals): propose agent-specific skill variants
Tracked repositories can ship different files for the same skill across
agents. Counting and syncing each copy independently sends incompatible
instructions to every target unless users maintain routing filters.
Propose repository-scoped logical identity and exact variant routing while
preserving source files, explicit controls, and existing naming behavior.
Leave activation and compatibility decisions for maintainer review.
Refs #648
* docs(proposals): clarify variant routing compatibility
Explain how recognition affects universal-only targets and how existing
per-variant overrides preserve the desired routing. Fix the precedence
between variant identity and generic host-style path inference.
Include analyze, move, and catalog consumers while preserving physical
identifiers and actual context-cost accounting.
Refs #648
* docs(proposals): clarify activation assumptions and scope
Make acceptance cases conditional on maintainer-approved recognition being
enabled for the tracked source. Separate the provisional implementation
estimate from this proposal-only PR so its size is clear.
Refs #648
* docs(proposals): qualify naming and opt-in assumptions
State that the reproduced routing behavior uses default flat target
naming. Leave any opt-in surface with the maintainer's activation decision
without ruling out future CLI or config fields.
Refs #648
* feat: recognize and route tracked agent skill variants
Count tracked variants as logical skills in source and repository summaries,
while preserving physical paths, sync operations, and context costs. Select
matching canonical agent variants, including account targets, through shared
discovery and selection with existing explicit routing precedence.
Refs #648
* fix: count logical skills in sync inventory summaries
Use shared logical and physical inventory counts in global and project sync
closing lines while preserving each target's operation totals.
Refs #648
* fix: preserve variant routing diagnostics across previews
Resolve target selections once so CLI and server previews keep ambiguity
reasons and physical skip counts. Explain managed variants removed by
automatic agent routing, and report logical inventory in doctor.
Keep warning rows read-only, document upgrade recovery in translated
filtering references, and remove the optional README-only addition.
Refs #648
* fix: align sync matrix previews with shared variant selection
Classify the full source selection once per target so matrix previews honor
canonical aliases, account identity, exact-agent routing, and ambiguous
variant skips. Preserve each rejected physical path's existing diagnostic
and draft filter disambiguation; skipped preview rows remain read-only.
Refs #648
* test: expect singular skill wording in doctor source checks
Keep the undiscovered-link count assertion aligned with logical source
inventory formatting for one skill in global and project mode.
Refs #648
* fix: retain selection diagnostics in catalog and diff verdicts
Report warning-only diff targets as requiring attention while preserving
local-only folder semantics. Reuse shared per-path selection diagnostics
in target-scoped catalogs without applying target naming to served paths.
Compute source counts once in summary callers and require variant counts
in the source status formatter.
Refs #648
* test: tighten tracked variant preview fixtures
Use a real committed tracked repository for status counts, verify sync
preview banners retain server warnings, and use emitted ambiguity reason
text in target preview fixtures.
Refs #648
* fix(sync): keep agent variants in shared target folders
Compatible targets sharing a skills folder need a combined selection so
Codex and universal do not prune one another in merge or copy mode.
Carry every shared reader through selection, pruning and previews,
including project targets, account identities and path aliases.
Require a matching skill suffix under two distinct agents before
inferring variants, keeping ordinary agent-named categories unrestricted.
Separate naming warnings from ambiguous selection in diff and explain
ambiguous removals. Add global/project regression coverage for repeated
sync, target-only sync, status JSON, diff and API consumers.
* fix(variants): align consumer counts, hints and diagnostics
Use logical source counts in list, tracked install and init summaries while matching audit caches against physical variants. Restore localized dashboard skip hints and explain symlink routing limits in status and doctor, including project and JSON output.
Document paired-agent detection and compatible shared-folder selection in the proposal, built-in skill and English plus translated command pages. Add focused regressions for the affected consumers.
* fix(sync): cover initial sync and ignored variant diagnostics
Init syncs a fresh in-memory config, so resolve shared target identities
before its first sync as well as when loading saved configuration.
A whole-directory symlink exposes ignored skills too. Diagnose agent
variants using physical inventory when active discovery has none, while
keeping logical counts and merge/copy selection restricted to enabled
skills. Cover global/project JSON status and doctor with regressions.
Reuse sourcewalk directory and canonical-path helpers so traversal guards
remain enforced and path resolution has a single existing owner.
* fix(variants): address conversion, counts and selection diagnostics
Ignore runtime agent identities when comparing convertible project targets and count logical skills during init. Keep selection warnings separate from naming warnings and preserve agent-named parent skills as ordinary skills.
Cover account sync/prune, project ambiguity and overrides in merge/copy modes, and init/status agreement. Focused verification ran in an isolated Linux Codex container, not the devcontainer, as authorized.
* refactor(variants): remove obsolete selection helpers
Remove the unused FilterSkillsByTarget wrapper and prune agent parameter, cache canonical target aliases once, and restore catalog skip ordering to avoid an unrelated behavior change. Completes the optional cleanup from PR 649 review.
* fix(ui): expose localized variant selection diagnostics
Show target warnings with source paths, localize ambiguity across preview and detail consumers, and let skipped preview rows add a physical exclude pattern. Show tracked repository variant counts alongside logical skills.
Drop display-only rendered cases while retaining mutation protection and plain TypeScript logic coverage. Inspect target states in Clean/Playful light/dark and Traditional Chinese.
* docs(variants): explain diagnostics and add sync runbook
Document doctor variant_routing and logical/physical counts, diff selection skips, and the nested parent-skill boundary. Keep all four command translations aligned and add isolated account/project E2E scenarios.
Both runbook steps passed in the authorized Linux Codex container with separate HOME/XDG/TMPDIR fixtures. Website typecheck and all five locale builds passed.
* test(config): use native paths in project conversion fixture
The shared-agent regression fixture appended slash-separated suffixes to Windows temporary paths, so project path matching returned no candidates. Build each path with filepath.Join and preserve all conversion assertions.
Focused project configuration tests passed in the authorized isolated Linux Codex container, not the devcontainer. Windows CI verifies the platform-specific fixture correction.
* fix(ui): recompute shared skill routing for filter previews
Evaluate edited include/exclude settings in the complete target map before
classifying the draft, so a formerly shared folder no longer keeps its old
union when the filters differ. Preserve the saved target configuration.
* fix(mcp): keep parent skills when peer variants route elsewhere
Do not treat an otherwise eligible variant for another agent as an unserved
nested skill. Continue blocking parent publication for explicitly filtered,
disabled, ambiguous, or invalid children so filters still hide their files.
* fix(ui): distinguish agent selection from naming skips
Expose separate naming and selection skip counts on target summaries.
Show each applicable remedy in target details and sync previews so ambiguity
keeps its filter/override guidance alongside naming and collision hints.
* fix(list): include disabled rows in tracked repository counts
Count the complete inventory that list displays, including ignored skills
and physical variants, without changing the enabled counts used by status,
install, or sync. Clone rows before counting to preserve disabled state.
* docs: align variant counts and routing recovery guidance
Show logical skill and physical variant counts in list/install documentation
and keep the four translations aligned with the filtering examples. Explain
that agent-named skill parents keep ordinary nested skills and retain the
devcontainer-only runbook environment. Removal warnings now recommend a
source-local override, since include filters cannot undo agent routing.
* fix(mcp): preserve explicit target restrictions on nested variants
Limit the differently routed child exemption to automatic layout inference.
Frontmatter targets and dashboard source-local overrides must still prevent
a parent from publishing files explicitly restricted to another target.
* fix(ui): fill target name in naming warning guidance
Pass the current target name when rendering localized warning hints so the
same naming guidance shown beside the controls does not expose a placeholder
in the warning banner. Verified in the populated target preview.
---------
Co-authored-by: Willie <egg358358@gmail.com>
Two dashboards (or a dashboard and the CLI) serving the same source ran
"Update all" at once. The server mutex only covers one process, so both
pulled into the same checkouts: one saw the other's half-applied merge as
"local changes would be overwritten", and concurrent fetches into a
blob:none clone failed with "fetch-pack: invalid index-pack output".
update.TrackedRepo, install --track --update, and the in-place pull of a
git-installed skill now hold a flock in the checkout's git directory; a
second process waits up to a minute, then fails with a clear message.
Force on a git-installed skill only skipped the local-modification check
and then ran a plain pull, which refused to merge over the edits the docs
say --force discards. It now fetches and resets to upstream, so a failed
fetch still keeps the edits. Followed checkouts keep pulling, since they
must be clean and may hold the user's unpushed commits.
The pull error dropped the file list git indents under it, and the
finished-update subtitle said everything was up to date even when items
had failed.
Shared configs can register roots that exist on other machines. Replace the per-root warning flood with one count and a hint to project list, which already exposes each missing folder in text and JSON. Keep root skipping and sync JSON unchanged.
* fix(config): honor OMP skills directory overrides
OMP reads global skills below PI_CODING_AGENT_DIR, but unpinned built-in
targets still selected the default home. Resolve that runtime default
without changing the canonical template used to derive named accounts.
Keep account scan paths independent of the override and document explicit
path precedence in target guidance and its existing translations.
* fix(config): preserve inferred OMP paths across saves
Saving an unpinned OMP target serialized its resolved skills path, so a
later agent-directory override no longer selected the native location.
Track this fallback with the existing derived-path marker so config saves
preserve its inferred status while explicit paths remain pinned.
Cover save/reload after environment changes and filter edits, and fold
redundant account and project-alias checks into their existing cases.
* docs(config): clarify when OMP skills paths stay fixed
Initialization and target addition save their selected destination, while
an OMP entry with no configured skills path follows later environment
changes. Clarify that distinction in public and built-in target guidance
and all four existing translations.
Keep project alias coverage in its existing owner test and remove
redundant OMP matcher and generic save assertions.
* test(config): normalize explicit OMP account paths
The explicit-path fixture combines a native temporary root with a forward
slash suffix. Clean the actual path for comparison so mixed separators
match the native expected path on Windows, retaining the original path
in failure output.
* test(config): use portable OMP whitespace override fixture
Windows normalizes a directory component ending in a space during native
absolute-path resolution. Use a leading-space component to preserve the
check that override values are not trimmed without depending on trailing
space filename behavior.
* fix(config): preserve default OMP home in account shells
Keep plain OMP skills on the canonical home when its environment override
matches a declared account, so the unfiltered default target cannot bypass
account filters. Share account-aware defaults with discovery and dashboard
selection, and keep canonical account templates separate from runtime homes.
Require an OMP install before automatic detection because Pi shares the same
override. Trim surrounding whitespace, ignore relative overrides, and retain
explicit saved paths. Cover account filtering, aliases, symlinks, saves,
discovery, and existing environment-selected file homes with regressions.
Feature PRs have arrived with a self-ticked "maintainer approved" box on
issues the maintainer never answered, and with large AI-generated diffs
the author could not stand behind. Make approval a label only the
maintainer can add, and state what an AI-assisted contribution owes
reviewers: an author who has read the diff, answers reviews personally,
does not split changes to dodge the size guideline, and makes only
checkable claims.
The Scope line and the end of Step 5 described fix mode differently:
one applied "verified" findings (which can include PLAUSIBLE) and ran the
testing topic's checks, the other applied only CONFIRMED findings and ran
the narrowest check. Keep the rule in Step 5 and point Scope at it so the
reviewer has one rule to follow.
A pathless deepseek-harness or gitlab-duo target resolves its skills
path from DSH_HOME, GLAB_CONFIG_DIR, or XDG_CONFIG_HOME, and the docs
promise it keeps following those overrides. decodeConfig filled the
omitted path in, though, and the next save (editing filters, changing
mode) wrote it back as an explicit path, so later environment changes
were ignored.
Mark a default that came from targetConfigHome as derived, reusing the
mechanism that already keeps config_dir paths out of the saved file.
Closes#661
Release-As: 0.27.1
* Add --all flag to plugin update and enable agy
Add -a/--all to skillshare plugin update so users can update all
tracked plugins in a single command without tying slow target CLI runs
to skillshare update --all or sync --all.
- Reject --all outside plugin update or when combined with a plugin
name or --source-ref
- Share source repository discoveries and discovery errors across the
Preview and Apply lifecycle via Service.WithDiscoveryCache so multi-
plugin marketplaces are cloned at most once per command
- Isolate source, manifest, and target failures per binding when --all
is active so healthy plugins update while partial failures exit
non-zero and leave failed bindings unchanged in config.yaml
- Skip unfiltered OMP bindings during --all updates so sibling targets
on the same package still update without failing the batch
- Enable plugin update for antigravity-cli while skipping disabled
plugins when agy extensions list reports an entry as disabled
Closes#653
* Add plugin update --all to docs and completions
Advertise -a/--all for skillshare plugin across all five shell
completion scripts and document the bulk update workflow and
antigravity-cli update support in the user and built-in skill docs.
- Add --all and -a to plugin completions in bash, zsh, fish,
PowerShell, and Nushell with TestPluginCompletionsIncludeAllFlag
- Document update [NAME | --all], -a/--all, and antigravity-cli source
updates in website/docs/reference/commands/plugin.md (and its
zh-Hans, zh-Hant, ja, and ko translations), sharing-plugins.md, and
quick-reference.md
- Document plugin update --all and antigravity-cli enablement checks in
skills/skillshare/references/plugins.md
* Require known enabled state for native updates
Require a matching EnabledKnown && Enabled inventory entry before
updating copilot or antigravity-cli bindings, and align the localized
plugin workflow pages with the English docs.
- Skip copilot and antigravity-cli updates in Service.Preview and
refuse reinstallation in applyNativeTarget when the binding is absent
from native inventory or not known to be enabled
- Cover absent native inventory in
TestAntigravityCLIUpdateRespectsEnablement
- Synchronize plugin update [name | --all] and Antigravity CLI update
guidance across the ja, ko, zh-Hans, and zh-Hant copies of
quick-reference.md and sharing-plugins.md
The desktop app shows this web UI in a cross-origin iframe and cannot read
its location. After an auto-sync reload it can only return to a route it
knows, so the user lands on the dashboard (runkids/skillshare-app#88).
When embedded, post { type: 'route-change', path } to the parent on every
router location change, where path is pathname + search relative to the
router basename. Standalone pages post nothing.
Use the target data already loaded by the dashboard so account logos do not depend on the slower all-targets request. Keep the all-targets mapping for additional targets.