Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
29 commits
Select commit Hold shift + click to select a range
7ce9b78
fix(circulatory): Fix Artery transformation order and linting
claude Nov 7, 2025
1f24aa2
fix(circulatory): Complete Phase 4 with tests fixed and linting cleanup
claude Nov 7, 2025
df6024d
feat(respiratory): Implement Phase 5 Part 1 - Diaphragm breathing con…
claude Nov 7, 2025
a2bd75b
feat(respiratory): Implement Phase 5 Parts 1-2 - Diaphragm + Lung
claude Nov 7, 2025
56912e4
feat(respiratory): Implement Phase 5 Part 3 - Bronchi protocol adapters
claude Nov 7, 2025
625cd99
feat(respiratory): Implement Phase 5 Part 4 - Alveoli API endpoints
claude Nov 7, 2025
088a52c
feat(respiratory): Implement Phase 5 Part 5 - Oxygen resource management
claude Nov 7, 2025
c8f51eb
fix(deps): Update vite to 7.2.2 to fix esbuild security vulnerability
claude Nov 7, 2025
e8b3d05
fix(deps): Upgrade to ESLint 9 and migrate to flat config
claude Nov 7, 2025
5bbd33f
docs(theater): Add The Anatomy Theater project plan and import tools
claude Nov 7, 2025
e3ea340
Potential fix for code scanning alert no. 12: Unused variable, import…
kluth Nov 7, 2025
6378f53
Potential fix for code scanning alert no. 9: Incomplete string escapi…
kluth Nov 7, 2025
056ba2d
Potential fix for code scanning alert no. 10: Incomplete string escap…
kluth Nov 7, 2025
314d6e6
Potential fix for code scanning alert no. 11: Unused variable, import…
kluth Nov 7, 2025
eac94b6
Potential fix for code scanning alert no. 13: Replacement of a substr…
kluth Nov 7, 2025
fe59e3c
Potential fix for code scanning alert no. 14: Incomplete string escap…
kluth Nov 7, 2025
69fd540
Potential fix for code scanning alert no. 15: Incomplete string escap…
kluth Nov 7, 2025
190b9ef
fix(lint): Fix ESLint and Prettier issues
claude Nov 7, 2025
440482b
feat(theater): Implement Phase 6.1 - Theater Core
claude Nov 7, 2025
c2ff4db
feat(theater): Implement Phase 6.2 - Specimen System
claude Nov 7, 2025
40f248e
feat(theater): Implement Phase 6.3 - Microscope debugging tools
claude Nov 7, 2025
20141f7
feat(theater): Implement Phase 6.4 - Laboratory testing system
claude Nov 8, 2025
99fd5cb
feat(theater): Implement Phase 6.5 - Atlas documentation system
claude Nov 8, 2025
82a4070
feat(theater): Implement Phase 6.6 - Server & Hot Reload System
claude Nov 8, 2025
8cd2a31
docs(theater): Add comprehensive Theater demo and examples
claude Nov 8, 2025
6903e55
feat(immune): Implement initial Immune System - Antibody and TCell
claude Nov 8, 2025
91f79f5
fix(immune): Fix exactOptionalPropertyTypes compliance
claude Nov 8, 2025
534be7a
feat(immune): Implement BCell - Authorization System
claude Nov 8, 2025
04a7693
feat(immune): Implement Macrophage - Input Sanitization System
claude Nov 8, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
82 changes: 0 additions & 82 deletions .eslintrc.json

This file was deleted.

21 changes: 21 additions & 0 deletions LINTING_DEBT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Linting Technical Debt

## Status
The circulatory and muscular systems were added in commit `d2214b0 wip: ready for take off` with 207 pre-existing linting errors.

## Current State
- **Tests**: ✅ 764/764 passing
- **TypeScript**: ✅ 0 errors (strict mode compliant)
- **Linting**: ⚠️ 142 errors (all pre-existing from d2214b0)

## Issue #19 Changes
The bug fixes for issue #19 added ZERO new linting errors. All changes are clean.

## Recommended Action
Create issue #36 (Deprecated Dependencies Audit) to include a linting cleanup task.

## Error Breakdown
- 46 @typescript-eslint/no-explicit-any
- 19 @typescript-eslint/no-non-null-assertion
- 15 @typescript-eslint/strict-boolean-expressions
- Others: require-await, no-misused-promises, etc.
206 changes: 206 additions & 0 deletions THEATER_IMPORT_README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,206 @@
# The Anatomy Theater - GitHub Import Guide

This directory contains files to import The Anatomy Theater project plan into GitHub.

## Files

1. **`anatomy-theater-github-import.json`** - Complete project structure with milestones and issues
2. **`import-theater-issues.sh`** - Shell script to automate GitHub import
3. **`THEATER_IMPORT_README.md`** - This file

## Project Overview

**The Anatomy Theater** is Phase 6 of the Synapse framework - a powerful component development and documentation system that replaces Storybook with medical-themed terminology and enhanced features.

### Milestones (8 phases)

- **Phase 6.1**: Theater Core (4 issues)
- **Phase 6.2**: Specimen System (3 issues)
- **Phase 6.3**: Microscope Tools (5 issues)
- **Phase 6.4**: Laboratory (4 issues)
- **Phase 6.5**: Atlas (4 issues)
- **Phase 6.6**: Server & Hot Reload (3 issues)
- **Phase 6.7**: CLI & Configuration (3 issues)
- **Phase 6.8**: Integration & Polish (6 issues)

**Total: 32 issues across 8 milestones**

## Import Methods

### Method 1: GitHub CLI (Recommended)

1. **Install GitHub CLI**:
```bash
# macOS
brew install gh

# Linux
sudo apt install gh

# Or download from: https://cli.github.com/
```

