projectstore-claude 0.30.12 → 0.30.14

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.12",
+      "version": "0.30.14",
       "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.12",
+  "version": "0.30.14",
   "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/agents/planner.md

@@ -85,8 +85,17 @@ generic best practice — cite the real files and patterns you found.
 8. **Proposed `code_refs`** — the paths/globs this epic (and story) will own once
    implemented, ready for `/projectstore:codemap set`. You PROPOSE; the command
    writes after approval.
+9. **Open questions** — at most five decisions the user must make that the
+   code and the vault cannot answer, the one that changes the plan most
+   first. One per line:
+   `Q<n>. <the question> Options: (a) … (b) … Recommend (b): <why>`, with two to four options. The
+   recommendation is one of the options, so it can be recorded as the answer
+   when the user skips the question. "None" is the normal case. With more than
+   five, return five, say how many you left out, and say the story is
+   probably too big: suggest how to split it. You ask the user nothing; the
+   plan step puts these to the user in one round.
 
 Rules: be concrete and cite real paths / symbols; if the task is ambiguous or has
-two plausible homes, say so and recommend one with the tradeoff. No code
+two plausible homes, say so in Open questions (item 9) and recommend one with the tradeoff. No code
 generation beyond tiny illustrative snippets. You are read-only — never write
 code or vault files.

package/node_modules/projectstore/commands/story.md

@@ -100,11 +100,32 @@ the two cannot collide).
    `plan_updated_at` / `closed_at` — stamped unconditionally; the
    `lifecycle_gates` key gates checks, never data).
 
+2a. **(plan only) Open questions, one round.** Before writing the plan,
+   collect the open questions: the planner's "Open questions" when it ran,
+   else your own; do not start the planner here. Keep only decisions the
+   user must make; skip what the conversation, or an earlier
+   `### Clarifications` in this plan, already settled. None is the normal
+   case: then ask nothing and write nothing. Keep at most five, the one that
+   changes the plan most first; with more, keep five, say how many were
+   dropped, and suggest splitting the story; when the planner says it left questions out, say so in the same round, with its split suggestion. Each question has two to four
+   options and one recommended option. Put them to the user in one round:
+   one call of AskUserQuestion for up to four questions; with five, or where
+   the harness has no question tool, one plain-text message with the
+   questions numbered. Ask once per gate run: the Edit in step 4 and the
+   re-check in step 5 never ask again. A skipped question, or every question
+   of a dismissed call, takes its recommendation, marked `(assumed)`. Record
+   the round under `### Clarifications`, last in the plan: a line with
+   today's date, then one bullet per question with its answer; a later plan
+   run appends its own dated line to the same subsection. An answer that changes a
+   contract of the covering spec says which one, and the spec is amended
+   the way it records its other amendments before the code is written.
+
 3. **Fill the section content** in the returned `content` before preview:
    - `plan` — write the Implementation Plan. When the story's `specs:` names a
      covering spec, the plan is a THIN ROUTE through that spec's behavioral
      contracts: which contracts, in what order, which files. Consult the
-     planner agent's output if one ran. Do not restate the spec.
+     planner agent's output if one ran. Do not restate the spec. End the plan
+     with the step 2a round, when there was one.
    - `close` — write the Final Summary (what changed / why / tests executed /
      risks & follow-ups), and update the Acceptance Criteria checkboxes with
      evidence suffixes: `- [x] <criterion> — evidence: <test | command | file:line>`.

package/node_modules/projectstore/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore",
-  "version": "0.30.12",
+  "version": "0.30.14",
   "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/tokens.mjs

@@ -24,9 +24,10 @@
 //     false "1 call/turn" for every turn (each record holds ≤1 tool_use).
 //
 // COST is computed at current API list prices (PRICING below) with the cache
-// multipliers: read 0.1× input, 5m write 1.25×, 1h write 2× (the usage records
-// carry the 5m/1h split). Under a subscription plan these dollars are a proxy
-// for rate-limit consumption, not an invoice — the RATIOS hold either way.
+// multipliers: read 0.1× input unless the model has its own read rate, 5m
+// write 1.25×, 1h write 2× (the usage records carry the 5m/1h split). Under
+// a subscription plan these dollars are a proxy for rate-limit consumption,
+// not an invoice — the RATIOS hold either way.
 // Historical price changes are not modeled; everything is priced at today's
 // list. Unknown models are priced at 0 and reported.
 //
