gsd-trae 1.0.1 → 1.0.2

package/refs/vbenchmark/tasks/saas-core/advanced/api-versioning/PROMPT.md

@@ -1,15 +0,0 @@
-# API Versioning Strategy
-
-Implement comprehensive API versioning system.
-
-## Requirements
-1. URL path, header, and query param versioning
-2. Content negotiation (Accept header)
-3. Version sunset/deprecation workflow
-4. Automatic request/response transformation
-5. Backward compatibility validation
-6. OpenAPI spec generation per version
-7. Client SDK version detection
-8. Traffic analytics per version
-9. Gradual migration tooling
-10. Breaking change detection in CI

package/refs/vbenchmark/tasks/saas-core/advanced/api-versioning/task.yaml

@@ -1,16 +0,0 @@
-name: API Versioning Strategy
-category: saas-core
-subcategory: advanced
-description: Implement API versioning with content negotiation, deprecation workflow, and backward compatibility
-difficulty: hard
-stack: go
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/versioning_test.go
-tags: [go, api, versioning, rest, openapi]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/circuit-breaker/PROMPT.md

@@ -1,13 +0,0 @@
-# Advanced Circuit Breaker
-
-Implement production-grade circuit breaker with advanced features.
-
-## Requirements
-1. Three states: Closed, Open, Half-Open
-2. Adaptive failure thresholds based on request volume
-3. Bulkhead isolation per service
-4. Multiple fallback strategies (cache, default, degraded)
-5. Metrics collection and alerting
-6. Request hedging for latency
-7. Circuit breaker per endpoint granularity
-8. Graceful degradation coordination

package/refs/vbenchmark/tasks/saas-core/advanced/circuit-breaker/task.yaml

@@ -1,16 +0,0 @@
-name: Advanced Circuit Breaker
-category: saas-core
-subcategory: advanced
-description: Implement circuit breaker with adaptive thresholds, bulkhead isolation, and fallback strategies
-difficulty: hard
-stack: go
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/circuitbreaker_test.go
-tags: [go, resilience, circuit-breaker, hystrix, bulkhead]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/compliance-gdpr/PROMPT.md

@@ -1,15 +0,0 @@
-# GDPR Compliance Engine
-
-Build a comprehensive GDPR compliance system.
-
-## Requirements
-1. Data Subject Access Request (DSAR) automation
-2. Right to erasure with cascading deletion
-3. Consent management with granular permissions
-4. Data lineage tracking across services
-5. Retention policy enforcement
-6. Data portability export (JSON/CSV)
-7. Privacy impact assessment tooling
-8. Breach notification workflow
-9. Cross-border transfer compliance
-10. Audit trail for all data operations

package/refs/vbenchmark/tasks/saas-core/advanced/compliance-gdpr/task.yaml

@@ -1,16 +0,0 @@
-name: GDPR Compliance Engine
-category: saas-core
-subcategory: advanced
-description: Build GDPR compliance system with data subject requests, consent management, and data lineage tracking
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/gdpr.test.ts
-tags: [typescript, gdpr, privacy, compliance, data-governance]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/cqrs-pattern/PROMPT.md

@@ -1,13 +0,0 @@
-# CQRS with Eventual Consistency
-
-Implement Command Query Responsibility Segregation with eventual consistency.
-
-## Requirements
-1. Separate command and query models
-2. Command validation and authorization
-3. Async projection updates via message queue
-4. Materialized views in Elasticsearch
-5. Consistency guarantees with versioning
-6. Query caching with invalidation
-7. Conflict resolution strategies
-8. Health monitoring for sync lag

package/refs/vbenchmark/tasks/saas-core/advanced/cqrs-pattern/task.yaml

@@ -1,16 +0,0 @@
-name: CQRS with Eventual Consistency
-category: saas-core
-subcategory: advanced
-description: Implement CQRS pattern with separate read/write models, eventual consistency, and materialized views
-difficulty: hard
-stack: go
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/cqrs_test.go
-tags: [go, cqrs, postgresql, elasticsearch, kafka]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/data-encryption/PROMPT.md

@@ -1,15 +0,0 @@
-# Field-Level Encryption
-
-Implement field-level encryption for sensitive data at rest.
-
-## Requirements
-1. AES-256-GCM encryption for fields
-2. Envelope encryption with DEK/KEK
-3. Automatic key rotation without downtime
-4. Searchable encryption (order-preserving or deterministic)
-5. HSM integration for key storage
-6. Per-tenant encryption keys
-7. Audit logging for key access
-8. Secure key derivation (HKDF)
-9. Emergency key recovery procedures
-10. Performance: < 1ms encryption overhead

