bunsane 0.3.2 → 0.4.0

package/.serena/memories/code_style_and_conventions.md

@@ -1,76 +0,0 @@
-# Code Style and Conventions
-
-## Formatting
-- **Indentation**: 4 spaces (configured in `.prettierrc`)
-- **No tabs**: Spaces only
-- **Prettier**: Used for formatting
-
-## TypeScript Configuration
-- **Strict mode**: Enabled
-- **Experimental decorators**: Enabled
-- **Emit decorator metadata**: Enabled
-- **Module**: ESNext/Preserve
-- **Path alias**: `@/*` maps to `./*`
-
-## Naming Conventions
-- **Classes**: PascalCase (e.g., `Entity`, `BaseComponent`, `CacheManager`)
-- **Methods/Functions**: camelCase (e.g., `createEntity`, `getEntityWithID`)
-- **Variables**: camelCase
-- **Constants**: camelCase or UPPER_SNAKE_CASE for environment-like values
-- **Private properties**: Prefix with underscore (e.g., `_dirty`, `_persisted`)
-- **Interfaces**: PascalCase, often prefixed with `I` (e.g., `IEntity`)
-- **Types**: PascalCase
-
-## Decorators Usage
-The framework heavily uses TypeScript decorators:
-
-```typescript
-// Component definition
-@Component
-class MyComponent extends BaseComponent {
-    @CompData()
-    myField!: string;
-}
-
-// ArcheType definition
-class MyArcheType extends BaseArcheType {
-    @ArcheTypeField(MyComponent)
-    myComponent!: MyComponent;
-}
-```
-
-## Import Style
-- **ALWAYS use relative imports** (`./`, `../`) for all internal modules
-- Do NOT use bare imports like `from "core/Logger"` - they rely on `baseUrl` and break consumer typechecking
-- The `@/` path alias is configured but not used in practice; prefer relative imports
-- Group imports: external packages first, then internal modules
-- **Type-only imports**: Use `import type` for interface/type imports when only used for type checking:
-  ```typescript
-  import type { CacheProvider } from './CacheProvider';
-  ```
-  Benefits: Clearer intent, reduced runtime dependencies, better tree-shaking
-
-## Testing Conventions
-- Test files: `*.test.ts`
-- Use Bun's built-in test runner (`bun:test`)
-- Structure: `describe` blocks for grouping, `test` for individual cases
-- Use `beforeAll`/`afterAll` for setup/cleanup
-- Integration tests should clean up created entities
-
-```typescript
-import { describe, test, expect, beforeAll, afterAll } from 'bun:test';
-
-describe('FeatureName', () => {
-    beforeAll(async () => { /* setup */ });
-    afterAll(async () => { /* cleanup */ });
-    
-    test('should do something', async () => {
-        expect(result).toBe(expected);
-    });
-});
-```
-
-## Documentation
-- Use JSDoc comments for public APIs
-- Block comments for file headers explaining purpose
-- Inline comments sparingly, only when logic is complex

package/.serena/memories/project_overview.md

@@ -1,43 +0,0 @@
-# BunSane Project Overview
-
-## Purpose
-BunSane is a batteries-included TypeScript API framework for Bun with:
-- Entity–Component storage on PostgreSQL (auto-migrates base tables on first run)
-- Fluent, performant Query builder
-- Zero-boilerplate GraphQL with GraphQL Yoga
-- Declarative Components with decorators and indexed fields
-
-**Status**: EXPERIMENTAL - Not Production Ready
-
-## Tech Stack
-- **Runtime**: Bun
-- **Language**: TypeScript 5.9+ (strict mode, experimental decorators)
-- **Database**: PostgreSQL
-- **GraphQL**: GraphQL Yoga + GQLoom (@gqloom/core, @gqloom/zod)
-- **Validation**: Zod 4.x
-- **Logging**: Pino (with pino-pretty for development)
-- **Cache**: Memory and Redis support (ioredis)
-- **Data Loading**: dataloader for batching
-
-## Key Concepts
-1. **Entity**: Base unit of data storage, identified by UUID
-2. **Component**: Data attached to entities (decorators: @Component, @CompData)
-3. **ArcheType**: Defines a template of components an entity should have
-4. **Query**: Fluent query builder for retrieving entities with components
-5. **Service**: Business logic layer with auto-generated GraphQL schema
-
-## Environment Variables
-Database configuration via environment variables:
-- `POSTGRES_HOST`, `POSTGRES_DB`, `POSTGRES_USER`, `POSTGRES_PASSWORD`
-- `POSTGRES_MAX_CONNECTIONS`
-- `LOG_LEVEL`, `LOG_PRETTY`
-
-## Cache Configuration
-Cache system supports multiple providers (configured in `config/cache.config.ts`):
-- **Providers**: `memory`, `redis`, `multilevel`
-- **Query cache**: Can be enabled with configurable TTL and max size
-- All providers implement standardized `CacheProvider` interface
-- Wrapper providers available: Analytics, MultiLevel, AdaptiveTTL
-
-## Repository
-https://github.com/yaaruu/bunsane

