@eddacraft/anvil-adapters 0.1.0

package/src/__tests__/fixtures/bmad/valid-story.md

@@ -0,0 +1,107 @@
+---
+name: 'User Story'
+version: '1.0.0'
+description: 'Email/Password Registration Story'
+output_file: 'US-001.md'
+variables:
+  story_id: 'US-001'
+  epic_id: 'EPIC-001'
+  author: 'Product Manager'
+  date: '2025-10-23'
+---
+
+# US-001: User Registration with Email and Password
+
+**Author:** Product Manager **Date:** 2025-10-23 **Version:** 1.0 **Epic:**
+EPIC-001
+
+## Change Log
+
+| Date       | Version | Description   | Author          |
+| :--------- | :------ | :------------ | :-------------- |
+| 2025-10-23 | 1.0     | Story created | Product Manager |
+
+## User Story
+
+As a new user, I want to create an account using my email address and password
+so that I can access the platform and save my preferences.
+
+## Description
+
+This story covers the complete email/password registration flow, including form
+display, validation, account creation, and email verification. The registration
+form should be simple and intuitive whilst collecting necessary information for
+account setup.
+
+## Acceptance Criteria
+
+1. Registration form displays with email and password fields
+2. Email field validates format (RFC 5322 compliant)
+3. Password field enforces minimum requirements:
+   - At least 8 characters
+   - Contains uppercase and lowercase letters
+   - Contains at least one number
+   - Contains at least one special character
+4. Password confirmation field matches password
+5. Terms and conditions checkbox is required
+6. Form submission creates user record in database
+7. Verification email is sent to provided email address
+8. Success message displays after registration
+9. Error messages are clear and actionable
+10. Form is accessible via keyboard navigation
+
+## Technical Implementation
+
+FR-11: Registration form shall be implemented as React component
+
+FR-12: Form validation shall use Zod schema validation
+
+FR-13: Password hashing shall use bcrypt with 12 rounds
+
+FR-14: Verification email shall use transactional email service
+
+## Test Cases
+
+### TC-001: Successful Registration
+
+- **Given:** User is on registration page
+- **When:** User enters valid email, password, confirms password, accepts terms
+- **Then:** Account is created, verification email sent, success message shown
+
+### TC-002: Invalid Email Format
+
+- **Given:** User is on registration page
+- **When:** User enters invalid email format (e.g., "notanemail")
+- **Then:** Error message "Please enter a valid email address" is displayed
+
+### TC-003: Password Too Weak
+
+- **Given:** User is on registration page
+- **When:** User enters password "pass"
+- **Then:** Error message lists missing password requirements
+
+### TC-004: Passwords Don't Match
+
+- **Given:** User is on registration page
+- **When:** User enters different values in password and confirm password
+- **Then:** Error message "Passwords do not match" is displayed
+
+### TC-005: Terms Not Accepted
+
+- **Given:** User is on registration page
+- **When:** User submits form without accepting terms
+- **Then:** Error message "You must accept the terms and conditions" is
+  displayed
+
+## Definition of Done
+
+- [ ] Frontend registration component implemented
+- [ ] Backend API endpoint implemented
+- [ ] Form validation working on client and server
+- [ ] Unit tests written and passing (>90% coverage)
+- [ ] Integration tests written and passing
+- [ ] Email verification flow tested
+- [ ] Accessibility requirements met (WCAG 2.1 AA)
+- [ ] Code reviewed and approved
+- [ ] QA testing completed
+- [ ] Documentation updated

package/src/__tests__/fixtures/bmad/valid-task.md

