skillshop 2.2.0 → 4.1.0

package/README.md

@@ -1,6 +1,6 @@
 # Skillshop
 
-Skillshop installs and manages agent skills. Its CLI includes a bundled skill registry, with the same named install, update, and agent configuration commands as the earlier `skillz` CLI. It also lets project owners export skills from their own npm packages. A skill is a directory containing `SKILL.md` and any supporting files.
+Skillshop installs and manages agent skills. For user-authored skills, a plain folder library is the source of truth. Download individual skills from GitHub, install them into project or global destinations, and sync later source edits across recorded copies. The bundled registry and npm package-library APIs remain available for compatibility. A skill is a directory containing `SKILL.md` and any supporting files.
 
 The command is `skillshop`; `sk` runs the same CLI. The previous `skillz` command is no longer an executable alias. Existing `.skillz-lock` and `~/.skillz` state remain readable.
 
@@ -15,26 +15,65 @@ skillshop init
 
 `skillshop init` asks which agents you use and saves their destinations in `~/.skillshop/config.json`. It is optional for project skill installs: without saved agent selection, Skillshop uses the nearest existing `.agents`, `.github`, or `.codex` directory and falls back to project-root `.agents/skills`. Run `skillshop init` to choose system-wide defaults; change that selection later with `skillshop config agents`. Codex and OpenCode use `.agents/skills` inside projects and `~/.agents/skills` for user-level installs. Copilot and Claude use their own skill directories. Shared destinations get one copy.
 
-### Install a named skill
+### Use a personal folder library
 
-List the skills bundled with Skillshop, then install one:
+```bash
+skillshop library init                 # selects ~/skillshop-library
+skillshop library init ./my-skills     # selects or adopts an existing folder
+skillshop library list
+skillshop download @alice/review       # adds source only
+skillshop install @alice/review        # downloads if absent, then installs locally
+skillshop install @alice/review --global
+skillshop install review               # installs an existing selected source
+skillshop sync                         # updates all recorded project and global copies
+```
+
+`library init` can create a missing folder or select an existing library. It preserves existing skill directories and config; no `package.json`, npm metadata, or version field is required. Without an explicit directory it selects the visible `~/skillshop-library` folder. The library config is `skillshop-library.json`; the default source directory is `skills/`. A skill can contain any regular files and nested folders, including hidden references and executable scripts.
+
+`download @owner/skill` reads `https://github.com/owner/skillshop-library.git` and copies only `skills/skill` into the selected personal library. The `@` marks a remote owner/skill reference; it is not part of the GitHub owner or repository URL. Download does not install the skill. `install @owner/skill` downloads when that source is absent, then installs from the library. If the same repository source is already present, local edits are reused without an upstream fetch. `install name` installs a matching skill from the selected library. Once a library is selected, named installs and `skillshop list` use that library; they do not fall back to bundled skills or add bundled guidance. Add `--global` to install into configured user directories. Unprefixed `owner/skill` inputs are rejected; use `@owner/skill` for remote references.
+
+`download @owner/skill --force` explicitly replaces the personal source directory after validation. A same-name authored or different-source skill otherwise fails safely. `skillshop sync` copies the current full directory from each recorded personal source to its Skillshop-managed project and global copies. It includes file additions, edits, removals, hidden files, binary contents, and modes; stale extras inside those owned copies are removed. Sync never fetches GitHub and changing the selected library does not redirect existing copies.
+
+`sync` is also the explicit migration step for older tracked bundled installs. `library init` does not migrate them. If a selected library already has a skill, that source wins and tracked bundle copies are synchronized from it. Otherwise, Skillshop imports a missing source only when every surviving tracked project and global copy agrees across full paths, bytes, and modes. Divergent copies and unreadable ownership state are reported. Unknown source kinds, unmanaged directories, and imported snapshots are left untouched; if they prevent a complete consensus decision, sync reports that conflict. Missing recorded destinations are pruned, never recreated. Keep durable edits in the personal source; sync intentionally replaces local edits inside an owned installed copy.
+
+### Installation ownership and project dependencies
+
+Every installed skills directory has its own `.skillshop-lock`. This is a local ownership manifest, not a project dependency lockfile. It records which installer owns each named directory and its source. Personal-library, bundled, package, package-import, and dependency workflows preserve one another's entries. An existing unmanaged or foreign-owned directory is never implicitly adopted, including with package import `--force`.
+
+For reproducible project requirements, opt into a separate dependency workflow:
 
 ```bash
-skillshop list
-skillshop one-shot
-# Equivalent: skillshop install one-shot
+skillshop dependency add @alice/review@v1.2.0
+skillshop dependency add @alice/triage@0123456789abcdef0123456789abcdef01234567
+skillshop install                        # restore declared dependencies
+skillshop ci                             # restore with a frozen lock
+skillshop dependency remove review
 ```
 