package/.serena/memories/schema-dsl-plan.md

@@ -1,107 +0,0 @@
-# Schema DSL for GraphQL Operation Inputs
-
-## Status: Planning Complete, Ready for Implementation
-
-**Date**: 2026-02-02
-
-## Problem Statement
-
-The current Zod → @gqloom → GraphQL pipeline is broken for complex input types:
-- `zod: 4.1.5` (Zod v4 has breaking internal changes)
-- `@gqloom/zod: ^0.12.2` (designed for Zod v3)
-- `generateInputTypeFromZod()` is 360 lines of workarounds that still fail
-
-### What's Broken
-- Nested `z.object()` - Broken
-- `.omit()`, `.extend()`, `.partial()` - Broken (empty `_def`)
-- Arrays of objects - Broken
-- Unions - Broken
-- Effects/transforms - Broken
-- Only basic scalars work: `z.string()`, `z.number()`, `z.boolean()`
-
-## Solution: Custom Schema DSL
-
-Build a purpose-built DSL (~400 lines) that:
-1. Generates GraphQL SDL directly (bypasses @gqloom for inputs)
-2. Uses Zod only for runtime validation
-3. Coexists with existing system (ArcheTypes still use @gqloom for outputs)
-
-## API Design
-
-```typescript
-import { t } from 'bunsane/schema';
-
-@GraphQLOperation({
-    type: "Mutation",
-    input: {
-        email: t.string().email().required(),
-        password: t.string().minLength(8).required(),
-        settings: t.object({
-            theme: t.enum(['light', 'dark'] as const, 'Theme'),
-            notifications: t.boolean(),
-        }, 'SettingsInput'),
-    },
-    output: User
-})
-async createUser(input: InferInput<typeof input>) { ... }
-```
-
-## File Structure
-
-```
-schema/
-├── index.ts           # Public exports: t, InferInput, SchemaType
-├── types.ts           # Core interfaces and constraint types
-├── builders/
-│   ├── index.ts       # Export all builders
-│   ├── base.ts        # BaseSchemaType abstract class
-│   ├── scalars.ts     # StringType, IntType, FloatType, BooleanType, IDType
-│   ├── enum.ts        # EnumType
-│   ├── object.ts      # ObjectType (nested inputs)
-│   ├── list.ts        # ListType (arrays)
-│   └── ref.ts         # RefType (reference existing GraphQL types)
-├── generators/
-│   ├── graphql.ts     # Generate GraphQL SDL from schema
-│   └── zod.ts         # Generate Zod schema from schema
-└── inference.ts       # TypeScript type inference helpers
-```
-
-## Implementation Phases
-
-### Phase 1: Foundation (Design Complete)
-- [x] Core types and interfaces
-- [x] Scalar types (String, Int, Float, Boolean, ID)
-- [x] `.required()` / `.optional()` / `.nullable()`
-- [x] Basic `toGraphQL()` and `toZod()` generation
-- [ ] Integration point in SchemaGeneratorVisitor
-- [ ] Basic tests
-
-### Phase 2: Validation Constraints
-- [ ] String: `.minLength()`, `.maxLength()`, `.email()`, `.url()`, `.uuid()`, `.pattern()`
-- [ ] Number: `.min()`, `.max()`, `.positive()`, `.negative()`
-- [ ] Zod schema generation with constraints
-
-### Phase 3: Complex Types
-- [ ] `ObjectType` for nested inputs
-- [ ] `ListType` for arrays
-- [ ] `EnumType` with proper GraphQL enum generation
-- [ ] Nested type definition collection
-
-### Phase 4: Polish & Migration
-- [ ] `InferInput<>` type helper
-- [ ] Error messages with field paths
-- [ ] Documentation
-- [ ] Migration guide
-
-## Key Design Decisions
-
-1. **Single source of truth** - One declaration generates GraphQL SDL + Zod validation + TypeScript types
-2. **No @gqloom for inputs** - Generate SDL directly, use Zod only for runtime validation
-3. **Coexist with existing system** - ArcheTypes still use @gqloom for output types
-4. **Incremental adoption** - Support legacy `GraphQLFieldTypes` alongside new `t.` API
-
-## Related Files
-
-- Plan document: `plan/schema-dsl-analysis.md`
-- Current broken implementation: `gql/generators/SchemaGeneratorVisitor.ts` (`generateInputTypeFromZod()`)
-- Integration target: `gql/generators/SchemaGeneratorVisitor.ts`

