@archme/cli 0.5.0 → 0.5.1

package/dist/cli.js

@@ -12138,21 +12138,32 @@ var init_affected = __esm({
   }
 });
 
+// ../shared/storyNaming.ts
+var STORY_NAMING_GUIDANCE;
+var init_storyNaming = __esm({
+  "../shared/storyNaming.ts"() {
+    STORY_NAMING_GUIDANCE = `Story titles:
+- **Leaves are actions.** A leaf story is a flow, so title it verb + object, imperative: \`sign up with email\`, \`refund a charge\`, \`retry a failed job\`. Not the noun phrase for the same flow (\`email signup\`, \`charge refunds\`, \`failed job retry\`).
+- **Groups are areas.** A parent story is a feature area, so title it as a noun phrase naming what its leaves have in common: \`auth\`, \`billing\`, \`job queue\`. Not an action (\`authenticate users\`).
+- Keep both as short as the hierarchy allows \u2014 the group supplies the context, so a leaf never restates it.
+  - Good: "web app" > "auth" > "sign up with email"
+  - Bad: "new user signs up with email on the web app"
+- **An existing convention wins.** If a story's siblings already agree on a different form, match them \u2014 cohesion across the tree is the goal, and the rules above are only the default when there is nothing to match. Restyle only titles you are already editing for another reason; a rename lands in someone's diff, so never sweep the tree for form alone.`;
+  }
+});
+
 // ../shared/scanPrompts.ts
 function buildFormatRefStories(opts) {
   const draftBlock = opts.persistentDrafts ? FORMAT_REF_DRAFT_STORIES_BLOCK : "";
   const uncoveredSubFlowRule = opts.persistentDrafts ? CROSS_REF_UNCOVERED_DRAFT_STUB : CROSS_REF_UNCOVERED_REAL_STORY;
-  const hierarchyExample = opts.persistentDrafts ? `- Example: storyUpdates: [{add: [{id: "auth", title: "Authentication", description: "User auth flows", draft: true, userStories: [{id: "login", title: "Login Flow", draft: true, acceptanceCriteria: ["< 1s response"]}]}]}]` : `- Example: storyUpdates: [{add: [{id: "auth", title: "Authentication", description: "User auth flows", userStories: [{id: "login", title: "Login Flow", acceptanceCriteria: ["< 1s response"], sequence: "sequenceDiagram\\n    ..."}]}]}]`;
+  const hierarchyExample = opts.persistentDrafts ? `- Example: storyUpdates: [{add: [{id: "auth", title: "Authentication", description: "User auth flows", draft: true, userStories: [{id: "login", title: "log in with email", draft: true, acceptanceCriteria: ["< 1s response"]}]}]}]` : `- Example: storyUpdates: [{add: [{id: "auth", title: "Authentication", description: "User auth flows", userStories: [{id: "login", title: "log in with email", acceptanceCriteria: ["< 1s response"], sequence: "sequenceDiagram\\n    ..."}]}]}]`;
   return `Recursive story hierarchy:
 - Stories can contain child stories via userStories: [...] \u2014 parent stories act as feature groups
 - Use top-level stories with description, links, and nested children to organize by feature area
 ${hierarchyExample}
 - Removing a parent story cascades to all descendants
 
-Story titles:
-- Keep titles as short as possible \u2014 rely on the parent group for context.
-- Good: "web app" > "auth" > "sign up with email"
-- Bad: "new user signs up with email on the web app"
+${STORY_NAMING_GUIDANCE}
 
 Story description format (markdown, 1-4 sentences \u2014 render target is a narrow side panel):
 - Write for someone who knows the product but isn't reading the code. Say what the system does and what the user/operator experiences at the highest useful altitude, not how it's implemented. A tl;dr, not a rehash.
@@ -12205,14 +12216,15 @@ storyUpdates targeting:
   - add: stories to add or update (merged by ID if story already exists)
   - remove: story IDs to remove
 - Examples:
-  - Add at root: storyUpdates: [{add: [{id: "us1", title: "Login", ...}]}]
-  - Add under story group: storyUpdates: [{under: "auth", add: [{id: "login", title: "Login Flow", ...}]}]
+  - Add at root: storyUpdates: [{add: [{id: "us1", title: "log in", ...}]}]
+  - Add under story group: storyUpdates: [{under: "auth", add: [{id: "login", title: "log in with email", ...}]}]
   - Remove: storyUpdates: [{remove: ["old_story"]}]
   - Combined: storyUpdates: [{under: "auth", add: [{id: "new_flow", ...}], remove: ["old_flow"]}]`;
 }
 var ANCHOR_RULES, ANCHOR_DISCOVERY, ANCHOR_VERIFICATION, FORMAT_REF_COMPONENTS, FORMAT_REF_CONNECTIONS, FORMAT_REF_DRAFT_STORIES_BLOCK, CROSS_REF_UNCOVERED_DRAFT_STUB, CROSS_REF_UNCOVERED_REAL_STORY, FORMAT_REF_STORIES;
 var init_scanPrompts = __esm({
   "../shared/scanPrompts.ts"() {
+    init_storyNaming();
     ANCHOR_RULES = `Every component must have either \`anchors\` (non-empty array) or \`unanchored: true\`. No bare components.
 
 Pick the anchor kind based on how the component lives in code:
@@ -12637,12 +12649,15 @@ async function getLanguage(lang, cacheRoot = defaultCacheRoot()) {
   return language;
 }
 async function getParser(lang, cacheRoot) {
+  const cached = parserCache.get(lang);
+  if (cached) return cached;
   const language = await getLanguage(lang, cacheRoot);
   const parser = new Parser();
   parser.setLanguage(language);
+  parserCache.set(lang, parser);
   return parser;
 }
-var initialized, languageCache;
+var initialized, languageCache, parserCache;
 var init_parser = __esm({
   "src/analyze/tree-sitter/parser.ts"() {
     "use strict";
@@ -12650,6 +12665,7 @@ var init_parser = __esm({
     init_grammars();
     initialized = false;
     languageCache = /* @__PURE__ */ new Map();
+    parserCache = /* @__PURE__ */ new Map();
   }
 });
 
@@ -12977,22 +12993,34 @@ var init_extract = __esm({
 
 // src/analyze/tree-sitter/symbols.ts
 import { Query } from "web-tree-sitter";
+async function getQuery(lang) {
+  const cached = queryCache.get(lang);
+  if (cached) return cached;
+  const query = new Query(await getLanguage(lang), SYMBOL_QUERIES[lang]);
+  queryCache.set(lang, query);
+  return query;
+}
 async function extractSymbols(lang, source) {
   const parser = await getParser(lang);
   const tree = parser.parse(source);
   if (!tree) {
     return [];
   }
-  const language = await getLanguage(lang);
-  const query = new Query(language, SYMBOL_QUERIES[lang]);
-  return symbolsFromMatches(query.matches(tree.rootNode));
+  try {
+    const query = await getQuery(lang);
+    return symbolsFromMatches(query.matches(tree.rootNode));
+  } finally {
+    tree.delete();
+  }
 }
+var queryCache;
 var init_symbols = __esm({
   "src/analyze/tree-sitter/symbols.ts"() {
     "use strict";
     init_parser();
     init_queries();
     init_extract();
+    queryCache = /* @__PURE__ */ new Map();
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@archme/cli",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Map your codebase into a living architecture diagram: run `archme init` in a repo to scan it, `archme daemon start` to keep it current on every commit.",
   "type": "module",
   "license": "SEE LICENSE IN LICENSE",