@codeyam/codeyam-cli 0.1.0-staging.6e699e5 → 0.1.0-staging.79ef713

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

@@ -1 +1 @@
-import{Y as G,M as H,N as I,W as J,O as K,R as L,T as Z,V as _,U as $,X as rr,Q as tr}from"./assets/server-build-DRTmerg9.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"react-syntax-highlighter";import"react-syntax-highlighter/dist/cjs/styles/prism/index.js";import"node:crypto";import"v8";import"react-markdown";import"react-diff-viewer-continued";export{G as assets,H as assetsBuildDirectory,I as basename,J as entry,K as future,L as isSpaMode,Z as prerender,_ as publicPath,$ as routeDiscovery,rr as routes,tr 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-Cq5Vqcob.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-01-27T18:34:59.371Z",
-  "buildTime": 1769538899371,
-  "buildNumber": 542,
-  "semanticVersion": "0.1.542",
-  "version": "0.1.542 (2026-01-27T18:34)"
+  "buildTimestamp": "2026-02-09T23:40:30.053Z",
+  "buildTime": 1770680430053,
+  "buildNumber": 618,
+  "semanticVersion": "0.1.618",
+  "version": "0.1.618 (2026-02-09T23:40)"
 }

package/codeyam-cli/templates/{codeyam-power-rules-hook.sh → codeyam-memory-hook.sh}

@@ -1,9 +1,9 @@
 #!/bin/bash
-# CodeYam Power Rules - Pre-commit Hook (BLOCKING)
+# CodeYam Memory - Pre-commit Hook (BLOCKING)
 # 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
@@ -177,7 +176,7 @@ done < <(find "$RULES_DIR" -name "*.md" -type f 2>/dev/null)
 if [ -n "$OUTDATED_RULES" ]; then
   echo ""
   echo "================================================================"
-  echo "  Power Rules: Outdated Documentation Detected"
+  echo "  Claude Rules (Codeyam Memory): Outdated Documentation Detected"
   echo "================================================================"
   echo ""
   echo "  The following rules have timestamps older than the code"
@@ -186,11 +185,11 @@ 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 run: /codeyam:power-rules to review all rules"
+  echo "  Or ask Claude to \"run \`codeyam memory status\` and follow the instructions.\""
   echo ""
   echo "================================================================"
   echo ""

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

