projectstore-claude 0.30.7 → 0.30.8

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.30.7",
+      "version": "0.30.8",
       "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.30.7",
+  "version": "0.30.8",
   "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

@@ -1,6 +1,6 @@
 # ProjectStore
 
-> Not agent memory, not a per-feature spec pipeline. Memory helps one agent recall; a feature spec plans one change. ProjectStore keeps the project's record — what was decided, what is in flight, what was checked — as reviewed markdown in git, readable by any agent and anyone with the repo.
+> ProjectStore is a method and a framework for building apps and services of any size with AI agents. It keeps the project's record — what was decided, what is in flight, what was checked — as reviewed markdown in git, readable by any agent and anyone with the repo.
 
 [![release](https://img.shields.io/github/v/release/SmartAndPoint/ProjectStore?label=release)](https://github.com/SmartAndPoint/ProjectStore/releases) [![license](https://img.shields.io/github/license/SmartAndPoint/ProjectStore?label=license)](./LICENSE) [![Star on GitHub](https://img.shields.io/badge/%E2%AD%90-star_us-yellow?logo=github)](https://github.com/SmartAndPoint/ProjectStore/stargazers)
 
@@ -183,7 +183,7 @@ npx projectstore codemap --for scripts/lib.mjs
 The same eight reads are an MCP server. The plugin registers it through its own `.mcp.json`, so a Claude Code session has `status`, `search`, `get_artifact`, `neighbors`, `lineage`, `code_refs`, `orientation` and `doctor` as tools with no shell; every tool result is the CLI's `--json` for the same arguments. Elsewhere:
 
 ```
-npx projectstore mcp --project "$PWD"
+npx projectstore mcp --project .
 ```
 
 Binding, too — naming the vault is the confirmation, and changing it needs `--rebind`. `init` creates a whole vault in one step, with no `mkdir` first: the directory, its git repository, the layout's folders and their README indexes; `scaffold --write` adds the folders to a vault that was bound without them:
@@ -401,7 +401,7 @@ ProjectStore has no server, no account and no telemetry. It collects nothing abo
 - **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.
+- **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, `.band-<session id>.json` under `.projectstore/state/sessions/`, while it draws; it starts no program and makes no request. It watches agent starts (`agent.spawn`), each agent's requests and tool calls, and each turn's end, only to show a ProjectStore agent's row. It passes each of these on unchanged, and it changes no agent, permission or setting.
 - **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.

package/node_modules/projectstore/commands/review.md

@@ -37,8 +37,8 @@ You are running a peer review on a projectstore artifact.
 
    ## Project context
 
-   <vault README excerpt>
-   <folder README excerpt>
+   <the vault's README excerpt>
+   <the folder's README excerpt>
 
    ## Structural checklist
 

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 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).
+Resolution is **per-session, with no cross-session read and no read of the vault** (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 runs `configure --set statusline=on|off` (the configure spec, contracts 6 and 9): install's own items record `statusline.enabled` and write or remove the `settings.local.json` entry and the launcher, in one plan. The command never writes `projectstore.json` itself. 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/docs/how-it-works.md

@@ -87,25 +87,28 @@ Edits made through the shell are not seen; a Read of the story sets the pointer.
 
 Continuity across a compaction is delivered by **SessionStart**, not by
 PreCompact — and that is a correction, not a design flourish. PreCompact has no
-model-facing channel: it accepts a top-level `systemMessage` and nothing else,
-so for its whole life the hook assembled a rich packet, printed a red *"Hook
-JSON output validation failed"*, and reached nobody. Worse, the invalid field
-sank the whole object, so the one line PreCompact *does* support never landed
-either.
+`additionalContext`, so for its early life the hook assembled a rich packet,
+printed a red *"Hook JSON output validation failed"*, and reached nobody. Its
+`systemMessage` is no channel either: Claude Code discards that field on
+PreCompact. What it does with a PreCompact hook is echo the hook's raw stdout in
+the `/compact` output.
 
 So the two hooks now split the work by what each can actually do.
 
-PreCompact prints one line, for you:
+PreCompact prints one plain line, for you:
 
 ```
-PreCompact [...pre-compact.mjs] completed successfully: {
-  "systemMessage": "projectstore: compacting — vault myapp-vault,
-                    in flight: `epics/WEB-101/epic.md`,
-                    orientation and this session's recent files return
-                    at session start"
-}
+⎿ Compacted (ctrl+o to see full summary)
+  PreCompact [...pre-compact.mjs] completed successfully: projectstore:
+  compacting — vault myapp-vault, in flight: `epics/WEB-101/epic.md`,
+  orientation and this session's recent files return at session start
 ```
 
+On a manual `/compact` the model reads that line too, after the summary. On an
+automatic compaction it is shown to no one. (On Codex, where none of this is
+measured yet, the hook keeps printing its line as a `{"systemMessage": …}`
+object.)
+
 That last clause is conditional on purpose. It appears only when the compaction
 is **manual** and `auto_inject` is on — the two things the hook can check at the
 moment it speaks. On an automatic compaction the plugin makes no claim that

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

@@ -115,7 +115,7 @@
     "_root_placeholder_literal_comment": "true = the harness passes the placeholder through as literal text and the installer must substitute an absolute path; false = the harness expands it. Claude Code expands ${CLAUDE_PLUGIN_ROOT}, so false. Measured value for Codex comes from the spike."
   },
   "output_channels": {
-    "_comment": "Per-event output channels (generation spec, contract 17). `fields` are the hookSpecificOutput keys the event honours; `system_message` is the top-level systemMessage; `decision` names the decision object where one exists; an optional `input_fields` lists the stdin keys; Stop's `carrier` is the shape the entry reminder's Stop carrier prints (additionalContext | block | null) — our choice where both are honoured. `evidence` is `measured` only where this repository's own hooks observe the fact, `documented` where the Claude Code hooks reference says so and we never emit it.",
+    "_comment": "Per-event output channels (generation spec, contract 17). `fields` are the hookSpecificOutput keys the event honours; `system_message` is the top-level systemMessage; `decision` names the decision object where one exists; an optional `input_fields` lists the stdin keys; Stop's `carrier` is the shape the entry reminder's Stop carrier prints (additionalContext | block | null) — our choice where both are honoured; PreCompact's `carrier` is how hooks/pre-compact.mjs prints its line (stdout | null, null keeping the {\"systemMessage\"} object). `system_message` is true where the field is honoured, false where it is measured discarded, null where unmeasured. `evidence` is `measured` only where this repository's own hooks observe the fact, `documented` where the Claude Code hooks reference says so and we never emit it.",
     "SessionStart": {
       "fields": [
         "additionalContext"
@@ -195,10 +195,11 @@
     },
     "PreCompact": {
       "fields": [],
-      "system_message": true,
+      "system_message": false,
       "decision": null,
+      "carrier": "stdout",
       "evidence": "measured",
-      "note": "Measured NEGATIVELY: an output object containing additionalContext is rejected whole, taking systemMessage down with it (hooks/pre-compact.mjs; vault story: PreCompact survival packet targets a channel PreCompact does not have). Only top-level decision/reason and systemMessage exist."
+      "note": "Measured NEGATIVELY: an output object containing additionalContext is rejected whole, taking systemMessage down with it (vault story: PreCompact survival packet targets a channel PreCompact does not have). A top-level `decision: \"block\"` exists (documented; never emitted here). The systemMessage field is discarded (hooks reference; measured on 2.1.312, 2026-10-28): what carries the line is the hook's raw stdout, echoed in the /compact output as `PreCompact [<command>] completed successfully: <stdout>` (the same form was seen on 2026-08-18). On a manual compaction the user sees it and the model reads it as <local-command-stdout> after the summary; on an automatic one nothing is shown, and the compacting model appears to receive it (nothing relies on that). stderr reaches no one. Vault story: On Claude Code PreCompact speaks plain text, because the host echoes its stdout and discards systemMessage."
     }
   },
   "surfaces": {

package/node_modules/projectstore/harnesses/codex.json

@@ -72,7 +72,7 @@
     "_root_placeholder_literal_comment": "true: Codex substitutes nothing in a hook command string. It does not need to — the hook process receives PLUGIN_ROOT in its environment (measured). The generator therefore renders an absolute interpreter and an absolute script path; a bare `node` is a PATH gamble."
   },
   "output_channels": {
-    "_comment": "Per-event channels (generation spec, contract 17, as amended 2026-10-15). `fields` are the hookSpecificOutput keys the event honours — the output side, as on every manifest; `input_fields` are the stdin keys it delivers, captured from live firings (759 on 2026-09-07/08; Run 4 of *Codex hook contract measured in a live session*, codex-cli 0.162.1, 2026-10-15, traces t1–t7). `decision` names the decision object where one exists; Stop's `carrier` is the shape the entry reminder's Stop carrier prints (additionalContext | block | null). `system_message` stays null: documented, not measured. `evidence` is about the output side.",
+    "_comment": "Per-event channels (generation spec, contract 17, as amended 2026-10-15). `fields` are the hookSpecificOutput keys the event honours — the output side, as on every manifest; `input_fields` are the stdin keys it delivers, captured from live firings (759 on 2026-09-07/08; Run 4 of *Codex hook contract measured in a live session*, codex-cli 0.162.1, 2026-10-15, traces t1–t7). `decision` names the decision object where one exists; Stop's `carrier` is the shape the entry reminder's Stop carrier prints (additionalContext | block | null); PreCompact's `carrier` is how hooks/pre-compact.mjs prints its line (stdout | null). `system_message` stays null: documented, not measured. `evidence` is about the output side.",
     "SessionStart": {
       "input_fields": [
         "session_id",
@@ -185,8 +185,9 @@
       "fields": [],
       "system_message": null,
       "decision": null,
+      "carrier": null,
       "evidence": "documented",
-      "note": "trigger is `auto` on an automatic compaction, and PostCompact follows (Run 4, t2:5–6). No permission_mode. Whether a systemMessage reaches anyone on Codex is unmeasured."
+      "note": "trigger is `auto` on an automatic compaction, and PostCompact follows (Run 4, t2:5–6). No permission_mode. Whether a systemMessage reaches anyone on Codex is unmeasured, so no carrier is set and hooks/pre-compact.mjs keeps its {\"systemMessage\"} object here."
     }
   },
   "surfaces": {

package/node_modules/projectstore/hooks/band.tsx

@@ -197,14 +197,14 @@ async function storiesOf($: EngineInterface, b: Band, epicDir: string): Promise<
     list: async (dir: string) => {
       const entries = await $.fs.list(dir)
       const out = []
-      for (const e of entries) {
-        let kind = e.kind
+      for (const entry of entries) {
+        let kind = entry.kind
         if (kind === 'other') {
           // A symbolic link: the board follows it, so the band does too.
-          try { kind = (await $.fs.stat(`${dir}/${e.name}`, { resolve: true })).kind } catch { kind = 'other' }
+          try { kind = (await $.fs.stat(`${dir}/${entry.name}`, { resolve: true })).kind } catch { kind = 'other' }
         }
-        seen.push(`${dir}/${e.name}:${kind}:${e.mtimeMs}`)
-        out.push({ ...e, kind })
+        seen.push(`${dir}/${entry.name}:${kind}:${entry.mtimeMs}`)
+        out.push({ ...entry, kind })
       }
       return out
     },
@@ -240,9 +240,9 @@ async function storiesOf($: EngineInterface, b: Band, epicDir: string): Promise<
       })
     }
   }
-  const next = { sig, counts: foldStages(statuses) as BandCounts, items }
-  b.stories.set(epicDir, next)
-  return next
+  const fresh = { sig, counts: foldStages(statuses) as BandCounts, items }
+  b.stories.set(epicDir, fresh)
+  return fresh
 }
 
 // This session's story, from its file (contract 8): the item the pointer's
