@noego/app 0.0.25 → 0.0.26

package/.bashlite/issue.yml

@@ -0,0 +1,799 @@
+name: Handle Ticket
+version: 1
+defaults:
+  engine: anthropic
+  model: claude-sonnet-4-5
+loopLimits:
+  perPhase: 3
+  total: 10
+git:
+  branchPattern: "bashly/issue-{{number}}"
+entry: learn
+
+phases:
+  # Phase 1: Learn the repository
+  - name: learn
+    systemPrompt: |
+      You will see the GitHub issue but do not focus on it yet. Focus only on learning the repository.
+      Read markdown files (NOEGO_FRAMEWORK_GUIDE.md, instructions/forge-testing.md),
+      examine the project structure, understand testing patterns, coding style,
+      and architectural decisions. Summarize the key standards that must be
+      followed when making changes.
+    readOnly: true
+    preActions:
+      - git.clone
+    next: classify_issue
+
+  # Phase 2: Classify the type of issue
+  - name: classify_issue
+    type: decision
+    prompt: |
+      Classify this GitHub issue by its primary nature. Score 0-1:
+
+      **Bug investigation (0.0-0.2):**
+      - Something is broken and needs debugging
+      - Unexpected behavior reported
+      - Error messages or stack traces mentioned
+      - Regression from a previous change
+
+      **Database/migration (0.2-0.4):**
+      - Requires new tables, columns, or schema changes
+      - Mentions database, migration, schema, or SQL
+      - Needs proper CLI migrations
+      - Data model changes
+
+      **Code change (0.4-1.0):**
+      - New feature, enhancement, or refactor
+      - UI changes, API changes, styling
+      - Documentation-only changes
+      - Test additions without code changes
+      - Any implementation work that doesn't involve debugging or migrations
+
+      Consider:
+      - Is the issue about something broken vs something new?
+      - Does it mention database tables, columns, or schema?
+      - Is the primary work investigation or implementation?
+    options: ["bug_investigate", "migration_plan", "code_change_triage"]
+    thresholds: [0.2, 0.5]
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  # ============================================================
+  # CODE CHANGE TRIAGE (bridge to complexity decision)
+  # ============================================================
+
+  - name: code_change_triage
+    systemPrompt: |
+      This issue has been classified as a code change (not a bug or migration).
+      Briefly summarize the scope of work needed so the next phase can assess complexity.
+    readOnly: true
+    next: assess_complexity
+    aiConfig:
+      model: claude-haiku-4-5
+
+  # ============================================================
+  # BUG INVESTIGATION FLOW
+  # ============================================================
+
+  - name: bug_investigate
+    systemPrompt: |
+      Read the GitHub issue carefully. This is a bug report. Your goal is to:
+      1. Understand the reported symptoms and expected behavior
+      2. Trace through the relevant code paths to identify the root cause
+      3. Reproduce the issue by reading tests or running the app if possible
+      4. Document the root cause clearly
+
+      Do not fix the bug yet. Focus on understanding and documenting.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        rootCause:
+          type: string
+          description: Clear explanation of the root cause
+        affectedFiles:
+          type: array
+          items:
+            type: string
+          description: Files involved in the bug
+        reproductionSteps:
+          type: array
+          items:
+            type: string
+          description: Steps to reproduce the issue
+      required:
+        - rootCause
+        - affectedFiles
+    next: bug_plan
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: bug_plan
+    systemPrompt: |
+      Based on the root cause analysis, create a plan to fix the bug.
+      Identify the minimal set of changes needed. Plan regression tests
+      to prevent this bug from recurring. Do not write code yet.
+
+      Categorize each file as: create (new), modify (existing), or delete (remove).
+      List files to read for context with a reason for each.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        filesToCreate:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              purpose:
+                type: string
+            required:
+              - path
+              - purpose
+          description: New files to create
+        filesToModify:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              changes:
+                type: string
+            required:
+              - path
+              - changes
+          description: Existing files to modify and what changes are needed
+        filesToDelete:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to remove
+        filesToRead:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to read for additional context before implementing
+        approach:
+          type: string
+        testCases:
+          type: array
+          items:
+            type: object
+            properties:
+              name:
+                type: string
+              type:
+                type: string
+            required:
+              - name
+              - type
+      required:
+        - filesToModify
+        - approach
+        - testCases
+    next: bug_fix
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: bug_fix
+    systemPrompt: |
+      Execute the fix plan. First read any files listed in filesToRead to gather context.
+      Then implement the minimal changes to resolve the bug and write regression tests.
+      Follow all repository standards.
+    next: bug_test
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: bug_test
+    systemPrompt: |
+      Run the tests to verify the bug fix. Ensure the regression tests pass
+      and no existing tests are broken. Report the results.
+    readOnly: true
+    next: bug_review
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: bug_review
+    type: loop
+    prompt: Are all tests passing and is the bug fully resolved with regression tests?
+    threshold: 0.9
+    loopTarget: bug_fix
+    next: check_svelte
+    aiConfig:
+      model: claude-opus-4-5
+
+  # ============================================================
+  # DATABASE / MIGRATION FLOW
+  # ============================================================
+
+  - name: migration_plan
+    systemPrompt: |
+      Read the GitHub issue carefully. This involves database schema changes.
+      Plan the migration(s) needed:
+      1. What tables/columns need to be created, altered, or dropped
+      2. What the up and down migrations should contain
+      3. How this affects existing repository classes, services, and controllers
+      4. What seed data changes are needed (if any)
+
+      Use the proper CLI to create migrations (never create migration files manually).
+      Do not write code yet.
+
+      Categorize each file as: create (new), modify (existing), or delete (remove).
+      List files to read for context with a reason for each.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        migrations:
+          type: array
+          items:
+            type: object
+            properties:
+              name:
+                type: string
+              description:
+                type: string
+            required:
+              - name
+              - description
+          description: Migrations to create
+        filesToCreate:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              purpose:
+                type: string
+            required:
+              - path
+              - purpose
+          description: New files to create (repos, services, SQL files, tests)
+        filesToModify:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              changes:
+                type: string
+            required:
+              - path
+              - changes
+          description: Existing files to modify and what changes are needed
+        filesToDelete:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to remove
+        filesToRead:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to read for additional context before implementing
+        approach:
+          type: string
+        testCases:
+          type: array
+          items:
+            type: object
+            properties:
+              name:
+                type: string
+              type:
+                type: string
+            required:
+              - name
+              - type
+      required:
+        - migrations
+        - approach
+    next: migration_implement
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: migration_implement
+    systemPrompt: |
+      Execute the migration plan. First read any files listed in filesToRead to gather context.
+      Then:
+      1. Create migrations using the proper CLI tool
+      2. Update repository classes with new queries
+      3. Update services and controllers as needed
+      4. Write tests for the new data layer
+      Follow all repository standards.
+    next: migration_test
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: migration_test
+    systemPrompt: |
+      Run the tests to verify the migration and related changes.
+      Ensure migrations run cleanly up and down. Check that all new
+      and existing tests pass. Report the results.
+    readOnly: true
+    next: migration_review
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: migration_review
+    type: loop
+    prompt: Are all tests passing, migrations running cleanly, and does the implementation fully address the issue?
+    threshold: 0.85
+    loopTarget: migration_implement
+    next: check_svelte
+    aiConfig:
+      model: claude-opus-4-5
+
+  # ============================================================
+  # CODE CHANGE FLOW — complexity routing
+  # ============================================================
+
+  - name: assess_complexity
+    type: decision
+    prompt: |
+      Analyze the complexity of this code change and score it 0-1:
+
+      **Simple (0.0-0.3):**
+      - Documentation updates, README changes
+      - Simple styling tweaks (colors, margins, font sizes)
+      - Typo fixes, renaming variables
+      - Adding comments or simple logging
+      - Straightforward single-file changes with no logic
+
+      **Medium (0.4-0.6):**
+      - Adding new components or routes with basic logic
+      - Simple form handling or validation
+      - Basic API endpoint changes (1-2 files)
+      - Moderate styling with some conditional logic
+      - Integration of existing patterns (2-3 files)
+
+      **Complex (0.7-1.0):**
+      - Touches 4+ files across multiple layers
+      - State management, complex business rules
+      - Async operations, race conditions
+      - Multi-layer changes (controller + service + repository + SQL)
+      - Multi-component coordination across server/client
+      - Performance optimization
+      - Integration of multiple systems
+      - New full-stack features (route + controller + service + repo + tests)
+      - Changes that ripple across many dependents
+
+      Consider:
+      - How many files will need to change? (4+ files = likely complex)
+      - Does it span multiple layers (API, service, repository, SQL, UI)?
+      - Does it require understanding the NoEgo framework deeply?
+      - Will it need multiple types of tests?
+      - Could a change in one file break behavior in several others?
+    options: ["easy_plan", "medium_plan", "hard_plan"]
+    thresholds: [0.4, 0.7]
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  # === Easy path: All Haiku ===
+  - name: easy_plan
+    systemPrompt: |
+      Read the GitHub issue carefully. Based on the issue and repository standards,
+      create a brief implementation plan. Do not write code yet.
+
+      Categorize each file as: create (new), modify (existing), or delete (remove).
+      List files to read for context with a reason for each.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        filesToCreate:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              purpose:
+                type: string
+            required:
+              - path
+              - purpose
+        filesToModify:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              changes:
+                type: string
+            required:
+              - path
+              - changes
+        filesToDelete:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+        filesToRead:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+        approach:
+          type: string
+      required:
+        - approach
+    next: easy_implement
+    aiConfig:
+      model: claude-haiku-4-5
+
+  - name: easy_implement
+    systemPrompt: |
+      Execute the plan. First read any files listed in filesToRead to gather context.
+      Then implement the changes as designed.
+      Follow all repository standards learned in the first phase.
+    next: check_svelte
+    aiConfig:
+      model: claude-haiku-4-5
+
+  # === Medium path: Haiku plan, Sonnet implement ===
+  - name: medium_plan
+    systemPrompt: |
+      Read the GitHub issue carefully. Based on the issue and repository standards,
+      create a detailed implementation plan. Plan what tests are needed.
+      Do not write code yet.
+
+      Categorize each file as: create (new), modify (existing), or delete (remove).
+      List files to read for context with a reason for each.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        filesToCreate:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              purpose:
+                type: string
+            required:
+              - path
+              - purpose
+        filesToModify:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              changes:
+                type: string
+            required:
+              - path
+              - changes
+        filesToDelete:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+        filesToRead:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+        approach:
+          type: string
+        testCases:
+          type: array
+          items:
+            type: object
+            properties:
+              name:
+                type: string
+              type:
+                type: string
+            required:
+              - name
+              - type
+      required:
+        - approach
+    next: medium_implement
+    aiConfig:
+      model: claude-haiku-4-5
+
+  - name: medium_implement
+    systemPrompt: |
+      Execute the plan. First read any files listed in filesToRead to gather context.
+      Then implement the changes and write tests as designed.
+      Follow all repository standards learned in the first phase.
+    next: medium_test
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  - name: medium_test
+    systemPrompt: |
+      Run the tests to verify the implementation. Check that all new and existing
+      tests pass. Report the results.
+    readOnly: true
+    next: medium_review
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  - name: medium_review
+    type: loop
+    prompt: Are all tests passing and does the implementation fully address the issue?
+    threshold: 0.85
+    loopTarget: medium_implement
+    next: check_svelte
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  # === Hard path: All Opus ===
+  - name: hard_plan
+    systemPrompt: |
+      Read the GitHub issue carefully. Understand the requirements, acceptance
+      criteria, and any context provided. Based on the issue and the repository
+      standards you learned, create a detailed implementation plan.
+      Identify risks and edge cases. Do not write code yet.
+
+      Categorize each file as: create (new), modify (existing), or delete (remove).
+      List files to read for context with a reason for each.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        filesToCreate:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              purpose:
+                type: string
+            required:
+              - path
+              - purpose
+          description: New files to create
+        filesToModify:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              changes:
+                type: string
+            required:
+              - path
+              - changes
+          description: Existing files to modify and what changes are needed
+        filesToDelete:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to remove
+        filesToRead:
+          type: array
+          items:
+            type: object
+            properties:
+              path:
+                type: string
+              reason:
+                type: string
+            required:
+              - path
+              - reason
+          description: Files to read for additional context before implementing
+        approach:
+          type: string
+        risks:
+          type: array
+          items:
+            type: string
+      required:
+        - approach
+    next: hard_plan_tests
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: hard_plan_tests
+    systemPrompt: |
+      Based on the implementation plan, design a testing strategy. Determine which
+      types of tests are needed (unit, integration, API, visual), what test cases
+      to cover, and how to verify the fix. Follow the repository's existing test patterns.
+    readOnly: true
+    input:
+      type: object
+      properties:
+        testTypes:
+          type: array
+          items:
+            type: string
+            enum:
+              - unit
+              - integration
+              - api
+              - visual
+        testCases:
+          type: array
+          items:
+            type: object
+            properties:
+              name:
+                type: string
+              type:
+                type: string
+              file:
+                type: string
+            required:
+              - name
+              - type
+      required:
+        - testTypes
+        - testCases
+    next: hard_implement
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: hard_implement
+    systemPrompt: |
+      Execute the plan. First read any files listed in filesToRead to gather context.
+      Then implement the changes and write the tests as designed.
+      Follow all repository standards learned in the first phase.
+    next: hard_test
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: hard_test
+    systemPrompt: |
+      Run the tests to verify the implementation. Check that all new and existing
+      tests pass. Report the results.
+    readOnly: true
+    next: hard_review
+    aiConfig:
+      model: claude-opus-4-5
+
+  - name: hard_review
+    type: loop
+    prompt: Are all tests passing and does the implementation fully address the issue?
+    threshold: 0.85
+    loopTarget: hard_implement
+    next: check_svelte
+    aiConfig:
+      model: claude-opus-4-5
+
+  # ============================================================
+  # SHARED: Visual check + Ship
+  # ============================================================
+
+  - name: check_svelte
+    type: decision
+    prompt: |
+      Check if any .svelte files were created or modified during this task.
+      Run: git diff --name-only HEAD $(git merge-base HEAD main)
+      Also check git status for untracked .svelte files.
+
+      Score 0-1:
+      **No .svelte changes (0.0-0.4):** No Svelte components were touched.
+      **Has .svelte changes (0.5-1.0):** One or more .svelte files were created or modified.
+    options: ["ship", "visual_test"]
+    thresholds: [0.5]
+    aiConfig:
+      model: claude-haiku-4-5
+
+  - name: visual_test
+    systemPrompt: |
+      Svelte files were changed in this task. You must run Forge visual tests to
+      verify the UI looks correct.
+
+      Read instructions/forge-testing.md for the full guide.
+
+      Steps:
+      1. Identify which pages/routes are affected by the .svelte changes
+      2. Check if visual tests already exist in test/ui/ for those pages
+      3. If tests exist, run them: npx forge test/ui/<feature>.forge.ts
+      4. If no tests exist, create them following the pattern in instructions/forge-testing.md:
+         - Use createImageRenderer with outputDir, stitchConfig, componentDir, template
+         - Capture at desktop (1920x1080), tablet (768x1024), mobile (375x812)
+         - Test relevant states (empty, loaded, error)
+         - Use mock data from test/helpers/mock_data.ts
+      5. Review the screenshots in test/output/screenshots/ to verify the design looks correct
+      6. If anything looks wrong, fix the Svelte components and re-run
+
+      Run all visual tests for affected pages and report results.
+    next: visual_review
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  - name: visual_review
+    type: loop
+    prompt: Do the visual screenshots look correct? Are all Forge visual tests passing and do the pages render properly at all resolutions?
+    threshold: 0.85
+    loopTarget: visual_test
+    next: ship
+    aiConfig:
+      model: claude-sonnet-4-5
+
+  - name: ship
+    systemPrompt: |
+      Create a pull request with a clear description of the changes, linking back
+      to the issue. Comment on the issue summarizing what was done.
+    readOnly: true
+    postActions:
+      - pr.create
+      - issue.comment
+    aiConfig:
+      model: claude-sonnet-4-5

