refactor: Migrate to pnpm monorepo with clean 3-layer architecture

  - Implement Ports and Adapters pattern with full separation of concerns
  - Split codebase into three packages:
    * @starfleet/data-core: Pure business logic with zero Node.js dependencies
    * @starfleet/data-host-node: Node.js adapters implementing core ports
    * @starfleet/data-cli: Thin presentation layer with composition root
  - Migrate from npm to pnpm for monorepo management
  - Add workspace configuration with pnpm-workspace.yaml
  - Configure .npmrc for optimal pnpm workspace behavior
  - Implement runtime port validation with ensurePort
  - Use workspace:* protocol for local package dependencies
  - Add proper package exports with /* patterns for directory mapping
  - Establish clean dependency injection via composition root
  - Ensure all tests pass with new architecture

Author: flyingrobots

.npmrc

@@ -0,0 +1,8 @@
+strict-peer-dependencies=true
+prefer-workspace-packages=true
+save-workspace-protocol=true
+auto-install-peers=false
+public-hoist-pattern[]=*eslint*
+public-hoist-pattern[]=@types/*
+public-hoist-pattern[]=*prettier*
+public-hoist-pattern[]=*vitest*

docs/README.md

@@ -8,6 +8,7 @@ Welcome to the D.A.T.A. (Database Automation, Testing, and Alignment) documentat
 ## 📚 Documentation Structure
 
 ### 🚀 [Features](/docs/features/)
+
 User-facing feature documentation and guides
 
 - **[Edge Functions Integration](features/edge-functions.md)** - Deploy and manage Supabase Edge Functions alongside migrations
@@ -16,6 +17,7 @@ User-facing feature documentation and guides
   - Production safety features
 
 ### ⚙️ [Configuration](/docs/configuration/)
+
 How to configure D.A.T.A. for your project
 
 - **[Testing Configuration](configuration/testing.md)** - Configure test execution, coverage, and automation
@@ -24,6 +26,7 @@ How to configure D.A.T.A. for your project
   - Watch mode and auto-compilation settings
 
 ### 🔮 [Roadmap](/docs/roadmap/)
+
 Future plans and vision for D.A.T.A.
 
 - **[Ideas and Future Features](roadmap/ideas-and-future.md)** - The grand vision for D.A.T.A.'s evolution
@@ -32,6 +35,7 @@ Future plans and vision for D.A.T.A.
   - AI-assisted migration intelligence
 
 ### 🔧 [Technical](/docs/technical/)
+
 Implementation details and architecture documentation
 
 - **[Memory Management](technical/memory-management.md)** - How D.A.T.A. handles large test suites
@@ -45,34 +49,39 @@ Implementation details and architecture documentation
   - Migration generation
 
 ### 🎯 [Decisions](/docs/decisions/)
+
 Architecture Decision Records (ADRs)
 
 - **[CLI Framework](decisions/cli-framework.md)** - Why Commander.js was chosen
 - **[Event Architecture](decisions/event-architecture.md)** - Event-driven command pattern
 - **[Testing Strategy](decisions/testing-strategy.md)** - pgTAP and Vitest integration
 
 ### 📋 [Tasks](/docs/TASKS/)
+
 Task management and project tracking
 
 - **[System Tasks](TASKS/system.md)** - Core system improvements and features
 - **[Test Tasks](TASKS/test.md)** - Testing infrastructure and coverage
 - **[Migration Tasks](TASKS/migration.md)** - Migration system enhancements
 
 ### 🔍 [Audits](/docs/audits/)
+
 Code quality and security audits
 
 - Repository structure audits
 - Security review documentation
 - Performance analysis reports
 
 ### 👀 [Code Reviews](/docs/code-reviews/)
+
 Code review templates and guidelines
 
 - Review checklists
 - Best practices documentation
 - Common patterns and anti-patterns
 
 ### 🖖 [Fun](/docs/fun/)
+
 Star Trek references and easter eggs
 
 - **[Bridge Crew Personalities](fun/personalities.md)** - Different personality modes for D.A.T.A.
@@ -82,35 +91,41 @@ Star Trek references and easter eggs
 ## 🗺️ Quick Navigation Guide
 
 ### For New Users
+
 1. Start with [Edge Functions Integration](features/edge-functions.md) to understand core features
 2. Review [Testing Configuration](configuration/testing.md) to set up your project
 3. Check the main [README](/README.md) for quick start instructions
 
 ### For Contributors
+
 1. Read relevant [Architecture Decisions](decisions/) to understand design choices
 2. Review [Technical Documentation](technical/) for implementation details
 3. Check [Tasks](TASKS/) for current work items
 4. Follow [Code Review Guidelines](code-reviews/) for contributions
 
 ### For System Architects
+
 1. Study the [Golden SQL Compilation Algorithm](technical/golden-sql-compilation-algorithm.md)
 2. Review [Memory Management](technical/memory-management.md) architecture
 3. Explore [Ideas and Future Features](roadmap/ideas-and-future.md) for roadmap planning
 
 ## 📖 Documentation Standards
 
 ### File Naming
+
 - Use kebab-case for all documentation files
 - Be descriptive but concise (e.g., `memory-management.md` not `mm.md`)
 - Group related docs in appropriate directories
 
 ### Content Structure
+
 - Start with a clear title and overview
 - Use hierarchical headings (H2 for main sections, H3 for subsections)
 - Include code examples where relevant
 - Add cross-references to related documentation
 
 ### Maintenance
+
 - Keep documentation synchronized with code changes
 - Archive outdated documentation rather than deleting
 - Date significant updates in document headers
@@ -134,12 +149,12 @@ When adding new documentation:
 
 ## 🔗 External Resources
 
-- [Main Repository](https://github.com/starfleet/supa-data)
-- [Issue Tracker](https://github.com/starfleet/supa-data/issues)
+- [Main Repository](https://github.com/flyingrobots/DATA)
+- [Issue Tracker](https://github.com/flyingrobots/DATA/issues)
 - [Supabase Documentation](https://supabase.com/docs)
 - [pgTAP Documentation](https://pgtap.org/)
 
 ---
 
 *"The complexity of our documentation structure is directly proportional to the sophistication of our system. Both are... fascinating."*  
-— Lt. Commander Data, Chief Documentation Officer
+— Lt. Commander Data, Chief Documentation Officer

package-lock.json

@@ -4,6 +4,7 @@
   "description": "🖖 D.A.T.A. - Database Automation, Testing, and Alignment for PostgreSQL/Supabase",
   "type": "module",
   "private": true,
+  "packageManager": "[email protected]",
   "workspaces": [
     "starfleet/*"
   ],

package.json

@@ -0,0 +1,2 @@
+packages:
+  - "starfleet/*"