@@ -0,0 +1,79 @@
+---
+name: 'Task Document'
+version: '1.0.0'
+description: 'Implement JWT Token Generation'
+output_file: 'TASK-001.md'
+variables:
+  task_id: 'TASK-001'
+  story_id: 'US-001'
+  author: 'Developer'
+  date: '2025-10-24'
+---
+
+# TASK-001: Implement JWT Token Generation
+
+**Author:** Developer **Date:** 2025-10-24 **Version:** 1.0 **Story:** US-001
+
+## Change Log
+
+| Date       | Version | Description  | Author    |
+| :--------- | :------ | :----------- | :-------- |
+| 2025-10-24 | 1.0     | Task created | Developer |
+
+## Task Description
+
+Implement JWT token generation functionality for user authentication. The system
+needs to generate secure, signed JWT tokens upon successful login that can be
+validated on subsequent requests.
+
+## Technical Requirements
+
+FR-15: JWT tokens shall be signed using RS256 algorithm FR-16: Tokens shall
+include user ID, email, and role claims FR-17: Token generation shall use
+environment variable for secret key FR-18: Tokens shall have configurable
+expiration time (default 24 hours)
+
+NFR-11: Token generation shall complete within 50ms NFR-12: Tokens shall be
+stateless and self-contained
+
+## Implementation Details
+
+**Files to Modify:**
+
+- `src/auth/token.service.ts` - Create new service
+- `src/auth/token.service.test.ts` - Add test suite
+- `src/config/jwt.config.ts` - Add JWT configuration
+- `.env.example` - Add JWT secret placeholder
+
+**Dependencies:**
+
+- jsonwebtoken: ^9.0.0
+- @types/jsonwebtoken: ^9.0.0
+
+## Test Coverage
+
+Must achieve >95% code coverage with tests for:
+
+1. Token generation with valid user data
+2. Token signing with correct algorithm
+3. Token expiration handling
+4. Invalid secret key handling
+5. Missing claims error handling
+
+## Acceptance Criteria
+
+1. JWT service generates valid tokens
+2. Tokens can be verified and decoded
+3. Tokens include all required claims
+4. Tokens expire at configured time
+5. All tests passing with >95% coverage
+6. Code reviewed and approved
+
+## Definition of Done
+
+- [ ] Token service implemented
+- [ ] Unit tests written and passing
+- [ ] Integration tests with auth flow completed
+- [ ] Code coverage >95%
+- [ ] Security review completed
+- [ ] Documentation updated

package/src/__tests__/fixtures/bmad/valid-v6-prd.md

@@ -0,0 +1,35 @@
+---
+name: 'Product Requirements Document'
+version: '6.0.0'
+description: 'BMAD v6 PRD with hyphenated variables'
+output_file: '{project-root}/docs/PRD.md'
+author: 'v6 Author'
+date: '2026-01-15'
+---
+
+# Product Requirements Document
+
+## Change Log
+
+| Date       | Version | Description         | Author    |
+| :--------- | :------ | :------------------ | :-------- |
+| 2026-01-15 | 6.0.0   | v6 format migration | v6 Author |
+
+## Executive Summary
+
+This PRD describes the migration to BMAD v6 format with updated folder structure
+and variable syntax. The project uses `_bmad/_config` for configuration and
+`{project-root}` for path references.
+
+## Functional Requirements
+
+<!-- prettier-ignore -->
+FR-01: Support `_bmad` folder structure for project configuration
+FR-02: Support `_config` folder for module configuration
+FR-03: Expand `{project-root}` hyphenated variable syntax
+
+## Non-Functional Requirements
+
+<!-- prettier-ignore -->
+NFR-01: Maintain backward compatibility with `.bmad` and `_cfg` folders
+NFR-02: Support both `{project_root}` and `{project-root}` variable formats

package/src/__tests__/fixtures/generic/plan-detailed.md

@@ -0,0 +1,39 @@
+# Implementation Plan: API Redesign
+
+## Overview
+
+This plan outlines the redesign of our REST API to improve performance,
+scalability, and developer experience. The migration will happen in phases to
+minimize disruption.
+
+## Goals
+
+- Reduce API response time by 50%
+- Improve API documentation quality
+- Implement versioning strategy
+- Add comprehensive error handling
+
+## Requirements
+
+1. All endpoints must support JSON response format
+2. Authentication must use OAuth 2.0
+3. Rate limiting must be applied per user
+4. Error responses must follow RFC 7807 format
+5. All endpoints must have OpenAPI 3.0 documentation
+
+## Features
+
+- GraphQL endpoint for complex queries
+- Webhook support for real-time updates
+- Batch operation endpoints
+- Pagination with cursor-based navigation
+- Field filtering and sparse fieldsets
+
+## Tasks
+
+1. Audit existing API endpoints
+2. Design new API schema
+3. Implement versioning infrastructure
+4. Migrate endpoints to v2
+5. Update client libraries
+6. Deploy to production

package/src/__tests__/fixtures/generic/prd-simple.md

@@ -0,0 +1,27 @@
+# Product Requirements Document
+
+## Purpose
+
+Build a user dashboard that displays key metrics and allows data export.
+
+## Requirements
+
+- Display user activity metrics
+- Show real-time statistics
+- Allow CSV export of data
+- Support date range filtering
+- Include visualization charts
+
+## Goals
+
+- Improve user engagement by 20%
+- Reduce support tickets related to data access
+- Enable self-service analytics
+
+## Tasks
+
+- [ ] Design dashboard layout
+- [ ] Implement metrics API
+- [ ] Add export functionality
+- [ ] Create visualization components
+- [ ] Write tests for all features

package/src/__tests__/fixtures/generic/rfc-example.md

