feat!: extract foundry-local-rest-api module to standalone repository

BREAKING CHANGE: The foundry-local-rest-api module has been moved to its own repository
to improve focus and enable independent versioning.

Changes:
- Remove foundry-local-rest-api/ directory and all contents
- Remove build infrastructure (process-template.cjs, build-foundry-module.yml)
- Remove related E2E tests (rest-api-module.spec.ts, issue-7-json-parsing.spec.ts, module-settings.spec.ts)
- Update package.json to remove process-template and test:issue-7 scripts
- Update CHANGELOG.md to document this architectural change

The module is now available at: https://github.com/yourusername/foundryvtt-local-rest-api

Author: laurigates

.github/workflows/build-foundry-module.yml

@@ -1,5 +1,15 @@
 # Changelog
 
+## Unreleased
+
+### Breaking Changes
+
+* **architecture:** extracted foundry-local-rest-api module to standalone repository
+  - Moved `foundry-local-rest-api/` directory to https://github.com/yourusername/foundryvtt-local-rest-api
+  - Removed module build infrastructure (process-template.cjs, build-foundry-module.yml)
+  - Removed related E2E tests (rest-api-module.spec.ts, issue-7-json-parsing.spec.ts, module-settings.spec.ts)
+  - This change improves repository focus and allows independent versioning of the FoundryVTT module
+
 ## [0.11.0](https://github.com/laurigates/foundryvtt-mcp/compare/foundry-mcp-server-v0.10.0...foundry-mcp-server-v0.11.0) (2025-08-03)
 
 

CHANGELOG.md

@@ -1,266 +1,47 @@
 # CLAUDE.md
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+This file provides guidance to Claude Code when working with the FoundryVTT MCP server repository.
 
-## Essential Commands
-
-### Development Workflow
-- `npm run build` - Compile TypeScript to JavaScript in dist/
-- `npm run dev` - Run server in development mode with hot reload
-- `npm start` - Run production server from dist/
-- `npm test` - Run test suite with Vitest
-- `npm run test:watch` - Run tests in watch mode
-- `npm run test:coverage` - Generate test coverage report
-- `npm run lint` - Lint TypeScript code with ESLint
-- `npm run test-connection` - Test connection to FoundryVTT server
-
-### Testing Commands
-- `fvtt launch` - Start FoundryVTT server for testing
-- `npm run test:e2e` - Run end-to-end tests with Playwright
-- `npm run test:e2e:ui` - Run tests in Playwright UI mode
-- `npm run test:e2e:headed` - Run tests in headed browser mode
-- `npm run test:e2e:debug` - Run tests in debug mode
-- `npm run test:e2e:report` - View Playwright test results
-- `tsx scripts/run-e2e-tests.ts` - Run E2E tests with server checks
-
-### Documentation
-- `npm run docs` - Generate TypeDoc documentation
-- `npm run docs:serve` - Generate and serve docs locally
-
-### Setup and Maintenance
-- `npm run setup` - Clean build and test connection
-- `npm run clean` - Remove dist/ directory
-
-## Architecture Overview
+## Project Overview
 
 This is a **Model Context Protocol (MCP) server** that bridges AI assistants with FoundryVTT tabletop gaming software.
 