-Run a project install inside a Git repository. Skillshop copies the skill into each configured project destination and records managed copies in `.skillshop-lock`. It also installs the `skillshop` guidance skill. The lockfile and managed skill directories go into the repository's local Git exclude file, leaving unrelated skill directories alone.
+`dependency add` writes `skillshop.json` and `skillshop-lock.json` at the project root and installs the skill. Commit both files. A reference can select a Git tag, branch, or full commit; omitting it resolves the current default branch. The lock records the exact resolved Git commit and SHA-256 integrity of the complete skill tree. It never follows a moved tag or branch during restore. These refs select repository revisions, not semver ranges or the version field in `SKILL.md`.
 
-To install a named skill for your user account instead:
+The project manifest declares `skillsDirectory` (default `.agents/skills`), independently of personal agent settings. Dependency installs use upstream sources directly; they do not create or modify your personal library. `skillshop sync`, ordinary named updates, and Skillshop upgrades leave dependency-owned content alone. Use `skillshop dependency update [name]` to re-resolve upstream refs, or add a different ref; ordinary installs reuse matching lock entries. `skillshop ci` or `skillshop install --frozen-lockfile` fails before installation if the dependency declaration and lock disagree.
+
+Use `skillshop dependency install` as an explicit alias for restore. For skills distributed through npm application packages, continue using npm's dependency declarations and package lock to pin the package; the destination `.skillshop-lock` records installation ownership only.
+
+`skillshop upgrade` automatically migrates legacy project-root `.skillshop-lock` / `.skillz-lock` files and `~/.skillshop/global-skills.json` (or the legacy state home) within its upgrade scope. Replacements are validated and saved before old records are removed, even when skill versions have not changed. Invalid/conflicting ownership or unsafe paths are preserved and reported as an incomplete migration. Unregistered repositories can be discovered with `skillshop migrate ~/workspace`. Installing the CLI directly with npm does not run migration hooks; use `skillshop migrate` or subsequent ownership-reconciling commands.
+
+See [installation and dependency state](docs/installation-and-dependency-state.md) for schemas, migration boundaries, and ownership rules.
+
+### Install a bundled registry skill (compatibility mode)
+
+When no personal library is selected, the bundled registry remains available:
 
 ```bash
+skillshop list
+skillshop one-shot
+# Equivalent: skillshop install one-shot
 skillshop one-shot --global
-# Equivalent: sk install one-shot --global
 ```
 
-For Codex or OpenCode, this writes `~/.agents/skills/one-shot`. A global install replaces an existing skill directory with that name, including local edits and extra files. Global installs use `~/.skillshop/global-skills.json` for bookkeeping. Except for `skillshop upgrade`, ordinary non-agent-instruction CLI runs reconcile recorded installations. Upgrade skips reconciliation in the old process and refreshes changed copies from the newly installed package in a fresh process. Agent instruction commands also bypass reconciliation and do not install the bundled registry.
+Run project installs inside a Git repository. Skillshop records ownership in `.skillshop-lock` inside each destination skills directory, for example `.agents/skills/.skillshop-lock`. It adds its local manifests and managed skill paths to the repository's local Git exclude file. In this compatibility mode it also installs bundled `skillshop` guidance. Global installs use the same directory-local format, for example `~/.agents/skills/.skillshop-lock`.
+
+In bundled compatibility mode, most ordinary commands reconcile recorded bundled installations. When a personal library is selected, `list` and named installs join library, download, qualified install, sync, upgrade, and agent instruction commands in bypassing that legacy reconciliation. Upgrade refreshes changed-version bundled copies from the newly installed package in a fresh process. Same-version bundled copies keep local edits; a changed-version replacement overwrites edits in that managed copy. To keep durable local changes, initialize a personal library, use `skillshop sync` to adopt tracked bundled copies where their contents agree, edit the library source, then sync it to owned copies. Personal-library copies are excluded from bundled refresh.
 
 ### Update or remove skills
 
