gsd-trae 1.0.1 → 1.0.2

package/refs/vbenchmark/tasks/code-evolution/legacy-migration/rest-to-grpc/PROMPT.md

@@ -1,47 +0,0 @@
-# Task: REST to gRPC Migration
-
-## Objective
-Migrate a REST API to gRPC while maintaining REST compatibility.
-
-## Given Code
-- REST handlers in Go
-- JSON request/response
-- HTTP status codes
-
-## Requirements
-
-1. **Proto Definitions**
-   - Define service proto files
-   - Message types from JSON schemas
-   - RPC methods from REST endpoints
-   - Proper field types
-
-2. **gRPC Server**
-   - Implement gRPC service
-   - Server streaming where appropriate
-   - Error handling with status codes
-   - Interceptors for logging/auth
-
-3. **gRPC-Gateway**
-   - REST compatibility layer
-   - HTTP/JSON transcoding
-   - Same REST paths work
-   - OpenAPI generation
-
-4. **Client**
-   - Go gRPC client
-   - Connection pooling
-   - Retry logic
-   - Deadline propagation
-
-## Files to Create
-- `proto/*.proto` - Proto definitions
-- `internal/grpc/server.go` - gRPC server
-- `internal/grpc/gateway.go` - REST gateway
-
-## Success Criteria
-- [ ] Proto files compile
-- [ ] gRPC service works
-- [ ] REST still works via gateway
-- [ ] Same behavior as before
-- [ ] Performance improved

package/refs/vbenchmark/tasks/code-evolution/legacy-migration/rest-to-grpc/task.yaml

@@ -1,24 +0,0 @@
-name: REST to gRPC Migration
-category: code-evolution
-subcategory: legacy-migration
-description: Migrate REST API to gRPC in Go
-difficulty: hard
-stack: go
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/grpc_test.go
-
-tags:
-  - go
-  - grpc
-  - rest
-  - protobuf
-  - migration
-
-evaluation:
-  functional: 0.5
-  quality: 0.3
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/performance/async-refactor/PROMPT.md

@@ -1,47 +0,0 @@
-# Task: Sync to Async Refactor
-
-## Objective
-Convert synchronous I/O-bound code to async for better performance.
-
-## Given Code
-- Sync HTTP requests
-- Sync file operations
-- Sync database queries
-- Sequential processing
-
-## Requirements
-
-1. **Async Conversion**
-   - Async HTTP with aiohttp/httpx
-   - Async file I/O with aiofiles
-   - Async database with asyncpg
-   - Async Redis with aioredis
-
-2. **Concurrency**
-   - Parallel requests with gather
-   - Semaphores for rate limiting
-   - Task groups
-   - Proper cancellation
-
-3. **Error Handling**
-   - Async exception handling
-   - Timeout handling
-   - Retry logic
-   - Graceful degradation
-
-4. **Testing**
-   - Async test fixtures
-   - pytest-asyncio
-   - Mock async functions
-
-## Files to Modify
-- `app/services/*.py` - Convert to async
-- `app/clients/*.py` - Async clients
-- `tests/*.py` - Async tests
-
-## Success Criteria
-- [ ] All I/O is async
-- [ ] Parallel operations work
-- [ ] Error handling preserved
-- [ ] Tests pass
-- [ ] Performance improved

package/refs/vbenchmark/tasks/code-evolution/performance/async-refactor/task.yaml

@@ -1,24 +0,0 @@
-name: Sync to Async Refactor
-category: code-evolution
-subcategory: performance
-description: Convert sync I/O to async for performance
-difficulty: medium
-stack: python
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/test_async.py
-
-tags:
-  - python
-  - async
-  - performance
-  - io
-  - refactoring
-
-evaluation:
-  functional: 0.5
-  quality: 0.3
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/performance/memory-leak-fix/PROMPT.md

