@codeyam/codeyam-cli 0.1.0-staging.483fdc2 → 0.1.0-staging.62d4615

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-BQ-1XyEa.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-C2h1v1XD.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-04T17:33:55.043Z",
-  "buildTime": 1770226435043,
-  "buildNumber": 583,
-  "semanticVersion": "0.1.583",
-  "version": "0.1.583 (2026-02-04T17:33)"
+  "buildTimestamp": "2026-02-09T18:13:22.190Z",
+  "buildTime": 1770660802190,
+  "buildNumber": 616,
+  "semanticVersion": "0.1.616",
+  "version": "0.1.616 (2026-02-09T18:13)"
 }

package/codeyam-cli/templates/codeyam-memory-hook.sh

@@ -3,7 +3,7 @@
 # Ensures rules are reviewed when associated code changes
 #
 # This hook checks that rules with matching `paths` patterns have been reviewed
-# (indicated by an updated `timestamp` field) when associated code files are modified.
+# (indicated by an updated timestamp in .claude/codeyam-rule-state.json) when associated code files are modified.
 
 set -e
 
@@ -84,15 +84,14 @@ matches_pattern() {
   echo "$file" | grep -qE "$regex_pattern" 2>/dev/null
 }
 
-# Parse timestamp from YAML frontmatter
+# Read timestamp from .claude/codeyam-rule-state.json
+RULE_STATE_FILE=".claude/codeyam-rule-state.json"
 get_rule_timestamp() {
   local rule_file="$1"
-  # Extract content between first two --- lines, then find timestamp
-  sed -n '1,/^---$/!{/^---$/q;p}' "$rule_file" 2>/dev/null | \
-    grep -E '^timestamp:' | \
-    sed 's/timestamp:[[:space:]]*//' | \
-    tr -d "'" | tr -d '"' | \
-    head -1
+  # Extract relative path from .claude/rules/
+  local rule_name="${rule_file#.claude/rules/}"
+  if [ ! -f "$RULE_STATE_FILE" ]; then echo ""; return; fi
+  node -e "try{const d=JSON.parse(require('fs').readFileSync('$RULE_STATE_FILE','utf-8'));console.log((d.rules&&d.rules['$rule_name']&&d.rules['$rule_name'].timestamp)||'')}catch{console.log('')}"
 }
 
 # Parse paths from YAML frontmatter
@@ -186,8 +185,8 @@ if [ -n "$OUTDATED_RULES" ]; then
   echo ""
   echo "  To proceed:"
   echo "    1. Review each rule to ensure it's still accurate"
-  echo "    2. Update the 'timestamp' field in the YAML frontmatter"
-  echo "    3. Stage the updated rule file(s)"
+  echo "    2. Run 'codeyam memory touch' to update timestamps"
+  echo "    3. Stage the updated .claude/codeyam-rule-state.json"
   echo "    4. Commit again"
   echo ""
   echo "  Or ask Claude to \"run \`codeyam memory status\` and follow the instructions.\""

package/codeyam-cli/templates/codeyam:memory.md

@@ -44,19 +44,21 @@ Check if this is the first time running memory.
 If CLAUDE.md doesn't contain a "When Confused / With Mistakes" section, add close to the top:
 
 ```markdown
-## When Confused / With Mistakes: Stop. Ask. Document.
+## Continuous Documentation
 
-- If you are not sure about something stop and ask about it.
-- If you attempt something and it goes wrong then you are confused. Stop and ask about it.
-- If the user is unable to help. Do your best to research.
-- Then document the findings!
+As you work, think about any information that might be helpful to know in future work sessions without the user re-providing the information.
+
+This might include
+
+- High-level architecture for complex areas of the codebase (if not obvious)
+- Specific commands that are recommended
+- Debugging strategies for complex areas of the codebase (if not obvious)
+- Anything confusing that is encountered in the work session
 
 ### Documenting Confusion / Mistakes
 
-It is very important to document any confusion or mistakes you encounter in Claude Rules (`.claude/rules`).
+It is very important to document any tribal knowledge, complex architectural decisions, and any confusion or mistakes you encounter in Claude Rules (`.claude/rules`).
 Please see `.codeyam/rules/instructions.md` for guidance.
-
-After making any code changes please run `codeyam memory status` and follow the instructions.
 ```
 
 ### 1B. Verify Instructions File
@@ -335,7 +337,6 @@ Use `pnpm jest` to run tests. Configuration is in `jest.config.ts`.
 ---
 paths:
   - 'specific/path/**/*.ts'
-category: architecture | testing | faq
 timestamp: [CURRENT_ISO_TIMESTAMP]
 ---
 

package/codeyam-cli/templates/codeyam:new-rule.md

@@ -8,45 +8,6 @@ description: |
 
 # Create New Claude Rule
 
-## Before Creating: The Confusion Test
-
-Only create rules that document genuinely confusing aspects—not things Claude can figure out by reading code.
-
-**Ask yourself:**
-
-1. **Could Claude figure this out by reading the code?**
-   - If YES → don't create the rule
-   - If NO → proceed
-
-2. **Does this explain "why" not just "what"?**
-   - Good: Historical context, gotchas, non-obvious behavior
-   - Bad: What functions do, how files are structured
-
-3. **Would this have prevented a past mistake?**
-   - If you can point to a bug or confusion this would have prevented → create it
-   - If it's just "nice to know" → skip it
-
-## Creating the Rule
-
 Read `.codeyam/rules/instructions.md` for detailed guidance on structure and formatting.
 
 If the instructions file doesn't exist, copy it from `codeyam-cli/templates/rules-instructions.md`.
-
-### Quick Template
-
-```markdown
----
-paths:
-  - 'specific/path/**/*.ts'
-category: architecture | testing | faq
-timestamp: [CURRENT_ISO_TIMESTAMP]
----
-
-## [Clear, Descriptive Title]
-
-[What's the gotcha/insight/non-obvious thing?]
-
-### Why This Matters
-
-[What would go wrong if someone didn't know this?]
-```

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

@@ -0,0 +1,54 @@
+#!/usr/bin/env python3
+"""
+UserPromptSubmit hook: surfaces rule-reflection notifications to the main session.
+
+The background rule-reflection agents write summaries to notification files
+in /tmp/claude-rule-markers/ when they create or update rules.
+This hook checks for those files on each user message, prints them to stdout
+(which Claude sees as injected context), and deletes them.
+
+Supports three notification files (legacy combined + split agents):
+- rule-notification.md (legacy/backward-compat)
+- rule-notification-stale.md (stale rules agent)
+- rule-notification-conversation.md (conversation review agent)
+"""
+
+import os
+import sys
+
+MARKER_DIR = '/tmp/claude-rule-markers'
+NOTIFICATION_FILES = [
+    'rule-notification.md',
+    'rule-notification-stale.md',
+    'rule-notification-conversation.md',
+]
+
+
+def main():
+    collected = []
+
+    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
+
+    if collected:
+        print('\n\n'.join(collected))
+
+
+if __name__ == '__main__':
+    main()