brain-dev 2.2.0 → 2.2.1

package/bin/lib/commands/discuss.cjs

@@ -5,7 +5,7 @@ const path = require('node:path');
 const { readState, writeState, atomicWriteSync } = require('../state.cjs');
 const { parseRoadmap } = require('../roadmap.cjs');
 const { loadTemplate, interpolate } = require('../templates.cjs');
-const { output, error, success, pipelineGate } = require('../core.cjs');
+const { output, error, success, prefix, pipelineGate } = require('../core.cjs');
 const { generateExpertise } = require('../stack-expert.cjs');
 
 /**
@@ -230,8 +230,11 @@ function handleSave(args, brainDir, state) {
     nextAction: '/brain:plan'
   };
 
-  success("Context captured.");
-  output(result, pipelineGate(`npx brain-dev plan --phase ${phaseNumber}`));
+  const humanLines = [
+    prefix('Context captured.'),
+    pipelineGate(`npx brain-dev plan --phase ${phaseNumber}`)
+  ].join('\n');
+  output(result, humanLines);
 
   return result;
 }

package/bin/lib/commands/verify.cjs

@@ -504,12 +504,12 @@ function handleLogRecovery(args, logRecoveryIdx, brainDir, state) {
     ? parseInt(args[phaseIdx + 1], 10)
     : state.phase.current;
 
-  logEvent(brainDir, phaseNumber, event);
-
   if (!event || typeof event !== 'object') {
     error('--log-recovery requires a JSON object, not null/primitive');
     return { error: 'invalid-json' };
   }
+
+  logEvent(brainDir, phaseNumber, event);
   output({ action: 'recovery-logged', event }, `[brain] Recovery event logged: ${event.type || 'unknown'}`);
   return { action: 'recovery-logged', event };
 }

package/bin/lib/stack-expert.cjs

@@ -30,7 +30,7 @@ const STACK_PATTERNS = {
       antiPatterns: 'N+1 queries (use eager loading with/load), fat controllers (extract to Services/Actions), raw SQL in controllers, logic in models (use Services), not using Form Requests for validation',
       testing: 'Feature tests in tests/Feature, Unit tests in tests/Unit, use RefreshDatabase trait, factories for test data',
       migration: 'php artisan make:migration create_X_table, php artisan migrate, php artisan migrate:rollback',
-      commonBugs: 'N+1 query on relationships (use ->with()), mass assignment vulnerability (use $fillable), missing foreign key constraints, not using transactions for multi-table writes, queue job serialization with deleted models',
+      commonBugs: ['N+1 query on relationships (use ->with())', 'Mass assignment vulnerability (use $fillable)', 'Missing foreign key constraints', 'Not using transactions for multi-table writes', 'Queue job serialization with deleted models'],
       verificationRules: ['Migrations exist for all new models', '.env.example has all required keys', 'Routes registered in routes/api.php or routes/web.php', 'Form Requests validate all user input', 'API Resources used for JSON responses', 'Factories exist for all models'],
       planningHints: ['Plan migration tasks BEFORE model/controller tasks', 'Each model needs: migration, model, factory, controller, request, resource, test', 'Group related migrations in same plan', 'Include seeder tasks for test data'],
       testExamples: {
@@ -44,7 +44,7 @@ const STACK_PATTERNS = {
       patterns: 'Server Components by default, use client directive for interactivity, Server Actions for mutations, Route Handlers for API, Metadata API for SEO, Suspense for loading states',
       antiPatterns: 'useEffect for data fetching (use Server Components), client-side state for server data, large client bundles, not using loading.tsx/error.tsx, fetching in client when server component suffices',
       testing: 'Jest + React Testing Library, or Vitest, test in __tests__/ or *.test.tsx',
-      commonBugs: 'Hydration mismatch (server vs client render difference), importing server-only code in client components, not handling loading/error states, stale cache in fetch(), middleware running on every request',
+      commonBugs: ['Hydration mismatch (server vs client render difference)', 'Importing server-only code in client components', 'Not handling loading/error states', 'Stale cache in fetch()', 'Middleware running on every request'],
       verificationRules: ['Page components exist in app/ directory', 'loading.tsx exists for async pages', 'error.tsx exists for error boundaries', 'API Route Handlers use correct HTTP method exports', 'Client components have "use client" directive', 'Metadata exported for SEO pages'],
       planningHints: ['Plan layout components before page components', 'Server Components first, add "use client" only when needed', 'Plan API Route Handlers separate from page components', 'Include loading.tsx and error.tsx for each route group'],
       testExamples: {
@@ -58,7 +58,7 @@ const STACK_PATTERNS = {
       patterns: 'Functional components + hooks, React Navigation/Expo Router, AsyncStorage, StyleSheet.create, Platform.select for platform-specific code',
       antiPatterns: 'Inline styles (use StyleSheet.create), heavy computation on JS thread, large FlatList without getItemLayout/keyExtractor, not using Platform.OS for platform checks, synchronous storage calls',
       testing: 'Jest + React Native Testing Library, detox for E2E',
-      commonBugs: 'Platform-specific rendering not tested on both OS, keyboard covering inputs (use KeyboardAvoidingView), memory leaks from unsubscribed listeners, navigation state persistence issues, StatusBar behavior differences iOS vs Android',
+      commonBugs: ['Platform-specific rendering not tested on both OS', 'Keyboard covering inputs (use KeyboardAvoidingView)', 'Memory leaks from unsubscribed listeners', 'Navigation state persistence issues', 'StatusBar behavior differences iOS vs Android'],
       verificationRules: ['Platform-specific code uses Platform.OS or Platform.select', 'FlatList has keyExtractor and getItemLayout', 'Navigation screens registered in navigator', 'Assets imported correctly (require() for local)', 'No web-only APIs used (document, window)'],
       planningHints: ['Plan shared components before screen-specific ones', 'Consider both iOS and Android in task descriptions', 'Plan navigation structure before individual screens', 'Include platform-specific testing tasks'],
       testExamples: {
@@ -72,7 +72,7 @@ const STACK_PATTERNS = {
       patterns: 'Router middleware chain, error handling middleware, async/await with express-async-errors, request validation with Joi/Zod, controller-service separation',
       antiPatterns: 'Callback hell, no error middleware, sync operations blocking event loop, not validating request body, try/catch in every route (use express-async-errors)',
       testing: 'Jest/Mocha + supertest for HTTP assertions',
-      commonBugs: 'Unhandled promise rejections crashing server, missing error middleware (must have 4 params), route order matters (specific before generic), CORS misconfiguration, not closing DB connections on shutdown',
+      commonBugs: ['Unhandled promise rejections crashing server', 'Missing error middleware (must have 4 params: err, req, res, next)', 'Route order matters (specific before generic)', 'CORS misconfiguration', 'Not closing DB connections on shutdown'],
       verificationRules: ['Error handling middleware exists (4 params: err, req, res, next)', 'Routes validate input before processing', 'Async handlers properly catch errors', 'CORS configured for production origins', 'Graceful shutdown handler exists'],
       planningHints: ['Plan middleware before routes', 'Error handling middleware is a separate task at the end', 'Group related routes in same router file', 'Plan validation schemas alongside route handlers'],
       testExamples: {
@@ -87,7 +87,7 @@ const STACK_PATTERNS = {
       antiPatterns: 'N+1 queries (use select_related/prefetch_related), logic in views (use services), not using serializers for validation, raw SQL without parameterization',
       testing: 'pytest-django or TestCase, factory_boy for fixtures',
       migration: 'python manage.py makemigrations, python manage.py migrate, python manage.py migrate <app> zero (rollback)',
-      commonBugs: 'Circular imports between apps, migration conflicts in teams, not using select_related causing N+1, signals firing during tests unexpectedly, timezone-naive datetime comparisons',
+      commonBugs: ['Circular imports between apps', 'Migration conflicts in teams', 'Not using select_related causing N+1', 'Signals firing during tests unexpectedly', 'Timezone-naive datetime comparisons'],
       verificationRules: ['Migrations created for all model changes', 'URLs registered in app urls.py and included in root urls.py', 'Admin registered for all models', 'Serializers validate all user input', 'Permissions set on views'],
       planningHints: ['Plan models and migrations before views', 'Each app should be self-contained', 'Plan serializers alongside models', 'Include admin registration tasks', 'Plan management commands for data operations'],
       testExamples: {
@@ -137,7 +137,7 @@ const STACK_PATTERNS = {
       antiPatterns: 'Sync database calls in async endpoints, no Pydantic validation, global mutable state, not using Depends() for shared logic, blocking the event loop',
       testing: 'pytest + httpx AsyncClient',
       migration: 'alembic init, alembic revision --autogenerate -m "description", alembic upgrade head',
-      commonBugs: 'Mixing sync/async database drivers, Pydantic v2 model_validator vs v1 validator, circular imports in routers, not closing DB connections in lifespan, CORS middleware order matters',
+      commonBugs: ['Mixing sync/async database drivers', 'Pydantic v2 model_validator vs v1 validator', 'Circular imports in routers', 'Not closing DB connections in lifespan', 'CORS middleware order matters'],
       verificationRules: ['Pydantic schemas exist for all request/response models', 'Dependencies use Depends() injection', 'Async endpoints use async database driver', 'Alembic migrations exist for schema changes', 'Error handlers return consistent JSON format'],
       planningHints: ['Plan Pydantic schemas before routers', 'Plan database models with Alembic migrations', 'Group related endpoints in same router', 'Plan dependency injection for shared resources (DB, auth)'],
       testExamples: {
@@ -318,7 +318,8 @@ function generateExpertise(brainDir, role = 'general') {
     if (fwInfo.commonBugs) {
       sections.push('');
       sections.push(`### Common ${framework} Bugs to Avoid`);
-      for (const [i, bug] of fwInfo.commonBugs.split(', ').entries()) {
+      const bugs = Array.isArray(fwInfo.commonBugs) ? fwInfo.commonBugs : fwInfo.commonBugs.split(', ');
+      for (const [i, bug] of bugs.entries()) {
         sections.push(`${i + 1}. ${bug}`);
       }
     }

package/bin/templates/overlays/nextjs/planner-overlay.md

@@ -0,0 +1,30 @@
+## Next.js-Specific Planning
+
+### Task Ordering
+1. **Layouts first**: Create layout.tsx before page components
+2. **Server Components first**: Default to Server Components, add "use client" only when needed
+3. **API Routes separate**: Plan Route Handlers as distinct tasks from pages
+4. **Error boundaries**: Include loading.tsx and error.tsx for each route group
+
+### Standard Feature Pattern
+For each new route/feature, plan these tasks:
+1. Layout component (if new route group)
+2. Page component (Server Component by default)
+3. Loading state (loading.tsx)
+4. Error boundary (error.tsx)
+5. API Route Handler (if needed)
+6. Client components (only for interactivity)
+7. Tests
+
+### must_haves Template for Next.js
+```yaml
+truths:
+  - "Page renders correctly as Server Component"
+  - "loading.tsx shows skeleton/spinner during data fetch"
+  - "error.tsx catches and displays errors gracefully"
+  - "No useEffect used for data fetching (Server Component handles it)"
+artifacts:
+  - path: "app/{route}/page.tsx"
+  - path: "app/{route}/loading.tsx"
+  - path: "app/{route}/error.tsx"
+```

package/bin/templates/overlays/react-native/planner-overlay.md

@@ -0,0 +1,27 @@
+## React Native-Specific Planning
+
+### Task Ordering
+1. **Navigation first**: Define navigation structure before screens
+2. **Shared components**: Plan reusable components before screen-specific ones
+3. **Platform handling**: Consider both iOS and Android in each task
+4. **Performance**: Plan FlatList optimization tasks alongside data display tasks
+
+### Standard Feature Pattern
+For each new screen/feature, plan these tasks:
+1. Navigation registration (add to navigator)
+2. Screen component with StyleSheet
+3. Shared sub-components (if needed)
+4. Platform-specific adjustments (Platform.OS checks)
+5. Tests (component + interaction)
+
+### must_haves Template for React Native
+```yaml
+truths:
+  - "Screen renders correctly on both iOS and Android"
+  - "Navigation to/from screen works with correct params"
+  - "StyleSheet.create used (no inline styles)"
+  - "FlatList has keyExtractor for list screens"
+artifacts:
+  - path: "app/{screen}.tsx or src/screens/{Screen}.tsx"
+  - path: "components/{Component}.tsx"
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "brain-dev",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "AI-powered development workflow orchestrator",
   "author": "halilcosdu",
   "license": "MIT",