@@ -1,47 +0,0 @@
-# Task: Fix Memory Leaks
-
-## Objective
-Identify and fix memory leaks in a Node.js application.
-
-## Symptoms
-- Memory grows over time
-- OOM crashes
-- Slow garbage collection
-- Degraded performance
-
-## Requirements
-
-1. **Leak Detection**
-   - Profile memory usage
-   - Heap snapshots
-   - Identify retained objects
-   - Find leak sources
-
-2. **Common Fixes**
-   - Clear event listeners
-   - Close database connections
-   - Clear intervals/timeouts
-   - Remove circular references
-
-3. **Specific Issues**
-   - Fix closure memory retention
-   - Proper resource cleanup
-   - Buffer management
-   - Cache size limits
-
-4. **Prevention**
-   - Add memory tests
-   - Monitor memory metrics
-   - Implement cleanup patterns
-
-## Files to Modify
-- `src/services/*.ts` - Fix leak sources
-- `src/lib/*.ts` - Resource management
-- `tests/memory.test.ts` - Memory tests
-
-## Success Criteria
-- [ ] Memory stable over time
-- [ ] No OOM crashes
-- [ ] Resources properly cleaned
-- [ ] Memory tests pass
-- [ ] Monitoring added

package/refs/vbenchmark/tasks/code-evolution/performance/memory-leak-fix/task.yaml

@@ -1,24 +0,0 @@
-name: Fix Memory Leaks
-category: code-evolution
-subcategory: performance
-description: Fix memory leaks in Node.js application
-difficulty: hard
-stack: nodejs
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/memory.test.ts
-
-tags:
-  - typescript
-  - nodejs
-  - memory
-  - performance
-  - debugging
-
-evaluation:
-  functional: 0.5
-  quality: 0.3
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/performance/query-optimization/PROMPT.md

@@ -1,49 +0,0 @@
-# Task: Database Query Optimization
-
-## Objective
-Identify and fix slow database queries in a Python application.
-
-## Given Issues
-- N+1 query problems
-- Missing indexes
-- Full table scans
-- Large result sets
-- No query caching
-
-## Requirements
-
-1. **Query Analysis**
-   - Profile slow queries
-   - Identify N+1 patterns
-   - Check execution plans
-   - Find missing indexes
-
-2. **Optimization Techniques**
-   - Add proper indexes
-   - Eager loading (joinedload)
-   - Pagination
-   - Select only needed columns
-   - Query caching
-
-3. **Specific Fixes**
-   - Fix N+1 in list views
-   - Optimize search queries
-   - Batch bulk operations
-   - Add compound indexes
-
-4. **Validation**
-   - Measure before/after
-   - Query count tests
-   - Performance benchmarks
-
-## Files to Modify
-- `app/repositories/*.py` - Query logic
-- `migrations/` - Index migrations
-- `tests/performance/` - Benchmarks
-
-## Success Criteria
-- [ ] N+1 queries eliminated
-- [ ] Response times < 100ms
-- [ ] Indexes added where needed
-- [ ] Query counts reduced
-- [ ] Benchmarks documented

package/refs/vbenchmark/tasks/code-evolution/performance/query-optimization/task.yaml

@@ -1,24 +0,0 @@
-name: Database Query Optimization
-category: code-evolution
-subcategory: performance
-description: Optimize slow database queries in Python
-difficulty: hard
-stack: python
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/test_performance.py
-
-tags:
-  - python
-  - database
-  - optimization
-  - performance
-  - sql
-
-evaluation:
-  functional: 0.4
-  quality: 0.35
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/code-evolution/refactoring/class-to-hooks/PROMPT.md

