@codeyam/codeyam-cli 0.1.6 → 0.1.7

package/codeyam-cli/src/webserver/build/server/index.js

@@ -1 +1 @@
-import{Y as H,Z as I,M as J,N as K,W as L,O as _,R as $,T as rr,V as tr,U as or,X as ir,Q as pr}from"./assets/server-build-69rRZnZo.js";import"react/jsx-runtime";import"node:stream";import"@react-router/node";import"react-router";import"isbot";import"react-dom/server";import"react";import"lucide-react";import"fetch-retry";import"better-sqlite3";import"pg";import"fs";import"path";import"kysely";import"kysely/helpers/sqlite";import"kysely/helpers/postgres";import"typescript";import"fs/promises";import"os";import"prompts";import"chalk";import"crypto";import"child_process";import"url";import"util";import"dotenv";import"events";import"uuid";import"openai";import"p-queue";import"p-retry";import"@aws-sdk/client-dynamodb";import"lru-cache";import"pluralize";import"piscina";import"json5";import"@aws-sdk/util-dynamodb";import"v8";import"react-syntax-highlighter";import"react-syntax-highlighter/dist/cjs/styles/prism/index.js";import"node:crypto";import"minimatch";import"react-markdown";import"remark-gfm";import"react-diff-viewer-continued";export{H as allowedActionOrigins,I as assets,J as assetsBuildDirectory,K as basename,L as entry,_ as future,$ as isSpaMode,rr as prerender,tr as publicPath,or as routeDiscovery,ir as routes,pr as ssr};
+import{Y as H,Z as I,M as J,N as K,W as L,O as _,R as $,T as rr,V as tr,U as or,X as ir,Q as pr}from"./assets/server-build-9OU4lmvL.js";import"react/jsx-runtime";import"node:stream";import"@react-router/node";import"react-router";import"isbot";import"react-dom/server";import"react";import"lucide-react";import"fetch-retry";import"better-sqlite3";import"pg";import"fs";import"path";import"kysely";import"kysely/helpers/sqlite";import"kysely/helpers/postgres";import"typescript";import"fs/promises";import"os";import"prompts";import"chalk";import"crypto";import"child_process";import"url";import"util";import"dotenv";import"events";import"uuid";import"openai";import"p-queue";import"p-retry";import"@aws-sdk/client-dynamodb";import"lru-cache";import"pluralize";import"piscina";import"json5";import"@aws-sdk/util-dynamodb";import"v8";import"react-syntax-highlighter";import"react-syntax-highlighter/dist/cjs/styles/prism/index.js";import"node:crypto";import"minimatch";import"react-markdown";import"remark-gfm";import"react-diff-viewer-continued";export{H as allowedActionOrigins,I as assets,J as assetsBuildDirectory,K as basename,L as entry,_ as future,$ as isSpaMode,rr as prerender,tr as publicPath,or as routeDiscovery,ir as routes,pr as ssr};

package/codeyam-cli/src/webserver/build-info.json

@@ -1,7 +1,7 @@
 {
-  "buildTimestamp": "2026-02-24T16:49:39.429Z",
-  "buildTime": 1771951779429,
-  "buildNumber": 694,
-  "semanticVersion": "0.1.694",
-  "version": "0.1.694 (2026-02-24T16:49)"
+  "buildTimestamp": "2026-02-25T00:13:21.654Z",
+  "buildTime": 1771978401654,
+  "buildNumber": 724,
+  "semanticVersion": "0.1.724",
+  "version": "0.1.724 (2026-02-25T00:13)"
 }

package/codeyam-cli/templates/prompts/conversation-guidance.txt

@@ -30,3 +30,15 @@ Read the full transcript for these signals:
 **Critical check:** Read the actual source files that were modified. If the code already contains comments, guard patterns, or tests that explain the insight, the code is the documentation — skip the rule unless the file is complex and you've made a mistake or the user had to interrupt and correct you.
 
 Show your thinking before proceeding with creating or updating rules.
+
+### How to write rules
+
+**Rules must be forward-looking, not historical.** You are reading a session transcript where bugs were found and fixed, but the rule should describe the *current* codebase, not tell the story of what went wrong, what was fixed, etc. The code has already been updated — past bugs are no longer relevant.
+
+- **DO**: State constraints and requirements ("this script MUST copy directories recursively, not just files")
+- **DO**: Explain *why* something matters ("errors in prompt copying are silently caught, so missing directories won't surface as errors")
+- **DON'T**: Describe what old code did ("the old version only copied files, causing X to be missing")
+- **DON'T**: Narrate the debugging journey ("we discovered that the catch block was swallowing errors")
+- **DON'T**: Note issues or known gaps if they are actively being worked on!
+
+Think of the reader as a developer about to modify these files. They need to know what constraints to preserve and what pitfalls to watch for — not what happened in the past if it is no longer relevant.

