Migrate from Python/ADK to Node.js/Bun with TypeScript

[elicollinson]

Summary

This PR represents a major architectural shift, migrating the entire codebase from a Python-based Google ADK agent system to a Node.js/Bun runtime with TypeScript. The Python agent framework, memory management, code execution, and related infrastructure have been removed in favor of a modern JavaScript/TypeScript stack.

Key Changes

Removed Components

• Python Agent Framework: Removed all Google ADK agent implementations (user_proxy_agent, code_executor_agent, chart_generator_agent)
• Memory System: Removed SQLite-based memory service, memory callbacks, and LLM-based memory extraction
• Code Execution: Removed WASM sandbox executor wrapper and Python code execution infrastructure
• Configuration: Removed Python-based YAML configuration loader and agent prompt management
• Context Compaction: Removed the context compaction system for managing conversation history

Added Components

• CI/CD Pipeline: Added .github/workflows/test-node.yml with:
  • Bun test execution with coverage reporting
  • TypeScript type checking
  • Biome linting
  • Build step with dependency ordering
  • Triggers on changes to src/, tests/, and config files
• Node.js Tooling:
  • package.json for dependency management
  • tsconfig.json for TypeScript configuration
  • biome.json for code formatting/linting
• Git Configuration: Updated .gitignore to exclude node_modules/ and added a new .gitignore template with Node.js-specific patterns

Migration Path

The codebase is transitioning from:

• Python 3.x → Node.js with Bun runtime
• Google ADK agents → TypeScript-based agent system
• YAML configuration → TypeScript/JSON configuration
• SQLite memory → TBD (new memory implementation)
• Python WASM execution → TBD (new code execution strategy)

Implementation Details

• Bun is configured as the primary runtime (latest version)
• TypeScript is the primary language for type safety
• Biome handles both linting and formatting
• Test coverage is tracked via Bun's built-in coverage tool
• Build process depends on successful test and lint jobs

Notes

• This is a foundational migration; new implementations for memory management and code execution will follow
• The workflow ensures code quality through type checking, linting, and test coverage before builds

https://claude.ai/code/session_01LALSEnt9kehERfr2Kgw886

[claude]

Code Review - CLAUDE.md Compliance Issue

Issue Found: claude.md contains outdated verification commands

The CLAUDE.md file still references Python/Poetry commands that no longer work after the migration to Node.js/Bun:

• Line 26: poetry run pytest tests/
• Line 34: poetry run python -m tests.eval.run_eval

These commands should be updated to:

bun test
bun test tests/e2e/harness-integration.test.tsx

Reference:

Solenoid/claude.md

Lines 22 to 35 in 598437b

	Execute the test suite to ensure all tests pass:
	```bash
	poetry run pytest tests/
	```
	### 3. Functional Testing with Agent Harness
	Use the agent harness to functionally test your changes before pushing:
	```bash
	poetry run python -m tests.eval.run_eval
	```