@@ -1,96 +0,0 @@
-# React Class to Hooks Migration
-
-Migrate the following React class components to functional components using hooks.
-
-## Components to Migrate
-
-### 1. UserProfile (Class Component)
-```tsx
-class UserProfile extends React.Component<Props, State> {
-  state = { user: null, loading: true, error: null };
-
-  componentDidMount() {
-    this.fetchUser();
-  }
-
-  componentDidUpdate(prevProps) {
-    if (prevProps.userId !== this.props.userId) {
-      this.fetchUser();
-    }
-  }
-
-  componentWillUnmount() {
-    this.abortController?.abort();
-  }
-
-  async fetchUser() {
-    // fetch logic
-  }
-
-  render() {
-    // render logic
-  }
-}
-```
-
-### 2. FormWithValidation (Class Component)
-- Uses setState for form fields
-- Has form validation logic
-- Handles async submission
-- Shows loading/error states
-
-### 3. InfiniteScrollList (Class Component)
-- Uses IntersectionObserver
-- Manages pagination state
-- Cleanup on unmount
-- Scroll position restoration
-
-### 4. ThemeProvider (Class Component)
-- Uses React Context
-- Persists to localStorage
-- System preference detection
-
-## Requirements
-
-1. Convert all lifecycle methods to hooks:
-   - `componentDidMount` → `useEffect`
-   - `componentDidUpdate` → `useEffect` with deps
-   - `componentWillUnmount` → `useEffect` cleanup
-
-2. Extract reusable custom hooks:
-   - `useFetch` - data fetching with abort
-   - `useForm` - form state and validation
-   - `useIntersectionObserver` - scroll detection
-   - `useLocalStorage` - persistent state
-
-3. Maintain all existing functionality
-4. Add TypeScript types for hooks
-5. No behavioral changes (tests should pass)
-
-## Custom Hook Signatures
-
-```typescript
-function useFetch<T>(url: string): {
-  data: T | null;
-  loading: boolean;
-  error: Error | null;
-  refetch: () => void;
-}
-
-function useForm<T>(initial: T, validate: (v: T) => Errors): {
-  values: T;
-  errors: Errors;
-  handleChange: (field: keyof T, value: any) => void;
-  handleSubmit: (onSubmit: (v: T) => Promise<void>) => void;
-  isSubmitting: boolean;
-}
-```
-
-## Acceptance Criteria
-
-- [ ] All 4 components converted
-- [ ] Custom hooks extracted and typed
-- [ ] No functionality regression
-- [ ] Proper cleanup in effects
-- [ ] Dependencies arrays correct
-- [ ] Code is more readable than original

package/refs/vbenchmark/tasks/code-evolution/refactoring/class-to-hooks/task.yaml

@@ -1,27 +0,0 @@
-name: React Class to Hooks Migration
-category: code-evolution
-subcategory: refactoring
-description: Migrate React class components to functional components with hooks
-difficulty: medium
-stack: nextjs-supabase
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/hooks.test.ts
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - react
-  - hooks
-  - refactoring
-  - migration
-  - typescript
-
-evaluation:
-  functional: 0.4
-  quality: 0.3
-  cost: 0.15
-  speed: 0.15

package/refs/vbenchmark/tasks/code-evolution/refactoring/dependency-injection/PROMPT.md

@@ -1,47 +0,0 @@
-# Task: Add Dependency Injection
-
-## Objective
-Refactor legacy Java code to use Spring dependency injection.
-
-## Given Code
-- Static getInstance() singletons
-- new keyword everywhere
-- Hardcoded dependencies
-- Untestable classes
-
-## Requirements
-
-1. **Bean Configuration**
-   - Convert singletons to beans
-   - Use constructor injection
-   - Define configuration classes
-   - Component scanning
-
-2. **Dependency Inversion**
-   - Extract interfaces
-   - Inject abstractions
-   - Remove static methods
-   - Eliminate new in business logic
-
-3. **Testing**
-   - Enable mock injection
-   - Unit test isolation
-   - Integration test config
-   - Test slices
-
-4. **Lifecycle**
-   - Proper bean scopes
-   - Initialization callbacks
-   - Destruction callbacks
-   - Lazy initialization
-
-## Files to Modify
-- `src/main/java/services/*.java` - Service classes
-- `src/main/java/config/*.java` - Configuration
-
-## Success Criteria
-- [ ] No static singletons
-- [ ] Constructor injection used
-- [ ] Interfaces extracted
-- [ ] Tests isolated
-- [ ] Application starts

package/refs/vbenchmark/tasks/code-evolution/refactoring/dependency-injection/task.yaml

@@ -1,24 +0,0 @@
-name: Add Dependency Injection
-category: code-evolution
-subcategory: refactoring
-description: Add DI to legacy Java codebase
-difficulty: medium
-stack: java
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/DITest.java
-
-tags:
-  - java
-  - spring
-  - di
-  - refactoring
-  - testing
-
-evaluation:
-  functional: 0.4
-  quality: 0.4
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/refactoring/error-handling/PROMPT.md