package/refs/vbenchmark/tasks/saas-core/advanced/data-encryption/task.yaml

@@ -1,16 +0,0 @@
-name: Field-Level Encryption
-category: saas-core
-subcategory: advanced
-description: Implement field-level encryption with key rotation, searchable encryption, and HSM integration
-difficulty: hard
-stack: go
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/encryption_test.go
-tags: [go, encryption, security, hsm, key-management]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/distributed-locking/PROMPT.md

@@ -1,46 +0,0 @@
-# Distributed Locking with Redis (Redlock)
-
-Implement a production-ready distributed locking system using Redis with the Redlock algorithm.
-
-## Requirements
-
-### Core Features
-1. Implement Redlock algorithm with N Redis instances (minimum 3)
-2. Handle automatic lock extension (fencing tokens)
-3. Implement lock acquisition with configurable retry and timeout
-4. Handle clock drift compensation
-5. Implement proper lock release with ownership verification
-
-### Edge Cases
-1. Handle network partitions gracefully
-2. Implement deadlock detection and prevention
-3. Handle Redis instance failures during lock operations
-4. Implement lock queuing for fair acquisition
-5. Handle split-brain scenarios
-
-### API Design
-```typescript
-interface DistributedLock {
-  acquire(resource: string, ttl: number): Promise<LockHandle | null>;
-  extend(handle: LockHandle, ttl: number): Promise<boolean>;
-  release(handle: LockHandle): Promise<boolean>;
-  isLocked(resource: string): Promise<boolean>;
-}
-
-interface LockHandle {
-  resource: string;
-  token: string;
-  validUntil: number;
-}
-```
-
-### Performance Requirements
-- Lock acquisition: < 50ms for uncontested locks
-- Support 10,000+ concurrent lock operations
-- Handle 5 Redis instances with 2 allowed failures
-
-## Evaluation Criteria
-- Correctness of Redlock implementation
-- Proper handling of all edge cases
-- Performance under contention
-- Code quality and test coverage

package/refs/vbenchmark/tasks/saas-core/advanced/distributed-locking/task.yaml

@@ -1,24 +0,0 @@
-name: Distributed Locking with Redis
-category: saas-core
-subcategory: advanced
-description: Implement distributed locking using Redis with Redlock algorithm, handling edge cases like clock drift, network partitions, and automatic lock extension
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-
-tests:
-  functional: tests/lock.test.ts
-
-tags:
-  - typescript
-  - redis
-  - distributed-systems
-  - concurrency
-  - redlock
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/event-sourcing/PROMPT.md

@@ -1,23 +0,0 @@
-# Event Sourcing with Snapshots
-
-Build a complete event sourcing system with optimized snapshot support.
-
-## Requirements
-1. Event store with PostgreSQL (append-only)
-2. Automatic snapshot creation every N events
-3. Event versioning and upcasting
-4. Projection rebuilding from events
-5. Optimistic concurrency control
-6. Event replay with filtering
-7. Idempotent event handlers
-8. Dead letter queue for failed events
-
-## API
-```typescript
-interface EventStore {
-  append(streamId: string, events: Event[], expectedVersion: number): Promise<void>;
-  read(streamId: string, fromVersion?: number): AsyncIterable<Event>;
-  snapshot(streamId: string): Promise<Snapshot | null>;
-  rebuild(projection: string): Promise<void>;
-}
-```

package/refs/vbenchmark/tasks/saas-core/advanced/event-sourcing/task.yaml

@@ -1,16 +0,0 @@
-name: Event Sourcing with Snapshots
-category: saas-core
-subcategory: advanced
-description: Build event sourcing system with snapshot optimization, event versioning, and projection rebuilding
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/eventsource.test.ts
-tags: [typescript, event-sourcing, cqrs, postgresql, kafka]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/feature-flags-ab/PROMPT.md

@@ -1,15 +0,0 @@
-# Feature Flags with A/B Testing
-
-Build a comprehensive feature flag system with A/B testing capabilities.
-
-## Requirements
-1. Boolean, multivariate, and percentage-based flags
-2. User/segment targeting rules
-3. Gradual rollout with percentage gates
-4. A/B test experiment configuration
-5. Statistical significance calculation
-6. Real-time flag evaluation (< 5ms)
-7. Flag dependency management
-8. Audit logging and rollback
-9. SDK for client-side evaluation
-10. Webhook notifications for flag changes

package/refs/vbenchmark/tasks/saas-core/advanced/feature-flags-ab/task.yaml

@@ -1,16 +0,0 @@
-name: Feature Flags with A/B Testing
-category: saas-core
-subcategory: advanced
-description: Build feature flag system with A/B testing, gradual rollouts, user targeting, and statistical significance
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/flags.test.ts
-tags: [typescript, feature-flags, ab-testing, statistics, redis]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/saga-orchestration/PROMPT.md