@@ -46,7 +85,7 @@ skillshop uninstall one-shot
 skillshop uninstall one-shot --global
 ```
 
-`update` replaces skills managed in the current project's lockfile. `update --push` updates registered projects. Neither command updates global copies; reinstall a global skill by name with `--global`. Project uninstall removes only a skill recorded in `.skillshop-lock`. Global uninstall removes the named skill from configured user directories.
+`update` refreshes Skillshop-owned personal or bundled skills in the current project from their recorded source. `update --push` updates registered projects. Use `skillshop sync` to propagate personal-library changes to recorded local and global copies. Project and global uninstall remove only Skillshop CLI-owned copies recorded in the destination manifests. They refuse unmanaged skills and copies owned by packages or project dependencies.
 
 ### Upgrade Skillshop
 
@@ -56,7 +95,7 @@ skillshop upgrade
 
 The command upgrades the npm installation that supplied the invoked CLI. A project-local installation updates Skillshop in the owning npm project and preserves the dependency section where it is already declared. It refreshes only that project's recorded Skillshop-managed skill copies. A global installation updates its npm prefix, then refreshes recorded global copies and copies in registered projects; it does not update those projects' package manifests. Running from a source checkout keeps the historical global-install behavior and does not edit the checkout's package manifest.
 
-After npm succeeds, the newly installed CLI runs in a fresh process and refreshes only existing copies recorded in `.skillshop-lock` or `~/.skillshop/global-skills.json` whose bundled skill version changed. Same-version copies retain their local bodies. A changed-version replacement overwrites local edits in that managed copy; make durable edits in the bundled source. Deleted paths are pruned from ownership records instead of recreated. Unmanaged directories and package-import snapshots are not adopted. An npm install failure stops before copy refresh; a later refresh failure reports that Skillshop was upgraded and gives a nonzero result with the partial-refresh summary.
+After npm succeeds, the newly installed CLI runs in a fresh process. It migrates legacy ownership records, then refreshes only existing CLI-owned copies whose bundled skill version changed. Same-version copies retain local edits. A changed-version replacement overwrites local edits in that managed copy. For durable local changes, initialize a personal library, explicitly sync to adopt tracked bundled copies when their surviving copies agree, then edit the library source and sync. Deleted paths are pruned from ownership records instead of recreated. Unmanaged directories and package-import snapshots are not adopted. An npm install failure stops before copy refresh; a later refresh failure reports that Skillshop was upgraded and gives a nonzero result with the partial-refresh summary.
 
 `skillshop init` is optional. It configures agent destinations and is not required to upgrade Skillshop. The upgrade command never initializes, renders, or rewrites project `AGENTS.md` files or instruction templates.
 
@@ -125,7 +164,7 @@ A distributor can declare which exported skills a global npm install should plac
 npm install --global @example/skill-library
 ```
 
-Those declared skills are copied during the package's install script. This package installer targets `~/.agents/skills` by default, independently of the agents selected with `skillshop init`. Updating the package replaces the same named user skills. If scripts are disabled, run `skillshop install-user /path/to/installed-package` manually.
+Those declared skills are copied during the package's install script. This package installer targets `~/.agents/skills` by default, independently of the agents selected with `skillshop init`. Updating the package replaces its own recorded user skills, refuses unmanaged or foreign-owned collisions, and removes its own copies when their declarations are removed. If scripts are disabled, run `skillshop install-user /path/to/installed-package` manually.
 
 To copy one exported skill into a project instead:
 
@@ -147,195 +186,37 @@ cd ~/work/sample-app
 skillshop changelog
 ```
 
-The global command writes `~/.agents/skills/one-shot/SKILL.md`. The project command writes `.agents/skills/changelog/SKILL.md` and `.agents/skills/skillshop/SKILL.md` inside `sample-app`, then records both managed skills in `.skillshop-lock`. It does not copy `one-shot` into the project. Running `skillshop update` in `sample-app` refreshes the locked project skills; run `skillshop one-shot --global` again to replace the global copy.
+The global command writes `~/.agents/skills/one-shot/SKILL.md`. The project command writes `.agents/skills/changelog/SKILL.md` and `.agents/skills/skillshop/SKILL.md` inside `sample-app`, then records both managed skills in `.agents/skills/.skillshop-lock`. It does not copy `one-shot` into the project. Running `skillshop update` in `sample-app` refreshes the locked project skills; run `skillshop one-shot --global` again to replace the global copy.
 
-Package imports are separate from this lockfile workflow. `import` copies a snapshot from another package; `skillshop update` does not refresh that snapshot. `export` names a skill for consumers of a package and does not install it anywhere.
+Package imports record package-import ownership in the destination manifest and remain separate from personal-library sync and project dependency locking. `import` copies a snapshot from another package; `skillshop update` does not refresh that snapshot. `export` names a skill for consumers of a package and does not install it anywhere.
 
 ## For project owners: distribute skills
 
-### 1. Export the skills
+### Personal skills: share a folder through GitHub
 
-In an npm package, put each skill in a directory with a `SKILL.md`. For example:
+The recommended authoring format is a normal folder. Fork the bundled template at [`templates/skillshop-library`](templates/skillshop-library) or create the same layout in a GitHub repository named `skillshop-library`:
 
 ```text