package/.serena/memories/suggested_commands.md

@@ -1,80 +0,0 @@
-# Suggested Commands
-
-## Development Commands
-
-### Running Tests
-```bash
-# Run all tests
-bun test
-
-# Run specific test file
-bun test path/to/file.test.ts
-
-# Run tests matching a pattern
-bun test --filter "pattern"
-```
-
-Test configuration is in `bunfig.toml`:
-- Preloads `./test/setup.ts` for database initialization
-- 30-second timeout for integration tests
-- Uses `smol = true` to limit parallelism (avoids DB connection pool exhaustion)
-
-### Building
-```bash
-# Full build (includes studio)
-bun run build
-
-# Build studio only
-bun run build:studio
-
-# Watch mode for development
-bun run dev
-```
-
-### Type Checking
-```bash
-# Run TypeScript compiler
-tsc
-
-# Watch mode
-tsc --watch
-```
-
-### Dead Code Detection
-```bash
-# Run knip for dead code detection
-bunx knip
-```
-
-## Git Commands (Windows)
-```bash
-git status
-git add .
-git commit -m "message"
-git push
-git pull
-git log --oneline -10
-```
-
-## File Operations (Windows)
-```bash
-# List directory
-dir
-ls  # works in Git Bash / PowerShell
-
-# Find files
-dir /s /b *.ts
-Get-ChildItem -Recurse -Filter "*.ts"  # PowerShell
-
-# Search in files
-findstr /s /i "pattern" *.ts
-Select-String -Path "*.ts" -Pattern "pattern" -Recurse  # PowerShell
-```
-
-## Database
-The framework uses PostgreSQL. Ensure a PostgreSQL instance is running and configured via `.env.test` or environment variables.
-
-## Environment Setup
-1. Copy `.env.test` to `.env` for local development
-2. Configure PostgreSQL connection
-3. Run `bun install` for dependencies

package/.serena/memories/typescript-compilation-status.md

@@ -1,54 +0,0 @@
-# TypeScript Compilation Status
-
-**Last Updated**: 2026-02-05
-**Current Error Count**: 69 (down from 100+)
-
-## Recent Improvements
-
-### Cache Interface Standardization (2026-01-24)
-**Errors Resolved**: 30+ cache-related errors
-**Status**: COMPLETE
-
-All cache-related TypeScript errors have been resolved by standardizing implementations of the `CacheProvider` interface. See `cache-interface-refactoring-2026-01-24` memory for details.
-
-## Remaining Error Categories
-
-### 1. SchedulerManager (Priority: High)
-- Location: `scheduler/` directory
-- Issue: Interface or implementation mismatches
-- Status: Not yet addressed
-
-### 2. GraphQL Builders (Priority: Medium)
-- Location: `gql/builders/` directory  
-- Issue: Schema generation type issues
-- Status: Not yet addressed
-
-### 3. Test Access to Private Members (Priority: Low)
-- Location: Various test files
-- Issue: Tests accessing private class members
-- Status: Not yet addressed
-- Note: These are test-specific and don't affect production code
-
-## Strategy for Further Reduction
-
-1. **Next Target**: SchedulerManager errors (highest priority)
-2. **Approach**: Similar to cache refactoring - identify interface, ensure implementations match
-3. **Goal**: Reduce to <50 errors by addressing scheduler issues
-4. **Long-term**: Aim for zero compilation errors
-
-## Metrics
-
-| Date | Error Count | Category Resolved | Notes |
-|------|-------------|-------------------|-------|
-| 2026-02-05 | 69 | Import Resolution | Converted 37 bare imports to relative paths across 18 files |
-| 2026-01-24 | 69 | Cache System | Standardized CacheProvider interface |
-| Prior | 100+ | - | Baseline before cache refactoring |
-
-## Best Practices Established
-
-1. Define clear interfaces before implementations
-2. Use `import type` for type-only imports
-3. Keep wrapper classes in sync with base interfaces
-4. Add explicit type parameters in tests for type safety
-5. Document interface contracts in code and memories
-6. Always use relative imports - bare imports relying on baseUrl break consumer typechecking