@@ -313,10 +313,12 @@ async function scan($: EngineInterface, b: Band, root: string, sid: string | nul
 // ── The clock: scan, heartbeat, prune (contract 10) ───────────────────
 
 async function writeHeartbeat($: EngineInterface, root: string, sid: string | null, body: unknown): Promise<boolean> {
-  const name = heartbeatFile(sid)
-  if (!name) return false
+  // An id that cannot name a file writes nothing. The path is spelled out,
+  // folder and name, so the directory's scan can read where the band writes;
+  // a node test holds it to layoutPaths() and heartbeatFile().
+  if (!heartbeatFile(sid)) return false
   try {
-    await $.fs.write(`${root}/${SESSIONS}/${name}`, JSON.stringify(body) + '\n')
+    await $.fs.write(`${root}/.projectstore/state/sessions/.band-${sid}.json`, JSON.stringify(body) + '\n')
     return true
   } catch {
     // A heartbeat missed: the status line keeps its own line, and the next
@@ -341,11 +343,11 @@ async function prune($: EngineInterface, now: number) {
   if (live.length !== list.length) await update($, crew, () => live)
 }
 
-async function show($: EngineInterface, b: Band, next: BandView | null) {
-  const key = JSON.stringify(next)
+async function show($: EngineInterface, b: Band, shown: BandView | null) {
+  const key = JSON.stringify(shown)
   if (key === b.shownKey) return
   b.shownKey = key
-  await update($, view, () => next)
+  await update($, view, () => shown)
 }
 
 async function tick($: EngineInterface, b: Band) {
@@ -362,7 +364,7 @@ async function tick($: EngineInterface, b: Band) {
   b.scan = { gen, startedAt: now }
   const current = () => b.scan?.gen === gen
   const scanning = scan($, b, root, sid)
-    .then(next => (current() ? show($, b, next) : undefined))
+    .then(found => (current() ? show($, b, found) : undefined))
     .catch(() => undefined)
     .finally(() => {
       if (current()) b.scan = null

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

@@ -3,12 +3,19 @@
 //
 // Fires before context compaction (both manual /compact and automatic).
 //
-// ONE channel: `systemMessage`, the line the user sees in their /compact
-// output. PreCompact has no `additionalContext` — the runtime rejects the whole
-// object when one is present, taking `systemMessage` down with it, so for its
-// entire history this hook assembled a packet, printed a red validation error,
-// and reached nobody. Agent-facing continuity after a compaction is
-// SessionStart's job, on `source: "compact"` (spec contract 19).
+// ONE line, through the identified harness's PreCompact carrier (spec
+// contract 22, as amended 2026-10-28). On Claude Code that is plain stdout: the
+// host discards a PreCompact `systemMessage` and echoes the hook's raw stdout in
+// the /compact output instead, where the user sees it and, on a manual
+// compaction, the model reads it after the summary. An automatic compaction
+// shows it to no one. Elsewhere — nothing identified, or nothing measured — the
+// line keeps the {"systemMessage"} object it has always had.
+//
+// PreCompact has no `additionalContext`: the runtime rejects the whole object
+// when one is present, so for its early history this hook assembled a packet,
+// printed a red validation error, and reached nobody. Agent-facing continuity
+// after a compaction is SessionStart's job, on `source: "compact"` (spec
+// contract 19).
 //
 // What this hook may CLAIM is narrower than what it knows, and deliberately so:
 //   - naming the in-flight artifact is always safe — it is a fact about the log
@@ -32,12 +39,22 @@ import {
   resolveInFlightArtifact,
   pathCell,
   commandForm,
+  preCompactCarrier,
 } from "../scripts/lib.mjs";
 
+// The file's one writer to stdout, for the success path and the catch-all
+// alike. A plain line stays one line: the object form escaped a line break in a
+// vault name or an error message for free, the text form has to fold it.
+//
 // Exits after the flush, never before: process.exit does not drain a pending
 // pipe write, and the budgeted read below can still be outstanding.
-function emit(systemMessage) {
-  process.stdout.write(JSON.stringify({ systemMessage }) + "\n", () => process.exit(0));
+function emit(line) {
+  let carrier = null;
+  try {
+    carrier = preCompactCarrier();
+  } catch {}
+  const out = carrier === "stdout" ? line.replace(/[\r\n]+/g, " ") : JSON.stringify({ systemMessage: line });
+  process.stdout.write(out + "\n", () => process.exit(0));
 }
 
 // Contract 13's budget applies here too. The session file lives inside the

package/node_modules/projectstore/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore",
-  "version": "0.30.7",
+  "version": "0.30.8",
   "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.",
   "keywords": [
     "project-management",

package/node_modules/projectstore/scripts/convergence.mjs

@@ -72,8 +72,6 @@ import { registrationPaths } from "./surfaces.mjs";
 // (rule 9's command-form rule). The shells bundle it; the notice and the stop
 // name the package that runs, never a shell.
 export const PACKAGE = "projectstore";
-// What the read uses when the user's registry cannot be resolved.
-export const DEFAULT_REGISTRY = "https://registry.npmjs.org/";
 // The abbreviated packument: what `npm install` itself reads (8 728 bytes
 // against 50 896 for the full document, measured 2026-10-09).
 export const ACCEPT = "application/vnd.npm.install-v1+json";
@@ -90,8 +88,8 @@ export const MIN_READ_MS = 50;
 export const FRESH_MS = 24 * 60 * 60 * 1000;
 export const NO_CHECK_ENV = "PROJECTSTORE_NO_UPDATE_CHECK";
 
-// Strict semver 2.0 (semver.org's own grammar): a `dist-tags.latest` that is
-// anything else counts as missing — never printed, never compared.
+// Strict semver 2.0 (the specification's own grammar): a `dist-tags.latest`
+// that is anything else counts as missing — never printed, never compared.
 const NUM = "(?:0|[1-9]\\d*)";
 const PRE = `(?:${NUM}|\\d*[A-Za-z-][0-9A-Za-z-]*)`;
 const SEMVER = new RegExp(

package/node_modules/projectstore/scripts/fetch-shell.mjs

@@ -214,8 +214,12 @@ export function npmError(stdout, stderr) {
 
 const seconds = (ms) => `${Number((ms / 1000).toFixed(ms % 1000 ? 1 : 0))} s`;
 
-// npm's own registry: the one README's registry-mirror advice names.
+// npm's own registry: the one README's registry-mirror advice names, and the
+// plugin's one spelling of it.
 export const PUBLIC_REGISTRY = "https://registry.npmjs.org";
+// npm's default: what the installer's registry read (readLatest) and its
+// registry comparison use when the user's own registry cannot be resolved.
+export const DEFAULT_REGISTRY = `${PUBLIC_REGISTRY}/`;
 
 // A registry that has no such shell may be a mirror that has not synced it:
 // the run once more, from npm's public registry, in README's form — the

package/node_modules/projectstore/scripts/harness.mjs

@@ -473,6 +473,38 @@ export function stopCarrierProblem(manifest) {
   return null;
 }
 
+// ─── The PreCompact carrier (generation spec, contract 17; skeleton spec,
+// contract 22, both as amended 2026-10-28) ─────────────────────────────
+//
+// How hooks/pre-compact.mjs prints its one line. Claude Code discards a
+// PreCompact systemMessage and echoes the hook's raw stdout in the /compact
+// output instead (measured 2026-10-28), so there the line goes out as plain
+// text. Null — nothing identified, or no carrier measured — keeps the
+// {"systemMessage"} object the hook has always printed: a plain line on a host
+// whose schema refuses it would be a failed hook, and an unchanged object is
+// not. The same identified-only rule as stopCarrier, for the same reason.
+export const PRECOMPACT_CARRIERS = Object.freeze(["stdout"]);
+export function preCompactCarrier(env = process.env, dir = MANIFEST_DIR) {
+  const id = identifiedHarnessId(env, dir);
+  const carrier = id ? loadHarness(id, dir)?.output_channels?.PreCompact?.carrier : null;
+  return PRECOMPACT_CARRIERS.includes(carrier) ? carrier : null;
+}
+
+// What is wrong with a manifest's PreCompact row, or null. The key is present
+// on every row (null when nothing is measured), and a carrier is only ever
+// chosen from a measured row.
+export function preCompactCarrierProblem(manifest) {
+  const row = manifest?.output_channels?.PreCompact;
+  if (row === null || row === undefined) return null;
+  if (typeof row !== "object") return "output_channels.PreCompact is not an object";
+  if (!("carrier" in row)) return "output_channels.PreCompact has no carrier (null when none is measured)";
+  if (![...PRECOMPACT_CARRIERS, null].includes(row.carrier))
+    return `output_channels.PreCompact.carrier ${JSON.stringify(row.carrier)} is not one of ${PRECOMPACT_CARRIERS.join(", ")} or null`;
+  if (row.carrier !== null && row.evidence !== "measured")
+    return "output_channels.PreCompact.carrier is set on a row that is not measured";
+  return null;
+}
+
 // ─── Who a message is for (generation spec, contract 18) ───────────────
 //
 // The core prints for ONE harness at a time, and a command it names must be

package/node_modules/projectstore/scripts/install-harness.mjs

@@ -159,6 +159,7 @@ import {
   fetchRefusal,
   fetchRunId,
   sweepFetchRuns,
+  DEFAULT_REGISTRY,
 } from "./fetch-shell.mjs";
 import { HOST_BUDGET_MS, startFailure, runHost } from "./run-host.mjs";
 import {
@@ -191,7 +192,6 @@ import {
   terminalRun,
   copyBehind,
   behindAdvice,
-  DEFAULT_REGISTRY,
   NOTICE_BUDGET_MS,
   READ_TIMEOUT_MS,
   MIN_READ_MS,

package/node_modules/projectstore/scripts/lib.mjs

@@ -54,6 +54,7 @@ import {
   whichOnPath,
   hostSessionId,
   stopCarrier,
+  preCompactCarrier,
   hostRegistry,
   autoUpdateDefault,
 } from "./harness.mjs";
@@ -194,6 +195,7 @@ export {
   speakingHarness,
   whichOnPath,
   stopCarrier,
+  preCompactCarrier,
 };
 
 // A hook's payload carries the `cwd` of the session that fired it, and on a

package/node_modules/projectstore/scripts/term.mjs

@@ -37,9 +37,9 @@ import { createInterface, emitKeypressEvents } from "node:readline";
 
 // FORCE_COLOR decides when it is set, as Node's own tty reads it: "", "1",
 // "2", "3" or "true" turn colour on even without a terminal, anything else
-// ("0", "false") turns it off. Otherwise NO_COLOR (https://no-color.org) turns
-// colour off when set to anything non-empty, and TERM=dumb means a terminal
-// that understands no escapes.
+// ("0", "false") turns it off. Otherwise NO_COLOR turns colour off when set
+// to anything non-empty, as the NO_COLOR convention has it, and TERM=dumb means
+// a terminal that understands no escapes.
 //
 // Glyphs are a switch of their own (presentation spec contract 2): ASCII
 // under TERM=dumb or PROJECTSTORE_ASCII set non-empty, Unicode otherwise, in

package/node_modules/projectstore/scripts/touch-session.mjs

@@ -80,7 +80,7 @@ import {
 const NUDGE_INTERVAL_MS = 10 * 60 * 1000;
 
 // Per-session active pointer (ADR-006) — denormalized titles/status captured
-// after the write so the statusline renders with zero vault reads — plus the
+// after the write so the statusline renders with no read of the vault — plus the
 // raw-edit nudge (PS-IMPROVE story-003): throttled, never blocking. Both in
 // patchPointer below.
 // The session-name offer (ADR: the settled-anchor offer). Returns a line or

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore-claude",
-  "version": "0.30.7",
+  "version": "0.30.8",
   "description": "projectstore for Claude Code: the core pinned and bundled, the harness fixed. A release artifact; the way in is npx projectstore setup",
   "keywords": [
     "projectstore",
@@ -37,7 +37,7 @@
     "README.md"
   ],
   "dependencies": {
-    "projectstore": "=0.30.7"
+    "projectstore": "=0.30.8"
   },
   "bundleDependencies": [
     "projectstore"