f400391a894e58378f58e53df55c96c307810b2f
The engines are moving into their own project. Session mixed the two jobs: deciding what a program means (the hub's cascade, parsing every language, diagnostics, the run, the proof, the fuzzer) and app concerns (the area, saving to localStorage, versions, compile history, the best-practices helper, change events). Tests of meaning could only reach it through the app's state. src/core/workspace.ts is the first job alone, with no DOM, storage or areas: Workspace reads a WorkState (sources, sync, lang, call, input, setup, machine), and edit() returns whether anything changed. Session now extends it, keeps every app concern, and overrides only what the app changes: the Bridge's Mojo is derived (derivesMojo), and the Mojo diagnostics come from the compiler's answer and the helper when there is one. No behavior changes; every test passes unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FgvbRdoEheAHqsRmr2WuKZ
Languages
TypeScript
47.7%
JavaScript
47.1%
Python
4.9%
Mojo
0.3%