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.
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
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.
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.
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.
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.
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.
* fix(plugin): trust symlinked ancestors of the Agent config root (#365)
noSymlink walked every ancestor up to / and refused the write if any was a
link, so macOS /var, a home on a linked volume, a dotfiles-linked ~/.pi, or a
PI_CODING_AGENT_DIR / CLAUDE_CONFIG_DIR / CODEX_HOME behind a link failed with
"refusing to modify symlinked native path".
noSymlink now takes the root the user chose (the Agent folder, the project,
or Skillshare's state dir) and checks only the path and the folders between
it and that root, refusing paths outside it. The root is compared lexically
because every checked path is built by joining onto it, so no EvalSymlinks
call is needed. A linked config file or a linked folder inside the root is
still refused, and Windows junctions are still detected via IsLinkMode.
* fix(plugin): bound the noSymlink ancestor walk by its relative depth
The walk stopped when p equalled root, but on Windows Dir spells a UNC
share root with a trailing separator (\\server\share\) while Clean keeps
the root without it, so the loop never ended for a PI_CODING_AGENT_DIR,
project root or StateDir on a share root. Walk up exactly as many levels
as the relative path has instead.
* 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.
* feat(pi): manage individual extensions per target
Keep package lifecycle in Plugins while letting global, account, and project Pi targets configure individual extensions with reviewed, lossless changes. Project overrides save only project settings and never grant trust.
Bind edits to native version contracts, settings snapshots, source ownership, and discovery; preserve unrelated resources and enforce renewable native locks, stale rejection, and backups. Verify Pi 0.99.2 and 1.0.0 without running extension factories.
Simplify configured-state UI and distinguish Skillshare-managed packages from native tool registrations, with localized guidance and regression coverage. Closes#342.
* fix(pi): address project extensions review findings
Keep exact project delta rules visible when their extension files are missing so users can remove stale rules without changing global settings or trust.
Show the project Extensions tab only when its generated Pi target resolves. Cover missing and agents-only projects, absent targets, and another project target with regression tests.
* fix(pi): recognize official Windows account launchers
Accept pi.cmd and pi.exe account launcher names on Windows, including case-insensitive and native Windows paths, before probing the existing exact-version gate. Preserve POSIX behavior and never probe unrecognized forks or stacked launcher suffixes.
Add platform-name and account-gate regressions covering verified, unsupported, and missing CLI versions. Focused race tests, make check, and Windows amd64/arm64 test cross-compilation pass; real Windows runtime remains unverified because the UTM guest is stopped.
* fix(pi): align rule removal and backup descriptions
Offer Remove rule only for owned exact +/- rules, not project delta globs that the apply path cannot remove. Keep supported glob rows switchable and cover delta and deltaOnly forms with RED/GREEN regressions.
Describe retained artifacts as extension-list and file-hash records rather than complete settings backups in English, all four website translations, and the implementation report.
* fix(pi): discard records for aborted extension applies
Require a validated preview and owned native lock before recording an extension change. Discard only the newly created record if final revalidation, lock ownership, or the atomic settings write fails; retain successful history and propagate cleanup errors with the original failure.
Keep discovery revalidation after record I/O so cleanup does not weaken the write-boundary guard. Cover global and new/existing project settings with nine RED/GREEN regressions, including injected commit failures. Align English and translated docs with the retained-record lifecycle.
* fix(pi): retain anonymous global packages in projects
Keep ordered anonymous registrations separate from the proven-identity map so unsupported query-bearing sources remain visible as redacted read-only packages, rather than being dropped or associated with a project override.
Preserve first-global-entry precedence for known identities. Add RED/GREEN coverage for string and object registrations, query/userinfo redaction, project entries, zero-write refusal, ordering, and continued editing of known packages.
* fix(pi): deduplicate only proven project identities
Exclude unresolved identities from project duplicate tracking. Preserve each anonymous registration as sourceUnknown instead of pretending unrelated query-bearing URLs are the same package.
Cover mixed string/object anonymous project sources, redaction and zero-write refusals, retained anonymous globals, and last-project-entry precedence for known packages. Verify known project entries remain editable.
* fix(pi): guard unresolved package precedence
An unresolved earlier global registration may own a later known package, and an unresolved later project registration may supersede an earlier known entry. Keep those potentially shadowed entries and inherited deltas Unknown/read-only instead of offering edits to ignored registrations. Do not infer identities by dropping credentials or queries.
Cover both ordering directions for global, inherited, project-owned, and delta views with RED/GREEN tests. Execute native query identity and dedupe evidence on Pi 0.99.2 and 1.0.0 through core and CLI-bundle contracts, now 28 scenarios and 87 assertions each. Align docs and evidence while retaining independent anonymous entries.
* fix(pi): propagate unreadable source ambiguity
Treat badSource entries as unresolved instead of letting an unreadable source expose editable later global registrations. Preserve the same uncertainty in inherited globals and before unreadable later project entries.
Add twelve global/inherited/project regressions for null, empty, whitespace and invalid UTF-8 sources. Native core and CLI-bundle evidence confirms invalid UTF-8 can decode to and own the same identity as a later valid source on both supported Pi versions; the executed contracts now pass 29 scenarios and 90 assertions.
* feat(pi): preserve filtered imports and reclaim stale locks
Adopt native object registrations without changing their configured resources. Keep lossless entries in scoped private state, retain current rules across lifecycle operations, restore filters before native installation, and preserve pending retries after failures.
Reclaim only unchanged empty directories after the native stale threshold, retaining renewed, replaced, nonempty and non-directory locks. Verify exact supported Pi contracts and keep unsupported cases read-only.
* docs(pi): record filtered import verification after branch sync
Document the current merged UI test count and repeated checks while retaining the native and visual verification limitations.
* docs(pi): clarify stale acquisition exception
Keep the lock safety summary consistent with the approved acquisition policy while preserving strict ownership for renewal and release.
* fix(pi): keep legacy npm fallback installations unknown
A missing user-scoped managed npm root cannot prove a package is absent because native Pi may use a legacy global npm or pnpm root. Keep it read-only without probing host-global state, while retaining missing-state behavior for project npm packages.
* fix(pi): preserve project precedence and batch restore ownership
Retain empty winning overrides when deleting them could expose older resource filters. Advance filtered restore batches only to exact writes made by the same Apply, while rejecting external changes and retaining failed native retries. Match Pi strict-false autoload semantics instead of treating null as a delta.