-my-library/
-  package.json
-  .agents/skills/review/SKILL.md
-  .agents/skills/triage/SKILL.md
+skillshop-library/
+  skillshop-library.json
+  skills/
+    review/
+      SKILL.md
+      references/
+      scripts/
 ```
 
-For example, `.agents/skills/review/SKILL.md` could contain:
-
-```markdown
----
-name: review
-description: Review a proposed code change
----
-
-# Review
-
-Read the diff, identify concrete defects, and cite the affected files.
-```
-
-Keep any references or scripts needed by the skill beside its `SKILL.md`; Skillshop copies the whole directory.
-
-Add Skillshop, initialize the export list, and name the skill you want to publish:
+The config declares the relative source directory. Each skill needs a standard `SKILL.md` with `name` and `description`; author/version metadata is optional. Put references, scripts, and other assets beside it. Skillshop downloads the complete directory and preserves executable modes.
 
 ```bash
-npm install skillshop
-npx skillshop library init
-npx skillshop export skill:review ./.agents/skills/review
-npx skillshop export skill:triage ./.agents/skills/triage
-```
-
-This writes `skillshop.library.json`:
-
-```json
-{
-  "schemaVersion": 1,
-  "exports": {
-    "skill:review": "./.agents/skills/review",
-    "skill:triage": "./.agents/skills/triage"
-  }
-}
-```
-
-The `exports` map is an explicit allowlist. Skillshop does not scan your repository for other skills. `skillshop export` also builds the library; run `skillshop build` after editing the JSON by hand. The build generates `skillshop.manifest.mjs`, adds the package's `./skillshop` export, and includes declared local skill directories in `package.json#files` when that field exists. Commit the resulting package files with your source.
-
-### 2. Declare user-level installation, if needed
-
-To copy selected skills during a global npm install, add `skillshop.userInstall` and the generic lifecycle command to the distributor's `package.json`:
-
-```json
-{
-  "name": "@example/skill-library",
-  "version": "1.0.0",
-  "dependencies": {
-    "skillshop": "^2.1.0"
-  },
-  "files": [],
-  "scripts": {
-    "prepack": "skillshop build",
-    "postinstall": "skillshop install-user . --if-global"
-  },
-  "skillshop": {
-    "userInstall": ["skill:review"]
-  }
-}
+skillshop download @alice/review
+skillshop install @alice/review
+skillshop install @alice/review --global
+skillshop sync
 ```
 
