Feat 0.0.2

.github/workflows/ci.yml

@@ -1,58 +1,58 @@
-name: Deploy website
+name: CI
 
 on:
   push:
     branches:
       - main
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  contents: write
 
 jobs:
-  setup:
+  build-and-test:
     runs-on: ubuntu-latest
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
-      - uses: pnpm/action-setup@v2
-        name: Install pnpm
-        with:
-          version: latest
-          run_install: false
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
 
       - name: Install Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: 18
-          cache: 'pnpm'
-
-      - uses: actions/cache@v3
-        name: Setup pnpm cache
+        uses: actions/setup-node@v4
         with:
-          path: node_modules
-          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+          node-version: 20
+          cache: "pnpm"
 
       - name: Install dependencies
-        run: pnpm install
+        run: pnpm install --frozen-lockfile
 
-  build-and-deploy:
-    runs-on: ubuntu-latest
-    needs: setup
-    steps:
-      - name: checkout
-        uses: actions/checkout@v3
+      - name: Lint
+        run: pnpm lint
 
-      - name: restore cache from node_modules
-        uses: actions/cache@v3
-        with:
-          path: node_modules
-          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
+      - name: Type Check
+        run: pnpm type-check
 
-      - name: build
-        run: npm run build
+      - name: Test
+        run: pnpm test:coverage
+
+      - name: Build
+        run: pnpm build
+
+      - name: Upload coverage reports
+        uses: actions/upload-artifact@v4
+        with:
+          name: coverage
+          path: "**/coverage/"
 
       - name: Deploy to GitHub Pages
-        uses: peaceiris/actions-gh-pages@v3
+        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+        uses: peaceiris/actions-gh-pages@v4
         with:
           github_token: ${{ secrets.GITHUB_TOKEN }}
-          publish_dir: ./dist
+          publish_dir: ./apps/cafe/dist
           force_orphan: true

.gitignore

@@ -2,5 +2,35 @@ node_modules/
 package-lock.json
 
 dist/
-.vscode
+
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
+
+node_modules
+dist
+dist-ssr
+*.local
+
+# Turbo (turborepo)
+.turbo/
+**/.turbo/
+
+coverage/
+**/coverage/
+
+# Editor directories and files
+.vscode/*
+!.vscode/extensions.json
+.idea
 .DS_Store
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?

.lintstagedrc

@@ -1,3 +1,7 @@
 {
-  "src/**/*.{ts,js}": ["prettier --write", "eslint --fix --max-warnings 0"]
+  "**/*.{ts,tsx,js,jsx}": [
+    "prettier --write",
+    "eslint --fix --max-warnings 0",
+    "vitest related --run"
+  ]
 }

.npmrc

@@ -0,0 +1,4 @@
+shamefully-hoist=true
+strict-peer-dependencies=false
+auto-install-peers=true
+link-workspace-packages=true

CONTRIBUTING.md

@@ -1,49 +1,147 @@
 # Contributing to Latte
 
-First off, thank you for considering contributing to Latte.
+First off, thanks for taking the time to contribute! 🎉
 
-## Where to Start
+Latte is a complex engineering project with a unique architecture. To maintain high performance and scalability, we follow strict **Data-Oriented Design (DOD)** principles.
 