@@ -1,13 +0,0 @@
-# Saga Orchestration Pattern
-
-Build a saga orchestrator for managing distributed transactions.
-
-## Requirements
-1. Orchestrator-based saga coordination
-2. Compensation actions for rollback
-3. Timeout handling with configurable policies
-4. State persistence and recovery
-5. Parallel step execution
-6. Idempotent operations
-7. Saga visualization and monitoring
-8. Dead letter handling for failed sagas

package/refs/vbenchmark/tasks/saas-core/advanced/saga-orchestration/task.yaml

@@ -1,16 +0,0 @@
-name: Saga Orchestration Pattern
-category: saas-core
-subcategory: advanced
-description: Implement saga orchestration for distributed transactions with compensation, timeout handling, and state persistence
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/saga.test.ts
-tags: [typescript, saga, distributed-transactions, postgresql, temporal]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/advanced/webhook-delivery/PROMPT.md

@@ -1,15 +0,0 @@
-# Reliable Webhook Delivery
-
-Build production-grade webhook delivery system.
-
-## Requirements
-1. At-least-once delivery guarantee
-2. HMAC signature verification (SHA-256)
-3. Exponential backoff with jitter
-4. Configurable retry policies
-5. Dead letter queue with manual replay
-6. Rate limiting per endpoint
-7. Request/response logging
-8. Idempotency key support
-9. Webhook endpoint health scoring
-10. Real-time delivery dashboard

package/refs/vbenchmark/tasks/saas-core/advanced/webhook-delivery/task.yaml

@@ -1,16 +0,0 @@
-name: Reliable Webhook Delivery
-category: saas-core
-subcategory: advanced
-description: Build webhook delivery system with guaranteed delivery, signature verification, and replay protection
-difficulty: hard
-stack: typescript
-timeout: 1200
-tokenLimit: 250000
-tests:
-  functional: tests/webhook.test.ts
-tags: [typescript, webhooks, queue, reliability, hmac]
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/audit/activity-logging/PROMPT.md

@@ -1,50 +0,0 @@
-# Task: Comprehensive Audit Trail System
-
-## Objective
-Build an audit logging system that captures all user and system actions for compliance and debugging.
-
-## Requirements
-
-1. **Event Capture**
-   - User actions (login, CRUD operations, settings changes)
-   - System events (scheduled jobs, integrations)
-   - API calls with request/response summary
-   - Capture: who, what, when, where, before/after state
-
-2. **Log Storage**
-   - Append-only log (immutable)
-   - Efficient time-range queries
-   - Retention policies (archive after 90 days)
-   - Export to S3 for compliance
-
-3. **Query API**
-   - `GET /audit/logs` - Search with filters
-   - Filter by: user, action, resource, date range
-   - Full-text search on log content
-   - Export to CSV/JSON
-
-4. **Middleware**
-   - Auto-capture all API mutations
-   - Extract user context from JWT
-   - Capture IP, user agent, request ID
-   - Async write to avoid latency
-
-## Technical Stack
-- Go 1.21+
-- Chi or Gin
-- PostgreSQL with partitioning
-- Elasticsearch for search (optional)
-
-## Files to Create
-- `internal/audit/logger.go` - Audit logger
-- `internal/audit/middleware.go` - Auto-capture middleware
-- `internal/audit/storage.go` - Log storage
-- `internal/audit/export.go` - Export functionality
-- `internal/handlers/audit.go` - Query endpoints
-
-## Success Criteria
-- [ ] All mutations automatically logged
-- [ ] Before/after state captured for updates
-- [ ] Logs are immutable (no update/delete)
-- [ ] Time-range queries perform well
-- [ ] Export to CSV works correctly

package/refs/vbenchmark/tasks/saas-core/audit/activity-logging/task.yaml

@@ -1,27 +0,0 @@
-name: Comprehensive Audit Trail System
-category: saas-core
-subcategory: audit
-description: Implement audit logging for all user and system actions in Go
-difficulty: medium
-stack: go
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/audit_test.go
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - go
-  - audit
-  - logging
-  - compliance
-  - security
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/auth/jwt-refresh-tokens/PROMPT.md