-Every `userInstall` entry must be unique and appear in `skillshop.library.json`. In this example, `skill:review` installs for the user on a global npm install. `skill:triage` remains available for explicit project imports. The runtime dependency makes the `skillshop` command available to npm's `postinstall` script. `--if-global` skips the user copy on a project-local install. npm's `--ignore-scripts` skips `postinstall` entirely.
-
-An install replaces each declared destination directory. If a later release removes a name from `userInstall`, Skillshop does not delete a copy previously installed in a user's directory.
-
-### 3. Check and pack the package
-
-```bash
-npx skillshop library list
-npx skillshop validate
-npx skillshop build
-npm pack --dry-run
-```
-
-Check that the npm package contains `skillshop.manifest.mjs`, every exported `SKILL.md`, and any assets those skills need. The export list controls what Skillshop can resolve; it does not prevent your own broad `files` patterns from publishing other files. A real `npm pack` and global install from its tarball are useful checks before a release.
-
-After checking the tarball, publish the package with `npm publish`. Use `npm publish --access public` for a public scoped package.
-
-### Example: what happens after publication
-
-With the two-skill package above published as `@example/skill-library`, a global install copies only the declared `skill:review` to the user's skill directory:
-
-```bash
-npm install --global @example/skill-library
-# ~/.agents/skills/review/SKILL.md now comes from the package
-```
-
-An application that needs `skill:triage` can install the package locally and copy that exported skill into its own repository:
-
-```bash
-cd ~/work/sample-app
-npm install @example/skill-library skillshop
-npx skillshop import @example/skill-library:triage
-```
-
-After the distributor publishes an update, reinstalling the package globally replaces the user's `review` directory. The application's `triage` snapshot stays as it was until the application updates the package and imports again with `--force`. The two installation paths are independent.
-
-### Re-export a skill from another library
-
-A package can expose a selected upstream skill under its own name:
-
-```bash
-npm install @example/upstream
-npx skillshop export skill:review --from @example/upstream --skill skill:review
-```
-
-The resulting export in `skillshop.library.json` is:
-
-```json
-{
-  "skill:review": {
-    "from": "@example/upstream",
-    "skill": "skill:review"
-  }
-}
-```
-
-That object is one entry inside the manifest's `exports` map. The upstream package must be a runtime dependency or a non-optional peer dependency. Re-exporting is explicit; depending on another library does not expose all of its skills.
-
-## CLI and JavaScript API
-
-```text
-skillshop init
-skillshop config agents
-skillshop list
-skillshop <name> [--global]
-skillshop install <name> [--global]
-skillshop update [name]
-skillshop update --push
-skillshop uninstall <name> [--global]
-skillshop agents init [--project <directory>]
-skillshop agents [--project <directory>] [--check]
-skillshop agents --global
-skillshop migrate [root ...]
-skillshop library init
-skillshop library list
-skillshop export skill:<name> <directory>
-skillshop export skill:<name> --from <package> [--skill skill:<source-name>]
-skillshop unexport skill:<name>
-skillshop validate
-skillshop build
-skillshop resolve <library>:<skill>
-skillshop import <library>:<skill> [--global] [--to <directory>] [--force]
-skillshop install-user [package-dir] [--if-global] [--to <skills-dir>]
-```
-
-`init` and `list` keep their bundled-registry meanings. `library init`, `library list`, `validate`, and `build` operate on the package library in the current directory. In a `library:skill` reference, `library` can be an installed package name or a local package directory. `import` defaults to `.agents/skills/<skill>`; `--global` replaces `~/.agents/skills/<skill>`. `unexport` changes the package's public skill list; it does not delete the source directory. Remove a skill from `userInstall` before unexporting it.
-
-Applications can use the same operations without invoking the CLI:
-
-```js
-import { exportSkill, reexportSkill, buildSkillLibrary } from 'skillshop/export';
-import { resolveSkill, importSkill } from 'skillshop/import';
-import { installDeclaredUserSkills } from 'skillshop/user-install';
-```
-
-For example, an application can read an exported skill directly from an installed package, or copy it into a workspace it manages:
-
-```js
-import { readFile } from 'node:fs/promises';
-import { resolveSkill, importSkill } from 'skillshop/import';
-
-const reference = '@example/skill-library:triage';
-const { manifestPath } = await resolveSkill({ reference });
-const instructions = await readFile(manifestPath, 'utf8');
-// Pass instructions to your agent runtime.
-
-await importSkill({
-  reference,
-  overwrite: true,
-});
-```
+`download @owner/skill` adds a source to the personal folder library without installing it. `install @owner/skill` downloads if needed and installs from that source; subsequent local edits are reused. `install name` uses a bare name for an existing library source. `sync` updates recorded local and global copies from the saved source roots. It never fetches upstream. See [the forkable library template](templates/skillshop-library/README.md) for its full layout and command details.
 
-`resolveSkill` leaves the skill inside the installed package. `importSkill` copies its complete directory, including files alongside `SKILL.md`. Set `overwrite: true` only when the application intends to replace an existing destination.
+### Existing package API compatibility
 
-`importSkill({ overwrite: true })` replaces a destination. Its optional `merge: true` mode overlays packaged files and preserves unrelated destination files. User-level installation always uses replacement, even when called through `installDeclaredUserSkills`.
+The published npm export/import APIs remain supported for existing consumers. Their authoring, lifecycle, and JavaScript API guide is in [Package library compatibility](docs/package-library-compatibility.md). New user-authored libraries can use the folder and GitHub workflow above without npm packaging.

package/docs/installation-and-dependency-state.md