@@ -1,48 +0,0 @@
-# Task: Standardize Error Handling
-
-## Objective
-Standardize error handling across a Go codebase using best practices.
-
-## Given Code
-- Inconsistent error handling
-- Silent error swallowing
-- No error wrapping
-- Generic error messages
-
-## Requirements
-
-1. **Error Types**
-   - Define domain errors
-   - Sentinel errors
-   - Custom error types
-   - Error codes for API
-
-2. **Error Wrapping**
-   - Use fmt.Errorf with %w
-   - Preserve error chain
-   - Add context at each level
-   - Unwrap for inspection
-
-3. **Error Handling**
-   - Check all errors
-   - Handle or propagate
-   - Log at appropriate level
-   - No panic in library code
-
-4. **API Errors**
-   - Map to HTTP status
-   - Consistent response format
-   - Don't leak internals
-   - Include error codes
-
-## Files to Modify
-- `internal/errors/errors.go` - Error definitions
-- `internal/*/` - Apply patterns
-- `internal/handlers/` - API error mapping
-
-## Success Criteria
-- [ ] Custom error types defined
-- [ ] All errors wrapped with context
-- [ ] No ignored errors
-- [ ] API errors consistent
-- [ ] Error chain inspectable

package/refs/vbenchmark/tasks/code-evolution/refactoring/error-handling/task.yaml

@@ -1,24 +0,0 @@
-name: Standardize Error Handling
-category: code-evolution
-subcategory: refactoring
-description: Standardize error handling patterns in Go
-difficulty: medium
-stack: go
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/errors_test.go
-
-tags:
-  - go
-  - errors
-  - refactoring
-  - patterns
-  - handling
-
-evaluation:
-  functional: 0.5
-  quality: 0.3
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/refactoring/monolith-to-modules/PROMPT.md

@@ -1,50 +0,0 @@
-# Task: Monolith to Modules
-
-## Objective
-Extract self-contained modules from a monolithic TypeScript application.
-
-## Given Code
-- Everything in one package
-- Circular dependencies
-- Shared global state
-- No clear boundaries
-
-## Requirements
-
-1. **Module Boundaries**
-   - Identify domain boundaries
-   - Extract modules with clear interfaces
-   - Define public APIs per module
-   - Hide internal implementation
-
-2. **Dependency Management**
-   - Eliminate circular dependencies
-   - Use dependency injection
-   - Define module contracts
-   - Explicit dependencies
-
-3. **Module Structure**
-   ```
-   modules/
-     users/
-       index.ts (public API)
-       internal/
-     orders/
-       index.ts
-       internal/
-   ```
-
-4. **Testing**
-   - Module-level tests
-   - Integration tests
-   - Mock modules for testing
-
-## Files to Organize
-- `src/*.ts` → `modules/*/`
-
-## Success Criteria
-- [ ] No circular dependencies
-- [ ] Clear module boundaries
-- [ ] Public APIs defined
-- [ ] All tests pass
-- [ ] Build still works

package/refs/vbenchmark/tasks/code-evolution/refactoring/monolith-to-modules/task.yaml

@@ -1,24 +0,0 @@
-name: Monolith to Modules
-category: code-evolution
-subcategory: refactoring
-description: Extract modules from monolith in TypeScript
-difficulty: hard
-stack: nodejs
-timeout: 900
-tokenLimit: 200000
-
-tests:
-  functional: tests/modules.test.ts
-
-tags:
-  - typescript
-  - modular
-  - refactoring
-  - architecture
-  - monolith
-
-evaluation:
-  functional: 0.4
-  quality: 0.4
-  cost: 0.1
-  speed: 0.1

package/refs/vbenchmark/tasks/code-evolution/refactoring/orm-migration/PROMPT.md

@@ -1,47 +0,0 @@
-# Task: SQLAlchemy to SQLModel
-
-## Objective
-Migrate from SQLAlchemy models to SQLModel with async support.
-
-## Given Code
-- SQLAlchemy ORM models
-- Sync database operations
-- Session management
-- Query patterns
-
-## Requirements
-
-1. **Model Conversion**
-   - SQLModel class definitions
-   - Field types with Pydantic
-   - Relationships
-   - Table configuration
-
-2. **Async Operations**
-   - AsyncSession usage
-   - Async queries
-   - Async relationship loading
-   - Transaction handling
-
-3. **Query Patterns**
-   - Select statements
-   - Joins and eager loading
-   - Aggregations
-   - Raw SQL where needed
-
-4. **Session Management**
-   - Async context managers
-   - Dependency injection
-   - Connection pooling
-
-## Files to Modify
-- `app/models/*.py` - Model files
-- `app/repositories/*.py` - Query logic
-- `app/database.py` - Session setup
-
-## Success Criteria
-- [ ] Models converted
-- [ ] Async throughout
-- [ ] Queries work
-- [ ] Tests pass
-- [ ] Performance maintained