projectstore-claude 0.30.5 → 0.30.7

package/node_modules/projectstore/.claude-plugin/marketplace.json

@@ -12,14 +12,14 @@
       "name": "projectstore",
       "displayName": "projectstore",
       "description": "📚 Your agent runs the project through a verified loop: task → artifact (ADR · spec · epic · story) → adversarial critic → backlog → planner → reviewer → done. Plain markdown in an Obsidian-friendly vault, every write approved by you — and any model can pick the project up tomorrow.",
-      "version": "0.30.5",
+      "version": "0.30.7",
       "author": {
         "name": "Evgenii Konev",
         "email": "ekonev@smartandpoint.com",
         "url": "https://github.com/SmartAndPoint"
       },
       "category": "productivity",
-      "homepage": "https://github.com/SmartAndPoint/ProjectStore",
+      "homepage": "https://projectstore.dev",
       "tags": [
         "obsidian",
         "markdown",

package/node_modules/projectstore/.claude-plugin/plugin.json

@@ -1,15 +1,19 @@
 {
   "name": "projectstore",
   "displayName": "projectstore",
-  "version": "0.30.5",
+  "version": "0.30.7",
   "description": "Your agent runs the project through a verified loop: task → artifact (ADR / spec / epic / story) → adversarial critic → backlog → planner → reviewer → done. Plain markdown in git — any model can pick the project up tomorrow.",
   "author": {
     "name": "Evgenii Konev @ SmartAndPoint",
     "email": "ekonev@smartandpoint.com",
     "url": "https://github.com/SmartAndPoint"
   },
-  "homepage": "https://github.com/SmartAndPoint/ProjectStore",
+  "homepage": "https://projectstore.dev",
   "repository": "https://github.com/SmartAndPoint/ProjectStore",
+  "icon": "./docs/images/icon.png",
+  "documentationUrl": "https://github.com/SmartAndPoint/ProjectStore#readme",
+  "supportUrl": "https://github.com/SmartAndPoint/ProjectStore/issues",
+  "privacyPolicyUrl": "https://projectstore.dev/privacy/",
   "license": "MIT",
   "types": "./hooks/band-state.d.ts",
   "keywords": [

package/node_modules/projectstore/.mcp.json

@@ -4,8 +4,7 @@
       "type": "stdio",
       "command": "node",
       "args": [
-        "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs",
-        "mcp",
+        "${CLAUDE_PLUGIN_ROOT}/scripts/mcp-server.mjs",
         "--project",
         "${CLAUDE_PROJECT_DIR}"
       ]

package/node_modules/projectstore/README.md

@@ -33,10 +33,7 @@ Decision logs, validators, session-start orientation and independent review each
 
 The thing that makes agentic coding work — the loop Claude Code's own creator keeps pointing at — is *gather context, act, verify, repeat*. ProjectStore runs that loop one level up: over the project, not just the code.
 
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="docs/images/loop.svg">
-  <img alt="The ProjectStore loop: task → artifact → critic (verify) → backlog → planner → implement → reviewer (verify) → done → views regenerate" src="docs/images/loop-light.svg">
-</picture>
+![The ProjectStore loop: task → artifact → critic (verify) → backlog → planner → implement → reviewer (verify) → done → views regenerate](docs/images/loop.svg)
 
 1. **You hand the agent a task.** It opens an artifact before it opens an editor: an ADR if something needs deciding, an epic and stories for the work, a spec when the "how" is non-trivial.
 2. **A fresh-context critic attacks the artifact.** Expect *revise* — on this repo it has yet to pass anything on the first try, and that is the point.
@@ -197,9 +194,25 @@ npx projectstore init ~/vaults/new-project --language ru
 npx projectstore scaffold --write
 ```
 
-`projectstore-claude`, `projectstore-codex` and `projectstore-opencode` are release artifacts: per-harness packages that carry the core, pinned at the same version and bundled, with the harness fixed. Nobody needs to type their names. Setup fetches the Codex one, which carries the Codex plugin; the Claude Code one is published at the core's version too; the opencode one publishes after its plugin root is rendered. The other `projectstore-*` names are reserved placeholders pointing back here. One source package, one version, N tarballs. How a release builds and publishes them, and how to run a checkout's own build: [`packaging/README.md`](./packaging/README.md).
+`projectstore-claude`, `projectstore-codex` and `projectstore-opencode` are release artifacts: per-harness packages that carry the core, pinned at the same version and bundled, with the harness fixed. Nobody needs to type their names. Setup fetches the Codex one, which carries the Codex plugin; the Claude Code one is published at the core's version too; the opencode one publishes after its plugin root is rendered. The other `projectstore-*` names are reserved placeholders pointing back here. One source package, one version, N tarballs. How a release builds and publishes them, and how to run a checkout's own build: [`packaging/README.md`](https://github.com/SmartAndPoint/ProjectStore/blob/main/packaging/README.md).
 </details>
 
+## Installed from Anthropic's directory
+
+If you added ProjectStore from Anthropic's plugin directory, it is already installed: it comes through your claude.ai account, Claude Code loads it as `projectstore@synced`, and no `npx` step is needed. Bind a vault in a Claude Code session in your project:
+
+```
+/projectstore:bind ~/Documents/my-project-vault
+```
+
+Updates come from claude.ai: when a new version is published, Claude Code downloads it at its next start and asks you to run `/reload-plugins` in the session. The upgrade commands below are for the other ways to install, and this copy needs none of them. To turn it off or remove it:
+
+- **Off for your account on this machine**: `/plugin` → **Installed**, then turn off `projectstore@synced`.
+- **Off for one project only**: set `"projectstore@synced": false` under `enabledPlugins` in that project's `.claude/settings.local.json`, or in its committed `.claude/settings.json` to keep it out for everyone who opens the project.
+- **Removed**: on claude.ai, where it was added.
+
+What the directory itself reports about a copy installed this way: [What Anthropic's directory reports](#what-anthropics-directory-reports).
+
 ## Configure
 
 Setup asks only what a first install needs. Everything after it is one command, from a terminal in your project:
@@ -210,7 +223,7 @@ npx projectstore configure
 
 At a terminal it opens a settings menu that works like a monitor's: ↑ and ↓ move, → opens a group or a setting in a frame beside it, space chooses, ← goes back, and Enter shows the plan. A second Enter writes it. Under the frames, a few lines say what the row under the cursor means. The settings:
 
-- each agent's model and effort, per harness. Claude Code offers its aliases: `fable`, `opus`, `sonnet` and `haiku`. Codex offers its own list of models, with its descriptions. With `ANTHROPIC_API_KEY` set, each alias also names the newest model of its line. A list is kept for a day in projectstore's user cache, and "refresh the list" asks again. Each agent's effort sits under its model: Claude Code's levels, `low` to `max`, or the levels that Codex model lists. With none set, a Claude Code agent runs at its frontmatter's level (`max`, the clerk `low`) and a Codex one at its model's own default;
+- each agent's model and effort, per harness. Claude Code offers its aliases: `fable`, `opus`, `sonnet` and `haiku`. Codex offers its own list of models, with its descriptions, kept for a day in projectstore's user cache; "refresh the list" asks Codex again. Each agent's effort sits under its model: Claude Code's levels, `low` to `max`, or the levels that Codex model lists. With none set, a Claude Code agent runs at its frontmatter's level (`max`, the clerk `low`) and a Codex one at its model's own default;
 - the status line and the band above the prompt (Claude Code);
 - the vault's template language, the default author and tags;
 - the vault's spec policy and lifecycle gates.
@@ -239,7 +252,7 @@ Installed with setup or from npm: from a terminal in your project, name the vers
 npx projectstore@<version> upgrade
 ```
 
-It upgrades every agent the project uses — each one whose own directory (`.claude/`, `.codex/`) or `.projectstore/state/<id>/` is there — in one plan, and fetches the Codex plugin at the same version. `npx projectstore setup` converges a project the same way and asks its questions again. Installed from the git marketplace in a Claude Code session: `/plugin update` (or auto-update) and a restart.
+It upgrades every agent the project uses — each one whose own directory (`.claude/`, `.codex/`) or `.projectstore/state/<id>/` is there — in one plan, and fetches the Codex plugin at the same version. `npx projectstore setup` converges a project the same way and asks its questions again. Installed from the git marketplace: in a Claude Code session, open `/plugin manage` and choose **Update now** on projectstore (or let auto-update do it), then run `/reload-plugins` to load it; from a terminal, `claude plugin update projectstore@SmartAndPoint` and a restart do the same.
 
 A bare upgrade selects agents by those directories, so on Codex name it, which upgrades Codex even in a project where no Codex session has run yet:
 
@@ -281,7 +294,7 @@ A project bound before 0.28 needs one more command. What an existing project see
   its new path and re-registers the agents block, whose template is now v4. An
   upgrade without `--no-register` on a git-marketplace install does more: it
   also registers the plugin from npm for this checkout and turns the
-  git-marketplace copy off here, so `/plugin update` stops reaching the
+  git-marketplace copy off here, so that copy's updates stop reaching the
   checkout. The 0.28.0-rc.1 and rc.2 startup lines named that form, without
   `--no-register`, so on those, update first and run what the new startup line
   names. If it already happened, this turns the git-marketplace copy back on
@@ -337,8 +350,8 @@ A project bound before 0.28 needs one more command. What an existing project see
   while two bindings exist. To come forward again, delete
   `.claude/projectstore.json`, then run the command the startup line names
   once more: a 0.27.x session writes its welcome marker back under `.claude/`.
-- **Installed from npm?** Then `/plugin update` has nothing to fetch: the
-  package itself refreshes the registration. The upgrade at the top of this
+- **Installed from npm?** Then Claude Code's plugin update has nothing to
+  fetch: the package itself refreshes the registration. The upgrade at the top of this
   section, run from a terminal outside the session, rewrites the local
   marketplace and runs the host's `plugin update` for this checkout.
   `/projectstore:doctor` says when the registration is behind the package, and
@@ -350,10 +363,7 @@ Two generated views exist for exactly that moment. `graph.md` holds every artifa
 
 ## Teams: many humans, many agents
 
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="docs/images/team.svg">
-  <img alt="Team setup: several developers, each with their own agent, bind to one vault in its own git repo; ADRs and specs are reviewed as merge requests" src="docs/images/team-light.svg">
-</picture>
+![Team setup: several developers, each with their own agent, bind to one vault in its own git repo; ADRs and specs are reviewed as merge requests](docs/images/team.svg)
 
 Put the vault in its own repository. Every teammate installs ProjectStore, binds to the same vault, and contributes through the same approval gates. ADRs and specs get reviewed like code — as merge requests, except what's under review is the *reasoning*. A teammate without an agent reviews on GitHub or in Obsidian: it is all just markdown.
 
@@ -381,6 +391,42 @@ The deep dive — real session files, measured payloads, how every mechanism wor
 4. **Layouts are opinionated.** v1 ships `engineering`; community adds `data-analytics`, `product`, `chatbot`, `library`.
 5. **One brain per project, not per person.** The vault travels with the repo. Karpathy's [LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) is its personal-research counterpart.
 
+## What ProjectStore runs, writes, sends and fetches
+
+ProjectStore has no server, no account and no telemetry. It collects nothing about you, your project or your vault, and it reads no credential from your environment. Its own code makes two requests, the ones under "What it sends and fetches" below, and each one is made by a command you run, never by a hook. One program it runs makes a request of its own: Codex's model command, which refreshes Codex's catalog with your Codex login. This list covers everything in the package, and a [test](https://github.com/SmartAndPoint/ProjectStore/blob/main/tests/disclosure.test.mjs) fails when a shipped module that starts a program or makes a request is not accounted for here.
+
+### What it runs
+
+- **Node.js.** The hooks, the MCP server, the status line and the `projectstore` command are Node.js scripts in the plugin. They start other scripts of the plugin through the same Node. When setup keeps a project on its git-marketplace copy, it runs that copy's own `bin/projectstore.mjs` to read the copy's plan and, once you confirm, to apply it.
+- **git**, on this machine only. ProjectStore never commits, pushes, pulls or fetches. The SessionStart hook runs `git rev-parse` in a project that is not bound, to see whether it is a worktree of a bound checkout; no other hook starts a program. Bind, init and setup run `git rev-parse --show-toplevel` to find the repository and `git init` to give a new vault its own repository. They run `git config --get user.name` to propose the default author; the binding keeps it, and each new artifact names it as its author. Doctor runs `git check-ignore` and `git ls-files` to check what git ignores and tracks, and `git diff --name-only` and `git log` to see what has changed. The reviewer's list of the files a story touched comes from `git diff` and `git log` too. The reviewer and archaeologist agents read the project's git history (`git status` and `git diff` or `git log` among others) through the agent's own tools, as any command the agent runs.
+- **The agent CLIs, `claude` and `codex`.** Setup, install, upgrade and uninstall run their plugin commands, such as `plugin marketplace add` and `plugin install` to register ProjectStore or `plugin uninstall` to remove it. Each one runs after you confirm the plan, which shows it verbatim. The model menu of `configure` also runs `codex debug models` to read Codex's model list, which Codex refreshes over the network with its own login.
+- **npm**, from setup, install and upgrade only. They run `npm config get registry` to learn which registry your npm uses. When they set up Codex, they also run `npm install` with `--ignore-scripts` to fetch the `projectstore-codex` package at the running version into a folder in ProjectStore's cache, because the Codex plugin ships in that package. No install script of that package runs.
+- **The band above the prompt** (Claude Code) is a module that runs inside Claude Code's own process, not in Node. It reads the binding, the session's pointer and its epic's files, and writes a heartbeat under `.projectstore/state/sessions/` while it draws; it starts no program and makes no request.
+- **Your own status line.** When ProjectStore's status line is on and your project's `.claude/settings.json` or your user `settings.json` already names a status line command, ProjectStore runs that command through your shell on every render, passes it the status data Claude Code gives a status line on its standard input, and shows what it prints under its own line.
+
+The package also ships `scripts/version-guard.mjs`, which runs `npm pack --dry-run` as the release's own check. The plugin never runs it.
+
+### What it writes
+
+Opening a project that is not bound writes nothing into it: the first-run welcome is remembered in the user cache below. Every other write in a project comes from a command you run, or from the hooks and the status line once the project is bound.
+
+- **In a bound project**: `.projectstore/`, with the binding (`projectstore.json`, machine-local and git-ignored), the agents' models (`harness/`, meant to be committed), `state/` (each session's state, the band's heartbeat, the welcome marker and the status line's launcher, machine-local) and its own `.gitignore`; the agents block between the `projectstore:agents` markers in `AGENTS.md` and `CLAUDE.md`; and `.claude/settings.local.json`, which gets the status line only when you turn it on, and this checkout's plugin registration when setup or install registers the npm copy, or turns the git-marketplace copy off here, through Claude Code's own CLI.
+- **In the vault**: the artifacts, each one after you approve it; the views generated from them (the kanban, the folder indexes, the code map and the graph); `.projectstore.json`, the vault's own settings; and `.projectstore/sessions/`, one small git-ignored file per session with its id, start time, project path, host name, process id and the vault files it read or edited last, with the tool and the time. A session's file is deleted at the next session start once it has been inactive for 24 hours. A new vault also gets its own git repository.
+- **In your home directory**: `~/.cache/projectstore/`, or `$XDG_CACHE_HOME/projectstore/` when that is set. It holds the newest version the npm registry named (`registry.json`, kept for 24 hours), the model lists (`models/`, kept for a day: model names, labels, descriptions and families, never a key), which agent has shown its first-run welcome in a project that is not bound (`welcomed/`, one marker per agent for the machine), and the Codex package while a run installs it (`fetch/`, removed when the run ends). Setup and install from npm also write a folder of their own, `projectstore/`, under Claude Code's home (`~/.claude`, or `$CLAUDE_CONFIG_DIR`) or Codex's (`~/.codex`, or `$CODEX_HOME`), holding the marketplace the agent installs ProjectStore from, and the agent's own CLI records the plugin in that agent's plugin registry.
+
+ProjectStore never changes Claude Code's or Codex's permission settings.
+
+### What it sends and fetches
+
+- **The npm registry**, `https://registry.npmjs.org/` or the registry your npm is set to. One `GET <registry>/projectstore` request with no credentials and a 2-second limit asks for the newest release. Setup, install and upgrade make it when they run from npm (npx or a global install) or from a git checkout. They never make it from the copy that Claude Code or Codex loads, and never in a dry run. The answer is kept for 24 hours, and `PROJECTSTORE_NO_UPDATE_CHECK=1` turns the request off.
+- **The Codex package.** The `npm install` above fetches `projectstore-codex` from the registry your npm is set to, with npm's own settings, only when setup, install or upgrade sets up Codex.
+
+ProjectStore's own code sends nothing else: the hooks, the MCP server, the band and the status line open no connection. Two programs it runs may connect on their own. When the model menu reads Codex's list, `codex debug models` refreshes Codex's catalog with your Codex login. The status line command you had before is yours, and it runs as you set it.
+
+### What Anthropic's directory reports
+
+For a copy added from Anthropic's plugin directory, Claude collects usage figures, not ProjectStore, and shows them to the maintainer on the directory's **Usage** tab ([Track published plugin usage](https://claude.com/docs/connectors/building/after-publishing#track-published-plugin-usage)): installs, active accounts and retention, with installs by surface and by where they came from; the share of accounts on each version; how often each skill, command, agent, hook and MCP server is used; load errors by Claude Code version, and the MCP server's tool calls, error rate and latency; and the listing's views, install clicks and installs. The maintainer sees these as totals across accounts, computed once a day. A copy installed with npx, npm or the git marketplace is not counted.
+
 ## Uninstalling
 
 From a terminal in your project:
@@ -448,15 +494,17 @@ See [`docs/extending.md`](./docs/extending.md) for adding layouts, templates, an
 
 Issues and discussions: https://github.com/SmartAndPoint/ProjectStore/issues. PRs welcome — adding a layout is a good first contribution (see `scaffold/layouts/engineering.json` for the format).
 
-The published package has no dependencies; the linter and the formatter are dev-only, pinned in `package-lock.json`. Every pull request runs the tests, ESLint and Prettier:
+The published package has no dependencies. The linter and the formatter are dev-only and live in a package of their own, `tools/lint/`, pinned in its `package-lock.json`. The repository root has no lockfile, because Claude Code installs whatever a lockfile at a plugin's root names into every user's copy. Every pull request runs the tests, ESLint and Prettier:
 
 ```sh
 npm test              # Node 20+, no install needed
-npm ci                # once, for the lint tools (Node 20.19+, 22.13+ or 24+)
+npm run lint:setup    # once per checkout, for the lint tools (Node 20.19+, 22.13+ or 24+)
 npm run lint
 npm run format        # rewrites; npm run format:check only reports
 ```
 
+Editors find the config at the root; point their tool path at the pinned copies — in VS Code, `"eslint.nodePath": "tools/lint/node_modules"` and `"prettier.prettierPath": "tools/lint/node_modules/prettier"`.
+
 One formatting-only commit is listed in `.git-blame-ignore-revs`. GitHub skips it in blame by itself; a local clone needs this once:
 
 ```sh
@@ -469,7 +517,7 @@ A branch opened before that commit rebases in two steps, so that the lint fixes
 git rebase <the commit before it>
 ```
 
-Then onto the formatting commit itself, where every conflict is formatting only: take your side, format the file with `npx prettier --write <file>` and `git add` it, then continue.
+Then onto the formatting commit itself, where every conflict is formatting only: take your side, format the file with `npm run format` and `git add` it, then continue.
 
 ```sh
 git rebase --onto <it> <the commit before it>

package/node_modules/projectstore/agents/archaeologist.md

@@ -1,6 +1,6 @@
 ---
 name: archaeologist
-description: Opus (max-effort) decision archaeologist for brownfield onboarding. Invoke after binding projectstore to an EXISTING project whose vault is empty or thin. Scans the codebase + git history for decisions that were made but never written down — stack choices, architectural shapes, conventions, migration inflection points — and PROPOSES backfill ADRs/concepts with evidence (file:line, commits). Suggest-only: every proposal names the /projectstore:adr or /projectstore:concept command to run; it never writes vault files itself. Read-only, deduplicates against existing artifacts first.
+description: "Opus (max-effort) decision archaeologist for brownfield onboarding. Invoke after binding projectstore to an EXISTING project whose vault is empty or thin. Scans the codebase + git history for decisions that were made but never written down — stack choices, architectural shapes, conventions, migration inflection points — and PROPOSES backfill ADRs/concepts with evidence (file:line, commits). Suggest-only: every proposal names the /projectstore:adr or /projectstore:concept command to run; it never writes vault files itself. Read-only, deduplicates against existing artifacts first."
 model: opus
 effort: max
 tools: Read, Grep, Glob, Bash

package/node_modules/projectstore/agents/librarian.md

@@ -1,6 +1,6 @@
 ---
 name: librarian
-description: Opus (max-effort) semantic vault curator for projectstore vaults. Invoke periodically, before releases, or after heavy vault growth — AFTER running /projectstore:doctor (doctor catches mechanical drift; librarian catches SEMANTIC drift that no deterministic rule can). Finds duplicate or contradicting artifacts (research vs an accepted ADR), missing wiki-links between related ADRs/epics/research, misplaced or misnamed files, and archive candidates. Read-only, suggest-only, no sycophancy: it reports concrete curation proposals; every fix goes through the normal approval-gated commands.
+description: "Opus (max-effort) semantic vault curator for projectstore vaults. Invoke periodically, before releases, or after heavy vault growth — AFTER running /projectstore:doctor (doctor catches mechanical drift; librarian catches SEMANTIC drift that no deterministic rule can). Finds duplicate or contradicting artifacts (research vs an accepted ADR), missing wiki-links between related ADRs/epics/research, misplaced or misnamed files, and archive candidates. Read-only, suggest-only, no sycophancy: it reports concrete curation proposals; every fix goes through the normal approval-gated commands."
 model: opus
 effort: max
 tools: Read, Grep, Glob, Bash

package/node_modules/projectstore/agents/planner.md

@@ -1,6 +1,6 @@
 ---
 name: planner
-description: Opus (max-effort) EPIC-IMPLEMENTATION planner for projectstore-bound projects — a narrow, vault-aware role, NOT a general software planner. Invoke BEFORE implementing an epic/story. Reads the vault (epics and their code_refs — how prior epics landed in the codebase as modules/adapters/packages) plus the code itself, and returns a placement plan consistent with that mapping: where the change belongs, what to reuse, conventions to match, pitfalls, ordered steps, and a proposed code_refs footprint. Read-only: it plans and proposes; it never writes code or vault files.
+description: "Opus (max-effort) EPIC-IMPLEMENTATION planner for projectstore-bound projects — a narrow, vault-aware role, NOT a general software planner. Invoke BEFORE implementing an epic/story. Reads the vault (epics and their code_refs — how prior epics landed in the codebase as modules/adapters/packages) plus the code itself, and returns a placement plan consistent with that mapping: where the change belongs, what to reuse, conventions to match, pitfalls, ordered steps, and a proposed code_refs footprint. Read-only: it plans and proposes; it never writes code or vault files."
 model: opus
 effort: max
 tools: Read, Grep, Glob, Bash, WebFetch

package/node_modules/projectstore/commands/doctor.md

@@ -32,7 +32,7 @@ You are running projectstore diagnostics (ADR-005: umbrella doctor).
      binding, leaves the vault shared and unchanged, carries no session state.
      Do not offer a fresh `bind <vault-path>` here — binding a second vault by
      hand is exactly what this finding exists to prevent.
-   - `vault-git` → offer `git init` (+ optional first commit) inside the vault.
+   - `vault-git` → offer `git init` inside the vault.
    - `gitignore` → offer appending the missing entries via Edit.
    - `agents-block` duplicate or stale → show the finding, then (after approval)
      run `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" install --harness claude-code --surface agents_block --project "${CLAUDE_PROJECT_DIR}"`
@@ -69,9 +69,10 @@ You are running projectstore diagnostics (ADR-005: umbrella doctor).
      it if it is yours, or delete it yourself to let `install` take the name.
      The verbs refuse it in code; this clause is the belt.
    - `version-drift` → report only: name both versions and where each was
-     read; the fix is the host's update path (`/plugin update` for a git-marketplace
-     copy; for the npm registration, the package's `upgrade` from a terminal
-     in the project — the `plugin-registration` finding spells the command),
+     read; the fix is the host's update path (for a git-marketplace copy,
+     open `/plugin manage` and choose **Update now** on projectstore; for
+     the npm registration, the package's `upgrade` from a terminal in the
+     project — the `plugin-registration` finding spells the command),
      not ours.
    - `layout-legacy` (warn; the startup line carries it as an offer) → the project
      still holds the pre-0.28 layout (`.claude/projectstore.json`,
@@ -138,11 +139,13 @@ You are running projectstore diagnostics (ADR-005: umbrella doctor).
      host registry naming our marketplace elsewhere. Print the finding verbatim;
      the user moves or removes it.
    - `harness` (info) → nothing to repair; it names what `install` can target.
-   - `mcp` → the plugin-bundled `.mcp.json` is missing or does not launch
-     `bin/projectstore.mjs mcp`: the install is incomplete — the fix is the
-     update for the channel this copy was installed through (`/plugin update`
-     for a git-marketplace copy; for the npm registration, the package's
-     `upgrade` from a terminal in the project, outside this session — the
+   - `mcp` → the plugin-bundled `.mcp.json` is missing, does not launch
+     `scripts/mcp-server.mjs`, or launches it from a plugin root without the
+     file: the install is incomplete — the fix is the
+     update for the channel this copy was installed through (for a
+     git-marketplace copy, open `/plugin manage` and choose **Update now** on
+     projectstore; for the npm registration, the package's `upgrade` from a
+     terminal in the project, outside this session — the
      `plugin-registration` finding spells the command), never a hand-written
      file.
    - `override-copies` → a copy carrying the provenance marker overrides nothing
@@ -154,8 +157,8 @@ You are running projectstore diagnostics (ADR-005: umbrella doctor).
    - `auto-update` off → offer adding `extraKnownMarketplaces.<marketplace>.autoUpdate: true`
      to `~/.claude/settings.json` (Edit with diff preview + approval — this is the
      user's global settings file), or point at `/plugin` → Marketplaces → toggle.
-     For "newer version available" → tell the user to run
-     `/plugin marketplace update <marketplace>` and `/reload-plugins` themselves.
+     For "newer version available" → tell the user to open `/plugin manage` and
+     choose **Update now** on projectstore, then run `/reload-plugins` themselves.
 
    **Boundary (ADR-005)**: `--fix` never repairs vault-side findings. For those,
    point at `/projectstore:kanban` (board regen) and `/projectstore:reconcile`

package/node_modules/projectstore/commands/reconcile.md

@@ -39,7 +39,7 @@ You are reconciling the vault's derived views with their source of truth (frontm
    When the approved set contains two or more targets, hand steps 6-7 to
    `projectstore:clerk`: pass the exact selector list from step 4's preview and
    the expectation that doctor ends clean. **Model and effort (ADR-008)**: resolve
-   them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model clerk --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter (`null` → pass nothing), and `result.effort` as its effort parameter when it is not `null` and the spawn offers one;
+   them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model clerk --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter, verbatim — never substitute the model you are running on (`null` → pass nothing), and `result.effort` as its effort parameter when it is not `null` and the spawn offers one;
    missing key, `inherit`, or unreadable config → pass nothing and let the
    agent's own frontmatter decide; never guess a model. The clerk applies
    through the core exactly as step 6 specifies and reports per target. A single

package/node_modules/projectstore/commands/review.md

@@ -23,7 +23,7 @@ You are running a peer review on a projectstore artifact.
 
 5. **Gather domain context**: read the vault's top-level `README.md` and the folder README of the artifact's parent (e.g. `adr/README.md`). Keep both short — they're context for the critic, not the focus.
 
-6. **Spawn the critic agent**. Prefer this plugin's own `projectstore:critic` (purpose-built fresh-context critic, no sycophancy). If unavailable, fall back to `oh-my-claudecode:critic`, then `general-purpose`. Use this exact prompt template:
+6. **Spawn the critic agent**. Prefer this plugin's own `projectstore:critic` (purpose-built fresh-context critic, no sycophancy). If unavailable, fall back to `general-purpose`. Use this exact prompt template:
 
    ```
    You are a critic-mode reviewer. You have ONLY the artifact and the
@@ -64,7 +64,7 @@ You are running a peer review on a projectstore artifact.
 
    Set the agent description to: `Peer-review of {{kind}} artifact at {{path}}`. Pass it as a foreground task (you need the result to continue).
 
-   **Model and effort (ADR-008)**: resolve them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model critic --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter (`null` → pass nothing), and `result.effort` as its effort parameter when it is not `null` and the spawn offers one. Missing key, `inherit`, or unreadable config → pass nothing and let the agent's own frontmatter decide; never guess a model. This is the only way the configured model and effort reach the agent — there are no override copies (`/projectstore:agents configure`). When falling back to `oh-my-claudecode:critic` or `general-purpose`, pass the same model and effort.
+   **Model and effort (ADR-008)**: resolve them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model critic --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter, verbatim — never substitute the model you are running on (`null` → pass nothing), and `result.effort` as its effort parameter when it is not `null` and the spawn offers one. Missing key, `inherit`, or unreadable config → pass nothing and let the agent's own frontmatter decide; never guess a model. This is the only way the configured model and effort reach the agent — there are no override copies (`/projectstore:agents configure`). When falling back to `general-purpose`, pass the same model and effort.
 
 7. **Show findings**: print the agent's report verbatim. Number is its number.
 

package/node_modules/projectstore/commands/story.md

@@ -80,7 +80,7 @@ the two cannot collide).
      files with different jobs: the scratch is what gets copied to the target;
      the baseline is what `--check` compares against. Handing `--check` the
      scratch makes it report drift on every run.
-   - **Model and effort (ADR-008)**: resolve them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model clerk --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter (`null` → pass nothing),
+   - **Model and effort (ADR-008)**: resolve them with `node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" agents model clerk --json --project "${CLAUDE_PROJECT_DIR}"` and pass `result.model` as the spawn's model parameter, verbatim — never substitute the model you are running on (`null` → pass nothing),
      and `result.effort` as its effort parameter when it is not `null` and the spawn offers one.
      Missing key, `inherit`, or unreadable config → pass nothing and let the
      agent's own frontmatter decide; never guess a model.

package/node_modules/projectstore/docs/getting-started.md

@@ -14,7 +14,7 @@ The next two sections are the other ways in: a checkout, for contributors, and t
 
 ## From a checkout
 
-For contributors working on projectstore itself. Clone it; [Running a checkout's build](../packaging/README.md#running-a-checkouts-build) covers the packed form.
+For contributors working on projectstore itself. Clone it; [Running a checkout's build](https://github.com/SmartAndPoint/ProjectStore/blob/main/packaging/README.md#running-a-checkouts-build) covers the packed form.
 
 ```bash
 git clone https://github.com/SmartAndPoint/ProjectStore.git ~/Projects/SmartAndPoint/ProjectStore
@@ -172,11 +172,10 @@ Installed with setup or from npm: from a terminal in your project, name the vers
 npx projectstore@<version> upgrade
 ```
 
-Installed from the git marketplace, in a Claude Code session:
+Installed from the git marketplace: in a Claude Code session, open `/plugin manage` and choose **Update now** on projectstore, then run `/reload-plugins` to load it. Or, from a terminal, then restart Claude Code:
 
 ```
-/plugin marketplace update SmartAndPoint
-/reload-plugins
+claude plugin update projectstore@SmartAndPoint
 ```
 
 Or enable auto-update once (`/plugin` → **Marketplaces** → **SmartAndPoint** → toggle **auto-update**) and Claude Code will detect new releases at startup.

package/node_modules/projectstore/docs/harnesses.md

@@ -93,7 +93,7 @@ Installation is user-global because Codex stores marketplace registrations and
 plugin caches in `CODEX_HOME`; the agents block in `AGENTS.md` remains
 project-local. Ordinary uninstall leaves the global plugin in place; add
 `--global` only when you mean to remove it for every project. A checkout's own
-build runs through the same flow: [`packaging/README.md`](../packaging/README.md#running-a-checkouts-build)
+build runs through the same flow: [`packaging/README.md`](https://github.com/SmartAndPoint/ProjectStore/blob/main/packaging/README.md#running-a-checkouts-build)
 has the tarball loop.
 
 `npx projectstore configure` changes Codex's settings as it does Claude Code's.

package/node_modules/projectstore/harnesses/claude-code.json

@@ -297,7 +297,7 @@
       "kind": "exclusive",
       "format": "mjs",
       "scope": "project",
-      "scope_reason": "The launcher resolves the currently installed plugin on every render, so the wired command carries no version; it is written only when the plugin runs from the marketplace cache — a dev checkout is wired directly.",
+      "scope_reason": "The launcher resolves the currently installed plugin on every render, so the wired command carries no version; it is written only when the plugin runs from a host install — the marketplace cache, or the folder Claude Code syncs a claude.ai copy into (registry.synced_dir), whose path may change or vanish — a dev checkout is wired directly. The condition key keeps its name, plugin_cache_install.",
       "file": ".projectstore/state/claude-code/statusline.mjs",
       "source": "scripts/statusline-launcher.mjs",
       "condition": "plugin_cache_install",
@@ -309,6 +309,8 @@
       "kind": "host",
       "dir": ".",
       "file": ".mcp.json",
+      "entry": "scripts/mcp-server.mjs",
+      "entry_reason": "The script .mcp.json runs, under the plugin root, with --project and the host's project directory as its only arguments. It lives under scripts/, never bin/ (a plugin's top-level bin/ is on the host's Bash PATH), and imports nothing from cli.mjs, so the server's imports reach no install verb (PS-DIRECTORY, the story \"The MCP server's entry reaches no install verb through a read-verb runner that shares the CLI's verb table…\"; the MCP ADR's decision 1 as amended). The CLI's `mcp` verb serves the same way, for a host without a plugin channel.",
       "scope": "plugin",
       "scope_reason": "Claude Code loads a plugin's .mcp.json from the plugin installation itself and expands ${CLAUDE_PLUGIN_ROOT} and ${CLAUDE_PROJECT_DIR} in it per session, so the one shipped file binds each server to one project (MCP ADR decision 6, amended 2026-09-05); nothing is installed and nothing is derived — the host kind install-harness skips, which the install spec's contract 0 does not yet name.",
       "launch": {
@@ -383,7 +385,44 @@
         ],
         "enabled_pointer": "enabledPlugins",
         "known_pointer": "extraKnownMarketplaces",
-        "install_path_layout": "<cache_dir>/<marketplace>/<plugin>/<version>"
+        "install_path_layout": "<cache_dir>/<marketplace>/<plugin>/<version>",
+        "synced_dir": [
+          "plugins",
+          "synced"
+        ],
+        "synced_origin": "synced",
+        "sync_setting": "syncClaudeAiPlugins",
+        "trash_dir": [
+          "plugins",
+          ".trash"
+        ],
+        "synced_reason": "A plugin on the person's claude.ai account (added from Anthropic's directory, or turned on by their organization) loads as <plugin>@synced, with no marketplace and no install record, and its files sit in <synced_dir>/<bucket>/<plugin>/ (code.claude.com/docs/en/plugins/loading, \"Plugins synced from claude.ai\"; the bucket layout measured 2026-10-15, undocumented). installChannel answers \"synced\" for a root there from the path alone; the copy's version is read from its own .claude-plugin/plugin.json, never from the bucket's manifest.json, whose version is claude.ai's string. It is on unless a settings file sets <plugin>@synced to false, and an enabled copy of the same name from any other origin loads over it (the loading reference, \"Name conflicts\", item 5). With sync_setting false in the user's settings, Claude Code moves the synced copies to trash_dir at its next start and stops loading them. CLAUDE_CODE_PLUGIN_CACHE_DIR moves the whole plugins root and is not read: a known gap, as for cache_dir.",
+        "marketplaces_claudeai": [
+          "plugins",
+          "known_marketplaces_claudeai.json"
+        ],
+        "claudeai_prefix": "claudeai-",
+        "claudeai_reason": "A marketplace added from claude.ai is registered under a local name that starts with claudeai- and is recorded in known_marketplaces_claudeai.json instead of known_marketplaces.json (code.claude.com/docs/en/plugins/install, \"Add a marketplace from claude.ai\"; the loading reference, \"Find plugins on disk\"). It is added again from /plugin → Marketplaces, never by a source.",
+        "auto_update": {
+          "on": [
+            "claude-plugins-official",
+            "claude-code-marketplace",
+            "claude-code-plugins",
+            "anthropic-marketplace",
+            "anthropic-plugins",
+            "agent-skills",
+            "anthropic-agent-skills",
+            "life-sciences",
+            "claude-for-legal",
+            "claude-for-financial-services",
+            "financial-services-plugins",
+            "claude-tag-plugins"
+          ],
+          "on_prefix": [
+            "claudeai-"
+          ],
+          "reason": "Whether a marketplace auto-updates when neither its extraKnownMarketplaces entry in a settings file nor its registry entry sets autoUpdate (the loading reference, \"Which marketplaces and plugins auto-update\", read 2026-10-15): on for Anthropic's official marketplace names (code.claude.com/docs/en/plugins/security#official-marketplace-names) except knowledge-work-plugins and first-party-plugins, on for a marketplace added from claude.ai, off for every other marketplace."
+        }
       },
       "cli": {
         "bin": "claude",
@@ -507,18 +546,28 @@
     ],
     "by_channel": {
       "marketplace": {
-        "line": "See /plugin → Marketplaces to enable auto-update.",
+        "line": "Updates come through the {marketplace} marketplace, whose auto-update is {auto_update} by default: /plugin → Marketplaces → {marketplace} turns it on or off.",
         "welcome": [
-          "**About future updates**: Claude Code does NOT auto-update third-party marketplaces by default. To get notified of new releases (v0.7+):",
+          "**About future updates**: this copy comes from the **{marketplace}** marketplace. Claude Code updates it in the background while that marketplace's auto-update is on, and for {marketplace} auto-update is **{auto_update}** by default. To check it:",
           "1. Open `/plugin` → **Marketplaces** tab.",
-          "2. Find **SmartAndPoint**.",
-          "3. Toggle **auto-update** on.",
+          "2. Find **{marketplace}**.",
+          "3. Make sure **auto-update** is on.",
           "",
-          "Without it, you'd run `/plugin marketplace update SmartAndPoint` manually. See https://github.com/SmartAndPoint/ProjectStore#upgrading for details."
+          "Without it, open `/plugin manage` and choose **Update now** on projectstore when a new version is out."
+        ]
+      },
+      "synced": {
+        "line": "Updates come from claude.ai: Claude Code downloads each new version at its next start, then asks for /reload-plugins. Off for your account on this machine: /plugin → Installed. Off for one project only: \"projectstore@synced\": false under enabledPlugins in that project's .claude/settings.local.json.",
+        "welcome": [
+          "**About future updates**: this copy comes from Anthropic's plugin directory, through your claude.ai account, and Claude Code loads it as `projectstore@synced`. Updates come from claude.ai: when a new version is published, Claude Code downloads it at its next start and asks you to run `/reload-plugins`.",
+          "",
+          "- **Off for your account on this machine**: `/plugin` → **Installed**, then turn off `projectstore@synced`.",
+          "- **Off for one project only**: set `\"projectstore@synced\": false` under `enabledPlugins` in that project's `.claude/settings.local.json`, or in its committed `.claude/settings.json` to keep it out for everyone who opens the project.",
+          "- **Removed**: on claude.ai, where it was added."
         ]
       }
     },
-    "reason": "What the first-run welcome and its one-line notice say about updates (generation spec, contract 18): `line` ends the notice, `welcome` is the welcome's update block, and `{upgrade}` is filled with the core's upgrade for this harness at latest, so what is printed runs as printed. `by_channel` holds the text for a copy that loads from another channel, by installChannel's answer: a copy from the git marketplace is updated by Claude Code itself, so its welcome keeps the auto-update toggle; the npm registration and a checkout get the npm form. update_instructions is the long-form guidance; this is the part a session prints, kept here so no hook names a harness's update path."
+    "reason": "What the first-run welcome and its one-line notice say about updates (generation spec, contract 18): `line` ends the notice, `welcome` is the welcome's update block, and `{upgrade}` is filled with the core's upgrade for this harness at latest, so what is printed runs as printed. `by_channel` holds the text for a copy that loads from another channel, by installChannel's answer: a marketplace copy is updated by Claude Code itself, so its welcome names that marketplace's auto-update toggle, with `{marketplace}` filled from the copy's own path and `{auto_update}` with its default (on or off, registry.auto_update); a copy synced from claude.ai (Anthropic's directory) is updated by claude.ai and names no npm, upgrade or marketplace command, only the two ways to turn it off (the story \"A copy installed from Anthropic's directory is a channel the core knows…\", PS-DIRECTORY); the npm registration and a checkout get the npm form. update_instructions is the long-form guidance; this is the part a session prints, kept here so no hook names a harness's update path."
   },
   "update_instructions": [
     "**About future updates**: installed from the git marketplace, Claude Code does NOT auto-update third-party marketplaces by default; an npm registration updates with `npx projectstore@<version> upgrade` from a terminal in the project. To get notified of new git-marketplace releases (v0.7+):",
@@ -526,7 +575,7 @@
     "2. Find **SmartAndPoint**.",
     "3. Toggle **auto-update** on.",
     "",
-    "Without it, you would run `/plugin marketplace update SmartAndPoint` manually. See https://github.com/SmartAndPoint/ProjectStore#upgrading for details.",
+    "Without it, open `/plugin manage` and choose **Update now** on projectstore when a new version is out. See https://github.com/SmartAndPoint/ProjectStore#upgrading for details.",
     "",
     "**Upgrading from 0.27.x to 0.28**: restart after the update, then move the project's files to `.projectstore/` with the one command the first session names, run from a terminal in the project, outside the session. For a git-marketplace install it is the installed copy's own `bin/projectstore.mjs` with `upgrade --harness claude-code --no-register`, which leaves the registration as it is. For the npm registration it is `npx projectstore@<version> upgrade --harness claude-code --no-register` and nothing else. The same run re-stamps the status-line launcher, and until then every reader falls back to the old paths. `status` and `search` answer from artifact facts; `doctor` gains surface, version-drift and mcp lines and exits 1 on findings; the plugin registers an MCP server the host may ask you to approve once. On 0.28.0-rc.1 or rc.2, update first: their startup line named the form without `--no-register`, which also switches a git-marketplace install to npm for the checkout (the README's Upgrading section has the way back). Before the move, a rollback to 0.27.x keeps working and the move is the way forward again; after the move, 0.27.x reads the project as unbound."
   ],
@@ -600,30 +649,8 @@
           "description": "Follows the newest Haiku model: Claude Code resolves the alias when it starts the agent."
         }
       ],
-      "static_reason": "The enum above, in the order the menu lists it. A line the catalog below reports that this list lacks is never offered: a Claude Code release that adds an alias is named with `--set`, with the warning, until this list learns it.",
-      "catalogs": [
-        {
-          "kind": "http",
-          "source": "the Anthropic API",
-          "caption": "Anthropic API",
-          "url": "https://api.anthropic.com/v1/models?limit=1000",
-          "base_env": "ANTHROPIC_BASE_URL",
-          "path": "/v1/models?limit=1000",
-          "key_env": "ANTHROPIC_API_KEY",
-          "key_header": "x-api-key",
-          "headers": { "anthropic-version": "2023-06-01" },
-          "fields": {
-            "list": "data",
-            "id": "id",
-            "label": "display_name",
-            "family": "line",
-            "order": "created_at",
-            "order_desc": true,
-            "keep_when": { "lifecycle": "active" }
-          },
-          "reason": "Measured 2026-10-13: 14 models in 0.5–0.7 s, each with id, display_name, created_at, line (fable, opus, sonnet, haiku) and lifecycle. `line` is the family an alias follows, so the newest active entry of a line is the best local account of what that alias starts; Claude Code resolves the alias itself. Read only when a model list opens with a stale cache, or on refresh, and only with ANTHROPIC_API_KEY set; ANTHROPIC_BASE_URL, when set, is the base the key belongs to."
-        }
-      ]
+      "static_reason": "The enum above, in the order the menu lists it. It is the whole list: Anthropic's model list takes a key, and ProjectStore reads no credential from the environment (the 0.30.7 story, PS-DIRECTORY), so no catalog is declared and the menu asks nothing. A Claude Code release that adds an alias is named with `--set`, with the warning, until this list learns it.",
+      "catalogs": []
     }
   }
 }

package/node_modules/projectstore/hooks/hooks.json

@@ -6,11 +6,11 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/session-start.mjs\""
           },
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/session-rules.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/session-rules.mjs\""
           }
         ]
       }
@@ -20,7 +20,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/touch-session.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/touch-session.mjs\""
           }
         ]
       }
@@ -31,7 +31,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/scripts/touch-session.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/touch-session.mjs\""
           }
         ]
       }
@@ -41,7 +41,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/session-stop.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/session-stop.mjs\""
           }
         ]
       }
@@ -51,7 +51,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/pre-compact.mjs"
+            "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/pre-compact.mjs\""
           }
         ]
       }