package/.bashlite/settings.yml

@@ -0,0 +1,6 @@
+git:
+  branchPattern: bashlite/task-{issueNumber}
+  cleanup: true
+defaults:
+  engine: anthropic
+  model: claude-sonnet-4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noego/app",
-  "version": "0.0.25",
+  "version": "0.0.26",
   "description": "Production build tool for Dinner/Forge apps.",
   "type": "module",
   "bin": {

package/src/commands/dev.js

@@ -506,7 +506,7 @@ async function runSplitServeWithWatch(context, tsxExecutable, tsxArgs, baseEnv,
   logger.info(`  Shared: ${sharedPatterns.length} patterns`);
   logger.info(`  Backend: ${backendPatterns.length} patterns`);
   logger.info(`  Frontend: ${frontendPatterns.length} patterns`);
-  logger.info(`  Watch targets (${watchTargets.size}): ${JSON.stringify(Array.from(watchTargets), null, 2)}`);
+  logger.info(`  Watch targets (${watchTargets.size}): ${JSON.stringify(Array.from(watchTargets))}`);
   
   // Create matchers
   const sharedMatcher = sharedPatterns.length > 0 ? picomatch(sharedPatterns) : null;
@@ -1112,8 +1112,8 @@ async function runSplitServeWithWatch(context, tsxExecutable, tsxArgs, baseEnv,
   // Create watcher
   // Use cwd with relative patterns for proper glob support
   logger.info(`[WATCHER] Creating watcher with cwd: ${root}`);
-  logger.info(`[WATCHER] Patterns (classification only): ${JSON.stringify(allPatterns, null, 2)}`);
-  logger.info(`[WATCHER] Concrete targets: ${JSON.stringify(Array.from(watchTargets), null, 2)}`);
+  logger.info(`[WATCHER] Patterns (classification only): ${JSON.stringify(allPatterns)}`);
+  logger.info(`[WATCHER] Concrete targets: ${JSON.stringify(Array.from(watchTargets))}`);
 
   let watcher;
   try {
@@ -1270,7 +1270,7 @@ async function createWatcher(context, yamlConfig, configFilePath) {
   }
 
   logger.info('Watching for changes to restart server...');
-  logger.info(`[WATCHER] Concrete targets: ${JSON.stringify(Array.from(watchTargets), null, 2)}`);
+  logger.info(`[WATCHER] Concrete targets: ${JSON.stringify(Array.from(watchTargets))}`);
   // Use cwd with relative targets for proper glob support
   let watcher;
   try {