package/codeyam-cli/templates/prompts/conversation-prompt.txt

@@ -23,6 +23,6 @@ The project root is {{PROJECT_DIR}}
 
 CRITICAL: All rule files MUST be written to {{PROJECT_DIR}}/.claude/rules/ (the project directory). Always use the full absolute path when writing rule files.
 
-CRITICAL: Before writing any rule file, you MUST call the rule-path API to determine the correct subdirectory:
-  curl -s 'http://localhost:3111/api/rule-path?paths=path/one&paths=path/two'
-Pass all paths from your frontmatter. The API returns the correct .claude/rules/ subdirectory. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.
+CRITICAL: Before writing any rule file, you MUST run the rule-path command to determine the correct subdirectory:
+  codeyam memory rule-path path/one path/two
+Pass all paths from your frontmatter. The command returns the correct .claude/rules/ subdirectory as JSON. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.

package/codeyam-cli/templates/prompts/interruption-prompt.txt

@@ -26,6 +26,6 @@ The project root is {{PROJECT_DIR}}
 
 CRITICAL: All rule files MUST be written to {{PROJECT_DIR}}/.claude/rules/ (the project directory). Always use the full absolute path when writing rule files.
 
-CRITICAL: Before writing any rule file, you MUST call the rule-path API to determine the correct subdirectory:
-  curl -s 'http://localhost:3111/api/rule-path?paths=path/one&paths=path/two'
-Pass all paths from your frontmatter. The API returns the correct .claude/rules/ subdirectory. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.
+CRITICAL: Before writing any rule file, you MUST run the rule-path command to determine the correct subdirectory:
+  codeyam memory rule-path path/one path/two
+Pass all paths from your frontmatter. The command returns the correct .claude/rules/ subdirectory as JSON. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.

package/codeyam-cli/templates/prompts/stale-rules-prompt.txt

@@ -19,6 +19,6 @@ The project root is {{PROJECT_DIR}}
 
 CRITICAL: All rule files MUST be written to {{PROJECT_DIR}}/.claude/rules/ (the project directory), NOT ~/.claude/rules/ (the user home directory). Always use the full absolute path when writing rule files.
 
-CRITICAL: Before writing any rule file, you MUST call the rule-path API to determine the correct subdirectory:
-  curl -s 'http://localhost:3111/api/rule-path?paths=path/one&paths=path/two'
-Pass all paths from your frontmatter. The API returns the correct .claude/rules/ subdirectory. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.
+CRITICAL: Before writing any rule file, you MUST run the rule-path command to determine the correct subdirectory:
+  codeyam memory rule-path path/one path/two
+Pass all paths from your frontmatter. The command returns the correct .claude/rules/ subdirectory as JSON. Do NOT guess the placement from the first path — rules with paths spanning multiple directories belong at their common ancestor.

package/codeyam-cli/templates/rule-notification-hook.py

