projectstore-claude 0.29.3 → 0.29.4

package/bin/projectstore-claude.mjs

@@ -24,7 +24,7 @@ const HARNESS = "claude-code";
 // scripts/cli.mjs; the packaging test pins it). Any other verb — doctor,
 // status, search, --version — passes through untouched: the core refuses an
 // option a verb does not declare, so a blanket insert would break `doctor`.
-const HARNESS_VERBS = new Set(["plan","install","uninstall","upgrade","agents"]);
+const HARNESS_VERBS = new Set(["setup","plan","install","uninstall","upgrade","agents"]);
 
 // The bundled core, by path — never by package resolution: a hoisted or global
 // copy at another version is exactly the pairing the pin exists to prevent,

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

@@ -12,7 +12,7 @@
       "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.29.3",
+      "version": "0.29.4",
       "author": {
         "name": "Evgenii Konev",
         "email": "ekonev@smartandpoint.com",

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

@@ -1,7 +1,7 @@
 {
   "name": "projectstore",
   "displayName": "projectstore",
-  "version": "0.29.3",
+  "version": "0.29.4",
   "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",

package/node_modules/projectstore/README.md

@@ -307,6 +307,23 @@ 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:
+
+```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
+npm run format        # rewrites; npm run format:check only reports
+```
+
+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
+git config blame.ignoreRevsFile .git-blame-ignore-revs
+```
+
+A branch opened before that commit rebases in two steps, so that the lint fixes before it are kept: `git rebase <the commit before it>` (real conflicts, resolved as usual), then `git rebase --onto <it> <the commit before it>`, where every conflict is formatting only: take your side, run `npx prettier --write <file>`, `git add` it and continue.
+
 ## License
 
 MIT — see [`LICENSE`](./LICENSE).

package/node_modules/projectstore/commands/bind.md

@@ -3,7 +3,7 @@ description: Bind this project to an Obsidian vault (or any markdown directory)
 argument-hint: <vault-path> | --inherit [--layout engineering] [--lang en|ru|es|de|fr|zh]
 ---
 
-You are binding the current project to a markdown vault for projectstore. The config is written by the core's `bind` / `init` verbs (roadmap A8); this interview decides the values, previews them, and asks — it never writes `projectstore.json` itself, except on the inherit path (step 0a), which copies the parent's file verbatim, and the two later stamps in steps 11–12 (`autoupdate_asked`, `statusline`), which `Edit` the file the verb wrote. The interview's `--lang` is the verb's `--language`.
+You are binding the current project to a markdown vault for projectstore. The config is written by the core's `bind` / `init` verbs (roadmap A8); this interview decides the values, previews them, and asks — it never writes `projectstore.json` itself, except on the inherit path (step 0a), which copies the parent's file verbatim, and the one later stamp in step 11 (`statusline`), which `Edit`s the file the verb wrote. The interview's `--lang` is the verb's `--language`.
 
 Parse `$ARGUMENTS`:
 - First positional arg: vault path. Expand `~` if present.
@@ -48,10 +48,10 @@ Steps:
 
    It prints `{state, worktree, mainCheckout, vaultPath}` and writes nothing.
    - `state` is **not** `inheritable` → say why in one line (not a worktree, its parent is unbound too, or git could not answer) and fall through to step 1, which needs a vault path; if none was given, ask for one.
-   - `state` is `inheritable` → read the parent's `<mainCheckout>/.projectstore/projectstore.json` (or, in a checkout not yet migrated, the legacy `<mainCheckout>/.claude/projectstore.json`), show it **verbatim as a code block** — but for a `channel_switch` key, which is left out (below) — and ask via AskUserQuestion: "Adopt the binding of `<mainCheckout>` (vault `<vaultPath>`)?" — Yes / No.
-   - On **Yes**: Write that JSON verbatim, without `channel_switch`, to `<project>/.projectstore/projectstore.json`, **and write `<project>/.projectstore/.gitignore` beside it** with the two lines `projectstore.json` and `state/` under a comment saying they are machine-local (the verb writes them itself on every other path; this one bypasses the verb, and without them the worktree commits an absolute vault path into the index it shares with its parent). If that file already exists, add any missing line and leave the rest — it is line-merged. Then **jump straight to step 10** (the summary). Steps 1–9 and 11–12 are decisions the parent already made and the copied config already carries — layout, language, statusline, agent models, auto-update. Do not re-ask them, and do not scaffold: the vault exists and is shared.
+   - `state` is `inheritable` → read the parent's `<mainCheckout>/.projectstore/projectstore.json` (or, in a checkout not yet migrated, the legacy `<mainCheckout>/.claude/projectstore.json`), show it **verbatim as a code block** — but for the `channel_switch` and `channel_keep` keys, which are left out (below) — and ask via AskUserQuestion: "Adopt the binding of `<mainCheckout>` (vault `<vaultPath>`)?" — Yes / No.
+   - On **Yes**: Write that JSON verbatim, without `channel_switch` and `channel_keep`, to `<project>/.projectstore/projectstore.json`, **and write `<project>/.projectstore/.gitignore` beside it** with the two lines `projectstore.json` and `state/` under a comment saying they are machine-local (the verb writes them itself on every other path; this one bypasses the verb, and without them the worktree commits an absolute vault path into the index it shares with its parent). If that file already exists, add any missing line and leave the rest — it is line-merged. Then **jump straight to step 10** (the summary). Steps 1–9 and 11 are decisions the parent already made and the copied config already carries — layout, language, statusline, agent models. Do not re-ask them, and do not scaffold: the vault exists and is shared.
    - Copy the **binding only** (`projectstore.json`). Never copy `.projectstore/state/` — per-session state belonging to the other checkout — and never `harness/`: the overlays are committed and arrive from git.
-   - **Never copy `channel_switch`.** It records that the parent checkout was switched to the npm install — a machine-local fact of that checkout, not of the binding it shares. Every other key is copied verbatim.
+   - **Never copy `channel_switch` or `channel_keep`.** They record which channel the parent checkout chose — switched to the npm install, or kept on the git marketplace — a machine-local fact of that checkout's own registry rows, not of the binding it shares. Every other key is copied verbatim.
    - Do not add a provenance key to the config. The parent is resolvable from git at any time; a key would be a second source of truth for the same fact.
 
 1. **Validate the vault path** read-only first: `ls -A "<path>"` (the verb has no dry run — running it on a fresh project would write the config before step 4's approval). If it does not exist, or exists and is empty, ask the user (via AskUserQuestion) whether to create the vault there; on Yes, step 5 runs `init` instead of `bind`. `init` creates the whole vault and binds: the directory (unless it is there and empty), its git repository with no commit, and the layout's folders and READMEs. Never `mkdir` it yourself. A directory that already holds files is bound with `bind`; `init` would bind it too, but never scaffolds or `git init`s inside it.
@@ -81,7 +81,7 @@ Steps:
    node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" bind "<vault-path>" [--layout <name>] [--language <code>] [--rebind]
    ```
 
-   `init "<vault-path>" …` instead when step 1 chose to create the vault — it creates the whole vault, so step 7 has nothing to offer after it; `--rebind` only when step 0 ended on **Replace bind**. Naming the vault is the verb's confirmation (there is no `--yes`); the interview's AskUserQuestion in step 4 is the in-session gate. Print the verb's output. A non-zero exit is a refusal or a usage error — relay it and stop — except an `init` whose output reports `git init failed` or `Scaffold failed`: the binding is written, so relay the remedy line it prints and continue. Steps 11 and 12 below `Edit` the file this step wrote; keep them after it.
+   `init "<vault-path>" …` instead when step 1 chose to create the vault — it creates the whole vault, so step 7 has nothing to offer after it; `--rebind` only when step 0 ended on **Replace bind**. Naming the vault is the verb's confirmation (there is no `--yes`); the interview's AskUserQuestion in step 4 is the in-session gate. Print the verb's output. A non-zero exit is a refusal or a usage error — relay it and stop — except an `init` whose output reports `git init failed` or `Scaffold failed`: the binding is written, so relay the remedy line it prints and continue. Step 11 below `Edit`s the file this step wrote; keep it after it.
 
 6. **Check `.gitignore`**: read `<project>/.gitignore` if it exists. Our own files are self-ignored inside `.projectstore/` — the verb writes that `.gitignore` itself, carrying `projectstore.json` and `state/`, with `harness/` committed on purpose (the layout ADR); on the inherit path of step 0a, which bypasses the verb, you wrote both by hand. Unless `.claude/` is ignored wholesale, the one machine-specific entry left is the host's `.claude/settings.local.json`. If it is missing, offer (AskUserQuestion) to append it. If the user declines, skip silently.
 
@@ -115,18 +115,7 @@ Steps:
 
 10. **Print summary**: confirm the bind, list the layout's folders, suggest next commands (`/projectstore:status`, `/projectstore:adr "<first decision>"`, `/projectstore:epic <ID> "<title>"`).
 
-11. **Auto-update reminder** (v0.7+, only on first successful bind in this project): After Step 5 (config write), check whether the newly-written config has `autoupdate_asked: true`. If not, ask the user via AskUserQuestion:
-
-   > "Claude Code does not auto-update third-party marketplaces by default. Want to enable auto-update for the SmartAndPoint marketplace so you'll be notified about future projectstore releases?"
-
-   Options:
-   - **Yes, show me how** (Recommended) — respond with: "Open `/plugin` → **Marketplaces** tab → **SmartAndPoint** → toggle **auto-update** on. New releases (v0.7+) will be detected at Claude Code startup; you'll need to run `/reload-plugins` after the notification to activate them."
-   - **No, I'll handle it manually** — respond with: "OK. To pull the latest version at any time, run `/plugin marketplace update SmartAndPoint`, then `/reload-plugins`."
-   - **Already enabled** — respond with: "Great. New releases will be detected at the next Claude Code startup."
-
-   After the question is answered (regardless of choice), Edit `<project>/.projectstore/projectstore.json` to add `"autoupdate_asked": true` to the JSON object. This guarantees we ask only once per project.
-
-12. **Status line offer** (v0.13, ADR-006 — the final step, language is known by now): read `${CLAUDE_PLUGIN_ROOT}/templates/<lang>/strings.json` (fall back to `en`) and the plugin version, then show the fully rendered example:
+11. **Status line offer** (v0.13, ADR-006 — the final step, language is known by now): read `${CLAUDE_PLUGIN_ROOT}/templates/<lang>/strings.json` (fall back to `en`) and the plugin version, then show the fully rendered example:
 
     > `[PS#<version>] 📚 <statusline_example_epic> › <statusline_example_story> (in-progress)`
 

package/node_modules/projectstore/commands/doctor.md

@@ -66,20 +66,25 @@ You are running projectstore diagnostics (ADR-005: umbrella doctor).
      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 `projectstore-claude` shell's `upgrade`
-     from a terminal — the `plugin-registration` finding spells the command),
+     copy; 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`,
-     `.claude/.projectstore/` — legacy, read through 0.29). The migration is one
+     `.claude/.projectstore/` — legacy, read through 0.30). The migration is one
      previewed `layout` item of `upgrade`, run **from a terminal outside this
      session** (it moves files this session reads and writes; the verb defers
      inside one). The finding names the form for the channel this plugin was
      installed through: the installed copy's own `bin/projectstore.mjs` for a
-     git-marketplace install or a checkout, the `projectstore-claude` shell for
-     the npm registration. Relay the finding's command verbatim and never
-     substitute the other form — the shell, run for a git-marketplace install,
-     would also move this checkout to the npm channel. When the finding carries
+     git-marketplace install or a checkout, the package's `upgrade` for the npm
+     registration. Relay the finding's command verbatim, with the directory its
+     words name, and never substitute the other form or drop its
+     `--no-register`. Both forms carry that flag, so neither changes the
+     channel: the named form runs the copy this project loads, so the move
+     re-stamps the launcher that copy renders, while the other form runs a
+     different copy. The package's `upgrade` without `--no-register` would
+     register the npm copy and turn a git-marketplace copy off for this
+     checkout. When the finding carries
      advice instead of a command — the installed copy predates the move, or
      predates `--no-register` — relay the advice and never compose a command
      yourself. Never move the files yourself. While this finding is in the report, its command is also the one

package/node_modules/projectstore/commands/statusline.md

@@ -5,7 +5,7 @@ argument-hint: "on | off | status"
 
 You are toggling the projectstore status line for THIS project. When enabled, `install-harness.mjs` points the project's `.claude/settings.local.json` at a launcher it writes at `.projectstore/state/claude-code/statusline.mjs`. That path carries no version, so it never goes stale: the launcher resolves the *currently installed* plugin on every render, and an update is reflected on the spot instead of one restart later. (A dev checkout or `--plugin-dir` root is wired straight to its `scripts/statusline.mjs` — those paths have no version to drift.) The line renders `[PS#<version>] 📚 <epic> › <story> (<status>)` **composed above** any existing HUD (e.g. oh-my-claudecode), never replacing it. While this session's band above the prompt is drawing (`/projectstore:bar`), the line gives way to it — your base HUD stays — and it comes back within 30 s of the band stopping.
 
-Resolution is **per-session with zero cross-session and zero vault reads** (ADR-006): the 📚 segment comes from this session's pointer (`.projectstore/state/sessions/<session_id>.json`, maintained by the PreToolUse hook); a fresh session shows an explicit localized cold-start line ("No epic or story in this session yet" / «Эпик и стори ещё не в работе в этой сессии») — never a silent blank; a corrupt pointer shows an error-marked string. Strings localize via `templates/<lang>/strings.json` (en fallback). The version badge is controlled by `statusline.show_version` (default true).
+Resolution is **per-session with zero cross-session and zero vault reads** (ADR-006): the 📚 segment comes from this session's pointer (`.projectstore/state/sessions/<session_id>.json`, maintained by the tool hooks — a write's patch after the write — by `story close`, and at session start; a done, closed or parked story leaves the segment); a fresh session shows an explicit localized cold-start line ("No epic or story in this session yet" / «Эпик и стори ещё не в работе в этой сессии») — never a silent blank; a corrupt pointer shows an error-marked string. Strings localize via `templates/<lang>/strings.json` (en fallback). The version badge is controlled by `statusline.show_version` (default true).
 
 This command flips the flag in `.projectstore/projectstore.json` and then runs the install verb, which writes `settings.local.json` and the launcher behind a preview. The SessionStart hook only refreshes an entry that is already ours and removes it when the flag is off — it never creates one.
 

package/node_modules/projectstore/commands/story.md

@@ -92,11 +92,11 @@ the two cannot collide).
      <baseline-path>`), the derived targets (`kanban`, plus `indexes=<epic
      folder>` when status changed), and the doctor pre-state line. On a clean
      report (`verbatim: true`, `stopped_at: null`, doctor no worse than the
-     pre-state) skip steps 6-6b — the clerk's report is the write evidence. On a
+     pre-state) skip steps 6-6b and run step 6c — the clerk's report is the write evidence. On a
      stopped report: fix what diverged, then re-delegate (the resume rule: after
      the copy, the ceremony restarts at reconcile, not at the race gate) or
      finish the remaining steps yourself (the copy is idempotent).
-   - No clerk available → perform steps 6-6b yourself. There is no fallback
+   - No clerk available → perform steps 6-6c yourself. There is no fallback
      agent: a general-purpose writer is an unpinned procedure.
 
 6. **On Yes** (undelegated path): Write the full file. On a `plan`, finish by
@@ -111,3 +111,16 @@ the two cannot collide).
    — a close is not done while doctor got worse. Then suggest the reviewer's
    proposed `code_refs` via `/projectstore:codemap set` (the reviewer computes it
    from `scripts/diff-refs.mjs --since <started_at>`).
+
+6c. **(close only, both paths) Refresh this session's story**, here in the
+   main thread, after the clerk's clean report or after 6b:
+
+   ```bash
+   node "${CLAUDE_PLUGIN_ROOT}/bin/projectstore.mjs" session refresh "<story-path>" --json --project "${CLAUDE_PROJECT_DIR}"
+   ```
+
+   `<story-path>` is the absolute `path` the compute script returned in
+   step 2. The copy went through Bash, which no hook sees, so without this the
+   session's band and status line keep naming the closed story. The core finds
+   the session itself; with none it writes nothing and exits 0. A non-zero
+   exit is reported and never undoes the close.

package/node_modules/projectstore/docs/how-it-works.md

@@ -67,8 +67,10 @@ sessions can't silently overwrite each other's new artifact.
 
 **The status line is stricter still**: it renders from a *per-session* pointer
 (`<project>/.projectstore/state/sessions/<session_id>.json`, written by the
-PreToolUse hook with denormalized titles) and performs **zero cross-session and
-zero vault reads**. 2–6 parallel sessions each see exactly their own epic/story;
+tool hooks with denormalized titles — after a write, from the file as written —
+by `story close` through the core, and refreshed at session start) and performs
+**zero cross-session and zero vault reads**. A story that is done, closed or
+parked leaves the line: it shows the epic alone, as the band does. 2–6 parallel sessions each see exactly their own epic/story;
 a fresh session gets a localized "no epic or story in this session yet" line; a
 corrupt pointer shows an error marker, never a false "no work". The renderer also
 drops a `.last-render.json` breadcrumb so `doctor` can detect session-id
@@ -162,7 +164,7 @@ resistance. v0.13 makes that safe instead of forbidden:
   (`--write`): each approved target is recomputed from the vault state at
   write time and replaced atomically, so a stale preview is never what lands;
   `--write` is also a sanctioned headless entry point (cron/CI repair job).
-- A throttled PreToolUse **nudge** fires when vault files are edited directly:
+- A throttled PostToolUse **nudge** fires when vault files are edited directly:
   "run reconcile afterwards so the derived views stay in sync" (disable with
   `"guard": "off"` in `projectstore.json`).
 - A once-per-session **entry reminder** fires on PostToolUse when a session has

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

@@ -134,16 +134,16 @@
       "system_message": true,
       "decision": "permissionDecision",
       "evidence": "measured",
-      "note": "systemMessage measured — scripts/touch-session.mjs uses it for the pointer nudge and the name offer. additionalContext and permissionDecision (allow|deny|ask) are documented; projectstore never emits them. A separate PermissionRequest event carries its own decision object."
+      "note": "systemMessage measured — scripts/touch-session.mjs used it for the raw-edit nudge and uses it for the name offer (the nudge moved to PostToolUse with the write's pointer patch, ADR-006 amended 2026-10-12). additionalContext and permissionDecision (allow|deny|ask) are documented; projectstore never emits them. A separate PermissionRequest event carries its own decision object."
     },
     "PostToolUse": {
       "fields": [
         "additionalContext"
       ],
-      "system_message": null,
+      "system_message": true,
       "decision": null,
       "evidence": "measured",
-      "note": "scripts/touch-session.mjs — the entry-rule reminder's primary carrier (entry-rule spec, contract 14)."
+      "note": "scripts/touch-session.mjs — the entry-rule reminder's primary carrier (entry-rule spec, contract 14). The measurement covers additionalContext only. systemMessage carries the raw-edit nudge since the pointer patch moved after the write (ADR-006, amended 2026-10-12): documented for every event, not yet observed on this one — the closed-story story's live check records it."
     },
     "PostToolUseFailure": {
       "fields": [
@@ -299,7 +299,7 @@
       "file": ".projectstore/state/claude-code/statusline.mjs",
       "source": "scripts/statusline-launcher.mjs",
       "condition": "plugin_cache_install",
-      "file_reason": "the harness's generated runtime files live under .projectstore/state/<harness id>/ (layout ADR decision 4); the 0.27.x path .claude/.projectstore/statusline.mjs is read as ours through 0.29",
+      "file_reason": "the harness's generated runtime files live under .projectstore/state/<harness id>/ (layout ADR decision 4); the 0.27.x path .claude/.projectstore/statusline.mjs is read as ours through 0.30",
       "legacy_file": ".claude/.projectstore/statusline.mjs"
     },
     "mcp": {
@@ -494,7 +494,7 @@
   "ui_vocabulary_reason": "This harness's UI affordances and tool names: words that mean nothing on another harness. The generator refuses them in another harness's rendered tree, and the runtime vocabulary lint refuses them in what the core prints for another harness (generation spec, contracts 6 and 18). A word here must be followed by a non-word character to count, so `/plugins/` in a path is not `/plugin`.",
   "update_hint": {
     "line": "See /plugin → Marketplaces to enable auto-update.",
-    "welcome": ["**About future updates**: Claude Code does NOT auto-update third-party marketplaces by default. To get notified of new releases (v0.7+):", "1. Open `/plugin` → **Marketplaces** tab.", "2. Find **SmartAndPoint**.", "3. Toggle **auto-update** on.", "", "Without it, you'd run `/plugin marketplace update SmartAndPoint` manually. See https://github.com/SmartAndPoint/ProjectStore#updates for details."],
+    "welcome": ["**About future updates**: Claude Code does NOT auto-update third-party marketplaces by default. To get notified of new releases (v0.7+):", "1. Open `/plugin` → **Marketplaces** tab.", "2. Find **SmartAndPoint**.", "3. Toggle **auto-update** on.", "", "Without it, you'd run `/plugin marketplace update SmartAndPoint` manually. See https://github.com/SmartAndPoint/ProjectStore#upgrading for details."],
     "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. 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": [

package/node_modules/projectstore/harnesses/codex.json

@@ -321,8 +321,7 @@
       "run `$projectstore-bind <vault-path>` in Codex"
     ],
     "next": [
-      "restart Codex from a terminal and approve the ProjectStore hooks when it asks",
-      "in an unbound project, run `$projectstore-bind <vault-path>` in Codex"
+      "restart Codex from a terminal and approve the ProjectStore hooks when it asks"
     ],
     "notes": [
       "The installation is user-global because Codex's marketplace, plugin row and cache live in CODEX_HOME; the AGENTS.md block is project-local.",
@@ -333,9 +332,9 @@
     "docs": "https://github.com/SmartAndPoint/ProjectStore#install--one-message"
   },
   "update_hint": {
-    "line": "Update with `{upgrade}`.",
-    "welcome": ["**About future updates**: run `{upgrade}` from a terminal, then restart Codex and approve any hook it asks about.", "", "See https://github.com/SmartAndPoint/ProjectStore#updates for details."],
-    "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 this harness's shell command at latest, so what is printed runs as printed. 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."
+    "line": "Update from a terminal in this project:\n{upgrade}",
+    "welcome": ["**About future updates**: from a terminal in this project, run:", "", "```", "{upgrade}", "```", "", "Then restart Codex and approve any hook it asks about. See https://github.com/SmartAndPoint/ProjectStore#upgrading for details."],
+    "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 (`--harness codex`, no `--project`), so what is printed runs as printed. Each says where to run it and puts the command alone on its line (the story \"User-facing text says where to run and names no project path and no shell\", rules 4 and 5). 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": "Run `npx projectstore-codex@<version> upgrade --project <dir>`. The installer atomically replaces its stable source and `codex plugin add projectstore@projectstore-npx` materialises the new version; this was measured across two dev builds on codex-cli 0.153.4. Restart Codex afterwards so the new skills and hooks are loaded.",
   "agent_translation": {

package/node_modules/projectstore/hooks/band.tsx

@@ -40,6 +40,9 @@ import {
   segments,
   stepOf,
   storyFiles,
+  storyIsCurrent,
+  storyKeyOf,
+  storyLayout,
   subjectLabel,
   subjectPath,
   totalOf,
@@ -80,6 +83,9 @@ const steps = atom({ plugin: 'projectstore', key: 'steps' } as const, {} as Reco
 
 type Json = Record<string, any>
 type Rendered = 'drew' | 'survey' | 'nothing' | 'unknown'
+// One story file as the scan read it: its key (storyKeyOf), title and status.
+type StoryItem = { key: string; title: string | null; status: string | null }
+type Stories = { counts: BandCounts; items: StoryItem[] }
 
 // What one load of the module remembers between events.
 type Band = {
@@ -90,7 +96,7 @@ type Band = {
   gen: number
   scan: { gen: number; startedAt: number } | null
   shownKey: string
-  stories: Map<string, { sig: string; counts: BandCounts }>
+  stories: Map<string, { sig: string } & Stories>
   shipped: Map<string, Json>
   place: { vault: string | null; kinds: string[] }
 }
@@ -180,10 +186,11 @@ async function layoutOf($: EngineInterface, b: Band, name: string) {
 
 // ── The scan (contracts 2, 4–9, 14) ───────────────────────────────────
 
-// The epic's stories by stage, re-read only when a listing changed. A story
-// that cannot be read keeps the last good counts (none yet: no progress row),
-// never a partial fold — the band draws less, never wrong.
-async function countsOf($: EngineInterface, b: Band, epicDir: string): Promise<BandCounts | null> {
+// The epic's stories by stage, and each one's key, title and status (the
+// story row's, contract 8), re-read only when a listing changed. A story that
+// cannot be read keeps the last good result (none yet: no progress row and no
+// story row), never a partial fold — the band draws less, never wrong.
+async function storiesOf($: EngineInterface, b: Band, epicDir: string): Promise<Stories | null> {
   const seen: string[] = []
   const fs = {
     list: async (dir: string) => {
@@ -213,18 +220,38 @@ async function countsOf($: EngineInterface, b: Band, epicDir: string): Promise<B
   const files: string[] = await storyFiles(fs, epicDir)
   const sig = seen.sort().join('|')
   const hit = b.stories.get(epicDir)
-  if (hit && hit.sig === sig) return hit.counts
+  if (hit && hit.sig === sig) return hit
   const statuses: unknown[] = []
+  const items: StoryItem[] = []
   for (const f of files) {
     const text = await readText($, f)
-    // An unreadable story (an evicted iCloud file): the last good counts, and
+    // An unreadable story (an evicted iCloud file): the last good result, and
     // nothing cached, so the next scan tries again.
-    if (text === null) return hit?.counts ?? null
-    statuses.push((parseFrontmatter(text).data as Json).status)
+    if (text === null) return hit ?? null
+    const data = parseFrontmatter(text).data as Json
+    statuses.push(data.status)
+    const key = storyKeyOf(f.slice(epicDir.length + 1))
+    if (key) {
+      items.push({
+        key,
+        title: typeof data.title === 'string' && data.title ? data.title : null,
+        status: data.status === null || data.status === undefined || data.status === '' ? null : String(data.status),
+      })
+    }
   }
-  const counts = foldStages(statuses) as BandCounts
-  b.stories.set(epicDir, { sig, counts })
-  return counts
+  const next = { sig, counts: foldStages(statuses) as BandCounts, items }
+  b.stories.set(epicDir, next)
+  return next
+}
+
+// This session's story, from its file (contract 8): the item the pointer's
+// key names, while it is work the session is moving. Never the pointer's own
+// title or status — the pointer can be older than the file.
+function storyOf(pointer: Json | null, stories: Stories | null) {
+  const key = pointer && typeof pointer.active_story === 'string' ? (pointer.active_story as string) : null
+  const item = key && stories ? stories.items.find(i => i.key === key) : null
+  if (!item || !storyIsCurrent(item.status)) return null
+  return { title: item.title || item.key, status: item.status }
 }
 
 async function scan($: EngineInterface, b: Band, root: string, sid: string | null): Promise<BandView | null> {
@@ -258,16 +285,14 @@ async function scan($: EngineInterface, b: Band, root: string, sid: string | nul
   if (text === null) return null
   const fm = parseFrontmatter(text).data as Json
   const registry = await shippedJson($, b, 'scaffold/headings.json')
-  const story = focus.why === 'this' && pointer && typeof pointer.story_title === 'string' && pointer.story_title
-    ? { title: pointer.story_title as string, status: typeof pointer.story_status === 'string' ? (pointer.story_status as string) : null }
-    : null
+  const stories = await storiesOf($, b, epicDir)
   return {
     id: typeof fm.id === 'string' && fm.id ? fm.id : focus.id,
     title: typeof fm.title === 'string' && fm.title ? fm.title : focus.id,
     goal: goalOf(text, goalForms(registry, lang)),
-    counts: await countsOf($, b, epicDir),
+    counts: stories ? stories.counts : null,
     why: focus.why,
-    story,
+    story: focus.why === 'this' ? storyOf(pointer as Json | null, stories) : null,
     version: binding.statusline?.show_version === false ? null : await versionOf($, b),
     hint: band.hint_seen !== true,
     words,
@@ -466,11 +491,14 @@ export const register: Register = on => {
         }
       }
 
-      const story = rows.includes('story') && v.story ? (
+      // The title is cut here so the status is never the part the host's
+      // truncation takes (contract 8); truncate-end stays as a backstop.
+      const sl = v.story ? storyLayout(w.band_story, v.story.title, v.story.status, e.props.bodyColumns) : null
+      const story = rows.includes('story') && sl ? (
         <Text wrap="truncate-end">
           <Text dimColor>   {w.band_story} </Text>
-          <Text color="cyan">{v.story.title}</Text>
-          <Text dimColor>{v.story.status ? ` · ${v.story.status.replace(/[_-]/g, ' ')}` : ''}</Text>
+          <Text color="cyan">{sl.title}</Text>
+          <Text dimColor>{sl.tail}</Text>
         </Text>
       ) : null
 

package/node_modules/projectstore/hooks/pre-compact.mjs

@@ -57,10 +57,7 @@ async function readActivityBudgeted(vault, sid, budgetMs) {
   const deadline = new Promise((resolve) => {
     timer = setTimeout(() => resolve(null), budgetMs);
   });
-  const out = await Promise.race([
-    readActivityAsync(vault, sid).catch(() => []),
-    deadline,
-  ]);
+  const out = await Promise.race([readActivityAsync(vault, sid).catch(() => []), deadline]);
   clearTimeout(timer);
   return out;
 }
@@ -85,9 +82,7 @@ async function main() {
   try {
     layout = loadLayout(cfg.layout);
   } catch {}
-  const artifact = activity && layout
-    ? resolveInFlightArtifact(activity, layout, cfg.vault_path)
-    : null;
+  const artifact = activity && layout ? resolveInFlightArtifact(activity, layout, cfg.vault_path) : null;
 
   const parts = [`vault ${basename(cfg.vault_path)}`];
   // Dropped rather than rendered empty when nothing resolves.
@@ -105,9 +100,11 @@ async function main() {
     // Recent files are a separate referent with a separate condition: an empty
     // log renders no continuity section, so the stronger wording would be false
     // on a path the activity log's last-tool-wins dedupe makes ordinary.
-    parts.push(activity && activity.length > 0
-      ? "orientation and this session's recent files return at session start"
-      : "orientation returns at session start");
+    parts.push(
+      activity && activity.length > 0
+        ? "orientation and this session's recent files return at session start"
+        : "orientation returns at session start",
+    );
   } else {
     // True on every path: plugin commands are installation-scoped and not
     // gated by auto_inject.

package/node_modules/projectstore/hooks/session-rules.mjs

@@ -25,11 +25,13 @@ import { readConfig, readStdinJson, adoptHookInput, roleForm, sharedRoleForm } f
 // told once that both name one role — otherwise the second rule below would
 // have it report the block as a contradiction every session.
 function rules() {
-  const critic = roleForm("critic"), reviewer = roleForm("reviewer");
+  const critic = roleForm("critic"),
+    reviewer = roleForm("reviewer");
   const shared = sharedRoleForm("critic");
-  const bridge = shared === critic
-    ? ""
-    : `\n\nThe \`AGENTS.md\` block may name roles as \`${shared}\`; that is the same role, called \`${critic}\` here.`;
+  const bridge =
+    shared === critic
+      ? ""
+      : `\n\nThe \`AGENTS.md\` block may name roles as \`${shared}\`; that is the same role, called \`${critic}\` here.`;
   return `# projectstore — standing rules for this session
 
 **Artifact-first order.** A feature-sized request opens a vault artifact before
@@ -46,9 +48,11 @@ contradiction becomes invisible to the person who could have settled it.${bridge
 }
 
 function emit(additionalContext) {
-  process.stdout.write(JSON.stringify({
-    hookSpecificOutput: { hookEventName: "SessionStart", additionalContext },
-  }) + "\n");
+  process.stdout.write(
+    JSON.stringify({
+      hookSpecificOutput: { hookEventName: "SessionStart", additionalContext },
+    }) + "\n",
+  );
 }
 
 function main() {
@@ -70,6 +74,8 @@ function main() {
   emit(rules());
 }
 
-try { main(); } catch {
+try {
+  main();
+} catch {
   // A hook must never break session startup.
 }