-1. **Issues**: The [issue list](https://github.com/DrugsZ/Latte/issues) is the best place to start. Issues tagged with `good first issue` are a good starting point.
-2. **Discussions**: Join the discussions on the project's [Discussions](https://github.com/DrugsZ/Latte/discussions) page to connect with other community members.
+Please read this guide carefully. Code that violates these rules will be rejected.
 
-## How to Contribute
+---
 
-### Reporting Bugs
+## Table of Contents
 
-1. **Search**: Check if the issue has already been reported.
-2. **Be clear**: Provide a clear and descriptive title for the issue.
-3. **Include details**: Include as much information as possible, such as the version of Latte, your operating system, and steps to reproduce the issue.
+- [Contributing to Latte](#contributing-to-latte)
+  - [Table of Contents](#table-of-contents)
+  - [🏗 Monorepo Setup](#-monorepo-setup)
+  - [📐 Architectural Constitution](#-architectural-constitution)
+    - [1. The Law of Dependency](#1-the-law-of-dependency)
+    - [2. The Law of Data (`@latte-js/espresso`)](#2-the-law-of-data-latte-jsespresso)
+    - [3. The Law of Rendering (`@latte-js/art`)](#3-the-law-of-rendering-latte-jsart)
+    - [4. The Law of Mutation](#4-the-law-of-mutation)
+  - [🛠 Development Workflow](#-development-workflow)
+    - [Example: Adding a New Feature ("Circle Tool")](#example-adding-a-new-feature-circle-tool)
+  - [🧪 Testing Strategy](#-testing-strategy)
+  - [🐛 Reporting Issues](#-reporting-issues)
+    - [Bug Reports](#bug-reports)
+    - [Feature Requests](#feature-requests)
+  - [🔀 Pull Request Guidelines](#-pull-request-guidelines)
+  - [📦 Project Structure](#-project-structure)
 
-### Suggesting Enhancements
+---
 
-1. **Search**: Check if the enhancement has already been suggested.
-2. **Be clear**: Provide a clear and descriptive title for the enhancement.
-3. **Explain**: Explain why this enhancement would be useful and how it would work.
+## 🏗 Monorepo Setup
 
-### Your First Code Contribution
+We use **pnpm** workspaces and **Turborepo**.
 
-1. **Fork** the repository to your own GitHub account.
-2. **Make your changes** and **add tests** if necessary.
-3. **Commit** your changes
-4. **Push** your branch to GitHub
-5. **Open a pull request** against the `main` branch.
+```bash
+# 1. Install dependencies
+pnpm install
 
-### Pull Request Guidelines
+# 2. Build all packages
+pnpm build
 
-1. **Update** the documentation if necessary.
-2. **Follow** the coding style of the project.
-3. **Write tests** for your changes.
-4. **Keep your changes** focused on a single feature or fix.
-5. **Rebase** your branch on the latest `main` before submitting a pull request.
+# 3. Start the editor (Dev mode)
+pnpm dev
+```
 
-## License
+---
 
-By contributing, you agree that your contributions will be licensed under the [Apache-2.0 license](https://github.com/DrugsZ/Latte?tab=Apache-2.0-1-ov-file) used within this project.
+## 📐 Architectural Constitution
 
-## Additional Notes
+Latte is **NOT** a standard React application. We enforce the following laws to ensure performance.
 
-- **Sign your work**: The sign-off is required for all contributions. It certifies that you wrote the patch or have the right to contribute it to the project.
-- **Ask for help**: If you’re stuck, create a draft pull request or ask for help on the [Discussions](https://github.com/DrugsZ/Latte/discussions) page.
+### 1. The Law of Dependency
 
-Thank you for your interest in contributing to Latte!
+Dependencies must flow **downwards**. Circular dependencies are strictly forbidden.
+
+- ✅ `milk` -> `counter` -> `syrup` -> `barista` -> `espresso` -> `bean`
+- ❌ `espresso` cannot import `milk`.
+- ❌ `bean` cannot import anything.
+
+### 2. The Law of Data (`@latte-js/espresso`)
+
+- **No Objects**: Do not store state as JS objects in the kernel (e.g., `{x: 10}`). Use `TypedArray` indices.
+- **No Classes in Buffer**: Data in `SharedArrayBuffer` must be flat numbers.
+- **Use Cursors**: Business logic must use `NodeCursor` to read/write data. Direct buffer access is restricted to internal `Ops`.
+
+### 3. The Law of Rendering (`@latte-js/art`)
+
+- **Read-Only**: The renderer should **NEVER** modify business data.
+- **No React**: Do not use React components inside the renderer logic.
+- **Performance**: Always use WorldMatrix for flat rendering. Do not traverse the tree recursively if possible.
+
+### 4. The Law of Mutation
+
+- **Single Source of Truth**: All writes must go through `NodeCursor` to trigger:
+  1.  Dirty Flags (for Renderer)
+  2.  Observers (for History/Sync)
+- **Transactions**: Complex operations must be wrapped in `history.startTransaction`.
+
+---
+
+## 🛠 Development Workflow
+
+### Example: Adding a New Feature ("Circle Tool")
+
+1.  **Define Type (`bean`)**: Add `ELLIPSE` to `NodeType` enum.
+2.  **Update Kernel (`espresso`)**: Ensure `Allocator` and `Serializer` handle the new type.
+3.  **Implement Rendering (`art`)**: Add drawing logic (`ctx.ellipse`) to the `RendererRegistry`.
+4.  **Implement Logic (`counter`)**:
+    - Create `CircleTool` extending `BaseTool`.
+    - Register command: `latte.tool.circle`.
+    - Handle drag events to update kernel data via RPC.
+5.  **Update UI (`milk`)**: Add an icon to the toolbar component.
+
+---
+
+## 🧪 Testing Strategy
+
+- **Unit Tests (`vitest`)**:
+  - **Required** for `espresso` (memory integrity) and `barista` (math logic).
+  - Run: `pnpm test`
+- **E2E Tests (`playwright`)**:
+  - **Required** for `art` (Visual Regression).
+  - Run: `pnpm e2e`
+
+---
+
+## 🐛 Reporting Issues
+
+### Bug Reports
+
+1.  **Search**: Check if the issue has already been reported.
+2.  **Be clear**: Provide a clear and descriptive title for the issue.
+3.  **Include details**: Include as much information as possible, such as the version of Latte, your operating system, and steps to reproduce the issue.
+
+### Feature Requests
+
+1.  **Search**: Check if the enhancement has already been suggested.
+2.  **Explain**: Explain why this enhancement would be useful and how it would work.
+
+---
+
+## 🔀 Pull Request Guidelines
+
+1.  **Fork** the repository to your own GitHub account.
+2.  **Create a branch** for your feature or fix.
+3.  **Commit** your changes following the **Conventional Commits** specification (e.g., `feat: add circle tool`, `fix: memory leak in loader`).
+4.  **Write tests** for your changes.
+5.  **Rebase** your branch on the latest `main` before submitting.
+6.  **Sign your work**: The sign-off is required. It certifies that you wrote the patch or have the right to contribute it.
+
+---
+
+## 📦 Project Structure
+
+```text
+packages/
+├── bean/         # Types (The Dictionary)
+├── espresso/     # Data (The Database)
+├── barista/      # Engine (The Worker)
+├── art/          # Render (The Painter)
+├── syrup/        # Infra (The OS)
+├── counter/      # Logic (The App)
+└── milk/         # UI (The Skin)
+```
+
+**Need Help?** If you’re stuck, create a draft pull request or ask for help on the [Discussions](https://github.com/DrugsZ/Latte/discussions) page.