@@ -0,0 +1,76 @@
+# Installed ownership and project dependency locks
+
+Skillshop separates editable source libraries, installed ownership, and reproducible project requirements. Installing a personal skill does not make it a project dependency. Applications distributed through npm continue to use npm's own dependency declarations and package lock.
+
+## Destination ownership
+
+Every destination skills directory has one `.skillshop-lock`. The destination itself identifies installed paths; entries do not repeat absolute destination paths or point to a second authoritative registry.
+
+```json
+{
+  "manifestVersion": 1,
+  "skills": {
+    "review": {
+      "owner": { "kind": "skillshop", "id": "project" },
+      "source": {
+        "kind": "personal-library",
+        "root": "/Users/example/skillshop-library",
+        "skill": "review",
+        "skillDirectory": "skills/review"
+      }
+    }
+  }
+}
+```
+
+CLI-owned copies use owner kind `skillshop` and id `project` or `global`. Project dependency copies use kind `dependency`, id `project`. These local ids survive moving an entire project directory. Package lifecycle installers use kind `package` and the package name as id; explicit snapshot imports use kind `package-import`. Package ids remain stable across versions and npm installation paths. Anonymous manifest-object imports use their source directory as id and should supply a package name for stable ownership.
+
+Each installer reads the destination manifest, checks ownership, and preserves entries belonging to other installers. Matching ownership permits updates. Existing directories without ownership records and records belonging to other owners are rejected. `import --force` permits replacing an existing matching package-import copy; it does not adopt unrelated directories. Global CLI uninstall checks ownership too. Package declaration updates prune only that package's obsolete copies; `uninstallUserSkill` provides explicit same-owner removal.
+
+The files `~/.skillshop/installations.json` and `repositories.json` are discovery indexes, not ownership authorities. Deleting or editing an index does not grant ownership. Known standard installation directories can still be discovered from the project or home directory. `sync` uses the source roots recorded in destination manifests, independently of the currently selected library.
+
+Ownership manifests are local machine state. Personal/bundled installation commands locally exclude their manifests and owned directories through Git's `info/exclude`. Dependency commands maintain a separate bounded exclude block for generated dependency content and destination manifests. Unrelated installed skill directories are not blanket-excluded. Project declarations and dependency locks remain commit candidates.
+
+## Project declarations and immutable resolution
+
+Add a dependency explicitly:
+
+```sh
+skillshop dependency add @alice/review@v1.2.0
+```
+
+This writes a project-owned `skillshop.json`:
+
+```json
+{
+  "schemaVersion": 1,
+  "skillsDirectory": ".agents/skills",
+  "dependencies": {
+    "review": "@alice/review@v1.2.0"
+  }
+}
+```
+
+A corresponding `skillshop-lock.json` records each requested reference, conventional GitHub repository URL, exact resolved commit, and `sha256-` integrity. It also records the project installation directory, so a frozen restore detects destination configuration changes. It contains no personal-library paths or machine-specific destination paths.
+
+Refs can select a Git tag, branch, or full commit hash. An omitted ref resolves the repository's default branch. These are Git revisions; there is no semver-range solver or historical registry of `SKILL.md` version fields. A moved upstream tag cannot change an existing lock entry. The complete directory is fetched from the locked commit, and integrity covers ordered paths, file bytes, and executable bits, including hidden files, scripts and binary references. Repository code is never executed while fetching.
+
+`skillshop install` and `skillshop dependency install` restore declared dependencies. Unchanged entries reuse their locked commit; a new or changed declaration resolves its ref. Already correct owned copies are left in place without upstream requests. Missing copies are restored and edited copies are repaired against the lock. Restoration requires upstream access when the required content is not already installed correctly.
+
+`skillshop ci`, `skillshop install --frozen-lockfile`, and `skillshop dependency install --frozen-lockfile` refuse a missing or stale lock before changing output. Use `skillshop dependency update [name]` to re-resolve selected or all upstream refs, or add a different ref. `skillshop dependency remove review` removes the declaration, locked resolution and matching owned copy while preserving other owners. Ordinary personal sync/update and CLI upgrade never refresh dependency copies.
+
+All required downloads, integrity checks and ownership checks finish before dependency content changes. Replacement/removal uses temporary directories and backups. A failed content or metadata write restores prior content, ownership and project declarations. Manifest writes use atomic rename. These records are ownership and reproducibility data, not process mutexes; concurrent writers targeting the same directory are not supported.
+
+Dependency APIs are exported from `skillshop/dependencies`: `addDependency`, `installDependencies`, `updateDependencies`, and `removeDependency`. They accept `cwd`; install accepts `frozen`. For CLI commands, the nearest project manifest takes precedence while ascending to the nearest Git root. Outside Git, an existing ancestor manifest is used; otherwise the working directory is the project boundary.
+
+## Migration and upgrade boundaries
+
+The new CLI reads legacy project-root `.skillshop-lock` / `.skillz-lock` files and the old state-home `global-skills.json`. It validates their schemas, owned paths and any existing destination claims before repair or migration. Divergent simultaneous legacy root files are rejected. Only explicit ownership records are migrated; scanning directories does not adopt arbitrary skills.
+
+Replacement manifests are saved beside installed skills before legacy records are removed. Retry is safe when a prior attempt saved only part of the replacement state. Malformed JSON, conflicting source/ownership records, and symlinked paths are preserved and reported rather than silently discarded. Upgrading does not merge or overwrite application-owned directories.
+
+`skillshop upgrade` installs the new npm package first and uses its fresh CLI for migration and version-based bundled refresh. A project-local npm installation migrates only its owning project's state. A global installation migrates global state and registered projects. Migration runs even for unchanged-version and personal-library copies. Same-version bundled edits survive; changed-version bundled refresh retains its existing replacement behavior. Missing copies are not recreated by ownership migration.
+
+Direct `npm install --global skillshop` replaces the CLI but does not run migration hooks. The next ownership-reconciling command can migrate its current project and global state; `skillshop migrate ~/workspace` discovers additional repositories. Personal-library initialization, downloading, listing and instruction-rendering commands retain their existing isolation from legacy reconciliation.
+
+Using an old CLI after migration is unsupported: old versions do not understand directory-local manifests. Reinstalling skills with an old package installer can also bypass the new ownership protections. Keep application integrations on the updated Skillshop API.