-### Core Components
-
-**Main Server (`src/index.ts`)**
-- FoundryMCPServer class handles all MCP protocol communication
-- Manages tool handlers for dice rolling, actor/item searches, NPC generation
-- Provides resource endpoints for world data access
-- Implements graceful shutdown and error handling
-
-**FoundryVTT Client (`src/foundry/client.ts`)**
-- Handles authentication via API key or username/password
-- Supports both REST API module and WebSocket connections
-- Implements retry logic and connection testing
-- Provides typed interfaces for all FoundryVTT data
-
-**Configuration System (`src/config/index.ts`)**
-- Environment-based configuration with defaults
-- Validation using Zod schemas
-- Supports multiple authentication methods
-
-**Type Definitions (`src/foundry/types.ts`)**
-- Complete TypeScript interfaces for FoundryVTT entities
-- Actor, Item, Scene, World, and DiceRoll types
-- Search parameter and result types
-
-### Data Flow
-1. AI assistant calls MCP tool (e.g., `roll_dice`, `search_actors`)
-2. Server validates parameters and routes to appropriate handler
-3. Handler uses FoundryClient to communicate with FoundryVTT
-4. Results are formatted and returned as MCP response
-5. Resources provide read-only access to world state
-
-### Authentication
-- **Primary**: API key authentication with FoundryVTT REST API module
-- **Fallback**: Username/password authentication
-- Environment variables: `FOUNDRY_API_KEY` or `FOUNDRY_USERNAME`/`FOUNDRY_PASSWORD`
-
-### Testing Strategy
-- Unit tests for individual components using Vitest framework
-- Integration tests for FoundryVTT connectivity
-- End-to-end testing with Playwright for UI validation (headless by default)
-- Mocked external dependencies in test environment
-- Test coverage reporting with V8
-
-**Playwright Configuration:**
-- **Headless Mode**: Tests run without opening browser windows by default
-- **Multi-Browser**: Tests run on Chromium, Firefox, and WebKit
-- **Auto-Server**: Automatically starts FoundryVTT server before tests
-- **Screenshots**: Captured on test failures for debugging
-- **Videos**: Recorded on failures for detailed analysis
-
-## Key Environment Variables
-
-Required:
-- `FOUNDRY_URL` - FoundryVTT server URL 
-  - Local: `http://localhost:30000`
-  - Reverse Proxy: `https://dnd.lakuz.com`
-  - Network IP: `http://192.168.1.100:30000`
-- `FOUNDRY_API_KEY` OR `FOUNDRY_USERNAME`/`FOUNDRY_PASSWORD`
-
-Optional:
-- `USE_REST_MODULE=true` - Enable REST API module features
-- `LOG_LEVEL=debug` - Detailed logging output
-- `FOUNDRY_TIMEOUT=10000` - Request timeout in milliseconds
-
-## Setup Types
-
-The setup wizard now properly handles different deployment scenarios:
-- **Local Development**: Auto-detects localhost:30000 and similar
-- **Reverse Proxy/Remote**: Prompts for custom URLs like https://dnd.lakuz.com
-- **Network/IP**: Supports custom IP addresses and ports
-
-## Development Notes
-
-- Uses ES modules with `.js` imports (required for MCP SDK compatibility)
-- Strict TypeScript configuration with comprehensive type checking
-- ESLint rules enforce functional programming patterns
-- WebSocket fallback when REST API module unavailable
-- Graceful degradation for missing FoundryVTT features
-
-## Testing Procedures
-
-### Unit and Integration Tests
-```bash
-# Run all tests with coverage
-npm test
-
-# Run tests in watch mode during development
-npm run test:watch
-
-# Generate coverage report
-npm run test:coverage
-
-# Test MCP server connection to FoundryVTT
-npm run test-connection
-```
-
-### End-to-End Testing with Playwright
-
-**Prerequisites:**
-- FoundryVTT installed and accessible
-- Browser automation tools available
-- Test world/data configured
-
-**E2E Testing (Headless by Default):**
-```bash
-# Run tests in headless mode (no browser windows open)
-npm run test:e2e
-
-# Run with visible browser for debugging
-npm run test:e2e:headed
-
-# Interactive test runner with UI
-npm run test:e2e:ui
-
-# Debug mode with breakpoints
-npm run test:e2e:debug
-
-# Generate and view test reports
-npm run test:e2e:report
-```
+## Essential Commands
 
-**Manual E2E Setup (if needed):**
 ```bash
-# 1. Start FoundryVTT server manually
-fvtt launch
-
-# 2. Wait for server to be fully ready (usually 30-60 seconds)  
-# 3. Verify FoundryVTT is accessible at configured URL
-
-# 4. Run tests (auto-starts server by default)
-npm run test:e2e
-
-# Alternative: Use test runner script (includes server checks)
-tsx scripts/run-e2e-tests.ts
+npm run build          # Compile TypeScript
+npm run dev           # Development mode with hot reload
+npm test              # Run tests
+npm run lint          # Lint code
+npm run test:e2e      # Run Playwright E2E tests
+fvtt launch          # Start FoundryVTT server
 ```
 
-**Automated E2E Pipeline:**
-For CI/CD integration, tests should include:
-1. **Pre-test setup**: Automated FoundryVTT server startup with `fvtt launch`
-2. **Health check**: Wait for server readiness before test execution
-3. **Test execution**: Playwright tests against live FoundryVTT instance
-4. **Cleanup**: Graceful server shutdown and resource cleanup
+## Architecture
 