@@ -14,6 +14,7 @@ Supports four notification files (legacy combined + split agents):
 - rule-notification-interruption.md (interruption review agent)
 """
 
+import json
 import os
 import sys
 
@@ -26,27 +27,53 @@ NOTIFICATION_FILES = [
 ]
 
 
+def get_project_slug():
+    """
+    Derive project slug from .codeyam/config.json (matching getProjectSlug() on the TS side).
+    Falls back to os.path.basename(project_dir) if config is absent or malformed.
+    """
+    project_dir = os.environ.get('CLAUDE_PROJECT_DIR', os.getcwd())
+    try:
+        config_path = os.path.join(project_dir, '.codeyam', 'config.json')
+        with open(config_path, 'r') as f:
+            config = json.load(f)
+        slug = config.get('projectSlug', '')
+        if slug:
+            return slug
+    except (IOError, json.JSONDecodeError, KeyError):
+        pass
+    return os.path.basename(project_dir)
+
+
 def main():
     collected = []
+    slug = get_project_slug()
+
+    # Check slug subdirectory first, then fall back to flat directory
+    dirs_to_check = [os.path.join(MARKER_DIR, slug), MARKER_DIR]
 
     for filename in NOTIFICATION_FILES:
-        filepath = os.path.join(MARKER_DIR, filename)
-        if not os.path.exists(filepath):
-            continue
-
-        try:
-            with open(filepath, 'r') as f:
-                content = f.read().strip()
-        except IOError:
-            continue
-
-        if content:
-            collected.append(content)
-
-        try:
-            os.remove(filepath)
-        except OSError:
-            pass
+        for check_dir in dirs_to_check:
+            filepath = os.path.join(check_dir, filename)
+            if not os.path.exists(filepath):
+                continue
+
+            try:
+                with open(filepath, 'r') as f:
+                    content = f.read().strip()
+            except IOError:
+                continue
+
+            if content:
+                collected.append(content)
+
+            try:
+                os.remove(filepath)
+            except OSError:
+                pass
+
+            # Found in this directory — don't check the fallback
+            break
 
     if collected:
         print('\n\n'.join(collected))

package/codeyam-cli/templates/rule-reflection-hook.py

@@ -120,6 +120,24 @@ def read_rule_content(rule_name):
     return text
 
 
+def get_project_slug():
+    """
+    Derive project slug from .codeyam/config.json (matching getProjectSlug() on the TS side).
+    Falls back to os.path.basename(project_dir) if config is absent or malformed.
+    """
+    project_dir = os.environ.get('CLAUDE_PROJECT_DIR', os.getcwd())
+    try:
+        config_path = os.path.join(project_dir, '.codeyam', 'config.json')
+        with open(config_path, 'r') as f:
+            config = json.load(f)
+        slug = config.get('projectSlug', '')
+        if slug:
+            return slug
+    except (IOError, json.JSONDecodeError, KeyError):
+        pass
+    return os.path.basename(project_dir)
+
+
 def load_memory_settings():
     """
     Load memory settings from .codeyam/config.json.
@@ -463,8 +481,9 @@ def handle_stop(hook_input):
     if not session_id or not transcript_path:
         return
 
-    marker_dir = Path('/tmp/claude-rule-markers')
-    marker_dir.mkdir(exist_ok=True)
+    slug = get_project_slug()
+    marker_dir = Path('/tmp/claude-rule-markers') / slug
+    marker_dir.mkdir(parents=True, exist_ok=True)
     marker_file = marker_dir / f'{session_id}.marker'
 
     last_line, _ = read_marker(marker_file)
@@ -539,8 +558,9 @@ def handle_user_prompt_submit(hook_input):
     if not session_id or not transcript_path:
         return
 
-    marker_dir = Path('/tmp/claude-rule-markers')
-    marker_dir.mkdir(exist_ok=True)
+    slug = get_project_slug()
+    marker_dir = Path('/tmp/claude-rule-markers') / slug
+    marker_dir.mkdir(parents=True, exist_ok=True)
     marker_file = marker_dir / f'{session_id}.marker'
 
     last_line, was_stop = read_marker(marker_file)

package/codeyam-cli/templates/rules-instructions.md

@@ -61,17 +61,18 @@ Audit dates live in `.claude/codeyam-rule-state.json` (managed by `codeyam memor
 
 Rules must be written to `.claude/rules/`, NOT `.codeyam/rules/`. The instructions file lives in `.codeyam/` but actual rule files go in `.claude/rules/`.
 
-Use the `rule-path` API to compute the correct directory from your frontmatter paths:
+Use `codeyam memory rule-path` to compute the correct directory from your frontmatter paths:
 
 ```
-$ curl -s 'http://localhost:3111/api/rule-path?paths=packages/ai/src/lib/foo.ts&paths=packages/ai/src/utils/bar.ts'
+$ codeyam memory rule-path packages/ai/src/lib/foo.ts packages/ai/src/utils/bar.ts
 {"result":".claude/rules/packages/ai/src/"}
 ```
 
-The API computes the deepest common directory shared by all paths and returns the `.claude/rules/` subdirectory where the rule file should live. Reserve the top level of `.claude/rules/` for rules whose paths genuinely span the entire repo.
+The command computes the deepest common directory shared by all paths and returns the `.claude/rules/` subdirectory where the rule file should live. Reserve the top level of `.claude/rules/` for rules whose paths genuinely span the entire repo.
 
 ## Content Guidelines
 
 - **Be actionable** — "Run `pnpm test:api` for API tests" not "Make sure to run the appropriate tests"
 - **Focus on why, not what** — Gotchas, non-obvious behavior, architectural decisions. The code already shows "what."
 - **Point to specifics** — "Auth tokens are stored in httpOnly cookies via `src/auth/cookies.ts`" beats a vague description.
+- **Be short!** - Context window space is precious! Do not ramble, use bullets, focus on providing clear actionable information.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codeyam/codeyam-cli",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Local development CLI for CodeYam analysis",
   "type": "module",
   "bin": {