@@ -94,28 +95,36 @@ const STAGE_OF = {
 };
 const STAGE_ORDER = ["authoring", "critique", "planning", "code-review", "curation", "upkeep", "other"];
 
-// USD per MTok [input, output], API list prices as of 2026-08-04 (Fable 5.1 added 2026-09-02)
-// (platform.claude.com pricing docs). Cache multipliers applied on top of
-// the input rate.
+// USD per MTok [input, output, cache read?], API list prices as of 2026-11-10
+// (platform.claude.com pricing docs). The third value is the cache-read rate
+// where it is not 0.1× input (Fable 5.1 and 5.2: 0.025×; Opus 5.5 and
+// Sonnet 5.5: 0.05×); writes stay 1.25× / 2× input. The `--json` output
+// carries these arrays as they are, with two or three values.
 export const PRICING = {
-  "claude-fable-5-1": [10, 50],
+  "claude-fable-5-2": [8, 40, 0.2],
+  "claude-fable-5-1": [10, 50, 0.25],
   "claude-fable-5": [10, 50],
+  "claude-opus-5-5": [4, 20, 0.2],
   "claude-opus-5": [5, 25],
   "claude-opus-4-8": [5, 25],
   "claude-opus-4-7": [5, 25],
-  "claude-sonnet-5": [2, 10], // intro pricing through 2026-08-31; sticker is [3, 15]
+  "claude-sonnet-5-5": [2, 10, 0.1],
+  "claude-sonnet-5": [2, 10],
   "claude-sonnet-4-6": [3, 15],
+  // reads at the default 0.1× ($0.01); prompts up to 100K, beyond [0.5, 2.5] (not modeled)
+  "claude-haiku-5-5": [0.1, 0.5],
   "claude-haiku-4-5": [1, 5],
 };
 
 // Transcripts carry variant ids ("claude-haiku-4-5-20251001", "opus",
 // "claude-opus-5[1m]") — normalize before the PRICING lookup so they don't
-// silently price at $0.
+// silently price at $0. A bare alias names the newest model of its line, so
+// an old record written as "haiku" prices at today's Haiku, not the one that ran.
 const MODEL_ALIASES = {
-  fable: "claude-fable-5-1",
-  opus: "claude-opus-5",
-  sonnet: "claude-sonnet-5",
-  haiku: "claude-haiku-4-5",
+  fable: "claude-fable-5-2",
+  opus: "claude-opus-5-5",
+  sonnet: "claude-sonnet-5-5",
+  haiku: "claude-haiku-5-5",
 };
 
 export function normModel(model) {
@@ -126,9 +135,9 @@ export function normModel(model) {
 export function rowCost(row) {
   const p = PRICING[normModel(row.model)];
   if (!p) return 0;
-  const [inP, outP] = p;
+  const [inP, outP, readP = 0.1 * inP] = p;
   return (
-    (row.input * inP + row.cw5m * 1.25 * inP + row.cw1h * 2 * inP + row.cacheRead * 0.1 * inP + row.output * outP) / 1e6
+    (row.input * inP + row.cw5m * 1.25 * inP + row.cw1h * 2 * inP + row.cacheRead * readP + row.output * outP) / 1e6
   );
 }
 
@@ -359,7 +368,7 @@ const n = (v) => v.toLocaleString("en-US");
 
 // `t/turn` — avg distinct tool calls per tool-using turn (batching level; 1.0
 // means fully sequential). `cost` — USD at current list prices; cache reads
-// bill at 0.1× input, so token counts and dollars rank differently.
+// bill at a small fraction of input, so token counts and dollars rank differently.
 const usd = (v) => `$${v.toFixed(2)}`;
 
 function table(groups, label, { runs = false } = {}) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore-claude",
-  "version": "0.30.12",
+  "version": "0.30.14",
   "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.12"
+    "projectstore": "=0.30.14"
   },
   "bundleDependencies": [
     "projectstore"