2. **Authenticate**:
```bash
gh auth login
```

3. **Edit the script** to set your repository:
```bash
# Edit import-theater-issues.sh
REPO="your-username/synapse" # Change this line
```

4. **Run the import**:
```bash
chmod +x import-theater-issues.sh
./import-theater-issues.sh
```

### Method 2: GitHub API with Node.js

```javascript
const fs = require('fs');
const https = require('https');

const data = JSON.parse(fs.readFileSync('anatomy-theater-github-import.json'));
const GITHUB_TOKEN = process.env.GITHUB_TOKEN;
const REPO = 'username/synapse';

// Create milestones
data.milestones.forEach(milestone => {
// POST to /repos/{owner}/{repo}/milestones
});

// Create issues
data.issues.forEach(issue => {
// POST to /repos/{owner}/{repo}/issues
});
```

### Method 3: Manual Import

1. **Create Milestones** (GitHub UI):
- Go to: `https://github.com/your-username/synapse/milestones/new`
- Create each milestone with title, description, and due date from the JSON

2. **Create Issues** (GitHub UI):
- Go to: `https://github.com/your-username/synapse/issues/new`
- Copy-paste title and body from the JSON
- Add labels and milestone

### Method 4: GitHub Projects (Beta)

GitHub Projects (beta) supports importing from CSV:

1. **Convert JSON to CSV**:
```bash
# Use jq to convert
jq -r '.issues[] | [.title, .body, .labels | join(","), .milestone] | @csv' anatomy-theater-github-import.json > theater-issues.csv
```

2. **Import to Project**:
- Create a new GitHub Project (beta)
- Use the "Import from CSV" feature

## Project Structure

```
The Anatomy Theater
├── Phase 6.1: Theater Core
│ ├── Issue #1: Implement Theater base class
│ ├── Issue #2: Implement Stage component
│ ├── Issue #3: Implement Amphitheater
│ └── Issue #4: Implement Instrument base interface
├── Phase 6.2: Specimen System
│ ├── Issue #5: Implement Specimen wrapper
│ ├── Issue #6: Implement Observation (variations)
│ └── Issue #7: Implement Dissection
├── Phase 6.3: Microscope Tools
│ ├── Issue #8: Implement Microscope hub
│ ├── Issue #9: Implement SignalTracer
│ ├── Issue #10: Implement StateExplorer
│ ├── Issue #11: Implement PerformanceProfiler
│ └── Issue #12: Implement HealthMonitor
├── Phase 6.4: Laboratory
│ ├── Issue #13: Implement Laboratory
│ ├── Issue #14: Implement PetriDish
│ ├── Issue #15: Implement Culture
│ └── Issue #16: Implement Experiment
├── Phase 6.5: Atlas
│ ├── Issue #17: Implement Atlas
│ ├── Issue #18: Implement ComponentCatalogue
│ ├── Issue #19: Implement Diagram
│ └── Issue #20: Implement Protocol
├── Phase 6.6: Server & Hot Reload
│ ├── Issue #21: Implement TheaterServer
│ ├── Issue #22: Implement HotReload system
│ └── Issue #23: Implement WebSocket communication
├── Phase 6.7: CLI & Configuration
│ ├── Issue #24: Implement Theater CLI
│ ├── Issue #25: Implement Theater configuration
│ └── Issue #26: Implement Specimen file loader
└── Phase 6.8: Integration & Polish
├── Issue #27: Create Theater UI components
├── Issue #28: Write Theater documentation
├── Issue #29: Create example specimens
├── Issue #30: Integration testing suite
├── Issue #31: Performance optimization
├── Issue #32: Accessibility audit and fixes
└── Issue #33: Production build system
```

## Key Features

The Anatomy Theater surpasses Storybook with:

- ✅ **Real-time Neural Signal Visualization** - See signals flowing between components
- ✅ **Time-Travel State Debugging** - Built-in with VisualAstrocyte
- ✅ **Live Connection Topology** - Interactive neural network graph
- ✅ **Signal Replay** - Record and replay user interactions
- ✅ **Smart Auto-Documentation** - Extract from TypeScript + JSDoc
- ✅ **Health Monitoring** - Integrated Microglia monitoring
- ✅ **A/B Testing** - Adaptive UI experimentation
- ✅ **Accessibility Testing** - Built-in sensory profile testing
- ✅ **Performance Profiling** - VisualOligodendrocyte integration
- ✅ **Component Composition Playground** - Drag-and-drop circuit building

## Labels Used

- `Phase 6.1`, `Phase 6.2`, ... `Phase 6.8` - Phase indicators
- `core` - Core functionality
- `specimen` - Specimen system
- `microscope` - Inspection tools
- `laboratory` - Testing environment
- `atlas` - Documentation
- `server` - Server and networking
- `cli` - Command-line interface
- `ui` - User interface
- `enhancement` - New feature
- `documentation` - Documentation
- `testing` - Test-related
- `performance` - Performance optimization
- `accessibility` - Accessibility improvements
- `build` - Build system

## Estimated Timeline

- **Phase 6.1-6.2**: 2 weeks (Core + Specimens)
- **Phase 6.3-6.4**: 3 weeks (Tools + Lab)
- **Phase 6.5**: 1 week (Documentation)
- **Phase 6.6-6.7**: 2 weeks (Server + CLI)
- **Phase 6.8**: 2 weeks (Polish)

**Total: ~10 weeks**

## Next Steps

1. Import issues to GitHub
2. Set up GitHub Project board
3. Assign issues to team members
4. Begin Phase 6.1 implementation
5. Set up CI/CD for The Anatomy Theater

## Questions?

Refer to the main Synapse documentation or open a discussion in the repository.
Loading
Loading