package/docs/package-library-compatibility.md

@@ -0,0 +1,194 @@
+# Package library compatibility
+
+This guide documents the existing npm package export/import APIs. It is retained for consumers of those published APIs. It is not required for personal folder libraries or GitHub skill sharing.
+
+### Package API compatibility: export skills from npm packages
+
+The npm export/import API remains supported for existing package-based libraries. It is not required for personal skill authoring.
+
+#### 1. Export the skills
+
+In an npm package, put each skill in a directory with a `SKILL.md`. For example:
+
+```text
+my-library/
+  package.json
+  .agents/skills/review/SKILL.md
+  .agents/skills/triage/SKILL.md
+```
+
+For example, `.agents/skills/review/SKILL.md` could contain:
+
+```markdown
+---
+name: review
+description: Review a proposed code change
+---
+
+# Review
+
+Read the diff, identify concrete defects, and cite the affected files.
+```
+
+Keep any references or scripts needed by the skill beside its `SKILL.md`; Skillshop copies the whole directory.
+
+Add Skillshop, initialize the export list, and name the skill you want to publish:
+
+```bash
+npm install skillshop
+npx skillshop library init
+npx skillshop export skill:review ./.agents/skills/review
+npx skillshop export skill:triage ./.agents/skills/triage
+```
+
+This writes `skillshop.library.json`:
+
+```json
+{
+  "schemaVersion": 1,
+  "exports": {
+    "skill:review": "./.agents/skills/review",
+    "skill:triage": "./.agents/skills/triage"
+  }
+}
+```
+
+The `exports` map is an explicit allowlist. Skillshop does not scan your repository for other skills. `skillshop export` also builds the library; run `skillshop build` after editing the JSON by hand. The build generates `skillshop.manifest.mjs`, adds the package's `./skillshop` export, and includes declared local skill directories in `package.json#files` when that field exists. Commit the resulting package files with your source.
+
+### 2. Declare user-level installation, if needed
+
+To copy selected skills during a global npm install, add `skillshop.userInstall` and the generic lifecycle command to the distributor's `package.json`:
+
+```json
+{
+  "name": "@example/skill-library",
+  "version": "1.0.0",
+  "dependencies": {
+    "skillshop": "^2.1.0"
+  },
+  "files": [],
+  "scripts": {
+    "prepack": "skillshop build",
+    "postinstall": "skillshop install-user . --if-global"
+  },
+  "skillshop": {
+    "userInstall": ["skill:review"]
+  }
+}
+```
+
+Every `userInstall` entry must be unique and appear in `skillshop.library.json`. In this example, `skill:review` installs for the user on a global npm install. `skill:triage` remains available for explicit project imports. The runtime dependency makes the `skillshop` command available to npm's `postinstall` script. `--if-global` skips the user copy on a project-local install. npm's `--ignore-scripts` skips `postinstall` entirely.
+
+An install records package ownership in `.skillshop-lock` inside the destination skills directory. It replaces only copies already owned by the same package and rejects unmanaged or foreign-owned destinations. A later install removes copies owned by that package when their names are removed from `userInstall`; other owners remain untouched. Package names identify owners across versions and installation paths. Applications can explicitly remove an owned skill with `uninstallUserSkill` from `skillshop/user-install`.
+
+### 3. Check and pack the package
+
+```bash
+npx skillshop library list
+npx skillshop validate
+npx skillshop build
+npm pack --dry-run
+```
+
+Check that the npm package contains `skillshop.manifest.mjs`, every exported `SKILL.md`, and any assets those skills need. The export list controls what Skillshop can resolve; it does not prevent your own broad `files` patterns from publishing other files. A real `npm pack` and global install from its tarball are useful checks before a release.
+
+After checking the tarball, publish the package with `npm publish`. Use `npm publish --access public` for a public scoped package.
+
+### Example: what happens after publication
+
+With the two-skill package above published as `@example/skill-library`, a global install copies only the declared `skill:review` to the user's skill directory:
+
+```bash
+npm install --global @example/skill-library
+# ~/.agents/skills/review/SKILL.md now comes from the package
+```
+
+An application that needs `skill:triage` can install the package locally and copy that exported skill into its own repository:
+
+```bash
+cd ~/work/sample-app
+npm install @example/skill-library skillshop
+npx skillshop import @example/skill-library:triage
+```
+
+After the distributor publishes an update, reinstalling the package globally replaces the user's `review` directory. The application's `triage` snapshot stays as it was until the application updates the package and imports again with `--force`. The two installation paths are independent.
+
+### Re-export a skill from another library
+
+A package can expose a selected upstream skill under its own name:
+
+```bash
+npm install @example/upstream
+npx skillshop export skill:review --from @example/upstream --skill skill:review
+```
+
+The resulting export in `skillshop.library.json` is:
+
+```json
+{
+  "skill:review": {
+    "from": "@example/upstream",
+    "skill": "skill:review"
+  }
+}
+```
+
+That object is one entry inside the manifest's `exports` map. The upstream package must be a runtime dependency or a non-optional peer dependency. Re-exporting is explicit; depending on another library does not expose all of its skills.
+
+## CLI and JavaScript API
+
+```text
+skillshop init
+skillshop config agents
+skillshop list
+skillshop <name> [--global]
+skillshop install <name> [--global]
+skillshop update [name]
+skillshop update --push
+skillshop uninstall <name> [--global]
+skillshop agents init [--project <directory>]
+skillshop agents [--project <directory>] [--check]
+skillshop agents --global
+skillshop migrate [root ...]
+skillshop library init
+skillshop library list
+skillshop export skill:<name> <directory>
+skillshop export skill:<name> --from <package> [--skill skill:<source-name>]
+skillshop unexport skill:<name>
+skillshop validate
+skillshop build
+skillshop resolve <library>:<skill>
+skillshop import <library>:<skill> [--global] [--to <directory>] [--force]
+skillshop install-user [package-dir] [--if-global] [--to <skills-dir>]
+```
+
+`init` and `list` keep their bundled-registry meanings. `library init`, `library list`, `validate`, and `build` operate on the package library in the current directory. In a `library:skill` reference, `library` can be an installed package name or a local package directory. `import` defaults to `.agents/skills/<skill>`; `--global` targets `~/.agents/skills/<skill>` and replaces only a matching package-import-owned copy. `unexport` changes the package's public skill list; it does not delete the source directory. Remove a skill from `userInstall` before unexporting it.
+
+Applications can use the same operations without invoking the CLI:
+
+```js
+import { exportSkill, reexportSkill, buildSkillLibrary } from 'skillshop/export';
+import { resolveSkill, importSkill } from 'skillshop/import';
+import { installDeclaredUserSkills } from 'skillshop/user-install';
+```
+
+For example, an application can read an exported skill directly from an installed package, or copy it into a workspace it manages:
+
+```js
+import { readFile } from 'node:fs/promises';
+import { resolveSkill, importSkill } from 'skillshop/import';
+
+const reference = '@example/skill-library:triage';
+const { manifestPath } = await resolveSkill({ reference });
+const instructions = await readFile(manifestPath, 'utf8');
+// Pass instructions to your agent runtime.
+
+await importSkill({
+  reference,
+  overwrite: true,
+});
+```
+
+`resolveSkill` leaves the skill inside the installed package. `importSkill` copies its complete directory, including files alongside `SKILL.md`. Set `overwrite: true` only when the application intends to replace an existing destination.
+
+`importSkill({ overwrite: true })` replaces a destination only when that copy is already owned by the same package-import source; it does not authorize taking ownership of unrelated content. Its optional `merge: true` mode overlays packaged files and preserves unrelated destination files. User-level installation always uses replacement of matching package-owned copies, even when called through `installDeclaredUserSkills`. Merge mode also requires matching ownership for existing targets.

package/docs/releases/4.1.0.md

@@ -0,0 +1,12 @@
+# Skillshop 4.1.0
+
+Separate installed skill ownership from reproducible project dependencies.
+
+- Store ownership in `.skillshop-lock` beside installed skills, with automatic migration of tracked legacy project/global records during `skillshop upgrade`.
+- Add committed `skillshop.json` declarations and `skillshop-lock.json` resolutions that pin exact Git commits and complete-tree SHA-256 integrity.
+- Add `skillshop dependency add/install/update/remove`, dependency restore through `skillshop install`, and frozen restore through `skillshop ci`.
+- Reject unmanaged and foreign-owned collisions, protect global uninstall, and prune removed application declarations only for their recorded package owner.
+
+Migration preserves unmanaged skills and same-version bundled edits. Invalid ownership records and unsafe paths are preserved and reported. Direct npm installation replaces the CLI without migration hooks; run `skillshop migrate ~/workspace` to discover and migrate additional repositories. Older CLI versions cannot read the new ownership format.
+
+Validated with the full automated suite, isolated local/global upgrade fixtures, and packed CLI installation/dependency smoke tests.