A managed project's name may hold spaces, so the Skillshare tab built
`--target my app@claude`, which the save path split into two words and
serve rejected as an unknown target. The command is now joined from
quoted words.
The Agent Skills format caps a description at 1,024 characters, and
hosts validating entries reject longer ones, so serve skips such a skill
with a warning instead of advertising it. The docs list every skip reason.
A root under mcp.projects is served from the global config, where its
project targets (app@claude) live, so the Skillshare tab now offers that
project's targets beside the global ones and saves no -p, which would
fail in a folder with no .skillshare/.
A nested skill skipped for any reason, not only one left unselected, now
skips its parents too: they were settled before the child was validated
and published its files as their own.
Also from review: a skill whose frontmatter JSON cannot carry (a
non-string key) is skipped instead of failing the whole skills/list page;
a listed file with a backslash in its name can be read; and stdio serve
exits 0 on SIGINT/SIGTERM without writing to stdout after the session.
Serving skills over MCP is meant for people who do not want to type the
command, so Add server gets a Skillshare tab next to the fields and the paste
tabs. It asks only for a name, which skills (all enabled ones, or one skills
target's selection) and the Agents, and shows the command it will run. It
marks the Agents that already get skills by sync, including through another
target's folder such as ~/.agents/skills, and warns when one is ticked,
because that Agent would see each skill twice.
Editing a server that runs skillshare mcp serve opens the same tab, in the
global page and under mcp.projects. The tab is named after Skillshare rather
than skills so it can hold more of what skillshare serves later.
Reject unsupported client registration values and CIMD client or callback conflicts before syncing invalid settings to Pi. Keep dcr and custom Pi options supported, identify the legacy codemode alias, and document current Pi launch behavior.
Update checks compare the source digest, not the version, so a repo that
pushes commits without bumping its manifest (ponytail ships dozens a day)
showed "4.12.0" with an Update button and looked like a stuck update.
Check now returns the source commit, and the version tag adds
"old → new" commits when the version itself did not move.
Standalone source links were added to every grouping regardless of the
active search or filters, so a query that matched nothing rendered the
links as zero-skill groups instead of the no-match state with its Clear
filters action. Links have no skills to match, so they are shown only
while no filter is active.
A loading Button inserted its spinner in front of the children, so buttons
with a leading icon (such as Check for updates) showed the spinner beside
the icon instead of in its place. Hiding the svg that directly follows the
spinner fixes every such button at once.
Source links disappeared from the dashboard when discovery found no skills, leaving empty or unavailable folders without an Unlink action. Return first-level links independently with their follow-policy availability and preserve their groups in every skills view, including empty unlink confirmations.
Cover empty and dangling inventory, disabled following, and empty-link removal in list, cards, and tree views; document the API field and rendering.
* feat(omp): add native Oh My Pi support
Support OMP skills, instructions, MCP, code hooks and guarded extension selection using its verified native contracts rather than Pi aliases.
Add reviewed marketplace plugin installation, cache-preserving scoped removal and fresh-cache reinstall. Align Pi/OMP extension cards and localize inventory guidance while keeping native ownership and read-only constraints.
Include regression coverage, isolated E2E runbooks, documentation and verification policies. Native plugin updates and unverified runtime platforms remain guarded.
Refs #409
* fix(omp): guard runtime ownership and localize inventory guidance
Native install recursively replaces its runtime destination, and a missing cache manifest could leave the real runtime link installed after removal. Bind and recheck an absent reviewed destination, and recover removal names only from verified scope-local links.
Localize fixed backend reasons and warnings across dashboard locales while preserving paths and external diagnostics. Restore the reviewed source in the existing reinstall fixture and record real native verification.
* fix(omp): allow forgetting natively removed plugins
A different plugin can retain node_modules after native uninstall deletes this installation. When its cache, registration and known runtime state are absent, forget only the stale Skillshare binding instead of demanding runtime-name proof for unrelated files.
Extend the existing removal recovery test with a failing-before-fix case that verifies the binding is dropped and unrelated native lock bytes and plugin files are preserved. make check passes.
Share policy-based link identity enrichment between skill list and detail responses. Use that identity in the detail action menu and shared uninstall dialog so followed checkout members keep single-skill confirmation and submit their own flat name.
The link icon and the muted target path already say that a group is a
followed link, so the extra `linked` tag only repeated the same fact on
the row. Remove it from the list and card headers, the tree row and the
detail pane, and delete the now unused locale key.
The unlink icon at rest read as a broken link, not as the linked folder
it marks. Show the link icon and swap to the unlink icon in the danger
color only on hover or keyboard focus, so the row says what it is and
the action appears where the pointer is.
Keep followed checkout updates in the Updates tab and expose unlink as a single quiet icon in group headers. Remove unused checkout metadata and linked-group menus while preserving the confirmation and single-skill uninstall flows.
Match tracked repository affordances without offering whole-repo uninstall for followed user checkouts. Resolve checkout identity for Update repo, keep linked skill uninstall scoped to the selected skill, and explain target preservation, sync impact, and trash recovery before destructive requests.
Expose policy-resolved first-level link identity on listed skills so linked groups can be distinguished from ordinary folders without another request. Add a confirmation that preserves the target folder and explains trash recovery, then refresh the dashboard after unlinking.
Let dashboard users add local skill folders through the shared source-link guards without creating links by hand. Keep follow_source_links opt-in in the current mode and expose link removal through the API with recoverable trash semantics.
Cover handler behavior, request shapes, dialog errors, and all dashboard locales, and document the endpoints in the API audit topic.
Separate user-owned followed Git checkouts into linked_repos in check and resources responses so the Updates tab renders information instead of tracked errors or retry actions. Refuse dashboard updates before Git runs, including force retries and descendant skills, while leaving managed repositories unchanged.
Keep one follow policy per list and status operation and report its skipped links without hiding healthy inventory. Send JSON diagnostics to stderr and expose sourceLinkWarnings in the dashboard resources response, reusing the sync warning formatter.
The sticky band stacked the title and the filters on two rows and padded
both ends by 24px, which left a large empty strip above and below the
filters. Merging them into one row removes the gap.
Refresh reloads every memory query (the note list and note contents), not
just the sidebar, so it belongs with the page-level actions next to
"New note". Next to the search box it crowded the sidebar and pushed past
the note tree's edge.
The Syncing column described what a target gets as one line of text,
and the whole row led to the Skills tab, so reaching a target's MCP,
Hooks or instruction file took an extra click and a search for the
tab. Each part is now its own link into that tab, and the connected
shared AGENTS.md shows up by its file name, so the list says at a
glance which targets are not connected yet.
* feat(memory): add a refresh button and keep short facts in INDEX.md
Agents write shared memory notes from outside the dashboard, so the note
list and content went stale until the page was reloaded. A refresh button
in the note header refetches both.
The active guidance also told agents to create a separate file for every
durable fact, which produced one-sentence files. Short facts now go
directly under Notes in INDEX.md; only multi-paragraph notes get a file.
* fix(ui): keep the memory refresh button available without a selected note
The button lived in the note header, so a search with no matches hid it
and the list could not be refreshed to pick up a note an agent had just
written. It now sits next to the search box.
The pending-changes bar was a full-width sticky box, unlike the floating
toolbar used for bulk selection elsewhere in the dashboard. Reusing
.ss-bulk keeps both bars consistent across Clean, Playful, and dark themes.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
* fix(plugin): find the Codex CLI the desktop app ships
Plugin commands ran the bare name `codex` from PATH, so a machine with only
the Codex desktop app, or a scheduled job started with a minimal PATH,
reported the CLI as missing. The account-only `cli` override did not help:
the default codex target cannot set it, and an absolute path in a config
shared between macOS and Windows is wrong on one of them.
When `codex` is not on PATH, look in Homebrew's folders and the CLI the app
installs (Codex.app on macOS, %LOCALAPPDATA%\OpenAI\Codex\bin on Windows).
SKILLSHARE_CODEX_CLI overrides the search on one machine without touching
the synced config. The missing-CLI error now lists every place searched, in
the CLI and the dashboard.
Refs #338
* docs(plugin): note where Skillshare finds the Codex CLI
The plugin reference and the sharing guide still said every native CLI must
be on PATH, and the built-in skill told agents a missing CLI has no
fallback. Codex now has one, plus a machine-local override that agents
should prefer over a path in a shared config.
Refs #338
* fix(plugin): look for the Codex CLI inside ChatGPT.app
Since the Codex desktop app merged with ChatGPT, macOS installs it as
ChatGPT.app, so an app-only Mac with a minimal PATH still reported Codex as
missing. Try ChatGPT.app before Codex.app in /Applications and
~/Applications, the order Codex's own desktop-app finder uses.
Refs #338
* fix(plugin): run the packaged CLI entrypoint of the ChatGPT app
ChatGPT Desktop 26.924 removed Contents/Resources/codex and ships the CLI
at the entrypoint its package manifest declares, codex-cli/bin/codex, so a
current app-only Mac still reported Codex as missing. Try that entrypoint
first in each app bundle and keep the old path for earlier builds.
Refs #338
* fix(plugin): find the Codex CLI from the Windows installer
The official PowerShell installer puts codex.exe in
%LOCALAPPDATA%\Programs\OpenAI\Codex\bin and adds it to the user PATH. A job
started without that PATH missed it, the same gap Homebrew's folders cover
on macOS. Try it before the desktop app's copy.
Refs #338
* fix(plugin): keep an account's cli even when it is codex
The Codex search ran whenever the executable was the bare name codex, so an
account that set cli: codex could get SKILLSHARE_CODEX_CLI or the app's CLI
instead, against the documented rule that an account's own cli is kept.
Search only when no account cli is set.
Refs #338
The generated guidance block defined "what is worth saving" the same way
agents' built-in memory does, but never said how the two relate, so agents
with their own memory kept saving there and left the shared folder alone.
The active rule now says to save here instead of tool-specific memory,
gives a note format and an INDEX.md line shape, and both modes read
INDEX.md at the start of each task instead of "when relevant". The
passive rule asks agents to point out facts worth keeping so the user
can ask for them to be saved.
Dashboard mode descriptions, the CLI help, and the website pages are
updated to match. Test fixtures that anchored on "Read only" follow the
new wording.
Narrowing the side columns made the English Field/Structure/Changes tabs
overflow the 240px panel. Split the tabs evenly with tighter padding,
trim the file list further and give the expanded dialog's panel more
room.
The file list and field panel took more width than they needed and left
the YAML editor cramped. Narrow both side columns so the editor gets the
extra space.
* fix(mcp): turn off a global server for Pi with its project override
Since Pi 1.0.1, a .pi/mcp.json entry without command, url or type
overrides only enabled, exposure and toolExposure of the global server
with that name, and Pi's own /mcp writes {"enabled": false} for it.
Skillshare still wrote the global server's command (or url without the
query) next to enabled: false. Pi reads that entry as a project server
that replaces the global one, so turning it back on in Pi's /mcp only
dropped enabled and started the server without its args, env or
headers, and a url server lost its query. It also needed the global
server, so project mode refused pi in a disabled entry.
The switch is now the override alone. It needs nothing from the global
server, so project mode accepts it; a switch written by an earlier
release is rewritten on the next sync, and an identical override Pi
already wrote is unchanged instead of a conflict. The dashboard counts
Pi as an Agent with a per-project switch. Pi before 1.0.1 reports the
override as invalid, as the docs now say.
Closes#378
* fix(mcp): compare the whole Pi override before calling it the switch
Codex review on #379: an unmanaged .pi/mcp.json override such as
{"enabled": false, "exposure": "direct"} has the same ownership hash as
the switch sync writes, because that hash leaves out Pi-only fields like
exposure and toolExposure. Sync then reported it as unchanged, although
it differs from the switch and the docs promise a conflict. The check
now compares the whole entry, so only an exact {"enabled": false} is
unchanged; Pi fields a person adds to a switch this config already owns
are still kept, as for any managed Pi entry.
* docs(mcp): say which Pi overrides of a switch conflict
Codex review on #379 read "the override differs from the disabled
entry" as covering a switch sync already owns, where Pi settings added
in Pi, such as exposure, are kept: managed Pi entries keep Pi-only
fields by design (withAgentFields, piOwnedFields), and exposure does
nothing while the server is off. Turning the server back on in Pi
changes enabled, which the ownership hash covers, so that is a conflict.
The docs now say so: an exact {"enabled": false} is no conflict, Pi
settings added to an owned switch are kept, re-enabling in Pi
conflicts, and a differing override sync did not write conflicts.
TestPiSwitchOwnedBySync pins both owned-switch cases.
* feat(memory): let each agent choose passive or active note updates
Shared memory guidance only told agents to update notes when asked, so
anything worth keeping was lost unless the user remembered to request it.
Some users want agents to maintain the notes themselves, but because the
notes are shared across every tool, blind writes would fill them with
noise.
Add an active mode whose guidance limits saves to facts that will matter
in later sessions, asks the agent to propose a note when unsure, to update
an existing note instead of duplicating it, and to report what it saved.
Passive stays the default and its block is byte-for-byte unchanged, so
existing connections remain configured.
The mode is recorded in each block's marker, so agents can differ. Agents
that read the same file share one block; the dashboard switches them
together and the API rejects conflicting modes for one file. The CLI
prints either block with `extras memory instructions --update-mode`
(`--mode` already means an extra's sync mode).
* feat(memory): review guidance changes as a unified diff
The side-by-side Before/After panes made users scan two windows to find
the one block that changed. A single Git-style diff shows only the
removed and added lines in context, with removals listed first.
* fix(memory): flag targets that read guidance in both update modes
A tool that imports several shared instruction files can read a passive
block in one and an active block in another. The status showed only the
best-ranked block, so the target looked configured in one mode while the
agent still received the other, and switching modes rewrote just one
file. Report such a target as needing attention instead, so the user
sets the tools on those files to one mode.
* fix(memory): refuse mode switches that would split a target's guidance
A target can read intact blocks in more than one file, such as its own
file and an imported shared file. Switching its mode rewrote only the
file the status pointed at, leaving the other block in the old mode and
creating the contradiction the mixed_modes state reports. Skip such a
switch as multiple_blocks so the user removes the extra block first.
Document guidance modes, mixed_modes and multiple_blocks in the
architecture topic, which still described a single implicit mode.
The dashboard listed every resource type except hooks, so a source with
hooks looked as if it had none. Hooks now sit between MCP and Plugins,
matching the sidebar, in both the global and project dashboards.
The Extensions tab lists the packages Plugins syncs to Pi, but a sync
refreshed only the plugin list and config. With a two-minute stale time,
a package removed from Pi stayed listed on the tab until the cache aged out.
Turning on a file that only a "-path" rule kept off wrote "+path", so the
row ended with a rule pinning it on and a separate Remove rule button that
did nearly the same thing. When removing the row's own rule gives the state
the switch wants, the view now says so (unruled) and the switch removes the
rule. Remove rule stays only where the rule is redundant. The prediction
uses the same rule edit, evaluation and guard as the write, so the preview
and the result agree.
Extension cells had a 300px minimum, so a wide page packed six to a row.
At that width the rule and status line wrapped over several lines in
Chinese, splitting words such as 待處理 across lines. A 440px minimum
keeps the line on one row and still fits several cells per row.
* feat(ui): accept a pasted npx skills add command in the install dialog
Skill pages commonly publish an install line such as
`npx skills@latest add owner/repo --skill=name`. Pasting it into the
source field used to send the whole command to discovery, which failed.
The field now reduces such a command to its source, and discovery of that
source preselects only the skills named with --skill. Flags that choose
install locations (-g, -a, -y, --all, --copy) are dropped because targets
decide those in skillshare.
* fix(ui): read owner/repo@skill and match skill names case-insensitively
Two gaps against how upstream npx skills reads the same command:
- `npx skills add owner/repo@skill` (the form find-skills emits) kept
`repo@skill` as the repository name, so discovery tried to clone a repo
that does not exist. The shorthand is now split into source and skill.
- A --skill value differing from the discovered name only by letter case
matched nothing, and the dialog fell back to selecting every uninstalled
skill. Names are now compared case-insensitively, as upstream does.
* refactor(ui): move pasted-command preselection rules into one function
What a pasted --skill means for the default selection was split between
the parser and InstallDialog: the source check and the fallback when
nothing matched lived in the component, and both sides relied on an
empty skills list meaning "no pick". requestedSkills now owns all of it
and returns null for "keep the default", so those branches are covered
by unit tests instead of only by a manual check in the browser.
* fix(ui): keep backslash-escaped spaces in a pasted skills add command
`npx skills add /tmp/my\ skill` works in a shell, but the tokenizer split
it into `/tmp/my\` and `skill`, so discovery got a path that does not
exist. Words are now read shell-style: quotes group, and a backslash
escapes whitespace, a quote or a backslash. Other backslashes stay as
written so a pasted Windows path such as C:\Users\me keeps its separators.
* fix(ui): skip option values and keep quoted Windows paths in pasted commands
Two more ways a valid npx skills add command reached discovery with the
wrong source:
- A --metadata value or --subagent names placed before the repository
were read as the source. Option values now follow upstream's
parseAddOptions: --metadata takes one value and --subagent, like
--agent, takes bare words up to the next flag.
- "C:\Users\me\my skill\" lost its trailing backslash because `\"` inside
quotes was read as an escaped quote. Backslash escapes now apply only
outside quotes; pasted skills commands do not quote quotes.
* fix(ui): keep @ in local paths of a pasted skills add command
`npx skills add ./repo@draft` was split as owner/repo@skill shorthand, so
discovery read ./repo and looked for a skill named draft. Upstream checks
for a local path before the shorthand; paths starting with . or ~ now
keep their @ (absolute and drive paths already did).
* fix(ui): preselect nothing when a pasted --skill is not found
When a pasted command named a skill that discovery did not list, the
dialog fell back to selecting every uninstalled skill, so one-skill
command could turn into a batch install. This is reachable because
discovery names a skill after its directory while upstream matches the
SKILL.md name. An explicit request with no match now preselects nothing
and leaves the choice to the list; upstream fails in the same case.
* fix(mcp): explain Pi project overrides in import and sync conflicts
Since Pi 1.0.1, /mcp in Pi writes a .pi/mcp.json entry with only
enabled, exposure or toolExposure to override the global server of that
name. Skillshare treated it as a broken server: import reported
"requires exactly one of command or url", and a project server with the
same name hit a conflict that told the user to import it, which import
always refused, so the user was left without a way forward in the CLI.
Import now names the entry as a Pi project override with nothing to
import. Sync reports the conflict as an override to replace or remove
with /mcp in Pi, and the dashboard offers only Replace for it. Sync
behavior is unchanged; detection matches Pi's own isOverride (no
command, url or type).
* fix(mcp): limit Pi override detection to project imports
Codex review on #371: importing Pi's global ~/.pi/agent/mcp.json, or a
pasted snippet, also reported a connection-less entry such as
{"enabled": false} as a project override and pointed to /mcp in a
project. Pi gives that shape override meaning only in a project's
.pi/mcp.json; elsewhere it is an invalid server. importNative now takes
the scope, so global and pasted imports keep the usual "requires exactly
one of command or url" problem.
* fix(mcp): classify a synced entry turned into a Pi override
Codex review on #371: when an entry this config synced to .pi/mcp.json
was later changed into a connection-less Pi override, the ledger still
marked it managed, so the generic "Agent configuration changed; import
it" conflict won and the dashboard offered an Import that project import
now refuses. The override case now comes first and covers a managed
entry whose content changed as well as an unmanaged one, so both offer
only Replace.
* fix(mcp): classify Pi overrides before every import-offering conflict
Codex review on #371: the prune conflict ("Pi setting changed since
sync; import it") still came before the override case, so a synced
server whose cleared Pi field Pi had replaced with an override again
offered an Import that project import refuses. Rather than chase each
earlier case, the override case now opens the switch. An entry owned by
another live config keeps its own message, since only that config can
release it.
* fix(mcp): treat a removed owner's entry like any other Pi override
Codex review on #371: an entry whose ledger owner was a removed config,
later turned into a connection-less Pi override, still got the orphaned
conflict, which offers an Import that project import refuses. Skillshare
never writes a connection-less Pi entry, so the override case now covers
every such entry except one a live config owns, which only that config
can release. It still skips an entry recorded at its current hash, which
is what Replace leaves, so Replace settles the conflict; a test now
covers that.
* feat(pi): edit extensions on any Pi at or above the verified minimum
Pi 1.0.1 was released and every user who updated found the Extensions
tab read-only, because the gate matched an exact list of versions. The
package contract has not changed between patch releases, so the gate now
accepts any plain X.Y.Z at or above PiMinVersion (0.99.2), the oldest
version with executed evidence. Older, prerelease or unparsable versions
stay read-only.
The version matrix now also records Pi 1.0.1, which passes every check.
The evidence test requires PiMinVersion to be recorded and every recorded
version to pass, instead of matching an exact list.
The read-only reason is renamed to unsupportedVersion and the API returns
minVersion, so the dashboard says which version is needed.
The Pi MCP project switch keeps writing the global command or url: from
1.0.1 Pi accepts a switch-only entry, but it is skipped by older Pi and
warns at every start where the global config lacks the server. Its
rationale in comments and docs is updated to say so.
* fix(docs): update Pi extensions design records for the minimum gate
Codex review on #367: the design records still described the exact
version list (PiVerifiedVersions, unverifiedVersion, "exact versions
only"), so a contributor relying on them would implement or validate the
old contract. implementation-report.md now states the current gate and
evidence, and phase-0.md gains a dated minimum-version update that the
older paragraphs point to, keeping the history intact.