@@ -0,0 +1,26 @@
+# RFC: Caching Strategy
+
+## Overview
+
+This RFC proposes a comprehensive caching strategy to improve application
+performance and reduce database load.
+
+## Goals
+
+- Reduce database queries by 70%
+- Improve page load times
+- Minimize cache invalidation complexity
+
+## Requirements
+
+- Must support distributed caching
+- Cache TTL must be configurable per resource type
+- Must handle cache invalidation on data updates
+- Should support cache warming for critical paths
+
+## Features
+
+- Redis-based distributed cache
+- Multi-level caching (memory + Redis)
+- Automatic cache invalidation
+- Cache analytics and monitoring

package/src/__tests__/fixtures/generic/todo-list.md

@@ -0,0 +1,23 @@
+# Project TODO
+
+## Overview
+
+This document tracks tasks for the Q1 2025 project deliverables.
+
+## Tasks
+
+- Set up CI/CD pipeline
+- Configure monitoring and alerting
+- Implement authentication system
+- Add rate limiting
+- Write API documentation
+- Conduct security audit
+- Deploy to staging environment
+- Perform load testing
+
+## Features
+
+- OAuth 2.0 integration
+- JWT token management
+- Role-based access control
+- API key authentication

package/src/__tests__/fixtures/speckit/sample-plan.md

@@ -0,0 +1,63 @@
+# Implementation Plan
+
+Generated from APS: aps-1234abcd
+
+## Summary
+
+Implement a user authentication system with JWT tokens to secure API endpoints
+and manage user sessions effectively.
+
+## Implementation Steps
+
+1. **Set up project dependencies**
+   - Install required npm packages
+   - Dependencies: None
+
+2. **Create database schema for users**
+   - Design user table structure
+   - Dependencies: Step 1
+
+3. **Implement password hashing utilities**
+   - Create bcrypt wrapper functions
+   - Dependencies: Step 1
+
+4. **Create JWT token service**
+   - Implement token generation and verification
+   - Dependencies: Step 1
+
+5. **Build authentication controller**
+   - Implement register, login, and refresh endpoints
+   - Dependencies: Step 3, Step 4
+
+6. **Create authentication middleware**
+   - Build token verification middleware
+   - Dependencies: Step 4
+
+7. **Set up authentication routes**
+   - Configure Express routes
+   - Dependencies: Step 5, Step 6
+
+8. **Add rate limiting**
+   - Configure rate limiting for auth endpoints
+   - Dependencies: Step 7
+
+9. **Create integration tests**
+   - Write comprehensive test suite
+   - Dependencies: Step 8
+
+10. **Update documentation**
+    - Document API endpoints and usage
+    - Dependencies: Step 9
+
+## Validation Requirements
+
+- Required checks: lint, test, coverage, secrets
+- All tests must pass with 80% coverage minimum
+- No hardcoded secrets in codebase
+- ESLint must pass with no errors
+
+## Timeline
+
+- Estimated completion: 2-3 days
+- Critical path: Steps 1-7 must be completed sequentially
+- Parallel work possible: Documentation can be written alongside implementation

package/src/__tests__/fixtures/speckit/sample-spec-namespaced.md

@@ -0,0 +1,50 @@
+# Specification
+
+## Intent
+
+Implement user authentication with OAuth2 support using the SpecKit agent-first
+workflow.
+
+## Overview
+
+This specification defines the authentication feature using SpecKit's
+agent-first architecture. Use `/speckit.clarify` for any ambiguous requirements
+and `/speckit.analyze` for cross-artifact validation.
+
+## Goals
+
+- Implement OAuth2 authentication flow
+- Support multiple identity providers
+- Integrate with speckit.analyze for validation
+
+## Requirements
+
+- Node.js 18+ runtime
+- OAuth2 client library
+- Session management middleware
+
+## Changes
+
+### Files to Create
+
+#### Create src/auth/oauth2.ts
+
+OAuth2 authentication handler with provider abstraction.
+
+```typescript
+export class OAuth2Handler {
+  async authenticate(provider: string): Promise<AuthResult> {
+    // Implementation
+  }
+}
+```
+
+#### Create src/auth/session.ts
+
+Session management middleware for authenticated users.
+
+### Files to Update
+
+#### Update src/app.ts
+
+Add authentication middleware to the application pipeline.

package/src/__tests__/fixtures/speckit/sample-spec.md