@@ -1,50 +0,0 @@
-# Task: JWT Authentication with Refresh Token Rotation
-
-## Objective
-Implement a secure JWT authentication system in Go with refresh token rotation to prevent token theft.
-
-## Requirements
-
-1. **Access Tokens**
-   - Short-lived JWT access tokens (15 minutes)
-   - Include user ID, email, and roles in claims
-   - Sign with RS256 algorithm
-
-2. **Refresh Tokens**
-   - Long-lived refresh tokens (7 days)
-   - Store hashed in database with device fingerprint
-   - Implement token rotation (new refresh token on each use)
-   - Invalidate old token after rotation
-
-3. **Endpoints**
-   - `POST /auth/login` - Issue access + refresh tokens
-   - `POST /auth/refresh` - Rotate refresh token, issue new access token
-   - `POST /auth/logout` - Invalidate refresh token
-   - `POST /auth/logout-all` - Invalidate all user sessions
-
-4. **Security**
-   - Detect refresh token reuse (potential theft)
-   - Invalidate entire token family on reuse detection
-   - Rate limit auth endpoints
-   - Store refresh tokens with bcrypt hash
-
-## Technical Stack
-- Go 1.21+
-- Gin or Echo framework
-- PostgreSQL
-- golang-jwt/jwt/v5
-
-## Files to Create
-- `cmd/server/main.go` - Entry point
-- `internal/auth/jwt.go` - JWT utilities
-- `internal/auth/refresh.go` - Refresh token logic
-- `internal/handlers/auth.go` - HTTP handlers
-- `internal/middleware/auth.go` - Auth middleware
-- `internal/models/token.go` - Token models
-
-## Success Criteria
-- [ ] Access tokens expire in 15 minutes
-- [ ] Refresh token rotation works correctly
-- [ ] Token reuse detection invalidates all tokens
-- [ ] Logout invalidates specific session
-- [ ] Logout-all invalidates all user sessions

package/refs/vbenchmark/tasks/saas-core/auth/jwt-refresh-tokens/task.yaml

@@ -1,27 +0,0 @@
-name: JWT Refresh Token Rotation
-category: saas-core
-subcategory: auth
-description: Implement JWT authentication with secure refresh token rotation in Go
-difficulty: medium
-stack: go
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/auth_test.go
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - go
-  - jwt
-  - authentication
-  - security
-  - tokens
-
-evaluation:
-  functional: 0.5
-  quality: 0.25
-  cost: 0.1
-  speed: 0.15

package/refs/vbenchmark/tasks/saas-core/auth/magic-link-email/PROMPT.md

@@ -1,53 +0,0 @@
-# Task: Magic Link Email Authentication
-
-## Objective
-Implement passwordless authentication using magic links sent via email with Python FastAPI.
-
-## Requirements
-
-1. **Magic Link Generation**
-   - Generate cryptographically secure tokens
-   - Token expires in 15 minutes
-   - One-time use (invalidate after use)
-   - Include device/browser fingerprint for security
-
-2. **Email Flow**
-   - `POST /auth/magic-link` - Request magic link
-   - Send email with link: `https://app.com/auth/verify?token=xxx`
-   - Rate limit: max 3 requests per email per hour
-   - Queue emails asynchronously
-
-3. **Verification**
-   - `GET /auth/verify` - Verify token and create session
-   - Check token expiration
-   - Check token hasn't been used
-   - Create user if first login
-   - Issue session cookie or JWT
-
-4. **Security**
-   - Store tokens hashed in database
-   - Log all authentication attempts
-   - Implement IP-based rate limiting
-   - Detect suspicious patterns (multiple IPs)
-
-## Technical Stack
-- Python 3.11+
-- FastAPI
-- PostgreSQL with asyncpg
-- Redis for rate limiting
-- Resend or SendGrid for emails
-
-## Files to Create
-- `app/main.py` - FastAPI application
-- `app/routers/auth.py` - Auth endpoints
-- `app/services/magic_link.py` - Token generation/verification
-- `app/services/email.py` - Email sending
-- `app/models/auth.py` - SQLAlchemy models
-- `app/core/security.py` - Security utilities
-
-## Success Criteria
-- [ ] Magic links are sent to valid emails
-- [ ] Tokens expire after 15 minutes
-- [ ] Tokens can only be used once
-- [ ] Rate limiting prevents abuse
-- [ ] New users are created on first login

package/refs/vbenchmark/tasks/saas-core/auth/magic-link-email/task.yaml

@@ -1,27 +0,0 @@
-name: Magic Link Email Authentication
-category: saas-core
-subcategory: auth
-description: Implement passwordless authentication using magic links with FastAPI
-difficulty: medium
-stack: python
-timeout: 600
-tokenLimit: 150000
-
-tests:
-  functional: tests/test_magic_link.py
-
-docker:
-  compose: docker-compose.yaml
-
-tags:
-  - python
-  - fastapi
-  - authentication
-  - passwordless
-  - email
-
-evaluation:
-  functional: 0.5
-  quality: 0.2
-  cost: 0.15
-  speed: 0.15