package/.serena/project.yml

@@ -1,114 +0,0 @@
-# list of languages for which language servers are started; choose from:
-#   al                  bash                clojure             cpp                 csharp
-#   csharp_omnisharp    dart                elixir              elm                 erlang
-#   fortran             fsharp              go                  groovy              haskell
-#   java                julia               kotlin              lua                 markdown
-#   matlab              nix                 pascal              perl                php
-#   powershell          python              python_jedi         r                   rego
-#   ruby                ruby_solargraph     rust                scala               swift
-#   terraform           toml                typescript          typescript_vts      vue
-#   yaml                zig
-#   (This list may be outdated. For the current list, see values of Language enum here:
-#   https://github.com/oraios/serena/blob/main/src/solidlsp/ls_config.py
-#   For some languages, there are alternative language servers, e.g. csharp_omnisharp, ruby_solargraph.)
-# Note:
-#   - For C, use cpp
-#   - For JavaScript, use typescript
-#   - For Free Pascal/Lazarus, use pascal
-# Special requirements:
-#   - csharp: Requires the presence of a .sln file in the project folder.
-#   - pascal: Requires Free Pascal Compiler (fpc) and optionally Lazarus.
-# When using multiple languages, the first language server that supports a given file will be used for that file.
-# The first language is the default language and the respective language server will be used as a fallback.
-# Note that when using the JetBrains backend, language servers are not used and this list is correspondingly ignored.
-languages:
-- typescript
-
-# the encoding used by text files in the project
-# For a list of possible encodings, see https://docs.python.org/3.11/library/codecs.html#standard-encodings
-encoding: "utf-8"
-
-# whether to use project's .gitignore files to ignore files
-ignore_all_files_in_gitignore: true
-
-# list of additional paths to ignore in all projects
-# same syntax as gitignore, so you can use * and **
-ignored_paths: []
-
-# whether the project is in read-only mode
-# If set to true, all editing tools will be disabled and attempts to use them will result in an error
-# Added on 2025-04-18
-read_only: false
-
-# list of tool names to exclude. We recommend not excluding any tools, see the readme for more details.
-# Below is the complete list of tools for convenience.
-# To make sure you have the latest list of tools, and to view their descriptions, 
-# execute `uv run scripts/print_tool_overview.py`.
-#
-#  * `activate_project`: Activates a project by name.
-#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
-#  * `create_text_file`: Creates/overwrites a file in the project directory.
-#  * `delete_lines`: Deletes a range of lines within a file.
-#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
-#  * `execute_shell_command`: Executes a shell command.
-#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
-#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
-#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
-#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
-#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
-#  * `initial_instructions`: Gets the initial instructions for the current project.
-#     Should only be used in settings where the system prompt cannot be set,
-#     e.g. in clients you have no control over, like Claude Desktop.
-#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
-#  * `insert_at_line`: Inserts content at a given line in a file.
-#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
-#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
-#  * `list_memories`: Lists memories in Serena's project-specific memory store.
-#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
-#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
-#  * `read_file`: Reads a file within the project directory.
-#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
-#  * `remove_project`: Removes a project from the Serena configuration.
-#  * `replace_lines`: Replaces a range of lines within a file with new content.
-#  * `replace_symbol_body`: Replaces the full definition of a symbol.
-#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
-#  * `search_for_pattern`: Performs a search for a pattern in the project.
-#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
-#  * `switch_modes`: Activates modes by providing a list of their names
-#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
-#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
-#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
-#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
-excluded_tools: []
-
-# initial prompt for the project. It will always be given to the LLM upon activating the project
-# (contrary to the memories, which are loaded on demand).
-initial_prompt: ""
-# the name by which the project can be referenced within Serena
-project_name: "bunsane"
-
-# list of tools to include that would otherwise be disabled (particularly optional tools that are disabled by default)
-included_optional_tools: []
-
-# list of mode names to that are always to be included in the set of active modes
-# The full set of modes to be activated is base_modes + default_modes.
-# If the setting is undefined, the base_modes from the global configuration (serena_config.yml) apply.
-# Otherwise, this setting overrides the global configuration.
-# Set this to [] to disable base modes for this project.
-# Set this to a list of mode names to always include the respective modes for this project.
-base_modes:
-
-# list of mode names that are to be activated by default.
-# The full set of modes to be activated is base_modes + default_modes.
-# If the setting is undefined, the default_modes from the global configuration (serena_config.yml) apply.
-# Otherwise, this overrides the setting from the global configuration (serena_config.yml).
-# This setting can, in turn, be overridden by CLI parameters (--mode).
-default_modes:
-
-# fixed set of tools to use as the base tool set (if non-empty), replacing Serena's default set of tools.
-# This cannot be combined with non-empty excluded_tools or included_optional_tools.
-fixed_tools: []
-
-# override of the corresponding setting in serena_config.yml, see the documentation there.
-# If null or missing, the value from the global config is used.
-symbol_info_budget:

package/CLAUDE.md

@@ -1,198 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## Project Overview
-
-BunSane is an experimental TypeScript API framework for Bun using Entity-Component-System (ECS) architecture with PostgreSQL storage. It provides GraphQL Yoga integration with automatic schema generation from decorated services.
-
-**Stack**: Bun, TypeScript, PostgreSQL, GraphQL Yoga, GQLoom, Zod 4.x, Pino logging
-
-## Commands
-
-```bash
-# Install dependencies
-bun install
-
-# Build (includes studio + typecheck)
-bun run build
-
-# Typecheck only
-tsc --noEmit
-
-# Tests (requires PostgreSQL)
-bun test                    # Unit + integration + GraphQL tests
-bun run test:unit           # Unit tests only
-bun run test:integration    # Integration tests only
-bun run test:graphql        # GraphQL schema tests only
-
-# Tests with PGlite (no PostgreSQL required)
-bun run test:pglite         # All tests with PGlite
-bun run test:pglite:unit    # Unit tests only with PGlite
-
-# E2E and stress tests
-bun run test:e2e            # HTTP tests (no DB needed)
-bun run test:stress         # Performance benchmarks
-
-# Run single test file
-bun test path/to/file.test.ts
-
-# Run tests matching pattern
-bun test --grep "pattern"
-```
-
-## Architecture
-
-### ECS Model
-- **Entities**: Generic containers with UUID, stored in `entities` table
-- **Components**: Data containers attached to entities, stored in `components` table with JSONB data
-- **Services**: Business logic with GraphQL operations
-
-### Core Classes
-
-**Entity** (`core/Entity.ts`):
-```typescript
-const entity = Entity.Create();
-entity.add(Position, { x: 0, y: 0 });    // Add component
-await entity.set(Position, { x: 10 });   // Update component
-const pos = await entity.get(Position);  // Get component data
-await entity.save();
-```
-
-**BaseComponent** (`core/components/BaseComponent.ts`):
-```typescript
-@Component
-class Position extends BaseComponent {
-    @CompData() x: number = 0;
-    @CompData({ indexed: true }) y: number = 0;  // Creates DB index
-}
-```
-
-**BaseArcheType** (`core/ArcheType.ts`):
-- Predefined entity templates with required components
-- Auto-generates GraphQL types and CRUD operations
-
-**Query** (`query/Query.ts`):
-```typescript
-const entities = await new Query()
-    .with(Position)                       // Require component
-    .with(Velocity, { filters: [...] })   // With filters
-    .populate()                           // Load all components
-    .limit(10)
-    .exec();
-```
-
-**BaseService** (`service/Service.ts`):
-```typescript
-class UserService extends BaseService {
-    @GraphQLOperation({ type: "Query", input: { id: t.id() }, output: User })
-    async getUser(input: { id: string }, ctx: GraphQLContext) { ... }
-}
-```
-
-### GraphQL
-
-- Schema generated automatically from decorated services and archetypes
-- Input types use Schema DSL (`gql/schema/index.ts`) via `t.` API
-- Operations: `@GraphQLOperation`, `@GraphQLSubscription`
-- Archetypes: `@ArcheTypeFunction` for computed fields
-
-### Database
-
-- PostgreSQL with Bun's native SQL driver (`Bun.SQL`)
-- Auto-migrations on startup for base tables
-- Component data stored as JSONB
-- Indexed fields create GIN indexes automatically
-
-### Caching
-
-- Multi-level cache: L1 (memory) + L2 (Redis)
-- `CacheManager.initialize(config)` is async - always await it
-- Strategies: write-through, write-invalidate
-- Cross-instance invalidation via Redis pub/sub
-
-### File Uploads
-
-- `UploadManager` handles file validation and storage
-- `S3StorageProvider` for S3-compatible storage (AWS, MinIO, R2)
-- REST: `handleUpload(req)` from `upload/RestUpload.ts`
-- GraphQL: `@Upload()` decorator
-
-## Critical Rules
-
-### Import Style
-**ALWAYS use relative imports** (`./`, `../`) for internal modules. Never use bare imports like `from "core/Logger"` - this breaks consumer typechecking.
-
-### Architecture Decisions
-- No Dependency Injection - uses singletons + global exports
-- Singleton access: `CacheManager.getInstance()`, `EntityManager.instance`, etc.
-- Services registered via `ServiceRegistry.register()`
-
-### Test Database Setup
-- Tests require `.env.test` with PostgreSQL config (or use PGlite mode)
-- `bunfig.toml` preloads `tests/setup.ts`
-- PGlite: `CREATE INDEX CONCURRENTLY` must check `process.env.USE_PGLITE`
-- PGlite JSONB: pass JS objects directly, never `JSON.stringify() + ::jsonb`
-
-### Running Tests with PGlite
-
-**IMPORTANT**: To run tests with PGlite, always use `tests/pglite-setup.ts` as the entry point. This script starts an in-memory PostgreSQL server before spawning the test runner.
-
-```bash
-# Correct - uses pglite-setup.ts wrapper
-bun run test:pglite                              # All tests
-bun run test:pglite:unit                         # Unit tests only
-bun tests/pglite-setup.ts tests/unit/            # Specific directory
-bun tests/pglite-setup.ts path/to/file.test.ts   # Single file
-
-# WRONG - will fail with connection errors
-USE_PGLITE=true bun test path/to/file.test.ts    # Won't work!
-```
-
-The wrapper script:
-1. Starts PGlite Socket server on port 54321
-2. Sets required env vars (`USE_PGLITE`, `POSTGRES_*`)
-3. Spawns `bun test` with correct configuration
-4. Cleans up server on exit
-
-**PGlite limitations:**
-- `?|` and `?&` operators not supported (use `@>` / `<@` instead)
-- `CREATE INDEX CONCURRENTLY` not supported
-- Single connection only (`POSTGRES_MAX_CONNECTIONS=1`)
-- **Known Bun SQL + PGlite visibility race**: under a single-connection
-  pool with background work from a prior test file, `await entity.save()`
-  may resolve ≥1ms before the `INSERT INTO entity_components` row is
-  visible to a subsequent `db.unsafe('SELECT ...')` on the same driver.
-  The per-component partition INSERT (e.g. `components_<compname>`) in
-  the same transaction is visible immediately; only the flat
-  `entity_components` row lags. This causes multi-component Query
-  INTERSECTs to return 0 rows when run immediately after save.
-
-  **Mitigation (not a full fix):**
-  1. Shut down application-owned background workers (AI processors,
-     outbox workers, hook-driven save chains) in `afterAll` of each test
-     file — prevents cross-file bleed that amplifies the race.
-  2. Call `await Entity.drainPendingSideEffects()` in `beforeAll` / test
-     `setup` to settle hook-triggered post-commit work (helpful but
-     insufficient on its own).
-  3. Skip the affected test or poll with a short `setTimeout(1)`.
-
-  Root cause lives in the Bun SQL adapter's ACK handling, not bunsane.
-  File upstream with a minimal repro if you hit this.
-
-## Directory Structure
-
-```
-core/           # ECS core: Entity, Component, ArcheType, App
-  cache/        # CacheManager, Redis, Memory caches
-  components/   # BaseComponent, decorators, registry
-  middleware/   # HTTP middleware (AccessLog, RequestId, SecurityHeaders)
-database/       # DatabaseHelper, SQL utilities
-gql/            # GraphQL generation, Schema DSL
-  schema/       # t.* Schema DSL for inputs
-query/          # Fluent Query builder, FilterBuilder
-service/        # BaseService, ServiceRegistry
-upload/         # File uploads, S3StorageProvider
-scheduler/      # Cron-style task scheduling
-tests/          # Unit, integration, GraphQL, E2E, stress tests
-```

package/TODO.md

@@ -1,2 +0,0 @@
-// CORE FEATURE
-TODO: Custom Component Table with Direct Column instead of jsonb. (Risk: Introduce schema migration)