@@ -0,0 +1,105 @@
+# Specification
+
+## Intent
+
+Implement a user authentication system with JWT tokens to secure API endpoints
+and manage user sessions effectively.
+
+## Overview
+
+This specification outlines the implementation of a JWT-based authentication
+system that will provide secure access control for our API endpoints. The system
+will support user registration, login, logout, and token refresh functionality.
+
+## Goals
+
+- Implement secure user authentication using JWT tokens
+- Add middleware for protecting API routes
+- Support token refresh mechanism for long-lived sessions
+- Implement proper password hashing and validation
+- Add rate limiting for authentication endpoints
+
+## Requirements
+
+- Node.js 18+ runtime environment
+- Express.js web framework
+- jsonwebtoken library for JWT handling
+- bcrypt for password hashing
+- Redis for session management (optional)
+
+## Changes
+
+### Files to Create
+
+#### Create authentication controller at `src/controllers/auth.controller.ts`
+
+This controller will handle all authentication-related endpoints including
+registration, login, and token refresh.
+
+```typescript
+import { Request, Response } from 'express';
+import jwt from 'jsonwebtoken';
+import bcrypt from 'bcrypt';
+
+export class AuthController {
+  async register(req: Request, res: Response) {
+    // Implementation here
+  }
+
+  async login(req: Request, res: Response) {
+    // Implementation here
+  }
+
+  async refresh(req: Request, res: Response) {
+    // Implementation here
+  }
+}
+```
+
+#### Create authentication middleware at `src/middleware/auth.middleware.ts`
+
+Middleware to verify JWT tokens and protect routes.
+
+```typescript
+import { Request, Response, NextFunction } from 'express';
+import jwt from 'jsonwebtoken';
+
+export function authenticateToken(
+  req: Request,
+  res: Response,
+  next: NextFunction
+) {
+  // Token verification logic
+}
+```
+
+### Files to Update
+
+#### Update main application file `src/app.ts`
+
+Add authentication routes and middleware to the Express application.
+
+#### Update environment configuration `src/config/env.ts`
+
+Add JWT secret and token expiration settings.
+
+### Configuration Changes
+
+#### Update `.env` file
+
+Add the following environment variables:
+
+- JWT_SECRET: Secret key for signing tokens
+- JWT_EXPIRES_IN: Token expiration time
+- REFRESH_TOKEN_EXPIRES_IN: Refresh token expiration time
+
+### Dependencies to Add
+
+- jsonwebtoken: For creating and verifying JWT tokens
+- bcrypt: For password hashing
+- express-rate-limit: For rate limiting authentication endpoints
+
+### Scripts to Execute
+
+- Run database migrations to add user table
+- Generate RSA key pair for token signing (optional)

package/src/__tests__/fixtures/speckit/sample-tasks.md

@@ -0,0 +1,87 @@
+# Tasks
+
+Generated from APS: aps-1234abcd Last updated: 2024-01-15T10:30:00Z
+
+## Task List
+
+- [x] ✅ Set up project dependencies
+  - [x] Install jsonwebtoken package
+  - [x] Install bcrypt package
+  - [x] Install express-rate-limit package
+  - [x] Update package.json scripts
+
+- [x] ✅ Create database schema for users
+  - [x] Design user table structure
+  - [x] Write migration script
+  - [x] Run migration
+
+- [x] ✅ Implement password hashing utilities
+  - [x] Create bcrypt wrapper functions
+  - [x] Add password validation rules
+  - [x] Write unit tests
+
+- [ ] ⏳ Create JWT token service
+  - [x] Implement token generation
+  - [ ] Implement token verification
+  - [ ] Add refresh token logic
+  - [ ] Write unit tests
+
+- [ ] ⏳ Build authentication controller
+  - [ ] Implement register endpoint
+  - [ ] Implement login endpoint
+  - [ ] Implement refresh endpoint
+  - [ ] Add input validation
+
+- [ ] ⏳ Create authentication middleware
+  - [ ] Build token verification middleware
+  - [ ] Add role-based access control
+  - [ ] Handle token expiration
+
+- [ ] ⏳ Set up authentication routes
+  - [ ] Configure Express routes
+  - [ ] Apply middleware to protected routes
+  - [ ] Add error handling
+
+- [ ] ⏳ Add rate limiting
+  - [ ] Configure rate limiting for auth endpoints
+  - [ ] Set appropriate limits
+  - [ ] Test rate limiting
+
+- [ ] ⏳ Create integration tests
+  - [ ] Write registration tests
+  - [ ] Write login tests
+  - [ ] Write protected route tests
+  - [ ] Test error scenarios
+
+- [ ] ⏳ Update documentation
+  - [ ] Document API endpoints
+  - [ ] Add usage examples
+  - [ ] Update README
+
+## Progress
+
+- Total tasks: 10
+- Completed: 3
+- Remaining: 7
+- Progress: 30%
+
+## Execution History
+
+### 2024-01-15 10:00:00
+
+- Status: in_progress
+- Executor: developer@example.com
+- Completed tasks 1-3
+
+### 2024-01-14 15:30:00
+
+- Status: started
+- Executor: developer@example.com
+- Initial setup and planning
+
+## Notes
+
+- Bcrypt rounds set to 10 for development, should be 12 for production
+- JWT secret needs to be stored securely in environment variables
+- Consider implementing logout functionality with token blacklisting
+- Rate limiting values may need adjustment based on usage patterns