@@ -23,6 +23,34 @@ When a user asks to debug a scenario or analysis (e.g., `/codeyam:diagnose [ID]`
 
 Stopping after identifying a bug category without capturing screenshots defeats the purpose of debugging.
 
+## Critical: Persistence and User Communication
+
+**DO NOT give up prematurely.** Every issue can be fixed by editing files in the tmp folder. If you find yourself thinking:
+
+- "This requires an engine-level fix"
+- "This is blocked by a code generation bug"
+- "The engine doesn't properly handle X"
+
+**STOP.** These statements are incorrect. You have full access to edit any file in `/tmp/codeyam/local-dev/{slug}/project/`. The "engine" just wrote those files—they're plain TypeScript/JavaScript that you can edit directly.
+
+### Before Stopping or Concluding
+
+1. **Try at least 3 different approaches** to fix the issue
+2. **Never unilaterally decide to stop.** If you've been debugging and aren't making progress, ASK THE USER:
+   > "I've tried X, Y, and Z but haven't resolved the issue yet. Would you like me to continue investigating other approaches, or should I document what I've found so far?"
+3. **Only stop when the user agrees** or when you've successfully captured quality screenshots
+
+### The "Engine Bug" Misconception
+
+When you identify a Category 4 issue (code generation bug), this does NOT mean you're blocked. It means:
+
+- The bug is in how CodeYam generates code (useful info for the CodeYam team)
+- You MUST still fix it manually by editing files in the tmp folder
+- You MUST still capture quality screenshots
+- You document what you fixed so the CodeYam team can improve the engine
+
+**"Engine bug" is a diagnosis category, not an excuse to stop.**
+
 ---
 
 ## Debug Flow Summary
@@ -34,11 +62,12 @@ Stopping after identifying a bug category without capturing screenshots defeats
 │          Retrieve the analysis id to use in the debug command       │
 │                    │                                                │
 │                    ▼                                                │
-│  Step 1: codeyam debug [ANALYSIS ID]  (generates files to inspect)  │
-│  Step 2: Identify error type from logs/output                       │
-│  Step 3: Diagnose root cause category (1-4)                         │
-│  Step 4: Attempt fix (database edit or universal mock)              │
-│  Step 5: Verify locally (curl returns 200)                          │
+│  Step 1: Copy the logs to a temporary location (see below).         |
+|  Step 2: codeyam debug [ANALYSIS ID]  (generates files to inspect)  │
+│  Step 3: Identify error type from logs/output                       │
+│  Step 4: Diagnose root cause category (1-4)                         │
+│  Step 5: Attempt fix (database edit or universal mock)              │
+│  Step 6: Verify locally (curl returns 200)                          │
 │                   │                                                 │
 │         ┌─────────┴─────────┐                                       │
 │         ▼                   ▼                                       │
@@ -52,12 +81,12 @@ Stopping after identifying a bug category without capturing screenshots defeats
 │         │         Verify without regenerating                       │
 │         │                   │                                       │
 │         ▼                   ▼                                       │
-│   Step 6: Recapture    Step 6: Recapture --capture-only             │
+│   Step 7: Recapture    Step 7: Recapture --capture-only             │
 │   (normal)             (preserves file fixes)                       │
 │         │                   │                                       │
 │         └─────────┬─────────┘                                       │
 │                   ▼                                                 │
-│   Step 7: Verify screenshots (check for client-side errors)         │
+│   Step 8: Verify screenshots (check for client-side errors)         │
 │                   │                                                 │
 │                   ▼                                                 │
 │   Verify ALL files exist on disk                                    │
@@ -68,18 +97,128 @@ Stopping after identifying a bug category without capturing screenshots defeats
 └─────────────────────────────────────────────────────────────────────┘
 ```
 
+**Logs:** Before debugging copy the original logs to a temorary location as the debugging will overwrite these logs and they are valuable for debugging issues.
+
+Original Logs Locaion: `/tmp/codeyam/local-dev/{slug}/codeyam/logs.txt`
+Temporary location: `/tmp/codeyam/local-dev/{slug}/debug/original-logs.txt`
+
 **Notice:** Both paths lead to "Recapture" and "Verify screenshots". There is no path that ends after just identifying a bug category. You must always capture quality screenshots before completing.
 
 ---
 
+## MANDATORY: Session Context (Do This First!)
+
+Long debugging sessions cause context loss. To prevent forgetting critical information:
+
+### Step 1: Create Session Context File
+
+At the **very start** of debugging, create `.codeyam/debug-session.md` in the **original project directory**:
+
+```markdown
+# Debug Session Context
+
+**IMPORTANT**: Keep a todo item "📍 Re-read debug session context" that is NEVER marked complete.
+If the todo disappears, add it back immediately.
+
+## Key Locations
+
+- **Original project**: [FULL PATH - run all codeyam commands here]
+- **Tmp folder**: /tmp/codeyam/local-dev/[SLUG]/project (edit files here, do NOT run codeyam commands)
+- **Database**: [ORIGINAL PROJECT]/.codeyam/db.sqlite3
+- **Logs**: /tmp/codeyam/local-dev/[SLUG]/codeyam/log.txt
+
+## IDs
+
+- **Analysis ID**: [ID]
+- **Scenario ID**: [ID]
+- **Entity**: [NAME] at [FILE PATH]
+
+## URLs (fill in after running codeyam debug)
+
+- **Scenario URL**: http://localhost:[PORT]/static/codeyam-sample
+- **Dev server port**: [PORT from codeyam debug output]
+
+## Commands Reference
+
+All commands run from: [ORIGINAL PROJECT PATH]
+
+- `codeyam debug [ANALYSIS_ID]` - regenerate files (overwrites tmp folder!)
+- `codeyam recapture [ID]` - regenerate AND capture (overwrites tmp folder!)
+- `codeyam recapture [ID] --capture-only` - capture WITHOUT regenerating (preserves your edits)
+- `codeyam test-startup` - test startup (overwrites tmp folder!)
+```
+
+### Step 2: Create Persistent Todo
+
+Use TodoWrite to create this todo list with the first item being a persistent reminder:
+
+```
+📍 Re-read .codeyam/debug-session.md before any codeyam command (NEVER complete this)
+```
+
+**CRITICAL**: The first todo item must NEVER be marked as completed. It serves as a constant reminder to check your session context before running commands. If you accidentally complete it or it disappears, add it back immediately.
+
+### Step 3: Read Context Before Actions
+
+**Before running ANY of these commands**, re-read `.codeyam/debug-session.md`:
+
+- `codeyam debug`
+- `codeyam recapture`
+- `codeyam test-startup`
+- Any database queries
+
+This prevents running commands from the wrong directory or forgetting key IDs.
+
+---
+
+## Critical: Where to Run Commands
+
+**All `codeyam` commands MUST be run from the ORIGINAL PROJECT DIRECTORY**, not from the tmp folder.
+
+| Location                                                               | What's There                                                   | Run Commands Here?                                |
+| ---------------------------------------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------- |
+| **Original project** (e.g., `/Users/.../clients-codeyam/boltwise/app`) | Database (`.codeyam/db.sqlite3`), config, universal mocks      | **YES - run all codeyam commands here**           |
+| **Tmp folder** (`/tmp/codeyam/local-dev/{slug}/project/`)              | Copy of project with mock injections, generated scenario files | **NO - only edit files here, don't run commands** |
+
+**Common mistake:** Running `codeyam recapture` from the tmp folder. This will fail with "Not in a CodeYam project" because the database doesn't exist there.
+
+```bash
+# WRONG - running from tmp folder
+cd /tmp/codeyam/local-dev/boltwise-app/project
+codeyam recapture abc123  # ❌ Fails: "Not in a CodeYam project"
+
+# CORRECT - running from original project directory
+cd /Users/jaredcosulich/workspace/codeyam/clients-codeyam/boltwise/app
+codeyam recapture abc123  # ✅ Works
+```
+
+**Workflow:**
+
+1. Edit files in `/tmp/codeyam/local-dev/{slug}/project/` to fix issues
+2. Test by curling the dev server running from the tmp folder
+3. **Switch back to the original project directory** to run `codeyam recapture`
+
+---
+
 ## What You Can and Cannot Modify
 
 **NEVER modify the client's original source code in the workspace.** Only modify files in the tmp folder.
 
+### CRITICAL: Fix the Mocks, Never the Client Code
+
+When debugging errors, the fix is ALWAYS in the mock data or mock code—never in the client's components or application code.
+
+**If a component crashes due to unexpected data:**
+
+- Fix the mock data to provide what the component expects
+- Do NOT modify the component to handle the bad data
+
+**The client's code is sacred.** Our job is to make the simulation environment correct, not to "improve" or "harden" the client's code. Even if a component could be more defensive, that's not our fix to make.
+
 **You CAN modify:**
 
-- Data in the local SQLite database (`.codeyam/db.sqlite3`)
-- Universal mocks in `.codeyam/universal-mocks`
+- Data in the local SQLite database (`.codeyam/db.sqlite3`) - in the **original project directory**
+- Universal mocks in `.codeyam/universal-mocks` - in the **original project directory**
 - **Files in `/tmp/codeyam/local-dev/{slug}/project/`** - These are temporary copies used for simulation
   - Generated mock files in `__codeyamMocks__/` directories
   - Layout/route files that wrap scenarios
@@ -168,12 +307,12 @@ This is the most important step. Determine WHERE in the pipeline the bug origina
 
 ### The 4 Error Categories
 
-| Category | What's Wrong                                         | Where to Check            | Fixable Locally?       |
-| -------- | ---------------------------------------------------- | ------------------------- | ---------------------- |
-| **1**    | Missing attribute in `isolatedDataStructure`         | `entities.metadata`       | Sometimes (re-analyze) |
-| **2**    | Attribute not merged into `mergedDataStructure`      | `analyses.metadata`       | Sometimes (re-analyze) |
-| **3**    | Data structure complete, but scenario data wrong     | `scenarios.metadata`      | Yes (edit mockData)    |
-| **4**    | Data complete, but mock code/mock data written wrong | Generated files in `/tmp` | **No (engine bug)**    |
+| Category | What's Wrong                                         | Where to Check            | Fixable Locally?              |
+| -------- | ---------------------------------------------------- | ------------------------- | ----------------------------- |
+| **1**    | Missing attribute in `isolatedDataStructure`         | `entities.metadata`       | Sometimes (re-analyze)        |
+| **2**    | Attribute not merged into `mergedDataStructure`      | `analyses.metadata`       | Sometimes (re-analyze)        |
+| **3**    | Data structure complete, but scenario data wrong     | `scenarios.metadata`      | Yes (edit mockData)           |
+| **4**    | Data complete, but mock code/mock data written wrong | Generated files in `/tmp` | **Yes (edit files directly)** |
 
 ### Diagnostic Queries
 
@@ -212,7 +351,7 @@ sqlite3 .codeyam/db.sqlite3 \
 6. **Check generated mock code** - Is the mock code syntactically/semantically correct? If wrong → **Category 4 (engine bug)**
 7. **Check generated imports** - Are the imports correct? Are entities containing environment variables mocked out? If wrong → **Category 4 (engine bug)**
 
-### Category 4 Indicators (Engine Bug)
+### Category 4 Indicators (Code Generation Issue)
 
 The issue is Category 4 if:
 
@@ -221,11 +360,15 @@ The issue is Category 4 if:
 - BUT the generated mock code has syntax errors, wrong structure, or doesn't match the data
 - Database edits don't fix the generated code (it regenerates wrong)
 
-**IMPORTANT: Identifying Category 4 is NOT the end of debugging.** You must still:
+**Category 4 does NOT mean you are blocked.** You have full access to fix these issues:
 
-1. Fix the code manually in the tmp folder
-2. Capture quality screenshots with `--capture-only`
-3. Document what you fixed for the CodeYam team
+1. **Edit the files directly** in `/tmp/codeyam/local-dev/{slug}/project/`
+2. **Fix any syntax errors, wrong imports, missing mocks** - these are just TypeScript files
+3. **Restart the dev server** and verify the fix works
+4. **Capture quality screenshots** with `codeyam recapture --capture-only`
+5. **Document what you fixed** for the CodeYam team to improve the engine
+
+The term "engine bug" means the CodeYam code generation has a bug—it does NOT mean you cannot fix the issue locally. You always can.
 
 ---
 
@@ -345,7 +488,9 @@ After making **database changes** (Categories 1-3):
 
 ## Step 5a: Fix Code Issues in Tmp Folder (Category 4)
 
-If the error is in bad imports, generated code or mock files, you can fix them directly in the tmp folder:
+If the error is in bad imports, generated code or mock files, you can fix them directly in the tmp folder.
+
+**REMINDER: Only fix GENERATED files (mocks, layouts, routes)—never the client's application code.** If a client component crashes, the fix is in the mock data or mock code, not in the component itself.
 
 ### Locate the Problematic File
 
@@ -384,11 +529,19 @@ cd /tmp/codeyam/local-dev/{slug}/project
 npm run dev  # or pnpm dev / yarn dev
 ```
 
-Then curl the scenario URL to verify the fix works:
+Then verify the fix works. You can either:
 
-```bash
-curl -s http://localhost:3112/static/codeyam-sample | head -50
-```
+1. **Curl the URL** to check for errors:
+
+   ```bash
+   curl -s http://localhost:3112/static/codeyam-sample | head -50
+   ```
+
+2. **Ask the user to verify visually**: If the fix involves visual output or you're unsure if it worked, ask the user to visit the URL and confirm:
+
+   > "I've fixed the mock data. Can you visit http://localhost:3112/static/codeyam-sample and let me know if the component renders correctly now?"
+
+   This is especially useful for client-side rendering issues that curl won't catch.
 
 ---