-**Test Categories:**
-- **Module Visibility**: Verify REST API module appears in module management
-- **Module Settings**: Validate module configuration options are accessible  
-- **API Endpoints**: Test REST API endpoint accessibility and responses
-- **Authentication**: Validate login flows and API key usage
-- **Module Installation**: Verify module files and manifest are properly installed
-- **Issue-Specific Testing**: Targeted tests for known issues and bug reproduction
+- **MCP Server** (`src/index.ts`): Handles tool/resource requests from AI assistants
+- **FoundryVTT Client** (`src/foundry/client.ts`): Communicates with FoundryVTT via REST API or WebSocket
+- **Tools**: Dice rolling, actor/item searches, NPC generation
+- **Resources**: Read-only access to world data
 
-**Test Data Requirements:**
-- Test world with sample actors, items, and scenes
-- Configured user accounts with appropriate permissions
-- Mock data for consistent test results
+## Environment Variables
 
-### Performance Testing
 ```bash
-# Load testing for concurrent MCP connections
-npm run test:load
-
-# Memory usage profiling
-npm run test:memory
-
-# Response time benchmarking
-npm run test:benchmark
+FOUNDRY_URL=http://localhost:30000  # FoundryVTT server URL
+FOUNDRY_API_KEY=your_api_key       # API authentication (preferred)
+# OR
+FOUNDRY_USERNAME=username          # Username authentication
+FOUNDRY_PASSWORD=password          # Password authentication
 ```
 
-### Browser Modes for E2E Testing
-
-**Headless Mode (Default):**
-- Fastest execution, no visual distractions
-- Perfect for CI/CD pipelines and automated testing
-- Use for regular development and verification
-
-**Headed Mode (Visual):**
-- Opens actual browser windows to see test execution
-- Useful for debugging failing tests or understanding test flow
-- Use when developing new tests or investigating issues
-
-**Interactive Mode (UI):**
-- Playwright's test runner interface with step-by-step control
-- Best for developing and debugging complex test scenarios
-- Allows pausing, stepping through, and inspecting test state
-
-**Debug Mode:**
-- Opens browser with developer tools and breakpoints
-- Enables step-by-step debugging with Playwright inspector
-- Essential for diagnosing complex test failures
-
-### Development Testing Workflow
-1. **Start FoundryVTT**: `fvtt launch` (optional - auto-started by tests)
-2. **Run unit tests**: `npm test`  
-3. **Test MCP connection**: `npm run test-connection`
-4. **Run E2E tests**: `npm run test:e2e` (headless by default)
-5. **Debug if needed**: `npm run test:e2e:headed` or `npm run test:e2e:debug`
-6. **Review test results**: `npm run test:e2e:report`
+## Testing
 
-### Issue-Specific Testing
+- **Unit Tests**: `npm test` (Vitest)
+- **E2E Tests**: `npm run test:e2e` (Playwright, headless by default)
+- **Issue #7 Tests**: `npm run test:issue-7` (JSON parsing error reproduction)
 
-**Issue #7 - JSON Parsing Errors:**
-```bash
-# Test for JSON parsing errors specifically
-npm run test:issue-7
-
-# Run with visible browser for debugging
-npm run test:issue-7:headed
-
-# Using Makefile
-make test-issue-7
-make test-issue-7-headed
-```
+## Key Notes
 
-This test specifically targets the malformed JSON error reported in GitHub issue #7:
-- Tests all REST API endpoints for JSON parsing errors
-- Validates array response formats 
-- Checks for malformation patterns like missing commas, extra commas, unclosed objects
-- Monitors console errors related to REST API
-- Tests timing issues during module initialization
-
-### Available Test Files
-- `tests/e2e/rest-api-module.spec.ts` - Module visibility and functionality tests
-- `tests/e2e/module-settings.spec.ts` - Comprehensive module settings validation
-- `tests/e2e/issue-7-json-parsing.spec.ts` - **NEW:** Issue #7 JSON parsing error reproduction
-- `tests/e2e/helpers/foundry-helpers.ts` - Reusable test utilities for FoundryVTT
-
-## Reference Links
-- https://foundryvtt.com/api/
-- https://playwright.dev/docs/intro
+- Uses ES modules with `.js` imports (MCP SDK requirement)
+- WebSocket fallback when REST API module unavailable
+- Playwright tests run headless by default (use `test:e2e:headed` for visual debugging)