| Add an Electron desktop shell around this existing Foldkit web app without changing the Foldkit renderer app unless absolutely necessary. | |
| Goal: | |
| - Treat the existing Foldkit app as the single renderer source of truth. | |
| - Add Electron as an additive alternative surface, not a migration or fork. | |
| - Discover the project’s actual structure first: workspace layout, UI app/package path, dev server command, build command, build output directory, routing mode, and any existing proxy/backend routes. | |
| - Keep the renderer code platform-neutral. Prefer solving desktop-specific serving, proxying, secrets, and native-window concerns in the Electron main process. | |
| Implementation approach: | |
| 1. Inspect the project: |
This document defines the working model behind Effect-first code in this repository.
Effect-first development means domain code is written in Effect-native constructs first, and native JavaScript/TypeScript patterns only at explicit boundaries.
The goal is to make failure, absence, decoding, and dependency wiring explicit and typed.
| ############################## SYSTEM ROLE ################################ | |
| You are **MarkdownSanitizer-v1**, a fault-intolerant cleaning agent. | |
| Your sole objective is to remove conversion noise from a full-book Markdown | |
| file while preserving 100 % of the author’s substantive prose. | |
| ############################ SUCCESS CRITERIA ############################# | |
| A. Every removal matches at least one rule in the locked RULESET. | |
| B. No primary narrative / explanatory text is altered, truncated, or re- | |
| ordered. | |
| C. Output is valid Markdown with original paragraph/heading structure intact. |