Initial commit

2026-08-02 18:10:18 +05:30 · 2025-09-01 19:16:06 +05:30
417 changed files with 670 additions and 84675 deletions
@@ -1,31 +0,0 @@
 name: CI
 on:
  push:
    branches: [master, react-electron]
  pull_request:
    branches: [master, react-electron]
 jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test
      - name: Run renderer tests
        run: npm run test:renderer
      - name: Run linter
        run: npm run lint
@@ -1,176 +0,0 @@
 name: Release
 on:
  push:
    tags: ['v*']
 permissions:
  contents: write
 jobs:
  build-linux:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - name: Install dependencies
        run: npm ci
      - name: Download external tools (pandoc)
        run: node scripts/download-tools.js
      - name: Run tests
        run: npm test
      - name: Build Linux packages
        run: npm run build:linux-ci -- --publish=always
      - name: Upload Linux artifacts
        uses: actions/upload-artifact@v4
        with:
          name: linux-artifacts
          path: |
            dist/*.deb
            dist/*.AppImage
            dist/*.snap
            dist/*.rpm
          retention-days: 5
  build-windows:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - name: Install dependencies
        run: npm ci
      - name: Download external tools (pandoc)
        run: node scripts/download-tools.js
      - name: Run tests
        run: npm test
      - name: Decode certificate (if available)
        if: ${{ env.CSC_LINK_BASE64 != '' }}
        shell: pwsh
        env:
          CSC_LINK_BASE64: ${{ secrets.CSC_LINK_BASE64 }}
        run: |
          $bytes = [Convert]::FromBase64String("$env:CSC_LINK_BASE64")
          [IO.File]::WriteAllBytes("${{ github.workspace }}\code-signing-cert.pfx", $bytes)
          echo "CERT_AVAILABLE=true" >> $env:GITHUB_ENV
      - name: Build Windows packages (signed)
        if: ${{ env.CERT_AVAILABLE == 'true' }}
        env:
          CSC_LINK: code-signing-cert.pfx
          CSC_KEY_PASSWORD: ${{ secrets.CSC_KEY_PASSWORD }}
        run: npm run build:win-signed -- --publish=always
      - name: Build Windows packages (unsigned)
        if: ${{ env.CERT_AVAILABLE != 'true' }}
        env:
          CSC_IDENTITY_AUTO_DISCOVERY: 'false'
        run: npm run build:win-unsigned -- --publish=always
      - name: Upload Windows artifacts
        uses: actions/upload-artifact@v4
        with:
          name: windows-artifacts
          path: |
            dist/*.exe
            dist/*.zip
          retention-days: 5
  build-macos:
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - name: Install dependencies
        run: npm ci
      - name: Download external tools (pandoc)
        run: node scripts/download-tools.js
      - name: Run tests
        run: npm test
      - name: Build macOS packages (unsigned)
        env:
          CSC_IDENTITY_AUTO_DISCOVERY: 'false'
        run: npm run build:mac -- --publish=always
      - name: Upload macOS artifacts
        uses: actions/upload-artifact@v4
        with:
          name: macos-artifacts
          path: |
            dist/*.dmg
            dist/*.zip
          retention-days: 5
  release:
    needs: [build-linux, build-windows, build-macos]
    if: always()
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Download Linux artifacts
        uses: actions/download-artifact@v4
        continue-on-error: true
        with:
          name: linux-artifacts
          path: dist
      - name: Download Windows artifacts
        uses: actions/download-artifact@v4
        continue-on-error: true
        with:
          name: windows-artifacts
          path: dist
      - name: Download macOS artifacts
        uses: actions/download-artifact@v4
        continue-on-error: true
        with:
          name: macos-artifacts
          path: dist
      - name: Create GitHub Release
        uses: softprops/action-gh-release@v2
        with:
          generate_release_notes: true
          files: dist/*
      - name: Mirror artifacts to ConcreteInfo update feed
        if: env.CONCRETEINFO_DEPLOY_HOOK != ''
        env:
          CONCRETEINFO_DEPLOY_HOOK: ${{ secrets.CONCRETEINFO_DEPLOY_HOOK }}
        run: |
          curl -fsSL -X POST \
            -H "Authorization: Bearer ${{ secrets.CONCRETEINFO_DEPLOY_HOOK }}" \
            -F "version=${GITHUB_REF_NAME#v}" \
            -F "artifacts=@dist/latest-mac.yml" \
            -F "artifacts=@dist/latest-linux.yml" \
            -F "artifacts=@dist/latest-windows.yml" \
            https://updates.concreteinfo.co.in/api/v1/ingest
@@ -1,48 +0,0 @@
 node_modules/
 dist/
 *.log
 .DS_Store
 Thumbs.db
 .env
 .env.local
 *.swp
 *.swo
 *~
 .vscode/*
 !.vscode/launch.json
 .idea/
 *.iml
 out/
 .cache/
 .npm/
 .electron/
 # package-lock.json is intentionally tracked for reproducible CI builds
 # Downloaded tool binaries (fetched at build time via scripts/download-tools.js)
 bin/
 # Code signing certificates — never commit private keys
 *.pfx
 *.p12
 # Screenshots and temp files
 *.png.bak
 Screen.png
 dark.png
 light.png
 pdf.png
 uvmodal.png
 nul
 *.tmp
 # Development screenshots
 pdf\ modal.png
 # Claude/AI development files
 .claude/
 CLAUDE.md
 agents.md
 coverage/
 # Superpowers brainstorm artifacts
 .superpowers/
@@ -1,11 +0,0 @@
 {
  "semi": true,
  "singleQuote": true,
  "tabWidth": 2,
  "useTabs": false,
  "trailingComma": "es5",
  "bracketSpacing": true,
  "arrowParens": "always",
  "printWidth": 100,
  "endOfLine": "auto"
 }
@@ -1,469 +0,0 @@
 # Security Assessment Report: MarkdownConverter v4.0.0
 **Assessment Date:** 2026-03-15
 **Application:** MarkdownConverter - Electron-based Markdown editor and document converter
 **Target Version:** 4.0.0
 **Assessor:** Security Audit Agent
 ---
 ## Executive Summary
 This assessment identified **10 security findings** ranging from **Critical to Low severity**. The most significant concerns involve insecure Electron security configuration that could allow XSS attacks to escalate to full system access, arbitrary code execution via the REPL feature, and missing input validation on file operations.
 | Severity | Count |
 |----------|-------|
 | Critical | 2 |
 | High | 3 |
 | Medium | 3 |
 | Low | 2 |
 ---
 ## Vulnerability Findings
 ### CVE-MC-001: Insecure Electron Security Configuration (Critical)
 **CVSS 3.1 Score: 9.6 (Critical)**
 **CWE-265: CWE-1021: Improper Restriction of Renderers**
 **Location:** `src/main.js` (lines 328-332)
 ```javascript
 webPreferences: {
  nodeIntegration: true,
  contextIsolation: false,
  spellcheck: true
 },
 ```
 **Description:**
 The main application window has `nodeIntegration: true` and `contextIsolation: false`, which is the most insecure Electron configuration. This allows the renderer process direct access to Node.js APIs, meaning any XSS vulnerability in the markdown rendering or external content could lead to full system compromise.
 **Exploitability:**
 - An attacker who can inject malicious JavaScript (via markdown files, XSS in preview, or compromised dependencies) gains immediate access to:
  - Full file system read/write via `fs` module
  - Command execution via `child_process`
  - Network access via `net` module
  - All system resources
 **Attack Scenario:**
 1. User opens a malicious markdown file containing embedded JavaScript
 2. The JavaScript executes in the renderer with full Node.js access
 3. Attacker can read sensitive files, execute commands, exfiltrate data
 **Remediation:**
 ```javascript
 webPreferences: {
  nodeIntegration: false,
  contextIsolation: true,
  sandbox: true,
  preload: path.join(__dirname, 'preload.js')
 }
 ```
 **Note:** The preload.js file already implements a secure IPC bridge but it is not being utilized for the main window.
 ---
 ### CVE-MC-002: Arbitrary Code Execution via REPL Feature (Critical)
 **CVSS 3.1 Score: 9.3 (Critical)**
 **CWE-94: Improper Control of Generation of Code ('Code Injection')**
 **Location:** `src/main.js` (lines 4369-4396)
 **Description:**
 The `execute-code` IPC handler allows execution of arbitrary Python and Bash scripts through the REPL panel. While JavaScript execution appears to have been removed or limited, Python and Bash commands are executed via `execFile` with user-supplied code.
 **Vulnerable Code Pattern:**
 ```javascript
 ipcMain.handle('execute-code', async (event, { code, language }) => {
  // ...
  if (language === 'python' || language === 'py') {
    cmd = 'python';
    args = ['-c', code];
  }
  // ...
  execFile(cmd, args, { timeout }, (err, stdout, stderr) => {
    // ...
  });
 });
 ```
 **Exploitability:**
 - Users can be tricked into running malicious code blocks
 - Markdown files can contain executable code blocks with "Run" buttons
 - No sandboxing or permission restrictions on executed code
 **Attack Scenario:**
 1. Attacker creates markdown file with malicious Python code block
 2. User clicks "Run" button in preview
 3. Python code executes with user's full permissions
 4. Attacker gains code execution on victim's machine
 **Remediation:**
 - Remove arbitrary code execution feature entirely, OR
 - Implement strict sandboxing (Docker, VM, or restricted Python environment)
 - Add user confirmation dialogs with clear warnings
 - Execute in isolated environment with no filesystem/network access
 - Implement allowlist of safe operations
 ---
 ### CVE-MC-003: Potential XSS in Markdown Rendering (High)
 **CVSS 3.1 Score: 8.0 (High)**
 **CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')**
 **Location:** `src/renderer.js` (lines 387-419)
 **Description:**
 While DOMPurify is used to sanitize HTML, several extensions to marked.js may bypass sanitization:
 1. **Custom Admonition Extension (lines 51-77):**
 ```javascript
 marked.use({
    extensions: [{
        name: 'admonition',
        // ...
        renderer(token) {
            const inner = this.parser.parse(token.text);
            return `<div class="admonition admonition-${token.admonitionType}">
                <div class="admonition-title">${icon} ${token.admonitionType...}</div>
                <div class="admonition-content">${inner}</div>
            </div>`;
        }
    }]
 });
 ```
 2. **innerHTML Assignments (line 419):**
 ```javascript
 preview.innerHTML = sanitizedHtml;
 ```
 **Exploitability:**
 - Combined with CVE-MC-001, XSS leads to full system compromise
 - Custom markdown extensions may not be properly sanitized
 - Admonition type is directly interpolated into HTML without escaping
 **Remediation:**
 - Ensure all custom markdown extensions escape user input
 - Add Content Security Policy that blocks inline scripts
 - Use `textContent` instead of `innerHTML` where possible
 - Audit all custom marked.js extensions for XSS vectors
 ---
 ### CVE-MC-004: Missing Path Traversal Protection (High)
 **CVSS 3.1 Score: 7.8 (High)**
 **CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')**
 **Location:** `src/main.js` (lines 4241-4281)
 **Description:**
 The `list-directory` and `open-file-path` IPC handlers accept arbitrary file paths without validation:
 ```javascript
 ipcMain.handle('list-directory', async (event, dirPath) => {
  try {
    if (!dirPath) { /* dialog */ }
    // No path validation - accepts any path
    const entries = fs.readdirSync(dirPath, { withFileTypes: true });
    // ...
  }
 });
 ipcMain.on('open-file-path', (event, filePath) => {
  // No path validation
  if (!fs.existsSync(filePath)) return;
  const content = fs.readFileSync(filePath, 'utf-8');
  mainWindow.webContents.send('file-opened', { path: filePath, content });
 });
 ```
 **Exploitability:**
 - Malicious renderer code can read any file on the system
 - No restriction to a sandbox directory
 - Combined with XSS, attacker can exfiltrate sensitive files
 **Remediation:**
 ```javascript
 const ALLOWED_DIRECTORIES = [app.getPath('documents'), app.getPath('desktop')];
 function isPathAllowed(filePath) {
  const resolved = path.resolve(filePath);
  return ALLOWED_DIRECTORIES.some(dir => resolved.startsWith(dir));
 }
 ```
 ---
 ### CVE-MC-005: Weak Content Security Policy (High)
 **CVSS 3.1 Score: 7.5 (High)**
 **CWE-1021: Improper Restriction of Renderers**
 **Location:** `src/index.html` (line 5)
 ```html
 <meta http-equiv="Content-Security-Policy" content="default-src 'self';
  script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net;
  style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com;
  img-src 'self' data: blob: file:;
  font-src 'self' data:;
  connect-src 'self' https://www.plantuml.com;">
 ```
 **Description:**
 The CSP contains several security weaknesses:
 1. **`'unsafe-inline'` in script-src** - Allows inline script injection
 2. **`'unsafe-eval'` in script-src** - Allows `eval()` and similar functions
 3. **`https://cdn.jsdelivr.net`** - Allows scripts from external CDN (supply chain risk)
 4. **`file:` in img-src** - Allows loading local files as images (potential information disclosure)
 **Exploitability:**
 - XSS attacks can execute arbitrary scripts
 - External CDN compromise could inject malicious code
 - `eval()` enables dynamic code execution
 **Remediation:**
 - Remove `'unsafe-inline'` and `'unsafe-eval'`
 - Use nonces or hashes for inline scripts
 - Remove external CDNs or use Subresource Integrity (SRI)
 - Remove `file:` from img-src
 ---
 ### CVE-MC-006: Insecure Window Configuration for PDF Export (Medium)
 **CVSS 3.1 Score: 6.5 (Medium)**
 **CWE-1021: Improper Restriction of Renderers**
 **Location:** `src/main.js` (lines 2579-2585)
 ```javascript
 const pdfWindow = new BrowserWindow({
  show: false,
  webPreferences: {
    nodeIntegration: true,
    contextIsolation: false
  }
 });
 ```
 **Description:**
 Hidden windows created for PDF export also have insecure configurations, allowing potential privilege escalation.
 **Remediation:**
 ```javascript
 webPreferences: {
  nodeIntegration: false,
  contextIsolation: true,
  sandbox: true
 }
 ```
 ---
 ### CVE-MC-007: PlantUML Server Data Exfiltration (Medium)
 **CVSS 3.1 Score: 5.3 (Medium)**
 **CWE-359: Exposure of Private Information**
 **Location:** `src/renderer.js` (lines 470-487)
 ```javascript
 const plantumlBlocks = preview.querySelectorAll('pre code.language-plantuml');
 plantumlBlocks.forEach((block) => {
    const code = block.textContent;
    // ...
    const encoded = plantumlEncode(code);
    const img = document.createElement('img');
    img.src = `https://www.plantuml.com/plantuml/svg/${encoded}`;
    // ...
 });
 ```
 **Description:**
 PlantUML diagram content is sent to an external server (plantuml.com) for rendering. This could leak sensitive information contained in diagrams.
 **Exploitability:**
 - Diagrams containing proprietary information, system architecture, or internal processes are sent to third-party servers
 - No user consent or notification before external data transmission
 **Remediation:**
 - Use local PlantUML rendering with Java
 - Add user warning before sending data to external service
 - Implement opt-in for external rendering
 ---
 ### CVE-MC-008: Inconsistent Security Settings Across Windows (Medium)
 **CVSS 3.1 Score: 5.5 (Medium)**
 **CWE-1021: Improper Restriction of Renderers**
 **Description:**
 Security settings are inconsistent across different windows:
 | Window | nodeIntegration | contextIsolation | Security |
 |--------|-----------------|------------------|----------|
 | Main Window | true | false | Insecure |
 | About Dialog | false | true | Secure |
 | Dependencies Dialog | false | true | Secure |
 | ASCII Generator | false | true | Secure |
 | Table Generator | false | true | Secure |
 | PDF Export Window | true | false | Insecure |
 | Hidden Conversion Window | true | false | Insecure |
 **Remediation:**
 Apply secure configuration (`nodeIntegration: false`, `contextIsolation: true`) consistently across all windows.
 ---
 ### CVE-MC-009: Command Execution via External Tools (Low)
 **CVSS 3.1 Score: 4.4 (Low)**
 **CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')**
 **Location:** `src/main.js` (lines 1915-1972)
 **Description:**
 While the application uses `execFile` instead of `exec` (good practice), external tools (Pandoc, LibreOffice, FFmpeg, ImageMagick) are invoked with file paths that could potentially be manipulated.
 **Positive Finding:**
 The code correctly uses `execFile` with argument arrays instead of shell commands, mitigating most command injection vectors.
 **Remaining Risk:**
 - File paths are not validated against malicious names
 - Special characters in filenames could cause issues with external tools
 **Remediation:**
 - Validate file paths before passing to external tools
 - Sanitize filenames of special characters
 ---
 ### CVE-MC-010: Missing Dependency Version Pinning (Low)
 **CVSS 3.1 Score: 3.5 (Low)**
 **CWE-1035: Using Components with Known Vulnerabilities**
 **Location:** `package.json`
 **Description:**
 Dependencies use `^` version ranges which could allow automatic updates to versions with vulnerabilities:
 ```json
 "dependencies": {
  "marked": "^17.0.3",
  "dompurify": "^3.3.1",
  "mermaid": "^11.12.3",
  // ...
 }
 ```
 **Remediation:**
 - Pin exact versions in production
 - Use lockfile (package-lock.json)
 - Implement dependency scanning in CI/CD pipeline
 ---
 ## Attack Surface Map
 ```
 ┌─────────────────────────────────────────────────────────────────┐
 │                    EXTERNAL ATTACK SURFACE                       │
 ├─────────────────────────────────────────────────────────────────┤
 │  Markdown Files (.md)     ─────► XSS via Preview Rendering      │
 │  Code Blocks              ─────► Arbitrary Code Execution       │
 │  PlantUML Diagrams        ─────► Data Exfiltration              │
 │  External CDNs            ─────► Supply Chain Attacks           │
 └─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
 ┌─────────────────────────────────────────────────────────────────┐
 │                    RENDERER PROCESS (Insecure)                   │
 ├─────────────────────────────────────────────────────────────────┤
 │  nodeIntegration: true   ─────► Direct Node.js Access           │
 │  contextIsolation: false ─────► Prototype Pollution Risk        │
 │  DOMPurify Sanitization  ─────► May be bypassed via extensions  │
 │  Custom Marked Extensions ────► XSS Vectors                     │
 └─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
 ┌─────────────────────────────────────────────────────────────────┐
 │                    IPC BRIDGE (Preload.js)                       │
 ├─────────────────────────────────────────────────────────────────┤
 │  Channel Whitelisting    ─────► Good Practice                   │
 │  Not Used for Main Window ────► Security Bypassed               │
 └─────────────────────────────────────────────────────────────────┘
                              │
                              ▼
 ┌─────────────────────────────────────────────────────────────────┐
 │                    MAIN PROCESS (Full Privileges)                │
 ├─────────────────────────────────────────────────────────────────┤
 │  File Operations         ─────► No Path Validation              │
 │  Code Execution          ─────► Python/Bash via REPL            │
 │  External Tools          ─────► Pandoc, FFmpeg, LibreOffice     │
 │  PDF Operations          ─────► Merge, Encrypt, Decrypt         │
 └─────────────────────────────────────────────────────────────────┘
 ```
 ---
 ## Positive Security Findings
 1. **Preload.js Implementation:** A secure IPC bridge with channel whitelisting is implemented
 2. **DOMPurify Usage:** HTML sanitization is applied to markdown output
 3. **execFile Usage:** External commands use `execFile` instead of `exec`
 4. **File Size Limits:** 50MB maximum file size is enforced
 5. **Rate Limiting:** Conversion operations have rate limiting (2 second minimum interval)
 6. **Error Message Sanitization:** Absolute paths are stripped from error messages
 ---
 ## Prioritized Remediation Roadmap
 ### Phase 1 - Critical (Immediate)
 1. Set `nodeIntegration: false` and `contextIsolation: true` for main window
 2. Remove or sandbox the code execution (REPL) feature
 3. Implement proper preload.js usage for all windows
 ### Phase 2 - High Priority (1-2 Weeks)
 4. Add path traversal protection to file operations
 5. Strengthen Content Security Policy
 6. Audit and fix custom markdown extensions for XSS
 ### Phase 3 - Medium Priority (1 Month)
 7. Implement consistent security settings across all windows
 8. Add local PlantUML rendering option
 9. Implement dependency scanning in CI/CD
 ### Phase 4 - Low Priority (Ongoing)
 10. Pin dependency versions
 11. Add security headers to all generated HTML
 12. Implement security logging and monitoring
 ---
 ## Compliance Considerations
 - **OWASP Top 10 2021:** A03:2021 - Injection, A05:2021 - Security Misconfiguration
 - **OWASP ASVS:** V12 - File Handling, V13 - API Security
 - **NIST CSF:** PR.AC - Access Control, PR.DS - Data Security
 ---
 ## Conclusion
 The MarkdownConverter application has significant security vulnerabilities that could allow an attacker to execute arbitrary code, access sensitive files, and compromise the user's system. The most critical issue is the insecure Electron configuration combined with XSS attack vectors in the markdown rendering pipeline.
 **Overall Security Rating: HIGH RISK**
 The positive finding is that much of the security infrastructure (preload.js, DOMPurify) is already in place but not properly utilized. With focused remediation effort, the application can achieve a much stronger security posture.
@@ -1,215 +0,0 @@
 # STRIDE Threat Model - MarkdownConverter v4.0.0
 **Analysis Date:** 2026-03-15
 **Methodology:** STRIDE + MITRE ATT&CK
 **Overall Risk Score:** 7.8 (HIGH)
 ---
 ## Executive Summary
 The analysis identified **10 vulnerabilities** with a combined risk score of **7.8 (HIGH)**. The most critical issues enable complete system compromise through XSS-to-RCE attack chains.
 ---
 ## Critical Findings
 | Priority | CVE | Vulnerability | CVSS | Impact |
 |----------|-----|---------------|------|--------|
 | P0 | CVE-MC-001 | Insecure Electron Config (`nodeIntegration: true`, `contextIsolation: false`) | 9.6 | Complete system compromise |
 | P0 | CVE-MC-002 | Arbitrary code execution via REPL feature | 9.3 | Remote code execution |
 | P1 | CVE-MC-003 | XSS in markdown rendering | 8.0 | Session hijacking, RCE chain |
 | P1 | CVE-MC-004 | Path traversal vulnerability | 7.8 | Arbitrary file write |
 | P1 | CVE-MC-005 | Weak Content Security Policy | 7.5 | XSS enablement |
 | P2 | CVE-MC-006 | Insecure window config for PDF export | 6.5 | Privilege escalation |
 | P2 | CVE-MC-007 | PlantUML server data exfiltration | 5.3 | Information disclosure |
 | P2 | CVE-MC-008 | Inconsistent security settings | 5.5 | Configuration weakness |
 | P3 | CVE-MC-009 | Command execution via external tools | 4.4 | Command injection risk |
 | P3 | CVE-MC-010 | Missing dependency version pinning | 3.5 | Supply chain risk |
 ---
 ## Key Attack Vectors
 ### 1. XSS to RCE Chain (Critical)
 ```
 Malicious Markdown File
        │
        ▼
 XSS in Preview (CVE-MC-003)
        │
        ▼
 nodeIntegration: true (CVE-MC-001)
        │
        ▼
 Full Node.js Access
        │
        ▼
 Complete System Compromise
 ```
 ### 2. REPL Code Execution (Critical)
 ```
 Code Block in Markdown
        │
        ▼
 User clicks "Run"
        │
        ▼
 REPL executes Python/Bash (CVE-MC-002)
        │
        ▼
 Arbitrary Code Execution
 ```
 ### 3. Data Exfiltration (Medium)
 ```
 PlantUML Diagram Content
        │
        ▼
 Sent to www.plantuml.com (CVE-MC-007)
        │
        ▼
 Sensitive Architecture Leaked
 ```
 ---
 ## STRIDE Analysis
 ### S - Spoofing
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | S1 | Attacker spoofs markdown file origin | Medium | High | High |
 | S2 | Malicious code pretends to be safe | High | Critical | Critical |
 ### T - Tampering
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | T1 | XSS modifies local files | High | Critical | Critical |
 | T2 | Conversion output tampered | Medium | Medium | Medium |
 ### R - Repudiation
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | R1 | No audit trail for operations | Low | Low | Low |
 ### I - Information Disclosure
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | I1 | XSS exposes file system | High | Critical | Critical |
 | I2 | PlantUML content leaked | Medium | Medium | Medium |
 | I3 | Error messages reveal paths | Low | Low | Low |
 ### D - Denial of Service
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | D1 | Malicious code crashes app | Medium | Medium | Medium |
 | D2 | Large file exhausts resources | Low | Low | Low |
 ### E - Elevation of Privilege
 | ID | Threat | Likelihood | Impact | Risk |
 |----|--------|------------|--------|------|
 | E1 | XSS → nodeIntegration → System | High | Critical | Critical |
 | E2 | REPL code execution | High | Critical | Critical |
 ---
 ## MITRE ATT&CK Mapping
 | Technique | ID | Applicability |
 |-----------|-----|---------------|
 | User Execution | T1204.002 | Malicious markdown file |
 | Command and Scripting Interpreter | T1059.007 | JavaScript via nodeIntegration |
 | Command and Scripting Interpreter | T1059.006 | Python via REPL |
 | Command and Scripting Interpreter | T1059.004 | Bash via REPL |
 | Exploit Public-Facing Application | T1190 | XSS in preview |
 | Data Exfiltration Over Web Service | T1043 | PlantUML server |
 | File and Directory Discovery | T1083 | Path traversal |
 ---
 ## Trust Boundaries
 ```
 ┌─────────────────────────────────────────────────────────────────────┐
 │                         TRUST BOUNDARY MAP                          │
 ├─────────────────────────────────────────────────────────────────────┤
 │                                                                     │
 │   ┌─────────────┐         ┌─────────────────────────────────────┐  │
 │   │   USER      │ ──────► │        APPLICATION                  │  │
 │   │ (Untrusted) │         │  ┌───────────┐  ┌───────────────┐  │  │
 │   └─────────────┘         │  │ Renderer  │  │ Main Process  │  │  │
 │                           │  │ (Sandbox) │  │ (Privileged)  │  │  │
 │                           │  └─────┬─────┘  └───────┬───────┘  │  │
 │                           │        │  IPC           │           │  │
 │                           │        ▼                ▼           │  │
 │                           │  ┌─────────────────────────────┐   │  │
 │                           │  │      File System            │   │  │
 │                           │  └─────────────────────────────┘   │  │
 │                           └─────────────────────────────────────┘  │
 │                                           │                        │
 │                                           ▼                        │
 │   ┌─────────────────────────────────────────────────────────────┐ │
 │   │                    EXTERNAL SERVICES                         │ │
 │   │  • PlantUML Server (www.plantuml.com)                       │ │
 │   │  • CDN (cdn.jsdelivr.net, cdnjs.cloudflare.com) [REMOVED]   │ │
 │   │  • External Tools (Pandoc, FFmpeg, LibreOffice)             │ │
 │   └─────────────────────────────────────────────────────────────┘ │
 │                                                                     │
 └─────────────────────────────────────────────────────────────────────┘
 ```
 ---
 ## Business Impact Analysis
 ### Successful Attack Consequences
 | Impact Category | Estimate |
 |-----------------|----------|
 | Data breach costs | $500,000 - $5,000,000+ |
 | Regulatory fines (GDPR) | Up to 4% annual revenue |
 | Reputation damage | Incalculable |
 | Business disruption | Hours to days |
 ### Affected Assets
 - User documents and files
 - System credentials
 - Proprietary information in diagrams
 - Application integrity
 ---
 ## Remediation Priority
 ### P0 - Immediate (24-48 hours)
 1. **CVE-MC-001**: Set `nodeIntegration: false`, `contextIsolation: true`
 2. **CVE-MC-002**: Remove or sandbox REPL code execution
 ### P1 - Short-term (1-2 weeks)
 3. **CVE-MC-003**: Audit markdown extensions for XSS
 4. **CVE-MC-004**: Add path validation (✅ COMPLETED)
 5. **CVE-MC-005**: Strengthen CSP (✅ COMPLETED)
 ### P2 - Medium-term (1 month)
 6. **CVE-MC-006**: Consistent window security settings
 7. **CVE-MC-007**: Add local PlantUML option or warning
 8. **CVE-MC-008**: Audit all BrowserWindow configurations
 ### P3 - Long-term
 9. **CVE-MC-009**: Validate filenames for external tools
 10. **CVE-MC-010**: Pin dependency versions, add scanning
 ---
 ## Conclusion
 The MarkdownConverter application has a **HIGH RISK** threat profile due to the combination of:
 - Untrusted content rendering (markdown preview)
 - Direct system access (nodeIntegration)
 - Code execution capability (REPL)
 **Immediate action required on P0 items to reduce attack surface.**
 The fixes applied in this session (CSP, path traversal, UI accessibility) have reduced the risk profile, but the critical nodeIntegration issue requires significant refactoring.
@@ -1,27 +0,0 @@
 {
  "target": "MarkdownConverter Electron Application",
  "status": "in_progress",
  "depth": "comprehensive",
  "compliance_frameworks": ["owasp"],
  "current_step": 3,
  "current_phase": 1,
  "completed_steps": ["vulnerability-scan", "threat-modeling"],
  "files_created": ["01-vulnerability-scan.md", "02-threat-model.md"],
  "started_at": "2026-03-15T00:09:00.000Z",
  "last_updated": "2026-03-15T00:25:00.000Z",
  "findings_summary": {
    "critical": 2,
    "high": 3,
    "medium": 3,
    "low": 2,
    "total": 10
  },
  "fixes_applied": {
    "csp_external_cdns_removed": true,
    "path_traversal_protection_added": true,
    "aria_labels_added": true,
    "focus_visible_styles_added": true,
    "tab_close_button_resized": true,
    "duplicate_font_size_fixed": true
  }
 }
@@ -1,522 +0,0 @@
 # Comprehensive UI Design Review - MarkdownConverter Electron Application
 ## Executive Summary
 This review covers the UI design of the MarkdownConverter Electron application, analyzing visual design, usability, code quality, and performance across all UI files. The application has a solid foundation but has several areas requiring attention.
 ---
 ## 1. Visual Design Review
 ### 1.1 Spacing & Layout Consistency
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Inconsistent padding values across files | Multiple CSS files | Standardize to 4px/8px base scale |
 | **Major** | Multiple reset declarations | `styles.css:1-5`, `styles-modern.css:42-47` | Consolidate resets into single file |
 | **Minor** | Tab padding varies between themes | `styles.css:36`, `styles-modern.css:101` | Use CSS variables for consistent padding |
 | **Minor** | Container padding inconsistency | `styles.css:17-21`, `styles-modern.css:63-69` | Define single container style |
 **Code Example - Duplicate Reset:**
 ```css
 /* styles.css:1-5 */
 * {
    margin: 0;
    padding: 0;
    box-sizing: border-box;
 }
 /* styles-modern.css:42-47 - DUPLICATE */
 * {
  margin: 0;
  padding: 0;
  box-sizing: border-box;
 }
 ```
 **Fix Recommendation:**
 ```css
 /* Create a single base.css or remove from styles-modern.css */
 /* Use CSS variables for spacing scale */
 :root {
  --space-1: 4px;
  --space-2: 8px;
  --space-3: 12px;
  --space-4: 16px;
  --space-5: 24px;
  --space-6: 32px;
 }
 ```
 ### 1.2 Typography Consistency
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Font-family declared multiple times with different fallbacks | `styles.css:8`, `styles-modern.css:50`, `styles-concreteinfo.css:32` | Standardize font stack |
 | **Major** | Duplicate font-size declarations | `styles.css:228-230` | Remove duplicate |
 | **Minor** | Inconsistent line-height values | Multiple files | Create type scale variables |
 **Code Example - Duplicate font-size:**
 ```css
 /* styles.css:226-230 */
 .preview-content {
    max-width: none;
    margin: 0;
    padding: 20px 24px 24px 24px;
    line-height: 1.6;
    font-size: 15px;
    font-size: 14px;  /* DUPLICATE - overwrites previous */
 }
 ```
 **Fix Recommendation:**
 ```css
 /* styles.css - Remove duplicate */
 .preview-content {
    font-size: 14px;  /* Keep only one */
    line-height: 1.6;
 }
 ```
 ### 1.3 Color Usage and Contrast Accessibility
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Critical** | Hardcoded colors instead of CSS variables | `styles.css:27-29`, `styles.css:37-38`, etc. | Use CSS custom properties |
 | **Major** | Inconsistent gray scale definitions | Multiple files define different grays | Consolidate to single palette |
 | **Minor** | Some contrast ratios may be insufficient | Status bar text colors | Verify WCAG 2.1 AA compliance |
 **Code Example - Hardcoded colors:**
 ```css
 /* styles.css:27-29 */
 .tab-bar {
    background: #f0f0f0;  /* Should use var(--gray-100) */
    border-bottom: 1px solid #ddd;  /* Should use var(--gray-300) */
 }
 ```
 **Fix Recommendation:**
 ```css
 /* Use the existing palette from styles-modern.css */
 .tab-bar {
    background: var(--gray-100, #f3f4f6);
    border-bottom: 1px solid var(--gray-300, #d1d5db);
 }
 ```
 ### 1.4 Dark Mode Support Quality
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Dark theme selectors inconsistent | `styles.css` uses `body.theme-dark`, `styles-sidebar.css:108` uses `body[class*="dark"]` | Standardize selector pattern |
 | **Minor** | Missing dark theme support for some components | `.breadcrumb-bar`, command palette | Add dark mode variants |
 | **Suggestion** | Repetitive dark theme declarations | `styles-concreteinfo.css:362-425` | Use CSS custom properties for theming |
 **Code Example - Inconsistent selectors:**
 ```css
 /* styles.css */
 body.theme-dark .tab-bar { ... }
 /* styles-sidebar.css */
 body[class*="dark"] .sidebar-icons { ... }
 ```
 **Fix Recommendation:**
 ```css
 /* Choose one pattern and apply consistently */
 /* Option 1: Class-based (recommended) */
 body.theme-dark .tab-bar,
 body.theme-dark .sidebar-icons { ... }
 /* Option 2: Attribute-based */
 body[data-theme="dark"] .tab-bar { ... }
 ```
 ---
 ## 2. Usability Review
 ### 2.1 Clickable/Tappable Areas
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Critical** | Tab close button too small (16x16px) | `styles.css:62-77` | Increase to minimum 24x24px |
 | **Major** | Sidebar icons at minimum size | `styles-sidebar.css:35-47` (36x36px) | Consider 40-44px for better touch |
 | **Minor** | Toolbar buttons at edge of minimum | `styles.css:120-131` (32x32px) | Acceptable for mouse, small for touch |
 **Code Example - Small close button:**
 ```css
 /* styles.css:62-77 */
 .tab-close {
    width: 16px;   /* TOO SMALL - below 24px minimum */
    height: 16px;  /* TOO SMALL */
 }
 ```
 **Fix Recommendation:**
 ```css
 .tab-close {
    width: 24px;
    height: 24px;
    border-radius: 4px;
 }
 /* Add touch-friendly hit area */
 .tab-close::before {
    content: '';
    position: absolute;
    top: -4px;
    left: -4px;
    right: -4px;
    bottom: -4px;
 }
 ```
 ### 2.2 Hover/Focus States
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Critical** | Missing focus-visible styles | All interactive elements | Add :focus-visible for keyboard navigation |
 | **Major** | No focus indicators on toolbar buttons | `styles.css:133-140` | Add visible focus ring |
 | **Minor** | Inconsistent hover transitions | Various components | Standardize transition duration |
 **Code Example - Missing focus styles:**
 ```css
 /* styles.css:120-131 - No focus state */
 .toolbar button {
    /* ... no focus style */
 }
 .toolbar button:hover {
    background: #e0e0e0;
    border-color: #ccc;
 }
 ```
 **Fix Recommendation:**
 ```css
 .toolbar button:focus-visible {
    outline: 2px solid var(--primary-dark, #5661b3);
    outline-offset: 2px;
 }
 .toolbar button:hover {
    background: #e0e0e0;
    border-color: #ccc;
 }
 ```
 ### 2.3 Loading and Error State Handling
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Generic error message without styling | `renderer.js:384-386`, `renderer.js:508-511` | Create styled error components |
 | **Minor** | No loading indicators for async operations | Sidebar panels | Add skeleton loaders or spinners |
 | **Minor** | `git-loading` class exists but minimal styling | `styles-sidebar.css:227` | Enhance with animation |
 **Code Example - Plain error display:**
 ```javascript
 // renderer.js:384-386
 preview.innerHTML = '<p style="color: red; padding: 20px;">Error: Required libraries...';
 // Inline styles should be in CSS
 ```
 **Fix Recommendation:**
 ```css
 /* Add to styles.css */
 .preview-error {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    padding: 40px 20px;
    color: var(--ci-danger, #dc3545);
    text-align: center;
 }
 .preview-error-icon {
    font-size: 48px;
    margin-bottom: 16px;
 }
 ```
 ### 2.4 Accessibility (ARIA, Semantic HTML)
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Critical** | Buttons without accessible labels | `index.html:31` (tab close), `index.html:33` (new tab) | Add aria-label |
 | **Critical** | SVG icons lack aria-hidden | All toolbar buttons | Add aria-hidden="true" |
 | **Major** | Missing role attributes on tabs | `index.html:29-33` | Add role="tablist", role="tab" |
 | **Major** | No skip links | `index.html` | Add skip to main content link |
 | **Minor** | Dialog missing aria-modal | Export dialogs | Add aria-modal="true" |
 **Code Example - Missing accessibility attributes:**
 ```html
 <!-- index.html:31 - Current -->
 <button class="tab-close" title="Close tab">x</button>
 <!-- index.html:33 - Current -->
 <button class="new-tab-button" id="new-tab-btn" title="New tab">+</button>
 ```
 **Fix Recommendation:**
 ```html
 <!-- Improved with ARIA -->
 <div class="tab-bar" id="tab-bar" role="tablist" aria-label="Document tabs">
    <div class="tab active" data-tab-id="1" role="tab" aria-selected="true" aria-controls="tab-content-1">
        <span class="tab-title">Untitled</span>
        <button class="tab-close" aria-label="Close tab" title="Close tab">×</button>
    </div>
    <button class="new-tab-button" id="new-tab-btn" aria-label="Create new tab" title="New tab">+</button>
 </div>
 <!-- SVG icons should have aria-hidden -->
 <button id="btn-bold" title="Bold (Ctrl+B)" aria-label="Bold">
    <svg width="16" height="16" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" aria-hidden="true">
        ...
    </svg>
 </button>
 ```
 ### 2.5 Keyboard Navigation
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Tab order may skip sidebar icons | Sidebar panel | Verify logical tab order |
 | **Minor** | No escape key handling for dialogs | Export dialogs | Add escape to close |
 | **Minor** | Find dialog lacks full keyboard support | `renderer.js:804-866` | Add Ctrl+F shortcut hint |
 ---
 ## 3. Code Quality Review
 ### 3.1 CSS Organization & Naming
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | No clear CSS architecture | All CSS files | Adopt BEM or similar methodology |
 | **Major** | Overly generic class names | `.pane`, `.tab`, `.container` | Use more specific naming |
 | **Minor** | Mixed naming conventions | camelCase (`tabBar`), kebab-case (`tab-bar`) | Standardize to kebab-case |
 | **Minor** | Magic numbers | Various pixel values | Replace with spacing variables |
 ### 3.2 CSS Specificity Issues
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Excessive use of `!important` | `styles.css:14` | Restructure to avoid |
 | **Major** | Deep selector nesting | Dark theme selectors | Flatten and use CSS variables |
 | **Minor** | ID selectors for styling | `styles.css:233-247` | Prefer class selectors |
 **Code Example - Problematic specificity:**
 ```css
 /* styles.css:14 - Avoid !important */
 .hidden {
    display: none !important;
 }
 /* styles.css:397-431 - Deep nesting */
 body.theme-dark #preview h1,
 body.theme-dark [id^="preview-"] h1,
 body.theme-dark .preview-content h1 {
    color: #c9d1d9;
    border-bottom-color: #21262d;
 }
 ```
 **Fix Recommendation:**
 ```css
 /* Use utility class pattern */
 [hidden] { display: none; }
 /* Use CSS custom properties for theming */
 .preview-content h1 {
    color: var(--text-primary);
    border-bottom-color: var(--border-color);
 }
 /* Theme applies variables */
 body.theme-dark {
    --text-primary: #c9d1d9;
    --border-color: #21262d;
 }
 ```
 ### 3.3 Reusable Style Definitions
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Repeated button styles | Multiple files | Create button component classes |
 | **Major** | Dialog styles duplicated | Export, batch, print preview dialogs | Create modal component |
 | **Minor** | Similar form field styles scattered | Export dialog inputs | Create form component |
 **Code Example - Duplicated button styles:**
 ```css
 /* styles.css */
 .toolbar button { /* button styles */ }
 .tab-close { /* button styles */ }
 .new-tab-button { /* button styles */ }
 #export-dialog-close { /* button styles */ }
 /* styles-sidebar.css */
 .sidebar-icon { /* similar button styles */ }
 .sidebar-panel-close { /* similar button styles */ }
 ```
 **Fix Recommendation:**
 ```css
 /* Create button component system */
 .btn {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    border: none;
    cursor: pointer;
    transition: all var(--transition-fast);
 }
 .btn--icon {
    width: 32px;
    height: 32px;
    border-radius: var(--radius-md);
 }
 .btn--close {
    font-size: 14px;
    font-weight: bold;
    border-radius: var(--radius-sm);
 }
 ```
 ### 3.4 Documentation
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Minor** | Limited CSS documentation | All CSS files | Add section comments |
 | **Minor** | No component documentation | Sidebar components | Add JSDoc-style comments |
 | **Suggestion** | No design tokens documentation | CSS variables | Create tokens documentation |
 ---
 ## 4. Performance Review
 ### 4.1 CSS Optimization
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | Large CSS files (105KB main, 78KB modern) | `styles.css`, `styles-modern.css` | Split into smaller modules |
 | **Major** | Duplicate style definitions | Multiple files | Remove redundancies |
 | **Minor** | Unused styles likely present | Theme variations | Audit and remove unused |
 ### 4.2 Asset Loading
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Major** | highlight.js CSS loaded synchronously | `index.html:14` | Load asynchronously or bundle |
 | **Minor** | Font files could be preloaded | `fonts.css` | Add preload links in HTML |
 | **Suggestion** | Consider CSS critical path | Above-the-fold styles | Inline critical CSS |
 **Code Example - Sync stylesheet loading:**
 ```html
 <!-- index.html:14 - Blocks rendering -->
 <link rel="stylesheet" href="../node_modules/highlight.js/styles/default.css">
 ```
 **Fix Recommendation:**
 ```html
 <!-- Non-blocking load -->
 <link rel="stylesheet" href="../node_modules/highlight.js/styles/default.css" media="print" onload="this.media='all'">
 <!-- Or preload fonts -->
 <link rel="preload" href="../assets/fonts/Inter-Regular.woff2" as="font" type="font/woff2" crossorigin>
 ```
 ### 4.3 Animation Performance
 | Severity | Issue | Location | Recommendation |
 |----------|-------|----------|----------------|
 | **Minor** | Some transitions on expensive properties | `styles-modern.css:111-112` | Prefer transform/opacity |
 | **Suggestion** | Missing will-change hints | Complex animations | Add will-change for GPU hints |
 ---
 ## 5. Component-Specific Issues
 ### 5.1 Tab System
 | File | Issues |
 |------|--------|
 | `styles.css:23-97` | Inconsistent active state styling, small close button |
 | `renderer.js:88-346` | Tab content created via innerHTML (XSS risk) |
 ### 5.2 Sidebar
 | File | Issues |
 |------|--------|
 | `styles-sidebar.css` | Good structure but missing focus states |
 | `sidebar-manager.js` | Clean implementation, needs ARIA |
 ### 5.3 Export Dialogs
 | File | Issues |
 |------|--------|
 | `styles.css:1060-1355` | Monolithic, should be component |
 | `index.html:171-331` | Complex nested structure needs semantic HTML |
 ### 5.4 Welcome Screen
 | File | Issues |
 |------|--------|
 | `styles-welcome.css` | Minimal styles, good foundation |
 | Missing hover states for keyboard focus | Add :focus-visible |
 ---
 ## 6. Prioritized Fix Recommendations
 ### Critical (Immediate)
 1. **Add missing ARIA attributes** to all interactive elements
 2. **Increase tab close button size** to minimum 24x24px
 3. **Add focus-visible styles** for keyboard navigation
 4. **Fix duplicate font-size declaration** in `.preview-content`
 ### Major (Next Sprint)
 1. **Consolidate CSS resets** into single location
 2. **Create button component system** with variants
 3. **Standardize dark theme selectors** across all files
 4. **Replace hardcoded colors** with CSS variables
 5. **Create modal/dialog component** to reduce duplication
 ### Minor (Future)
 1. **Document CSS architecture** and naming conventions
 2. **Audit and remove unused styles**
 3. **Add loading state components** (skeletons, spinners)
 4. **Implement CSS module splitting** for better performance
 ---
 ## 7. Summary Statistics
 | Category | Critical | Major | Minor | Suggestions |
 |----------|----------|-------|-------|-------------|
 | Visual Design | 1 | 5 | 4 | 1 |
 | Usability | 3 | 4 | 4 | 0 |
 | Code Quality | 0 | 6 | 4 | 1 |
 | Performance | 0 | 3 | 2 | 2 |
 | **Total** | **4** | **18** | **14** | **4** |
 ---
 ## Conclusion
 The MarkdownConverter application has a functional UI with good visual variety through its theme system. However, there are significant opportunities for improvement in:
 1. **Accessibility** - Critical for users with disabilities
 2. **Code organization** - Reduce CSS duplication and improve maintainability
 3. **Component consistency** - Standardize interactive element sizing and states
 4. **Performance** - Optimize CSS loading and reduce bundle size
 Addressing the Critical and Major issues will significantly improve both user experience and code maintainability.
@@ -1,17 +0,0 @@
 {
  "review_id": "full-ui-review_20260315",
  "target": "src/ (Entire UI Directory)",
  "focus_areas": ["visual", "usability", "code", "performance"],
  "context": "comprehensive",
  "platform": "desktop",
  "status": "complete",
  "started_at": "2026-03-15T00:09:00.000Z",
  "completed_at": "2026-03-15T00:12:00.000Z",
  "issues_found": 40,
  "severity_counts": {
    "critical": 4,
    "major": 18,
    "minor": 14,
    "suggestion": 4
  }
 }
@@ -1,48 +0,0 @@
 {
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug Main Process",
      "type": "node",
      "request": "launch",
      "cwd": "${workspaceFolder}",
      "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron",
      "windows": {
        "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron.cmd"
      },
      "args": ["."],
      "outputCapture": "std",
      "env": {
        "NODE_ENV": "development"
      }
    },
    {
      "name": "Debug Renderer Process",
      "type": "chrome",
      "request": "attach",
      "port": 9222,
      "webRoot": "${workspaceFolder}/src",
      "timeout": 30000
    },
    {
      "name": "Debug Main + Renderer",
      "type": "node",
      "request": "launch",
      "cwd": "${workspaceFolder}",
      "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron",
      "windows": {
        "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron.cmd"
      },
      "args": [".", "--remote-debugging-port=9222"],
      "outputCapture": "std",
      "env": {
        "NODE_ENV": "development"
      },
      "serverReadyAction": {
        "pattern": "listening on port ([0-9]+)",
        "uriFormat": "http://localhost:%s",
        "action": "debugWithChrome"
      }
    }
  ]
 }
@@ -1,25 +0,0 @@
 # Repository Guidelines
 ## Project Structure & Module Organization
 Core application code lives in `src/`. Use `src/main.js` for the Electron main process, `src/preload.js` for the preload bridge, and `src/renderer.js` plus `src/editor/`, `src/sidebar/`, `src/repl/`, and `src/utils/` for renderer-side features. Electron adapter code is in `src/adapters/electron/`. Reusable markdown/document templates live in `src/templates/`. Static assets and icons are in `assets/`. Tests are in `tests/`, and build output goes to `dist/`.
 ## Build, Test, and Development Commands
 - `npm start`: launch the Electron app locally.
 - `npm test`: run the Jest suite once.
 - `npm run test:watch`: rerun tests during local development.
 - `npm run test:coverage`: generate coverage output.
 - `npm run lint` / `npm run lint:fix`: check or fix ESLint issues in `src` and `tests`.
 - `npm run format` / `npm run format:check`: apply or verify Prettier formatting.
 - `npm run build:linux`, `npm run build:win`, `npm run build:mac`: create platform packages with `electron-builder`.
 ## Coding Style & Naming Conventions
 This repo uses Prettier and ESLint. Follow `.prettierrc`: 2-space indentation, single quotes, semicolons, trailing commas where valid in ES5, and a 100-character line width. Prefer `camelCase` for variables/functions, `PascalCase` for classes, and kebab-case for file names only when already established. Keep module boundaries clear: UI logic in renderer modules, OS/file-system work behind Electron IPC and adapters.
 ## Testing Guidelines
 Tests use Jest with `jest-environment-jsdom`. Add new tests under `tests/` with `*.test.js` names, mirroring the feature area when possible, for example `tests/sidebar.test.js` or `tests/print-preview.test.js`. Update or add regression tests for renderer behavior, preload APIs, and utility helpers when fixing bugs. Run `npm test` before opening a PR; use `npm run test:coverage` for larger refactors.
 ## Commit & Pull Request Guidelines
 Recent history follows Conventional Commit prefixes such as `feat:`, `fix:`, and `refactor:`. Keep subjects short and imperative, for example `fix: guard modal cleanup on close`. PRs should describe the user-visible change, note test coverage, link any related issue, and include screenshots or GIFs for UI changes.
 ## Security & Configuration Tips
 Do not bypass preload boundaries or introduce direct `eval`/dynamic code paths; ESLint already treats these as errors. Export and conversion features depend on external tools such as Pandoc, FFmpeg, ImageMagick, and LibreOffice, so document any new runtime dependency in `README.md` and packaging config.
@@ -1,67 +0,0 @@
 # Changelog
 All notable changes to markdown-converter will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 ## [5.1.0] - 2026-06-08
 ### Added
 - Auto-update via electron-updater against GitHub Releases (default) or ConcreteInfo self-hosted feed.
 - Light, skippable first-run wizard: theme, update channel, starter template.
 - One-shot v4.4.1 → v5 settings migration with backup at `settings.v4.bak.json`.
 - Local crash dump capture (cap 20, auto-prune) and a CrashReportModal.
 - "Updates" section in Settings: channel picker, Check now, auto-check toggle.
 ## [5.0.0] - 2026-06-06
 ### Added
 - **Complete React 19 + Vite + TypeScript renderer** replacing the legacy vanilla-JS UI (Phases 1-9 of the React UI redesign)
 - Native macOS/Windows/Linux menus with command palette and keyboard shortcuts
 - Settings sheet with 5 tabs (editor, theme, keybindings, advanced, about) and 17+ persisted fields
 - Modal layer with 13 modal kinds (export PDF/DOCX/HTML/Word, batch, settings, about, welcome, confirm, ASCII gen, table gen, find in files)
 - 10 advanced tools: ASCII generator (figlet), table generator, Word export (.docx via `docx` lib), find-in-files (recursive regex), REPL (markdown snippet preview), print preview, zen mode (Esc exits), minimap, breadcrumbs-with-symbols, git status (porcelain parser)
 - Sonner toast notifications at 4 wire points (file save, open file/folder, 4 export dialogs)
 - 3 mount strategies: ModalLayer dialogs, App.tsx global overlays, editor/sidebar integrations
 - `ipc.file.writeBuffer` for renderer-side binary file output (used by Word .docx export)
 - `ipc.file.search` (recursive regex), `ipc.file.gitStatus`, `ipc.print.show`, `ipc.app.showSaveDialog`
 - 305 unit + integration tests (vitest + React Testing Library)
 - Per-package @radix-ui primitives (checkbox, dialog, select, switch, tabs, radio-group, scroll-area, slider, collapsible, label, context-menu)
 - shadcn/ui (new-york style) primitives, manually pasted (CLI broken on Node 24)
 - Feature-first main process decomposition: `src/main/{files,menu,window,word-template,utils}/` + glue files
 ### Changed
 - **BREAKING**: Renderer is now React-only. The legacy `src/renderer.js` (5319 lines) and all vanilla-JS UI scripts/styles are removed.
 - Main process decomposed from a 4311-line `src/main.js` into feature-first modules under `src/main/`
 - New entrypoint: `src/main/index.js` (was `src/main.js`)
 - `src/index.html` (1667-line legacy orphan) removed; renderer served by `src/renderer/index.html` (Vite root)
 - IPC contract: handlers throw on error, `safeCall` catches → returns `{ ok: false, error }`. `result.ok` is at top level, NOT nested in `result.data.ok`
 - Settings store: `useSettingsStore` (zustand persist with zod validation), 17+ persisted fields
 - Modal state: `useAppStore.modal: ModalState` discriminated union with 13 kinds; `openModal` uses TS conditional types to enforce prop requirements
 ### Removed
 - `src/renderer.js` (legacy vanilla-JS renderer, 5319 lines)
 - 8 legacy stylesheets: `src/styles.css`, `src/styles-modern.css`, `src/styles-concreteinfo.css`, `src/styles-sidebar.css`, `src/styles-zen.css`, `src/styles-welcome.css`, `src/fonts.css`
 - 5 legacy scripts: `src/command-palette.js`, `src/print-preview.js`, `src/welcome.js`, `src/zen-mode.js`, `src/wordTemplateExporter.js`
 - 2 legacy HTMLs: `src/ascii-generator.html`, `src/table-generator.html`
 - `src/main.js` (4311-line god file, replaced by `src/main/index.js`)
 - `src/index.html` (1667-line legacy orphan at project root, replaced by `src/renderer/index.html`)
 - 9 dead IPC channels from `src/preload.js`: `toggle-command-palette`, `print-preview`, `print-preview-styled`, `open-ascii-generator`, `open-table-generator`, `show-ascii-generator`, `show-ascii-generator-window`, `show-table-generator`, `show-table-generator-window`
 [5.0.0]: https://github.com/amitwh/markdown-converter/releases/tag/v5.0.0
 ## [5.1.0] - 2026-07-23 - react-electron parity
 ### Added
 - **Monospace font embedding** — bundles JetBrains Mono + Fira Code TTFs and embeds the active font into PDF (xelatex fontspec), DOCX (post-pandoc zip patch with `fontTable.xml`), EPUB (`--epub-embed-font` + manifest), and HTML (woff2 base64 in CSS) exports. ASCII art and code blocks now render with the exact same font across machines.
 - **Monospace settings** — `get-monospace-settings` / `set-monospace-settings` IPC, with `monospaceFont` (`jetbrains-mono` / `fira-code`) and `monospaceLigatures` (boolean).
 - **Renderer body-class toggle** — `useMonospaceClasses` hook toggles `mono-jetbrains-mono` / `mono-fira-code` and `mono-ligatures-on` / `mono-ligatures-off` on `document.body`, driving `--font-mono-active` and `--font-mono-feature` CSS tokens.
 ### Changed
 - **App renamed to Markdown Converter React** (`com.concreteinfo.markdownconverter.react`, npm name `markdown-converter-react`, deb `markdown-converter-react_*_amd64.deb`) so the dev build coexists with the installed `markdown-converter` deb without single-instance lock conflicts.
 - Window title shows `Markdown Converter — React Dev` in dev mode.
 - `download-tools.js` pins Fira Code to release `6.2` with SHA-256 digests verified before atomic rename; downloads refuse to start on digest mismatch.
 ### Security
 - `PdfFontHeader` uses `fs.mkdtempSync` for an exclusive temp directory; the caller unlinks it after pandoc consumes the header (no racy `Date.now()+pid` filenames).
@@ -1,145 +0,0 @@
 # CLAUDE.md — MarkdownConverter (react-electron)
 > General code-quality, TypeScript, git, security, and testing standards are in the **global CLAUDE.md**. This file holds project- and branch-specific notes.
 ## Project Overview
 Electron desktop app for Markdown editing and universal file conversion powered by Pandoc. Cross-platform (Win/macOS/Linux). Features: multi-tab editor with live preview, 25+ themes, PDF viewer/editor (merge/split/compress/rotate/watermark/password), export to 20+ formats (PDF/DOCX/ODT/EPUB/HTML/LaTeX/RTF/PPTX), batch conversion, syntax highlighting, diagram support (Mermaid), Git integration, plugin system, and auto-updater.
 - **Version:** 5.0.1
 - **License:** MIT
 - **App ID:** `com.concreteinfo.markdownconverter`
 ## Branch Specifics
 This is the **React rewrite branch** — the renderer has been rebuilt with React 19 + TypeScript + Tailwind CSS + shadcn/ui, replacing the vanilla JS renderer from master. The main process remains vanilla CommonJS JavaScript. A dual dev workflow runs Vite (renderer) and Electron (main) concurrently.
 Key differences from master:
 - Renderer: React 19 + TypeScript (TSX) instead of vanilla JS DOM manipulation
 - Bundler: Vite for the renderer (`vite.renderer.config.ts`)
 - UI: shadcn/ui (Radix primitives + Tailwind) instead of hand-rolled CSS
 - State: Zustand 5 stores instead of global mutable state
 - Security: `contextIsolation: true` + `nodeIntegration: false` (preload with channel whitelisting) instead of master's open renderer
 - Build: two-stage (Vite build renderer, then electron-builder packages) instead of single electron-builder pass
 - Testing: dual test runners — Vitest (renderer/React/TS) + Jest (main process/JS)
 - Main process is now in `src/main/` (modular) instead of flat `src/main.js`
 - Adds auto-updater via `electron-updater` with GitHub Releases + self-hosted feed support
 - Adds React Hook Form + Zod for form validation, Lucide React icons, Motion for animations
 - Legacy sidebar modules (`src/sidebar/*.js`) still exist alongside new React sidebar (`src/renderer/components/sidebar/`)
 ## Architecture
 ### Main Process (`src/main/`)
 Modular structure (improvement over master's monolith):
 - `src/main/index.js` — IPC handlers, Pandoc invocation, export logic (~3,500 lines)
 - `src/main/PDFOperations.js` — PDF manipulation via `pdf-lib`
 - `src/main/GitOperations.js` — Git operations via `simple-git`
 - `src/main/store.js` — Custom JSON settings store (NOT electron-store)
 - `src/main/window/index.js` — BrowserWindow creation with three-mode loading (dev/prod/packaged)
 - `src/main/menu/` — Application menu definitions
 - `src/main/ipc/` — Crash handlers, updater handlers
 - `src/main/updater/` — Auto-update service, feed config, migration runner
 - `src/main/files/` — File operation modules
 - `src/main/word-template/` — Word template export
 ### Preload (`src/preload.js`)
 Properly isolated. Uses `contextBridge` with **channel whitelisting** (`ALLOWED_SEND_CHANNELS`, `ALLOWED_RECEIVE_CHANNELS` arrays). The renderer has no direct Node access.
 ### Renderer (`src/renderer/`)
 React 19 + TypeScript application bundled by Vite:
 - `src/renderer/App.tsx` — Root component: assembles AppShell, modals, command palette, toaster
 - `src/renderer/components/layout/AppShell.tsx` — Three-panel resizable layout (sidebar | editor | preview)
 - `src/renderer/stores/` — Zustand stores: `app-store`, `editor-store`, `file-store`, `preview-store`, `settings-store`, `command-store`
 - `src/renderer/hooks/` — Custom hooks: `use-shortcut`, `use-file-shortcuts`, `use-menu-action`, `use-scroll-sync`, `use-zen-mode`, `use-export-source`
 - `src/renderer/components/modals/` — 30+ modal dialogs as React components
 - `src/renderer/components/editor/` — CodeMirror 6 editor React wrapper
 - `src/renderer/components/preview/` — Markdown renderer with Mermaid lazy loading
 - `src/renderer/components/sidebar/` — React sidebar panels (FileTree, GitStatus, Outline, Snippets, Templates)
 - `src/renderer/components/ui/` — shadcn/ui primitives (button, dialog, sheet, select, tabs, etc.)
 - `src/renderer/lib/` — Utilities: typed IPC wrapper (`ipc.ts`), export modules, validators
 - `src/renderer/types/` — TypeScript declarations: `electron.d.ts` (window.electronAPI), `ipc.ts` (IPC types)
 ### Security Model
 - **`contextIsolation: true` + `nodeIntegration: false`** (properly secured, unlike master)
 - Preload with explicit channel whitelisting
 - TypeScript declarations ensure type-safe IPC
 - Pandoc invoked via `execFile` (not `exec`)
 - Permission handler: only `clipboard-read`/`clipboard-write` allowed
 - ESLint enforces `no-eval`, `no-implied-eval`, `no-new-func`
 - CSP in `index.html` restricts script/style/img/font/connect sources
 ### Plugin System (`src/plugins/`)
 Unchanged from master. Manifest-based discovery, built-in `writing-studio` plugin.
 ## System Dependencies
 | Dependency | Required | Notes |
 |---|---|---|
 | **Node.js** | >= 20 | Electron 41 bundles Node 20.x; Vite 8 requires Node 18+ |
 | **Pandoc** | Yes (for exports) | Downloaded to `bin/<platform>/pandoc` via `scripts/download-tools.js` (v3.9.0.2). Falls back to system PATH. |
 | **FFmpeg** | Bundled | `ffmpeg-static` npm package; `asarUnpacked` |
 | **MiKTeX / TeX Live** | Optional | LaTeX PDF export; MiKTeX PATH injected on Windows |
 | **ImageMagick** | Optional | Linux image conversion; deb dependency |
 | **LibreOffice** | Optional | Enhanced document conversion; deb dependency |
 ## Development Commands
 ```bash
 npm run dev                # Start dev mode: Vite dev server (port 5173) + Electron (concurrently)
 npm run dev:renderer       # Vite dev server only (port 5173)
 npm run dev:electron       # Electron only (waits for Vite on tcp:5173)
 npm start                  # Launch Electron app (prod mode, requires built renderer)
 npm run preview            # Build renderer then launch Electron
 npm test                   # Jest — main process tests (vanilla JS)
 npm run test:renderer      # Vitest — renderer tests (React/TS)
 npm run lint               # ESLint check
 npm run lint:fix           # ESLint auto-fix
 npm run format             # Prettier write
 npm run format:check       # Prettier check
 npm run download-tools     # Download Pandoc binaries
 npm run generate-icons     # Generate app icons
 ```
 **Dev workflow:** `npm run dev` starts Vite (renderer HMR on `:5173`) and Electron concurrently. The main process loads from `http://localhost:5173` in dev mode.
 ## Build & Package
 **Two-stage build process:**
 1. `npm run build:renderer` — Vite builds renderer to `dist/renderer/`
 2. `npm run build` — electron-builder packages main process + preload + built renderer
 **Tool:** `electron-builder` (v26.0.12), config inline in `package.json`.
 | Target | Platforms |
 |---|---|
 | `npm run build:win` | Windows: NSIS + portable + zip (x64) |
 | `npm run build:mac` | macOS: dmg + zip (x64 + arm64) |
 | `npm run build:linux` | Linux: deb + AppImage + snap |
 **Packaged files:** `src/main/**`, `src/preload.js`, `src/plugins/**`, `package.json`. Renderer built output copied to resources as `renderer/`.
 **Bundled with builds:** Pandoc binary per platform, FFmpeg (asarUnpacked).
 **Output:** `dist/` directory.
 **Auto-updater:** `electron-updater` with GitHub Releases (default) and optional ConcreteInfo self-hosted feed.
 **CI:** GitHub Actions workflows in `.github/workflows/` (ci.yml, release.yml).
 ## Project Conventions / Gotchas
 - **Dual-process architecture.** Main process is vanilla CommonJS JavaScript (`src/main/`). Renderer is React 19 + TypeScript + Tailwind (`src/renderer/`). They are separate build targets.
 - **Vite for renderer only.** Main process is NOT bundled — Electron loads `src/main/index.js` directly. Do not add TypeScript to main process files.
 - **Tailwind + shadcn/ui.** Use shadcn/ui components (`src/renderer/components/ui/`) for all UI primitives. Custom theme in `tailwind.config.js`. Path alias `@` maps to `src/renderer/`. Brand color: `#e5461f`.
 - **Zustand for state.** All renderer state lives in `src/renderer/stores/`. Each store is a separate file. Use immer for immutable updates.
 - **Typed IPC.** `src/renderer/types/electron.d.ts` declares `window.electronAPI`. `src/renderer/lib/ipc.ts` provides type-safe wrappers. When adding new IPC channels, update both the preload whitelist AND the TypeScript declarations.
 - **Legacy + new sidebar.** `src/sidebar/*.js` (vanilla JS) and `src/renderer/components/sidebar/` (React TSX) both exist. New sidebar features go in the React version.
 - **Pandoc is external.** Must be present for non-HTML/PDF exports. Download via `npm run download-tools` or install system-wide.
 - **PDF export fallback chain:** xelatex -> pdflatex -> lualatex -> Electron built-in `printToPDF()`.
 - **PDF rendering:** `pdfjs-dist` (viewer). **PDF manipulation:** `pdf-lib` in main process.
 - **Editor:** CodeMirror 6, configured in `src/editor/codemirror-setup.js`, wrapped as React component in `src/renderer/components/editor/CodeMirrorEditor.tsx`.
 - **Tests:** Jest (main process, `tests/**/*.test.js`, 15% threshold) + Vitest (renderer, `tests/**/*.{test,spec}.{ts,tsx}`, v8 coverage on `src/renderer/`).
 - **ESLint flat config** with ECMAScript 2022. Prettier: 2-space, single quotes, semicolons, 100-char width.
 - **No tsconfig.json at root** — TypeScript is renderer-only, handled by Vite. Do not add `tsconfig.json` for the main process.
 - **File associations:** `.md`, `.markdown`, `.pdf` registered at install.
 - **Single instance lock** via `app.requestSingleInstanceLock()`.
@@ -1,103 +0,0 @@
 # Export Functionality Fix - Summary
 ## Issues Found and Fixed
 ### 1. **Primary Issue: Pandoc Installation Problem**
 - **Problem**: Pandoc is installed but has a system error (paging file too small)
 - **Impact**: All pandoc-dependent exports (DOCX, LaTeX, etc.) were failing
 - **Solution**: Added robust fallback mechanisms
 ### 2. **Export Function Improvements**
 #### Before (Issues):
 - ❌ No pandoc availability checking
 - ❌ Poor error messages
 - ❌ No fallback for missing pandoc
 - ❌ Limited debugging information
 #### After (Fixed):
 - ✅ **Pandoc Detection**: Automatically checks if pandoc is available
 - ✅ **Built-in HTML Export**: Works without pandoc using marked library
 - ✅ **Built-in PDF Export**: Works without pandoc using Electron's printToPDF
 - ✅ **Better Error Messages**: Clear instructions for users
 - ✅ **Comprehensive Logging**: Debug information in console
 - ✅ **Graceful Fallbacks**: Falls back to built-in converters when pandoc fails
 ## How It Works Now
 ### Export Process Flow:
 1. **User clicks export** → Check if file is saved
 2. **Select output location** → Show save dialog
 3. **Check pandoc availability** → Async pandoc detection
 4. **Choose export method**:
   - **If pandoc available**: Use pandoc with format-specific options
   - **If pandoc not available**: 
     - HTML → Use built-in marked converter
     - PDF → Use Electron's printToPDF
     - Other formats → Show helpful error with installation guide
 ### Supported Export Formats:
 #### ✅ **Always Work** (no pandoc required):
 - **HTML**: Built-in converter using marked library
 - **PDF**: Built-in converter using Electron
 #### ✅ **Work with Pandoc** (better quality):
 - **DOCX**: Microsoft Word format
 - **LaTeX**: LaTeX document
 - **RTF**: Rich Text Format  
 - **ODT**: OpenDocument Text
 - **EPUB**: E-book format
 - **PPTX**: PowerPoint presentations
 - **ODP**: OpenDocument Presentations
 ## Testing the Fixes
 ### Manual Test Procedure:
 1. **Start the application**: `npm start`
 2. **Open test file**: Load `test-export.md`
 3. **Test HTML export**: File → Export → HTML (should work)
 4. **Test PDF export**: File → Export → PDF (should work)
 5. **Test DOCX export**: File → Export → DOCX (will show pandoc error)
 ### Expected Behavior:
 - **HTML/PDF exports**: Should work immediately and create files
 - **Other format exports**: Should show informative error about pandoc
 - **Console logs**: Should show debug information about export process
 ## Fix Summary
 ### Code Changes Made:
 1. **Added `checkPandocAvailability()` function** - Detects pandoc
 2. **Added `exportToHTML()` function** - Built-in HTML export
 3. **Added `exportToPDFElectron()` function** - Built-in PDF export
 4. **Added `exportWithPandoc()` helper** - Generic pandoc export
 5. **Added `exportWithPandocPDF()` helper** - PDF with fallbacks
 6. **Improved `exportFile()` function** - Main export logic with detection
 7. **Enhanced error handling** - Better user messages
 8. **Added comprehensive logging** - Debug information
 ### Files Modified:
 - `src/main.js` - Enhanced export functionality
 - `test-export.md` - Created test file
 - `test-export-functionality.js` - Created test script
 ## User Instructions
 ### For Users Without Pandoc:
 - ✅ **HTML and PDF exports work perfectly**
 - ✅ **No additional software needed**
 - ✅ **Professional-looking output with proper styling**
 ### For Users Who Want All Formats:
 1. **Install Pandoc**: Visit https://pandoc.org/installing.html
 2. **For PDF with LaTeX**: Also install MiKTeX or TeX Live
 3. **Restart the application** after installation
 4. **All export formats will then be available**
 ## Result
 🎉 **Export functionality is now working reliably!**
 - Built-in exports (HTML, PDF) work without any dependencies
 - Clear error messages guide users for advanced formats
 - Robust error handling prevents crashes
 - Better user experience with informative dialogs
@@ -1,82 +0,0 @@
 # GEMINI.md
 ## Project Overview
 This project is a cross-platform Markdown editor and converter named **PanConverter**. It is built using the Electron framework, allowing it to run on Windows, macOS, and Linux. The application provides a rich text editor for writing Markdown, a live preview pane, and robust export capabilities powered by Pandoc.
 The core technologies used are:
 - **Electron:** For creating the desktop application.
 - **JavaScript:** The primary programming language.
 - **Pandoc:** For converting Markdown to various formats like PDF, DOCX, HTML, etc.
 - **Marked:** For parsing and rendering the Markdown preview in real-time.
 - **CodeMirror:** As the underlying text editor component.
 - **highlight.js:** For syntax highlighting in the editor.
 - **DOMPurify:** To sanitize the HTML output in the preview pane for security.
 The application features a tabbed interface for working with multiple files, various themes, find and replace functionality, and detailed document statistics.
 ## Building and Running
 To build and run this project locally, you will need to have Node.js and npm installed.
 ### Installation
 1.  **Clone the repository:**
    ```bash
    git clone https://github.com/amitwh/pan-converter.git
    cd pan-converter
    ```
 2.  **Install dependencies:**
    ```bash
    npm install
    ```
 ### Running the Application
 To run the application in development mode, use the following command:
 ```bash
 npm start
 ```
 ### Building the Application
 You can build the application for different platforms using the scripts defined in `package.json`.
 -   **Build for the current platform:**
    ```bash
    npm run build
    ```
 -   **Build for a specific platform:**
    ```bash
    npm run build:win    # For Windows
    npm run build:mac    # For macOS
    npm run build:linux  # For Linux
    ```
 -   **Build for all platforms at once:**
    ```bash
    npm run dist:all
    ```
 The distributable files will be located in the `dist/` directory.
 ### Testing
 The project does not have a dedicated test suite configured. The `test` script in `package.json` currently returns an error.
 ```bash
 npm test
 ```
 ## Development Conventions
 -   **Code Style:** The codebase is written in JavaScript (ES6+). There is no linter or formatter configured, but the code generally follows standard JavaScript conventions.
 -   **Main vs. Renderer Process:** The application logic is split between the Electron main process (`src/main.js`) and the renderer process (`src/renderer.js`).
    -   `src/main.js` handles window management, application menus, file system operations, and communication with the operating system.
    -   `src/renderer.js` manages the user interface, editor functionality, and the Markdown preview.
 -   **Dependencies:** Project dependencies are managed through `package.json`. `devDependencies` are used for the build process, while `dependencies` are required for the application to run.
 -   **User Data:** The application stores settings and recent files in the user's application data directory.
 -   **Pandoc Integration:** The application relies on a system-installed version of Pandoc for its export functionality. It does not bundle Pandoc.
@@ -1,21 +1,674 @@
-MIT License
+                    GNU GENERAL PUBLIC LICENSE
                       Version 3, 29 June 2007
-Copyright (c) 2024 Amit Haridas
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.
-Permission is hereby granted, free of charge, to any person obtaining a copy
+                            Preamble
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
-The above copyright notice and this permission notice shall be included in all
+  The GNU General Public License is a free, copyleft license for
-copies or substantial portions of the Software.
+software and other kinds of works.
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+  The licenses for most software and other practical works are designed
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+to take away your freedom to share and change the works.  By contrast,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+the GNU General Public License is intended to guarantee your freedom to
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+share and change all versions of a program--to make sure it remains free
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+software for all its users.  We, the Free Software Foundation, use the
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+GNU General Public License for most of our software; it applies also to
-SOFTWARE.
+any other work released this way by its authors.  You can apply it to
 your programs, too.
  When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
 have the freedom to distribute copies of free software (and charge for
 them if you wish), that you receive source code or can get it if you
 want it, that you can change the software or use pieces of it in new
 free programs, and that you know you can do these things.
  To protect your rights, we need to prevent others from denying you
 these rights or asking you to surrender the rights.  Therefore, you have
 certain responsibilities if you distribute copies of the software, or if
 you modify it: responsibilities to respect the freedom of others.
  For example, if you distribute copies of such a program, whether
 gratis or for a fee, you must pass on to the recipients the same
 freedoms that you received.  You must make sure that they, too, receive
 or can get the source code.  And you must show them these terms so they
 know their rights.
  Developers that use the GNU GPL protect your rights with two steps:
 (1) assert copyright on the software, and (2) offer you this License
 giving you legal permission to copy, distribute and/or modify it.
  For the developers' and authors' protection, the GPL clearly explains
 that there is no warranty for this free software.  For both users' and
 authors' sake, the GPL requires that modified versions be marked as
 changed, so that their problems will not be attributed erroneously to
 authors of previous versions.
  Some devices are designed to deny users access to install or run
 modified versions of the software inside them, although the manufacturer
 can do so.  This is fundamentally incompatible with the aim of
 protecting users' freedom to change the software.  The systematic
 pattern of such abuse occurs in the area of products for individuals to
 use, which is precisely where it is most unacceptable.  Therefore, we
 have designed this version of the GPL to prohibit the practice for those
 products.  If such problems arise substantially in other domains, we
 stand ready to extend this provision to those domains in future versions
 of the GPL, as needed to protect the freedom of users.
  Finally, every program is threatened constantly by software patents.
 States should not allow patents to restrict development and use of
 software on general-purpose computers, but in those that do, we wish to
 avoid the special danger that patents applied to a free program could
 make it effectively proprietary.  To prevent this, the GPL assures that
 patents cannot be used to render the program non-free.
  The precise terms and conditions for copying, distribution and
 modification follow.
                       TERMS AND CONDITIONS
  0. Definitions.
  "This License" refers to version 3 of the GNU General Public License.
  "Copyright" also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
  "The Program" refers to any copyrightable work licensed under this
 License.  Each licensee is addressed as "you".  "Licensees" and
 "recipients" may be individuals or organizations.
  To "modify" a work means to copy from or adapt all or part of the work
 in a fashion requiring copyright permission, other than the making of an
 exact copy.  The resulting work is called a "modified version" of the
 earlier work or a work "based on" the earlier work.
  A "covered work" means either the unmodified Program or a work based
 on the Program.
  To "propagate" a work means to do anything with it that, without
 permission, would make you directly or secondarily liable for
 infringement under applicable copyright law, except executing it on a
 computer or modifying a private copy.  Propagation includes copying,
 distribution (with or without modification), making available to the
 public, and in some countries other activities as well.
  To "convey" a work means any kind of propagation that enables other
 parties to make or receive copies.  Mere interaction with a user through
 a computer network, with no transfer of a copy, is not conveying.
  An interactive user interface displays "Appropriate Legal Notices"
 to the extent that it includes a convenient and prominently visible
 feature that (1) displays an appropriate copyright notice, and (2)
 tells the user that there is no warranty for the work (except to the
 extent that warranties are provided), that licensees may convey the
 work under this License, and how to view a copy of this License.  If
 the interface presents a list of user commands or options, such as a
 menu, a prominent item in the list meets this criterion.
  1. Source Code.
  The "source code" for a work means the preferred form of the work
 for making modifications to it.  "Object code" means any non-source
 form of a work.
  A "Standard Interface" means an interface that either is an official
 standard defined by a recognized standards body, or, in the case of
 interfaces specified for a particular programming language, one that
 is widely used among developers working in that language.
  The "System Libraries" of an executable work include anything, other
 than the work as a whole, that (a) is included in the normal form of
 packaging a Major Component, but which is not part of that Major
 Component, and (b) serves only to enable use of the work with that
 Major Component, or to implement a Standard Interface for which an
 implementation is available to the public in source code form.  A
 "Major Component", in this context, means a major essential component
 (kernel, window system, and so on) of the specific operating system
 (if any) on which the executable work runs, or a compiler used to
 produce the work, or an object code interpreter used to run it.
  The "Corresponding Source" for a work in object code form means all
 the source code needed to generate, install, and (for an executable
 work) run the object code and to modify the work, including scripts to
 control those activities.  However, it does not include the work's
 System Libraries, or general-purpose tools or generally available free
 programs which are used unmodified in performing those activities but
 which are not part of the work.  For example, Corresponding Source
 includes interface definition files associated with source files for
 the work, and the source code for shared libraries and dynamically
 linked subprograms that the work is specifically designed to require,
 such as by intimate data communication or control flow between those
 subprograms and other parts of the work.
  The Corresponding Source need not include anything that users
 can regenerate automatically from other parts of the Corresponding
 Source.
  The Corresponding Source for a work in source code form is that
 same work.
  2. Basic Permissions.
  All rights granted under this License are granted for the term of
 copyright on the Program, and are irrevocable provided the stated
 conditions are met.  This License explicitly affirms your unlimited
 permission to run the unmodified Program.  The output from running a
 covered work is covered by this License only if the output, given its
 content, constitutes a covered work.  This License acknowledges your
 rights of fair use or other equivalent, as provided by copyright law.
  You may make, run and propagate covered works that you do not
 convey, without conditions so long as your license otherwise remains
 in force.  You may convey covered works to others for the sole purpose
 of having them make modifications exclusively for you, or provide you
 with facilities for running those works, provided that you comply with
 the terms of this License in conveying all material for which you do
 not control copyright.  Those thus making or running the covered works
 for you must do so exclusively on your behalf, under your direction
 and control, on terms that prohibit them from making any copies of
 your copyrighted material outside their relationship with you.
  Conveying under any other circumstances is permitted solely under
 the conditions stated below.  Sublicensing is not allowed; section 10
 makes it unnecessary.
  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
  No covered work shall be deemed part of an effective technological
 measure under any applicable law fulfilling obligations under article
 11 of the WIPO copyright treaty adopted on 20 December 1996, or
 similar laws prohibiting or restricting circumvention of such
 measures.
  When you convey a covered work, you waive any legal power to forbid
 circumvention of technological measures to the extent such circumvention
 is effected by exercising rights under this License with respect to
 the covered work, and you disclaim any intention to limit operation or
 modification of the work as a means of enforcing, against the work's
 users, your or third parties' legal rights to forbid circumvention of
 technological measures.
  4. Conveying Verbatim Copies.
  You may convey verbatim copies of the Program's source code as you
 receive it, in any medium, provided that you conspicuously and
 appropriately publish on each copy an appropriate copyright notice;
 keep intact all notices stating that this License and any
 non-permissive terms added in accord with section 7 apply to the code;
 keep intact all notices of the absence of any warranty; and give all
 recipients a copy of this License along with the Program.
  You may charge any price or no price for each copy that you convey,
 and you may offer support or warranty protection for a fee.
  5. Conveying Modified Source Versions.
  You may convey a work based on the Program, or the modifications to
 produce it from the Program, in the form of source code under the
 terms of section 4, provided that you also meet all of these conditions:
    a) The work must carry prominent notices stating that you modified
    it, and giving a relevant date.
    b) The work must carry prominent notices stating that it is
    released under this License and any conditions added under section
    7.  This requirement modifies the requirement in section 4 to
    "keep intact all notices".
    c) You must license the entire work, as a whole, under this
    License to anyone who comes into possession of a copy.  This
    License will therefore apply, along with any applicable section 7
    additional terms, to the whole of the work, and all its parts,
    regardless of how they are packaged.  This License gives no
    permission to license the work in any other way, but it does not
    invalidate such permission if you have separately received it.
    d) If the work has interactive user interfaces, each must display
    Appropriate Legal Notices; however, if the Program has interactive
    interfaces that do not display Appropriate Legal Notices, your
    work need not make them do so.
  A compilation of a covered work with other separate and independent
 works, which are not by their nature extensions of the covered work,
 and which are not combined with it such as to form a larger program,
 in or on a volume of a storage or distribution medium, is called an
 "aggregate" if the compilation and its resulting copyright are not
 used to limit the access or legal rights of the compilation's users
 beyond what the individual works permit.  Inclusion of a covered work
 in an aggregate does not cause this License to apply to the other
 parts of the aggregate.
  6. Conveying Non-Source Forms.
  You may convey a covered work in object code form under the terms
 of sections 4 and 5, provided that you also convey the
 machine-readable Corresponding Source under the terms of this License,
 in one of these ways:
    a) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by the
    Corresponding Source fixed on a durable physical medium
    customarily used for software interchange.
    b) Convey the object code in, or embodied in, a physical product
    (including a physical distribution medium), accompanied by a
    written offer, valid for at least three years and valid for as
    long as you offer spare parts or customer support for that product
    model, to give anyone who possesses the object code either (1) a
    copy of the Corresponding Source for all the software in the
    product that is covered by this License, on a durable physical
    medium customarily used for software interchange, for a price no
    more than your reasonable cost of physically performing this
    conveying of source, or (2) access to copy the
    Corresponding Source from a network server at no charge.
    c) Convey individual copies of the object code with a copy of the
    written offer to provide the Corresponding Source.  This
    alternative is allowed only occasionally and noncommercially, and
    only if you received the object code with such an offer, in accord
    with subsection 6b.
    d) Convey the object code by offering access from a designated
    place (gratis or for a charge), and offer equivalent access to the
    Corresponding Source in the same way through the same place at no
    further charge.  You need not require recipients to copy the
    Corresponding Source along with the object code.  If the place to
    copy the object code is a network server, the Corresponding Source
    may be on a different server (operated by you or a third party)
    that supports equivalent copying facilities, provided you maintain
    clear directions next to the object code saying where to find the
    Corresponding Source.  Regardless of what server hosts the
    Corresponding Source, you remain obligated to ensure that it is
    available for as long as needed to satisfy these requirements.
    e) Convey the object code using peer-to-peer transmission, provided
    you inform other peers where the object code and Corresponding
    Source of the work are being offered to the general public at no
    charge under subsection 6d.
  A separable portion of the object code, whose source code is excluded
 from the Corresponding Source as a System Library, need not be
 included in conveying the object code work.
  A "User Product" is either (1) a "consumer product", which means any
 tangible personal property which is normally used for personal, family,
 or household purposes, or (2) anything designed or sold for incorporation
 into a dwelling.  In determining whether a product is a consumer product,
 doubtful cases shall be resolved in favor of coverage.  For a particular
 product received by a particular user, "normally used" refers to a
 typical or common use of that class of product, regardless of the status
 of the particular user or of the way in which the particular user
 actually uses, or expects or is expected to use, the product.  A product
 is a consumer product regardless of whether the product has substantial
 commercial, industrial or non-consumer uses, unless such uses represent
 the only significant mode of use of the product.
  "Installation Information" for a User Product means any methods,
 procedures, authorization keys, or other information required to install
 and execute modified versions of a covered work in that User Product from
 a modified version of its Corresponding Source.  The information must
 suffice to ensure that the continued functioning of the modified object
 code is in no case prevented or interfered with solely because
 modification has been made.
  If you convey an object code work under this section in, or with, or
 specifically for use in, a User Product, and the conveying occurs as
 part of a transaction in which the right of possession and use of the
 User Product is transferred to the recipient in perpetuity or for a
 fixed term (regardless of how the transaction is characterized), the
 Corresponding Source conveyed under this section must be accompanied
 by the Installation Information.  But this requirement does not apply
 if neither you nor any third party retains the ability to install
 modified object code on the User Product (for example, the work has
 been installed in ROM).
  The requirement to provide Installation Information does not include a
 requirement to continue to provide support service, warranty, or updates
 for a work that has been modified or installed by the recipient, or for
 the User Product in which it has been modified or installed.  Access to a
 network may be denied when the modification itself materially and
 adversely affects the operation of the network or violates the rules and
 protocols for communication across the network.
  Corresponding Source conveyed, and Installation Information provided,
 in accord with this section must be in a format that is publicly
 documented (and with an implementation available to the public in
 source code form), and must require no special password or key for
 unpacking, reading or copying.
  7. Additional Terms.
  "Additional permissions" are terms that supplement the terms of this
 License by making exceptions from one or more of its conditions.
 Additional permissions that are applicable to the entire Program shall
 be treated as though they were included in this License, to the extent
 that they are valid under applicable law.  If additional permissions
 apply only to part of the Program, that part may be used separately
 under those permissions, but the entire Program remains governed by
 this License without regard to the additional permissions.
  When you convey a copy of a covered work, you may at your option
 remove any additional permissions from that copy, or from any part of
 it.  (Additional permissions may be written to require their own
 removal in certain cases when you modify the work.)  You may place
 additional permissions on material, added by you to a covered work,
 for which you have or can give appropriate copyright permission.
  Notwithstanding any other provision of this License, for material you
 add to a covered work, you may (if authorized by the copyright holders of
 that material) supplement the terms of this License with terms:
    a) Disclaiming warranty or limiting liability differently from the
    terms of sections 15 and 16 of this License; or
    b) Requiring preservation of specified reasonable legal notices or
    author attributions in that material or in the Appropriate Legal
    Notices displayed by works containing it; or
    c) Prohibiting misrepresentation of the origin of that material, or
    requiring that modified versions of such material be marked in
    reasonable ways as different from the original version; or
    d) Limiting the use for publicity purposes of names of licensors or
    authors of the material; or
    e) Declining to grant rights under trademark law for use of some
    trade names, trademarks, or service marks; or
    f) Requiring indemnification of licensors and authors of that
    material by anyone who conveys the material (or modified versions of
    it) with contractual assumptions of liability to the recipient, for
    any liability that these contractual assumptions directly impose on
    those licensors and authors.
  All other non-permissive additional terms are considered "further
 restrictions" within the meaning of section 10.  If the Program as you
 received it, or any part of it, contains a notice stating that it is
 governed by this License along with a term that is a further
 restriction, you may remove that term.  If a license document contains
 a further restriction but permits relicensing or conveying under this
 License, you may add to a covered work material governed by the terms
 of that license document, provided that the further restriction does
 not survive such relicensing or conveying.
  If you add terms to a covered work in accord with this section, you
 must place, in the relevant source files, a statement of the
 additional terms that apply to those files, or a notice indicating
 where to find the applicable terms.
  Additional terms, permissive or non-permissive, may be stated in the
 form of a separately written license, or stated as exceptions;
 the above requirements apply either way.
  8. Termination.
  You may not propagate or modify a covered work except as expressly
 provided under this License.  Any attempt otherwise to propagate or
 modify it is void, and will automatically terminate your rights under
 this License (including any patent licenses granted under the third
 paragraph of section 11).
  However, if you cease all violation of this License, then your
 license from a particular copyright holder is reinstated (a)
 provisionally, unless and until the copyright holder explicitly and
 finally terminates your license, and (b) permanently, if the copyright
 holder fails to notify you of the violation by some reasonable means
 prior to 60 days after the cessation.
  Moreover, your license from a particular copyright holder is
 reinstated permanently if the copyright holder notifies you of the
 violation by some reasonable means, this is the first time you have
 received notice of violation of this License (for any work) from that
 copyright holder, and you cure the violation prior to 30 days after
 your receipt of the notice.
  Termination of your rights under this section does not terminate the
 licenses of parties who have received copies or rights from you under
 this License.  If your rights have been terminated and not permanently
 reinstated, you do not qualify to receive new licenses for the same
 material under section 10.
  9. Acceptance Not Required for Having Copies.
  You are not required to accept this License in order to receive or
 run a copy of the Program.  Ancillary propagation of a covered work
 occurring solely as a consequence of using peer-to-peer transmission
 to receive a copy likewise does not require acceptance.  However,
 nothing other than this License grants you permission to propagate or
 modify any covered work.  These actions infringe copyright if you do
 not accept this License.  Therefore, by modifying or propagating a
 covered work, you indicate your acceptance of this License to do so.
  10. Automatic Licensing of Downstream Recipients.
  Each time you convey a covered work, the recipient automatically
 receives a license from the original licensors, to run, modify and
 propagate that work, subject to this License.  You are not responsible
 for enforcing compliance by third parties with this License.
  An "entity transaction" is a transaction transferring control of an
 organization, or substantially all assets of one, or subdividing an
 organization, or merging organizations.  If propagation of a covered
 work results from an entity transaction, each party to that
 transaction who receives a copy of the work also receives whatever
 licenses to the work the party's predecessor in interest had or could
 give under the previous paragraph, plus a right to possession of the
 Corresponding Source of the work from the predecessor in interest, if
 the predecessor has it or can get it with reasonable efforts.
  You may not impose any further restrictions on the exercise of the
 rights granted or affirmed under this License.  For example, you may
 not impose a license fee, royalty, or other charge for exercise of
 rights granted under this License, and you may not initiate litigation
 (including a cross-claim or counterclaim in a lawsuit) alleging that
 any patent claim is infringed by making, using, selling, offering for
 sale, or importing the Program or any portion of it.
  11. Patents.
  A "contributor" is a copyright holder who authorizes use under this
 License of the Program or a work on which the Program is based.  The
 work thus licensed is called the contributor's "contributor version".
  A contributor's "essential patent claims" are all patent claims
 owned or controlled by the contributor, whether already acquired or
 hereafter acquired, that would be infringed by some manner, permitted
 by this License, of making, using, or selling its contributor version,
 but do not include claims that would be infringed only as a
 consequence of further modification of the contributor version.  For
 purposes of this definition, "control" includes the right to grant
 patent sublicenses in a manner consistent with the requirements of
 this License.
  Each contributor grants you a non-exclusive, worldwide, royalty-free
 patent license under the contributor's essential patent claims, to
 make, use, sell, offer for sale, import and otherwise run, modify and
 propagate the contents of its contributor version.
  In the following three paragraphs, a "patent license" is any express
 agreement or commitment, however denominated, not to enforce a patent
 (such as an express permission to practice a patent or covenant not to
 sue for patent infringement).  To "grant" such a patent license to a
 party means to make such an agreement or commitment not to enforce a
 patent against the party.
  If you convey a covered work, knowingly relying on a patent license,
 and the Corresponding Source of the work is not available for anyone
 to copy, free of charge and under the terms of this License, through a
 publicly available network server or other readily accessible means,
 then you must either (1) cause the Corresponding Source to be so
 available, or (2) arrange to deprive yourself of the benefit of the
 patent license for this particular work, or (3) arrange, in a manner
 consistent with the requirements of this License, to extend the patent
 license to downstream recipients.  "Knowingly relying" means you have
 actual knowledge that, but for the patent license, your conveying the
 covered work in a country, or your recipient's use of the covered work
 in a country, would infringe one or more identifiable patents in that
 country that you have reason to believe are valid.
  If, pursuant to or in connection with a single transaction or
 arrangement, you convey, or propagate by procuring conveyance of, a
 covered work, and grant a patent license to some of the parties
 receiving the covered work authorizing them to use, propagate, modify
 or convey a specific copy of the covered work, then the patent license
 you grant is automatically extended to all recipients of the covered
 work and works based on it.
  A patent license is "discriminatory" if it does not include within
 the scope of its coverage, prohibits the exercise of, or is
 conditioned on the non-exercise of one or more of the rights that are
 specifically granted under this License.  You may not convey a covered
 work if you are a party to an arrangement with a third party that is
 in the business of distributing software, under which you make payment
 to the third party based on the extent of your activity of conveying
 the work, and under which the third party grants, to any of the
 parties who would receive the covered work from you, a discriminatory
 patent license (a) in connection with copies of the covered work
 conveyed by you (or copies made from those copies), or (b) primarily
 for and in connection with specific products or compilations that
 contain the covered work, unless you entered into that arrangement,
 or that patent license was granted, prior to 28 March 2007.
  Nothing in this License shall be construed as excluding or limiting
 any implied license or other defenses to infringement that may
 otherwise be available to you under applicable patent law.
  12. No Surrender of Others' Freedom.
  If conditions are imposed on you (whether by court order, agreement or
 otherwise) that contradict the conditions of this License, they do not
 excuse you from the conditions of this License.  If you cannot convey a
 covered work so as to satisfy simultaneously your obligations under this
 License and any other pertinent obligations, then as a consequence you may
 not convey it at all.  For example, if you agree to terms that obligate you
 to collect a royalty for further conveying from those to whom you convey
 the Program, the only way you could satisfy both those terms and this
 License would be to refrain entirely from conveying the Program.
  13. Use with the GNU Affero General Public License.
  Notwithstanding any other provision of this License, you have
 permission to link or combine any covered work with a work licensed
 under version 3 of the GNU Affero General Public License into a single
 combined work, and to convey the resulting work.  The terms of this
 License will continue to apply to the part which is the covered work,
 but the special requirements of the GNU Affero General Public License,
 section 13, concerning interaction through a network will apply to the
 combination as such.
  14. Revised Versions of this License.
  The Free Software Foundation may publish revised and/or new versions of
 the GNU General Public License from time to time.  Such new versions will
 be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.
  Each version is given a distinguishing version number.  If the
 Program specifies that a certain numbered version of the GNU General
 Public License "or any later version" applies to it, you have the
 option of following the terms and conditions either of that numbered
 version or of any later version published by the Free Software
 Foundation.  If the Program does not specify a version number of the
 GNU General Public License, you may choose any version ever published
 by the Free Software Foundation.
  If the Program specifies that a proxy can decide which future
 versions of the GNU General Public License can be used, that proxy's
 public statement of acceptance of a version permanently authorizes you
 to choose that version for the Program.
  Later license versions may give you additional or different
 permissions.  However, no additional obligations are imposed on any
 author or copyright holder as a result of your choosing to follow a
 later version.
  15. Disclaimer of Warranty.
  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
 APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
 HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
 OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
 THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
 IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
 ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
  16. Limitation of Liability.
  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
 WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
 THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
 GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
 USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
 DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
 PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
 EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
 SUCH DAMAGES.
  17. Interpretation of Sections 15 and 16.
  If the disclaimer of warranty and limitation of liability provided
 above cannot be given local legal effect according to their terms,
 reviewing courts shall apply local law that most closely approximates
 an absolute waiver of all civil liability in connection with the
 Program, unless a warranty or assumption of liability accompanies a
 copy of the Program in return for a fee.
                     END OF TERMS AND CONDITIONS
            How to Apply These Terms to Your New Programs
  If you develop a new program, and you want it to be of the greatest
 possible use to the public, the best way to achieve this is to make it
 free software which everyone can redistribute and change under these terms.
  To do so, attach the following notices to the program.  It is safest
 to attach them to the start of each source file to most effectively
 state the exclusion of warranty; and each file should have at least
 the "copyright" line and a pointer to where the full notice is found.
    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>
    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.
    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.
    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.
 Also add information on how to contact you by electronic and paper mail.
  If the program does terminal interaction, make it output a short
 notice like this when it starts in an interactive mode:
    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.
 The hypothetical commands `show w' and `show c' should show the appropriate
 parts of the General Public License.  Of course, your program's commands
 might be different; for a GUI interface, you would use an "about box".
  You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU GPL, see
 <https://www.gnu.org/licenses/>.
  The GNU General Public License does not permit incorporating your program
 into proprietary programs.  If your program is a subroutine library, you
 may consider it more useful to permit linking proprietary applications with
 the library.  If this is what you want to do, use the GNU Lesser General
 Public License instead of this License.  But first, please read
 <https://www.gnu.org/licenses/why-not-lgpl.html>.
@@ -1,12 +0,0 @@
 # Test Double-Click File Opening
 This is a test file to verify double-click functionality.
 ## Features to Test
 - File should load automatically
 - Content should display in editor
 - Tab should show filename
 - Preview should render markdown
 **This text should be bold**
 *This text should be italic*
@@ -1,378 +0,0 @@
 \hypertarget{panconverter}{%
 \section{PanConverter}\label{panconverter}}
 A cross-platform Markdown editor and converter powered by Pandoc.
 \begin{figure}
 \centering
 \includegraphics{assets/icon.png}
 \caption{PanConverter}
 \end{figure}
 \hypertarget{features}{%
 \subsection{Features}\label{features}}
 \hypertarget{advanced-markdown-editor}{%
 \subsubsection{✨ Advanced Markdown
 Editor}\label{advanced-markdown-editor}}
 \begin{itemize}
 \tightlist
 \item
  🗂️ \textbf{Tabbed Interface} - Work with multiple files simultaneously
  in separate tabs
 \item
  📝 \textbf{Rich Text Editor} - Full-featured editor with syntax
  highlighting and comprehensive toolbar
 \item
  🔍 \textbf{Find \& Replace} - Powerful search and replace with match
  highlighting and navigation
 \item
  🔢 \textbf{Line Numbers} - Toggle line numbers for easier code editing
  and navigation
 \item
  ↩️ \textbf{Smart Auto-Indentation} - Automatic list continuation and
  intelligent indentation
 \item
  ⏪ \textbf{Undo/Redo} - Full undo/redo support with keyboard shortcuts
 \item
  ⌨️ \textbf{Advanced Shortcuts} - Tab indentation, line selection, and
  smart text formatting
 \item
  📂 \textbf{File Association Support} - Open markdown files directly
  from file manager
 \end{itemize}
 \hypertarget{themes-interface}{%
 \subsubsection{🎨 Themes \& Interface}\label{themes-interface}}
 \begin{itemize}
 \tightlist
 \item
  👁️ \textbf{Live Preview} - See your markdown rendered in real-time
  with synchronized scrolling
 \item
  🎨 \textbf{Multiple Themes} - Choose from Light, Dark, Solarized,
  Monokai, or GitHub themes
 \item
  💾 \textbf{Auto-Save} - Never lose your work with automatic saving
  every 30 seconds
 \end{itemize}
 \hypertarget{export-conversion}{%
 \subsubsection{📤 Export \& Conversion}\label{export-conversion}}
 \begin{itemize}
 \tightlist
 \item
  📄 \textbf{Enhanced PDF Export} - Robust PDF generation with multiple
  LaTeX engine fallbacks (XeLaTeX, PDFLaTeX, wkhtmltopdf)
 \item
  📄 \textbf{Document Export} - Convert to HTML, DOCX, LaTeX, RTF, ODT,
  EPUB, PowerPoint (PPTX), and OpenDocument Presentation (ODP)
 \item
  📊 \textbf{Spreadsheet Export} - Export markdown tables to Excel
  (XLSX/XLS) and OpenDocument Spreadsheet (ODS) formats
 \item
  📥 \textbf{Document Import} - Import DOCX, ODT, RTF, HTML, PDF, and
  presentation files to markdown
 \item
  📋 \textbf{Table Creation Helper} - Built-in table generator for easy
  markdown table creation
 \end{itemize}
 \hypertarget{platform-support}{%
 \subsubsection{🖥️ Platform Support}\label{platform-support}}
 \begin{itemize}
 \tightlist
 \item
  \textbf{Cross-Platform} - Works seamlessly on Windows, macOS, and
  Linux
 \end{itemize}
 \hypertarget{installation}{%
 \subsection{Installation}\label{installation}}
 \hypertarget{prerequisites}{%
 \subsubsection{Prerequisites}\label{prerequisites}}
 \begin{itemize}
 \tightlist
 \item
  \href{https://pandoc.org/installing.html}{Pandoc} must be installed
  for export functionality
  \begin{itemize}
  \tightlist
  \item
    \textbf{Ubuntu/Debian}: \texttt{sudo\ apt-get\ install\ pandoc}
  \item
    \textbf{macOS}: \texttt{brew\ install\ pandoc}
  \item
    \textbf{Windows}: Download installer from Pandoc website
  \end{itemize}
 \end{itemize}
 \hypertarget{pdf-export-requirements}{%
 \subsubsection{PDF Export Requirements}\label{pdf-export-requirements}}
 For optimal PDF export, install a LaTeX engine (recommended): -
 \textbf{Ubuntu/Debian}:
 \texttt{sudo\ apt-get\ install\ texlive-xetex\ texlive-latex-base} -
 \textbf{macOS}: \texttt{brew\ install\ -\/-cask\ mactex} -
 \textbf{Windows}: Install MiKTeX or TeX Live - \textbf{Alternative}:
 \texttt{sudo\ apt-get\ install\ wkhtmltopdf} (fallback option)
 \hypertarget{download}{%
 \subsubsection{Download}\label{download}}
 Download the latest release for your platform from the
 \href{https://github.com/amitwh/pan-converter/releases}{Releases} page.
 \hypertarget{linux}{%
 \paragraph{Linux}\label{linux}}
 \begin{itemize}
 \tightlist
 \item
  \textbf{AppImage}: \texttt{PanConverter-1.3.1.AppImage} (universal,
  may require \texttt{-\/-no-sandbox} flag)
 \item
  \textbf{Debian Package}: \texttt{pan-converter\_1.3.1\_amd64.deb}
 \item
  \textbf{Snap Package}: \texttt{pan-converter\_1.3.1\_amd64.snap}
 \end{itemize}
 \hypertarget{install-from-source}{%
 \subsubsection{Install from Source}\label{install-from-source}}
 \begin{Shaded}
 \begin{Highlighting}[]
 \FunctionTok{git}\NormalTok{ clone https://github.com/amitwh/pan{-}converter.git}
 \BuiltInTok{cd}\NormalTok{ pan{-}converter}
 \ExtensionTok{npm}\NormalTok{ install}
 \ExtensionTok{npm}\NormalTok{ start}
 \end{Highlighting}
 \end{Shaded}
 \hypertarget{usage}{%
 \subsection{Usage}\label{usage}}
 \hypertarget{basic-workflow}{%
 \subsubsection{Basic Workflow}\label{basic-workflow}}
 \begin{enumerate}
 \def\labelenumi{\arabic{enumi}.}
 \tightlist
 \item
  \textbf{Write} - Use the editor to write your Markdown content
 \item
  \textbf{Preview} - Toggle the preview pane to see rendered output
 \item
  \textbf{Theme} - Choose your preferred theme from the View menu
 \item
  \textbf{Export} - Export your document to various formats
 \end{enumerate}
 \hypertarget{export-options}{%
 \subsubsection{Export Options}\label{export-options}}
 \begin{itemize}
 \tightlist
 \item
  \textbf{Documents}: HTML, PDF, DOCX, LaTeX, RTF, ODT, EPUB
 \item
  \textbf{Presentations}: PowerPoint (PPTX), OpenDocument Presentation
  (ODP)
 \item
  \textbf{Spreadsheets}: Excel (XLSX/XLS), OpenDocument Spreadsheet
  (ODS)
 \end{itemize}
 \hypertarget{import-conversion}{%
 \subsubsection{Import \& Conversion}\label{import-conversion}}
 \begin{itemize}
 \tightlist
 \item
  \textbf{Import Documents}: Convert DOCX, ODT, RTF, HTML, PDF, and
  presentation files to Markdown
 \item
  \textbf{Cross-Format Conversion}: Convert current file between
  multiple formats
 \item
  \textbf{Smart Presentation Handling}: Automatic slide-level formatting
  for PPTX/ODP exports
 \end{itemize}
 \hypertarget{table-creation}{%
 \subsubsection{Table Creation}\label{table-creation}}
 \begin{itemize}
 \tightlist
 \item
  Click the table button in the toolbar
 \item
  Specify number of rows and columns
 \item
  Automatically generates properly formatted Markdown tables
 \end{itemize}
 \hypertarget{keyboard-shortcuts}{%
 \subsection{Keyboard Shortcuts}\label{keyboard-shortcuts}}
 \hypertarget{file-operations}{%
 \subsubsection{File Operations}\label{file-operations}}
 \begin{itemize}
 \tightlist
 \item
  \texttt{Ctrl/Cmd\ +\ N} - New file/tab
 \item
  \texttt{Ctrl/Cmd\ +\ T} - New tab
 \item
  \texttt{Ctrl/Cmd\ +\ W} - Close current tab
 \item
  \texttt{Ctrl/Cmd\ +\ Tab} - Switch to next tab
 \item
  \texttt{Ctrl/Cmd\ +\ O} - Open file
 \item
  \texttt{Ctrl/Cmd\ +\ S} - Save file
 \item
  \texttt{Ctrl/Cmd\ +\ Shift\ +\ S} - Save as
 \item
  \texttt{Ctrl/Cmd\ +\ I} - Import document
 \end{itemize}
 \hypertarget{editor-features}{%
 \subsubsection{Editor Features}\label{editor-features}}
 \begin{itemize}
 \tightlist
 \item
  \texttt{Ctrl/Cmd\ +\ F} - Find \& Replace
 \item
  \texttt{Ctrl/Cmd\ +\ Z} - Undo
 \item
  \texttt{Ctrl/Cmd\ +\ Shift\ +\ Z} - Redo
 \item
  \texttt{Tab} - Indent lines or insert 4 spaces
 \item
  \texttt{Shift\ +\ Tab} - Outdent selected lines
 \item
  \texttt{Enter} - Auto-continue lists with proper indentation
 \end{itemize}
 \hypertarget{view-navigation}{%
 \subsubsection{View \& Navigation}\label{view-navigation}}
 \begin{itemize}
 \tightlist
 \item
  \texttt{Ctrl/Cmd\ +\ P} - Toggle preview
 \item
  \texttt{Ctrl/Cmd\ +\ Enter} - Toggle preview (alternative)
 \item
  \texttt{Escape} - Close find dialog
 \end{itemize}
 \hypertarget{building}{%
 \subsection{Building}\label{building}}
 \begin{Shaded}
 \begin{Highlighting}[]
 \CommentTok{\# Install dependencies}
 \ExtensionTok{npm}\NormalTok{ install}
 \CommentTok{\# Generate icons}
 \ExtensionTok{npm}\NormalTok{ run generate{-}icons}
 \CommentTok{\# Build for current platform}
 \ExtensionTok{npm}\NormalTok{ run build}
 \CommentTok{\# Build for specific platform}
 \ExtensionTok{npm}\NormalTok{ run build:win    }\CommentTok{\# Windows}
 \ExtensionTok{npm}\NormalTok{ run build:mac    }\CommentTok{\# macOS  }
 \ExtensionTok{npm}\NormalTok{ run build:linux  }\CommentTok{\# Linux (generates .deb, .AppImage, and .snap)}
 \CommentTok{\# Build for all platforms}
 \ExtensionTok{npm}\NormalTok{ run dist:all}
 \end{Highlighting}
 \end{Shaded}
 \hypertarget{version-history}{%
 \subsection{Version History}\label{version-history}}
 \begin{itemize}
 \tightlist
 \item
  \textbf{v1.3.1} - Bug fixes: Fixed file associations for
  double-clicking .md files, corrected 50/50 layout alignment for
  editor/preview panes
 \item
  \textbf{v1.3.0} - Major update: Tabbed interface for multiple files,
  enhanced PDF export with LaTeX engines, fixed file associations,
  removed redundant converter menu, improved UI architecture
 \item
  \textbf{v1.2.1} - Comprehensive editor enhancements: Find \& Replace,
  Line Numbers, Undo/Redo, Auto-indentation, PowerPoint export, document
  conversion menu, table creation helper, spreadsheet export
 \item
  \textbf{v1.1.0} - Added Excel/ODS spreadsheet export, updated author
  information, renamed to PanConverter
 \item
  \textbf{v1.0.0} - Initial release with basic markdown editing, themes,
  and Pandoc export
 \end{itemize}
 \hypertarget{known-issues}{%
 \subsection{Known Issues}\label{known-issues}}
 \begin{itemize}
 \tightlist
 \item
  AppImage may require \texttt{-\/-no-sandbox} flag on some Linux
  systems
 \item
  Windows/Mac builds require platform-specific build environments
 \item
  Large files may cause performance issues
 \end{itemize}
 \hypertarget{contributing}{%
 \subsection{Contributing}\label{contributing}}
 Contributions are welcome! Please feel free to submit a Pull Request to
 the \href{https://github.com/amitwh/pan-converter}{GitHub repository}.
 \hypertarget{license}{%
 \subsection{License}\label{license}}
 MIT License - see LICENSE file for details.
 \hypertarget{author}{%
 \subsection{Author}\label{author}}
 \textbf{Amit Haridas} -
 \href{mailto:amit.wh@gmail.com}{\nolinkurl{amit.wh@gmail.com}}
 \hypertarget{acknowledgments}{%
 \subsection{Acknowledgments}\label{acknowledgments}}
 \begin{itemize}
 \tightlist
 \item
  Built with \href{https://www.electronjs.org/}{Electron}
 \item
  Markdown parsing by \href{https://marked.js.org/}{marked}
 \item
  Export functionality powered by \href{https://pandoc.org/}{Pandoc}
 \item
  Syntax highlighting by \href{https://highlightjs.org/}{highlight.js}
 \item
  Spreadsheet export by \href{https://www.npmjs.com/package/xlsx}{XLSX}
 \item
  HTML sanitization by
  \href{https://www.npmjs.com/package/dompurify}{DOMPurify}
 \end{itemize}
@@ -1,180 +0,0 @@
 # MarkdownConverter
 A powerful cross-platform Markdown editor and document converter powered by Pandoc, built with Electron. 100% open-source with no proprietary dependencies.
 ## Features
 ### Markdown Editor
 <img width="1920" height="1032" alt="image" src="https://github.com/user-attachments/assets/5f53ba94-7663-47c3-b12b-b7b8bd2645aa" />
 - **Multi-tab editing** - Work on multiple files simultaneously
 - **Live preview** - Real-time markdown rendering with syntax highlighting
 - **Dynamic splitter** - Drag to resize editor and preview panes
 - **25+ themes** - Light and dark themes including Atom One Light, Dracula, Nord, Sepia, and more
 - **Find & Replace** - Search and replace with regex support
 - **Line numbers** - Toggle line numbers in the editor
 - **Auto-save** - Automatic saving every 30 seconds
 - **Math support** - KaTeX integration for mathematical expressions
 ### PDF Viewer & Editor
 <img width="1920" height="1032" alt="image" src="https://github.com/user-attachments/assets/f10f62be-af3d-496e-81df-37ab4f91abfd" />
 - **Built-in PDF viewer** - Open and view PDF files directly in the app
 - **Page navigation** - Navigate pages with keyboard or buttons
 - **Zoom controls** - Zoom in/out, fit to width, fit to page
 - **Rotation** - Rotate pages left or right
 - **PDF Editor tools**:
  - Merge multiple PDFs
  - Split PDFs by page range
  - Compress PDFs
  - Rotate pages
  - Delete pages
  - Reorder pages
  - Add watermarks
  - Password protection
  - Remove passwords
  - Set permissions
 ### Export Options
 - **PDF** - Export to PDF with customizable page sizes and orientation
 - **DOCX** - Standard and Enhanced (template-based) Word export
 - **ODT** - OpenDocument format
 - **HTML** - Web-ready HTML export
 - **PowerPoint** - PPTX presentation export
 - **EPUB** - E-book format
 - **LaTeX** - Academic document format
 - **RTF** - Rich Text Format
 ### Advanced Features
 - **Custom headers & footers** - Add headers/footers to exports with dynamic fields
 - **Page size configuration** - A3, A4, A5, B4, B5, Letter, Legal, Tabloid, or custom sizes
 - **Batch conversion** - Convert entire folders of markdown files
 - **ASCII Art Generator** - Create text banners and diagrams
 - **Word templates** - Use custom Word templates for enhanced exports
 - **Import documents** - Import from 30+ formats (DOCX, PDF, HTML, etc.)
 ## Installation
 ### Prerequisites
 - [Node.js](https://nodejs.org/) (v16 or later)
 - [Pandoc](https://pandoc.org/installing.html) (required for export functionality)
 ### Install Dependencies
 ```bash
 npm install
 ```
 ### Run the Application
 ```bash
 npm start
 ```
 ### Build for Distribution
 ```bash
 # Windows
 npm run build:win
 # macOS
 npm run build:mac
 # Linux
 npm run build:linux
 ```
 ## Keyboard Shortcuts
 | Action | Shortcut |
 |--------|----------|
 | New File | Ctrl+N |
 | Open File | Ctrl+O |
 | Open PDF | Ctrl+Shift+O |
 | Save | Ctrl+S |
 | Save As | Ctrl+Shift+S |
 | Export | Ctrl+E |
 | Print | Ctrl+P |
 | Find | Ctrl+F |
 | Undo | Ctrl+Z |
 | Redo | Ctrl+Shift+Z |
 | New Tab | Ctrl+T |
 | Close Tab | Ctrl+W |
 | Toggle Preview | Ctrl+Shift+P |
 | Zoom In | Ctrl+Shift++ |
 | Zoom Out | Ctrl+Shift+- |
 ## Themes
 ### Light Themes
 - Atom One Light (Default)
 - GitHub Light
 - Light
 - Solarized Light
 - Gruvbox Light
 - Ayu Light
 - Sepia
 - Paper
 - Rose Pine Dawn
 - Concrete Light
 ### Dark Themes
 - Dark
 - One Dark
 - Dracula
 - Nord
 - Monokai
 - Material
 - Gruvbox Dark
 - Tokyo Night
 - Palenight
 - Ayu Dark
 - Ayu Mirage
 - Oceanic Next
 - Cobalt2
 - Concrete Dark
 - Concrete Warm
 ## PDF Viewer
 Open PDF files directly in MarkdownConverter:
 - **File > Open PDF** or **Ctrl+Shift+O**
 - Navigate pages with arrow buttons or page input
 - Zoom controls: +/- buttons, Fit Width, Fit Page
 - Rotate pages left or right
 - Close PDF to return to editor
 ## Distribution & Updates
 v5.x uses `electron-updater` against two feeds:
 - **GitHub Releases** (default, public): the public release at `https://github.com/amitwh/markdown-converter/releases`. The CI workflow publishes `latest-{mac,linux,windows}.yml` on every tag.
 - **ConcreteInfo self-hosted** (opt-in for enterprise deployments): `https://updates.concreteinfo.co.in/v5/`. CI mirrors artifacts on every release when `CONCRETEINFO_DEPLOY_HOOK` is set as a repository secret.
 Users switch the feed in **Settings → Updates → Update channel**. Auto-check is enabled by default; disable it in the same panel.
 ### Manual mirror
 ```bash
 CONCRETEINFO_DEPLOY_HOOK=... npm run publish:concreteinfo -- 5.1.0
 ```
 ## Open Source
 MarkdownConverter is 100% open-source. All dependencies are permissively licensed:
 - **Electron** - MIT License
 - **pdf-lib** - MIT License
 - **pdfjs-dist** - Apache 2.0 License
 - **marked** - MIT License
 - **highlight.js** - BSD 3-Clause License
 - **dompurify** - Apache 2.0/MIT License
 - **docx** - MIT License
 - **xlsx** - Apache 2.0 License (SheetJS Community Edition)
 ## License
 MIT License - see LICENSE file for details.
 ## Author
 Amit Haridas (amit.wh@gmail.com)
 ## Version
 v4.1.0
@@ -1,217 +0,0 @@
 # PanConverter - Updates & Changelog
 ## Version 4.0.0 (2026-03-04)
 ### Major Changes
 - **CodeMirror 6 Editor** — Replaced textarea with CodeMirror 6 featuring syntax highlighting, code folding, bracket matching, multiple cursors, and auto-indent
 - **Sidebar Panel System** — Collapsible sidebar with File Explorer, Git, Snippets, and Templates panels
 - **Command Palette** — Ctrl+Shift+P to search and execute all app actions
 - **Code Execution (REPL)** — Run JavaScript, Python, and Bash code blocks directly from the preview
 ### New Features
 - Print Preview dialog with paper size, orientation, margins, scale, and page range controls
 - Image paste from clipboard and drag-drop support with auto-save to assets folder
 - Document templates library (10 templates: blog post, meeting notes, tech spec, changelog, README, project plan, API docs, tutorial, release notes, comparison)
 - Markdown extensions: footnotes, admonitions (note/warning/tip/danger/info), and [[toc]] table of contents
 - PlantUML diagram rendering alongside Mermaid
 - Welcome tab with onboarding and "What's New" feature showcase
 - System spell checking with context menu suggestions and dictionary support
 - Enhanced status bar with word count, character count, line/column, encoding, and language mode
 - Grouped toolbar with visual section separators
 - Breadcrumb bar showing current file path
 ### New Export/Import Formats
 - Reveal.js slides (.html)
 - Beamer slides (.pdf)
 - Confluence/Jira wiki markup (.txt)
 - MOBI e-books (via Calibre)
 - Developer formats: JSON, YAML, XML, TOML
 ### Security
 - Content Security Policy (CSP) meta tag
 - File size validation (50MB limit)
 - Error message sanitization (stripped file paths)
 - Conversion rate limiting (2-second debounce)
 ### Dependencies Updated
 - marked: 16.x to 17.x (with marked-highlight extension)
 - pdfjs-dist: 3.x to 5.x (new worker model)
 - html2pdf.js: 0.10 to 0.14
 - pdfkit: 0.14 to 0.17
 - dompurify, docx, and others updated to latest
 ### Testing
 - 80 tests across 7 test suites
 - New tests for sidebar manager, command palette, print preview, markdown extensions, and utility functions
 ### Breaking Changes
 - Editor is now CodeMirror 6 (replaces textarea)
 - marked API changed to use marked.use() instead of marked.setOptions()
 - pdfjs-dist upgraded to v5 with new worker model
 ---
 ## Version 2.1.0 (December 14, 2025)
 ### 🎨 UI/UX Improvements
 #### Subtle & Small Preview Popout Button
 - Redesigned popout button with minimalist aesthetic
 - Removed border for cleaner appearance
 - Reduced size: 11px font, 2px×6px padding (previously 14px font, 4px×8px padding)
 - Added opacity transition: 50% when idle, 100% on hover
 - Subtle background effect on hover instead of heavy border styling
 - **File**: `src/styles.css:195-211`
 #### Simplified Table Headers in Preview
 - Removed gradient background from table headers in modern theme
 - Changed from `var(--primary-gradient)` (purple gradient) to simple light gray (#f0f0f0)
 - Updated text color to dark (#333333) for better readability
 - Clean, professional appearance matching standard themes
 - **File**: `src/styles-modern.css:445-449`
 ### 📥 Enhanced Import Capabilities
 #### Comprehensive Format-to-Markdown Conversion
 Dramatically expanded the "Import Document" feature to support 30+ file formats:
 **Supported Formats:**
 - **Documents**: DOCX, ODT, RTF, HTML, HTM, TEX, EPUB, PDF, TXT
 - **Presentations**: PPTX, ODP
 - **Markup Languages**: RST, Textile, MediaWiki, Org-mode, AsciiDoc, TWiki, OPML
 - **E-book Formats**: EPUB, FB2
 - **LaTeX Formats**: TEX, LATEX, LTX
 - **Web Formats**: HTML, HTM, XHTML
 - **Wiki Formats**: MediaWiki, DokuWiki, TikiWiki, TWiki
 - **Data Formats**: CSV, TSV, JSON
 **Format-Specific Optimizations:**
 - PDF text extraction with XeLaTeX engine
 - CSV/TSV automatic table conversion
 - JSON structure handling
 - Improved error messages with format hints
 **Access**: File → Import Document (Ctrl+I)
 **File**: `src/main.js:1933-1994`
 ### 🎨 Exhaustive ASCII Art Generator
 #### 5 New Text Banner Styles
 Complete alphabet (A-Z) and numbers (0-9) support for all styles:
 1. **Standard** - Classic ASCII art with slashes and underscores
 2. **Banner** - Large format using # characters (7-line height)
 3. **Block** - Modern Unicode block characters (█ ╔ ╗ ═ ║)
 4. **Bubble** - Circular bubble letters (Ⓐ Ⓑ Ⓒ)
 5. **Digital** - Digital display style (▄ ▀ ▐ ▌)
 **File**: `src/renderer.js:3397-3537`
 #### 19 Professional ASCII Templates
 Organized into 4 categories with expanded options:
 **Arrows & Flow (4 templates):**
 - Arrow Right - Horizontal flow indicators
 - Arrow Down - Vertical flow indicators
 - Decision - Binary decision diagrams
 - Process Flow - Multi-step process visualization
 **Diagrams & Charts (6 templates):**
 - Flowchart - Advanced flowchart with decision branches and loops
 - Sequence - Sequence diagrams for User-System-Database interactions
 - Network - Server-client network topology
 - Hierarchy - Organizational tree structures
 - Timeline - Milestone visualization with dates
 - Table Simple - Basic table template with borders
 **Boxes & Containers (4 templates):**
 - Header - Section header with decorative borders
 - Note Box - Important notes with rounded corners (┏━━┓)
 - Warning Box - Warning messages with bold borders (╔═══╗)
 - Info Box - Information boxes with subtle styling (╭───╮)
 **Decorative Elements (6 templates):**
 - Divider - Horizontal section separator (═══)
 - Separator Fancy - Elegant rounded divider
 - Brackets - Japanese-style brackets 【 】
 - Banner Stars - Star-bordered banners
 - Checklist - Task lists with ✓ checkmarks
 - Progress Bar - Visual progress indicators
 **Features:**
 - All ASCII art automatically wrapped in code blocks for proper rendering
 - Preserved formatting in markdown preview and all export formats
 - Categorized template selection interface
 - Real-time preview generation
 **Access**: Tools → ASCII Art Generator
 **Files**: `src/renderer.js:3513-3671`, `src/index.html:427-466`
 ### 📝 Technical Improvements
 - Enhanced ASCII art detection in Word template exporter
 - Improved monospace font rendering across all export formats
 - Better code block preservation in PDF and Word exports
 - Optimized template categorization and organization
 ### 🔧 Files Modified
 - `src/styles.css` - Preview popout button styling
 - `src/styles-modern.css` - Table header simplification
 - `src/main.js` - Enhanced import function, version update
 - `src/renderer.js` - ASCII art generator enhancements
 - `src/index.html` - ASCII template UI organization
 - `package.json` - Version bump to 2.1.0
 ---
 ## Version 2.0.0 (Previous Release)
 ### Major Features
 - Export Profiles - Save and reuse export configurations
 - Mermaid.js diagram support
 - Command Palette (Ctrl+Shift+P)
 - GitHub Light/Dark preview themes
 - Table Generator
 - ASCII Art Generator (basic)
 - Resizable Preview Pane
 - Pop-out Preview Window
 - Configurable page sizes (A3-A5, B4-B5, Letter, Legal, Tabloid, Custom)
 - Custom Headers & Footers for exports
 - Enhanced PDF and Word export with templates
 - 22 beautiful themes
 ### Core Capabilities
 - Cross-platform markdown editor with live preview
 - Universal document conversion (30+ formats)
 - PDF Editor (merge, split, compress, rotate, watermark, encrypt)
 - Batch file conversion
 - File association support
 - Advanced export options
 - Multi-tab interface
 ---
 ## Installation & Usage
 ### Prerequisites
 - **Pandoc** - Required for document conversion
 - **Optional**: LibreOffice, ImageMagick, FFmpeg for universal converter
 ### Download
 Get the latest release from: https://github.com/amitwh/pan-converter/releases
 ### Supported Platforms
 - Windows (x64)
 - Linux (AppImage, .deb, .snap)
 - macOS (planned)
 ---
 ## Contributing
 Contributions are welcome! Please see [CLAUDE.md](CLAUDE.md) for development guidelines.
 **Author**: Amit Haridas (amit.wh@gmail.com)
 **License**: MIT
 **Repository**: https://github.com/amitwh/pan-converter
@@ -1,93 +0,0 @@
 Copyright (c) 2014, The Fira Code Project Authors (https://github.com/tonsky/FiraCode)
 This Font Software is licensed under the SIL Open Font License, Version 1.1.
 This license is copied below, and is also available with a FAQ at:
 http://scripts.sil.org/OFL
 -----------------------------------------------------------
 SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
 -----------------------------------------------------------
 PREAMBLE
 The goals of the Open Font License (OFL) are to stimulate worldwide
 development of collaborative font projects, to support the font creation
 efforts of academic and linguistic communities, and to provide a free and
 open framework in which fonts may be shared and improved in partnership
 with others.
 The OFL allows the licensed fonts to be used, studied, modified and
 redistributed freely as long as they are not sold by themselves. The
 fonts, including any derivative works, can be bundled, embedded,
 redistributed and/or sold with any software provided that any reserved
 names are not used by derivative works. The fonts and derivatives,
 however, cannot be released under any other type of license. The
 requirement for fonts to remain under this license does not apply
 to any document created using the fonts or their derivatives.
 DEFINITIONS
 "Font Software" refers to the set of files released by the Copyright
 Holder(s) under this license and clearly marked as such. This may
 include source files, build scripts and documentation.
 "Reserved Font Name" refers to any names specified as such after the
 copyright statement(s).
 "Original Version" refers to the collection of Font Software components as
 distributed by the Copyright Holder(s).
 "Modified Version" refers to any derivative made by adding to, deleting,
 or substituting -- in part or in whole -- any of the components of the
 Original Version, by changing formats or by porting the Font Software to a
 new environment.
 "Author" refers to any designer, engineer, programmer, technical
 writer or other person who contributed to the Font Software.
 PERMISSION & CONDITIONS
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of the Font Software, to use, study, copy, merge, embed, modify,
 redistribute, and sell modified and unmodified copies of the Font
 Software, subject to the following conditions:
 1) Neither the Font Software nor any of its individual components,
 in Original or Modified Versions, may be sold by itself.
 2) Original or Modified Versions of the Font Software may be bundled,
 redistributed and/or sold with any software, provided that each copy
 contains the above copyright notice and this license. These can be
 included either as stand-alone text files, human-readable headers or
 in the appropriate machine-readable metadata fields within text or
 binary files as long as those fields can be easily viewed by the user.
 3) No Modified Version of the Font Software may use the Reserved Font
 Name(s) unless explicit written permission is granted by the corresponding
 Copyright Holder. This restriction only applies to the primary font name as
 presented to the users.
 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
 Software shall not be used to promote, endorse or advertise any
 Modified Version, except to acknowledge the contribution(s) of the
 Copyright Holder(s) and the Author(s) or with their explicit written
 permission.
 5) The Font Software, modified or unmodified, in part or in whole,
 must be distributed entirely under this license, and must not be
 distributed under any other license. The requirement for fonts to
 remain under this license does not apply to any document created
 using the Font Software.
 TERMINATION
 This license becomes null and void if any of the above conditions are
 not met.
 DISCLAIMER
 THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
 OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
 COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
 INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
 DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
 OTHER DEALINGS IN THE FONT SOFTWARE.
@@ -1,93 +0,0 @@
 Copyright 2020 The JetBrains Mono Project Authors (https://github.com/JetBrains/JetBrainsMono)
 This Font Software is licensed under the SIL Open Font License, Version 1.1.
 This license is copied below, and is also available with a FAQ at:
 https://scripts.sil.org/OFL
 -----------------------------------------------------------
 SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
 -----------------------------------------------------------
 PREAMBLE
 The goals of the Open Font License (OFL) are to stimulate worldwide
 development of collaborative font projects, to support the font creation
 efforts of academic and linguistic communities, and to provide a free and
 open framework in which fonts may be shared and improved in partnership
 with others.
 The OFL allows the licensed fonts to be used, studied, modified and
 redistributed freely as long as they are not sold by themselves. The
 fonts, including any derivative works, can be bundled, embedded, 
 redistributed and/or sold with any software provided that any reserved
 names are not used by derivative works. The fonts and derivatives,
 however, cannot be released under any other type of license. The
 requirement for fonts to remain under this license does not apply
 to any document created using the fonts or their derivatives.
 DEFINITIONS
 "Font Software" refers to the set of files released by the Copyright
 Holder(s) under this license and clearly marked as such. This may
 include source files, build scripts and documentation.
 "Reserved Font Name" refers to any names specified as such after the
 copyright statement(s).
 "Original Version" refers to the collection of Font Software components as
 distributed by the Copyright Holder(s).
 "Modified Version" refers to any derivative made by adding to, deleting,
 or substituting -- in part or in whole -- any of the components of the
 Original Version, by changing formats or by porting the Font Software to a
 new environment.
 "Author" refers to any designer, engineer, programmer, technical
 writer or other person who contributed to the Font Software.
 PERMISSION & CONDITIONS
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of the Font Software, to use, study, copy, merge, embed, modify,
 redistribute, and sell modified and unmodified copies of the Font
 Software, subject to the following conditions:
 1) Neither the Font Software nor any of its individual components,
 in Original or Modified Versions, may be sold by itself.
 2) Original or Modified Versions of the Font Software may be bundled,
 redistributed and/or sold with any software, provided that each copy
 contains the above copyright notice and this license. These can be
 included either as stand-alone text files, human-readable headers or
 in the appropriate machine-readable metadata fields within text or
 binary files as long as those fields can be easily viewed by the user.
 3) No Modified Version of the Font Software may use the Reserved Font
 Name(s) unless explicit written permission is granted by the corresponding
 Copyright Holder. This restriction only applies to the primary font name as
 presented to the users.
 4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
 Software shall not be used to promote, endorse or advertise any
 Modified Version, except to acknowledge the contribution(s) of the
 Copyright Holder(s) and the Author(s) or with their explicit written
 permission.
 5) The Font Software, modified or unmodified, in part or in whole,
 must be distributed entirely under this license, and must not be
 distributed under any other license. The requirement for fonts to
 remain under this license does not apply to any document created
 using the Font Software.
 TERMINATION
 This license becomes null and void if any of the above conditions are
 not met.
 DISCLAIMER
 THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
 OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
 COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
 INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
 DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
 OTHER DEALINGS IN THE FONT SOFTWARE.
@@ -1,20 +0,0 @@
 {
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "new-york",
  "rsc": false,
  "tsx": true,
  "tailwind": {
    "config": "tailwind.config.js",
    "css": "src/renderer/styles/globals.css",
    "baseColor": "neutral",
    "cssVariables": true,
    "prefix": ""
  },
  "aliases": {
    "components": "@/components",
    "ui": "@/components/ui",
    "lib": "@/lib",
    "hooks": "@/hooks"
  },
  "iconLibrary": "lucide"
 }
@@ -1,866 +0,0 @@
 # MarkdownConverter - STRIDE Threat Model Analysis
 **Version:** 4.1.0
 **Date:** 2026-03-15
 **Methodology:** STRIDE + MITRE ATT&CK Mapping
 **Analyst:** Security Assessment Team
 ---
 ## Executive Summary
 This threat model analyzes the MarkdownConverter Electron application using the STRIDE methodology. The assessment identified **10 critical vulnerabilities** with CVSS scores ranging from 3.5 to 9.6. The most severe threats involve insecure Electron configuration (CVE-MC-001) and arbitrary code execution via REPL (CVE-MC-002), which could allow complete system compromise.
 **Risk Summary:**
 | Severity | Count | Total CVSS Impact |
 |----------|-------|-------------------|
 | Critical (9.0+) | 2 | 18.9 |
 | High (7.0-8.9) | 3 | 23.3 |
 | Medium (5.0-6.9) | 3 | 17.3 |
 | Low (<5.0) | 2 | 7.9 |
 ---
 ## 1. System Architecture Overview
 ### 1.1 Application Components
 ```
 +------------------------------------------------------------------+
 |                    MarkdownConverter v4.0.0                       |
 +------------------------------------------------------------------+
 |                                                                   |
 |  +------------------+     +------------------+                    |
 |  |   Main Process   |<--->|  Renderer Process|                    |
 |  |    (Node.js)     |     |   (Chromium)     |                    |
 |  +------------------+     +------------------+                    |
 |          |                        |                               |
 |          | IPC Channels           |                               |
 |          v                        v                               |
 |  +------------------+     +------------------+                    |
 |  |   preload.js     |     |   renderer.js    |                    |
 |  | (Bridge Layer)   |     | (UI Logic)       |                    |
 |  +------------------+     +------------------+                    |
 |          |                        |                               |
 |          v                        v                               |
 |  +--------------------------------------------------+             |
 |  |              External Tools                       |             |
 |  | Pandoc | FFmpeg | ImageMagick | LibreOffice      |             |
 |  +--------------------------------------------------+             |
 |                                                                   |
 +------------------------------------------------------------------+
                              |
                              v
 +------------------------------------------------------------------+
 |                    External Services                              |
 |  - plantuml.com (diagram rendering)                              |
 |  - cdn.jsdelivr.net (scripts)                                    |
 |  - cdnjs.cloudflare.com (styles)                                 |
 +------------------------------------------------------------------+
 ```
 ### 1.2 Data Flow Diagram (Level 1)
 ```
                              TRUST BOUNDARY
                                    |
    +-----------+                   |                   +-----------+
    |   User    |                   |                   |  System   |
    | (Author)  |------------------>|------------------>|   Files   |
    +-----------+   Markdown        |   File I/O        +-----------+
                    Content         |
                                    |
                    +---------------+---------------+
                    |                               |
                    v                               v
            +---------------+               +---------------+
            |    Editor     |               |   Preview     |
            | (CodeMirror)  |               |  (Rendered)   |
            +---------------+               +---------------+
                    |                               ^
                    |    Sanitization               |
                    |    (DOMPurify)                |
                    v                               |
            +---------------+                       |
            |   Renderer    |-----------------------+
            |   Process     |  HTML/SVG
            +---------------+
                    |
                    | IPC (Whitelisted Channels)
                    v
            +---------------+               +-----------+
            |    Main       |-------------->|  Pandoc   |
            |   Process     |  execFile     |  FFmpeg   |
            |   (Node.js)   |               |  etc.     |
            +---------------+               +-----------+
                    |
                    | HTTPS
                    v
            +---------------+
            |  PlantUML     |
            |  Server       |
            | (External)    |
            +---------------+
 ```
 ### 1.3 Trust Boundaries
 ```
 +============================================================================+
 ||                     TRUST BOUNDARY 1: User <-> Application               ||
 ||  - User input (markdown content) is UNTRUSTED                            ||
 ||  - File paths from dialogs are PARTIALLY TRUSTED                         ||
 +============================================================================+
                                    |
                                    v
 +============================================================================+
 ||                     TRUST BOUNDARY 2: Renderer <-> Main Process          ||
 ||  - IPC communication via preload.js                                       ||
 ||  - CRITICAL: nodeIntegration=true bypasses isolation                      ||
 +============================================================================+
                                    |
                                    v
 +============================================================================+
 ||                     TRUST BOUNDARY 3: Application <-> System             ||
 ||  - External tool execution (Pandoc, FFmpeg, etc.)                         ||
 ||  - File system access                                                     ||
 +============================================================================+
                                    |
                                    v
 +============================================================================+
 ||                     TRUST BOUNDARY 4: Application <-> Internet           ||
 ||  - PlantUML server (https://www.plantuml.com)                            ||
 ||  - CDN resources (jsdelivr, cdnjs)                                        ||
 +============================================================================+
 ```
 ---
 ## 2. STRIDE Analysis
 ### 2.1 Spoofing
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | S-01 | **PlantUML Server Spoofing** | Application sends diagram content to external PlantUML server. MITM or compromised server could return malicious SVG content. | CVE-MC-007 | 5.3 |
 | S-02 | **CDN Compromise** | Scripts loaded from cdn.jsdelivr.net and styles from cdnjs.cloudflare.com could be compromised in supply chain attack. | - | 6.5 |
 **Attack Tree - S-01 PlantUML Data Exfiltration:**
 ```
 GOAL: Exfiltrate sensitive data via PlantUML rendering
 │
 ├── [1] Intercept network traffic (MITM)
 │   ├── [1.1] Exploit weak TLS implementation
 │   └── [1.1] DNS hijacking
 │
 ├── [2] Compromise PlantUML server
 │   ├── [2.1] Server breach
 │   └── [2.2] Supply chain compromise
 │
 └── [3] Inject malicious SVG response
    ├── [3.1] XSS via SVG onload
    └── [3.2] Data exfiltration via image src
 ```
 ### 2.2 Tampering
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | T-01 | **Markdown Content Tampering** | XSS in markdown rendering could modify rendered content or inject malicious scripts. | CVE-MC-003 | 8.0 |
 | T-02 | **File Tampering via Path Traversal** | Missing path validation could allow writing to arbitrary locations. | CVE-MC-004 | 7.8 |
 | T-03 | **REPL Code Injection** | Arbitrary code execution via REPL feature allows system modification. | CVE-MC-002 | 9.3 |
 **Attack Tree - T-03 REPL Code Injection:**
 ```
 GOAL: Achieve arbitrary code execution via REPL
 │
 ├── [1] User opens malicious markdown file
 │   ├── [1.1] Phishing/social engineering
 │   └── [1.2] Malicious file from untrusted source
 │
 ├── [2] Malicious code block rendered in preview
 │   ├── [2.1] JavaScript code block
 │   ├── [2.2] Python code block
 │   └── [2.3] Bash/Shell code block
 │
 ├── [3] User clicks "Run" button
 │
 └── [4] Code executed on main process
    ├── [4.1] File system access
    ├── [4.2] Process execution
    └── [4.3] Network access
        └── [4.3.1] Data exfiltration
        └── [4.3.2] C2 communication
 ```
 ### 2.3 Repudiation
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | R-01 | **Missing Audit Logging** | No logging of security-relevant events (file access, code execution, exports). | - | 4.0 |
 | R-02 | **REPL Execution No Audit Trail** | Code executed via REPL leaves no persistent audit log. | CVE-MC-002 | 5.0 |
 ### 2.4 Information Disclosure
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | I-01 | **Path Disclosure in Error Messages** | Error messages may expose absolute file paths. Partially mitigated by `sanitizeErrorMessage()`. | - | 4.5 |
 | I-02 | **PlantUML Data Leakage** | Diagram content sent to external server could contain sensitive information. | CVE-MC-007 | 5.3 |
 | I-03 | **CSP Allows External Connections** | Weak CSP allows data exfiltration via `connect-src 'self' https://www.plantuml.com`. | CVE-MC-005 | 7.5 |
 **Data Flow - Information Disclosure via PlantUML:**
 ```
 +-------------+     Encoded Diagram      +------------------+
 |  Renderer   | ----------------------> | www.plantuml.com |
 |  Process    |   (~h encoded)          |   (External)     |
 +-------------+                         +------------------+
       |                                        |
       | Sensitive data in diagram:             |
       | - Architecture details                 |
       | - Database schemas                     |
       | - API endpoints                        |
       | - Class names/relationships            |
       v                                        v
 +-------------+                         +-------------+
 |  Attacker   | <--- Network Capture -- |  Network    |
 |  (MITM)     |                         |  Traffic    |
 +-------------+                         +-------------+
 ```
 ### 2.5 Denial of Service
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | D-01 | **REPL Resource Exhaustion** | Code execution has 10s timeout but could consume CPU/memory. | CVE-MC-002 | 4.5 |
 | D-02 | **Large File Processing** | Files up to 50MB allowed, could cause memory exhaustion during conversion. | - | 5.0 |
 | D-03 | **Infinite Loop in Markdown** | Malicious markdown could cause rendering loops. | - | 4.0 |
 ### 2.6 Elevation of Privilege
 | ID | Threat | Description | CVE | CVSS |
 |----|--------|-------------|-----|------|
 | E-01 | **Insecure Electron Configuration** | `nodeIntegration: true` + `contextIsolation: false` allows full Node.js access from renderer. | CVE-MC-001 | 9.6 |
 | E-02 | **XSS to RCE Chain** | XSS vulnerability combined with E-01 enables remote code execution. | CVE-MC-003 + CVE-MC-001 | 9.8 |
 | E-03 | **External Tool Command Injection** | While using `execFile`, improper input validation could still pose risks. | CVE-MC-009 | 4.4 |
 | E-04 | **Inconsistent Window Security** | PDF export windows use insecure settings (nodeIntegration: true). | CVE-MC-006 | 6.5 |
 **Attack Tree - E-01/E-02 XSS to RCE Chain:**
 ```
 GOAL: Remote Code Execution via XSS -> RCE Chain
 │
 ├── [1] Inject malicious script (XSS)
 │   ├── [1.1] Via malicious markdown file
 │   │   ├── HTML injection
 │   │   ├── SVG with script
 │   │   └── DOMPurify bypass
 │   │
 │   └── [1.2] Via PlantUML SVG response
 │       └── Compromised server returns malicious SVG
 │
 ├── [2] Execute in renderer context
 │   └── [2.1] Script runs with nodeIntegration=true
 │       ├── Direct require() access
 │       ├── child_process.exec()
 │       └── fs module access
 │
 └── [3] Achieve RCE
    ├── [3.1] Execute system commands
    ├── [3.2] Read/write arbitrary files
    ├── [3.3] Install persistence mechanisms
    └── [3.4] Lateral movement
 ```
 ---
 ## 3. Attack Scenarios
 ### 3.1 Scenario: Malicious Markdown Document (Critical)
 **Attack Chain:**
 ```
 1. Attacker creates malicious.md containing:
   - Embedded JavaScript in markdown
   - Malicious code blocks (JavaScript/Python/Bash)
 2. Victim opens file in MarkdownConverter
 3. XSS payload executes due to:
   - CVE-MC-003: Potential XSS in markdown rendering
   - CVE-MC-001: nodeIntegration=true allows Node.js access
 4. Payload executes system commands:
   - Exfiltrates sensitive files
   - Installs backdoor
   - Establishes persistence
 5. Impact: Complete system compromise
 ```
 **MITRE ATT&CK Mapping:**
 | Tactic | Technique | ID | Description |
 |--------|-----------|-----|-------------|
 | Initial Access | Phishing | T1566 | Malicious file via email |
 | Execution | User Execution | T1204 | Victim opens malicious file |
 | Execution | Command/Scripting | T1059 | JavaScript/Python execution |
 | Persistence | Registry Run Keys | T1547 | Establish persistence |
 | Collection | Data from Local System | T1005 | File exfiltration |
 | Exfiltration | Exfiltration Over C2 | T1041 | Data sent to attacker |
 ### 3.2 Scenario: REPL Code Execution (Critical)
 **Attack Chain:**
 ```
 1. Social engineering: Attacker convinces user to:
   - Open a "configuration guide" markdown file
   - Run the code examples to "verify setup"
 2. Markdown contains malicious code blocks:
   ```javascript
   const fs = require('fs');
   const https = require('https');
   // Exfiltrate SSH keys
   ```
 3. User clicks "Run" button on code block
 4. Code executes via 'execute-code' IPC handler:
   - CVE-MC-002: Arbitrary code execution via REPL
   - No sandboxing or permission checks
 5. Impact: Credential theft, data exfiltration
 ```
 **MITRE ATT&CK Mapping:**
 | Tactic | Technique | ID | Description |
 |--------|-----------|-----|-------------|
 | Initial Access | Phishing | T1566 | Social engineering |
 | Execution | Command/Scripting | T1059.004 | Bash execution |
 | Execution | Command/Scripting | T1059.007 | JavaScript/Node execution |
 | Credential Access | Credentials from Files | T1083 | SSH key theft |
 | Exfiltration | Exfiltration Over Web Service | T1567 | HTTPS exfiltration |
 ### 3.3 Scenario: PlantUML Data Exfiltration (Medium)
 **Attack Chain:**
 ```
 1. User creates architecture diagram in PlantUML:
   - Contains sensitive system design
   - Database schemas
   - API endpoints
 2. Renderer encodes and sends to www.plantuml.com:
   - CVE-MC-007: Data sent to external server
 3. Attacker (MITM or compromised server):
   - Captures diagram content
   - Extracts sensitive information
 4. Impact: Intellectual property theft, reconnaissance
 ```
 ### 3.4 Scenario: PDF Export Window Exploitation (Medium)
 **Attack Chain:**
 ```
 1. User exports document to PDF
 2. Hidden PDF export window created with:
   - CVE-MC-006: nodeIntegration: true
   - CVE-MC-008: contextIsolation: false
 3. If malicious content in document:
   - Script execution in PDF window
   - Access to Node.js APIs
 4. Impact: Code execution during export process
 ```
 ---
 ## 4. Risk Matrix & Prioritization
 ### 4.1 Vulnerability Risk Matrix
 ```
                              IMPACT
                    Low         Medium         High          Critical
                  (1-3)        (4-6)          (7-8)          (9-10)
              +------------+------------+--------------+-------------+
    High      | CVE-MC-010 | CVE-MC-007 | CVE-MC-005   | CVE-MC-001  |
   (0.7-1.0)  |   3.5      |   5.3      |    7.5       |    9.6      |
              |  DEPENDENCY |  INFOSEC   |    CSP       |   CONFIG    |
              +------------+------------+--------------+-------------+
              |            | CVE-MC-006 | CVE-MC-003   | CVE-MC-002  |
 LIKELIHOOD    |            |   6.5      |    8.0       |    9.3      |
   (0.4-0.6)  |            |  PDF-WIN   |    XSS       |    REPL     |
              +------------+------------+--------------+-------------+
    Medium    |            | CVE-MC-008 | CVE-MC-004   |             |
   (0.2-0.4)  |            |   5.5      |    7.8       |             |
              |            |  INCONSIST |  PATH-TRAV   |             |
              +------------+------------+--------------+-------------+
    Low       |            |            | CVE-MC-009   |             |
   (0-0.2)    |            |            |    4.4       |             |
              |            |            |  CMD-EXEC    |             |
              +------------+------------+--------------+-------------+
 ```
 ### 4.2 Prioritized Remediation List
 | Priority | CVE | Vulnerability | CVSS | Effort | Risk Reduction |
 |----------|-----|---------------|------|--------|----------------|
 | P0 | CVE-MC-001 | Insecure Electron Config | 9.6 | Medium | Critical |
 | P0 | CVE-MC-002 | REPL Code Execution | 9.3 | High | Critical |
 | P1 | CVE-MC-003 | XSS in Markdown | 8.0 | Medium | High |
 | P1 | CVE-MC-004 | Path Traversal | 7.8 | Low | High |
 | P1 | CVE-MC-005 | Weak CSP | 7.5 | Medium | High |
 | P2 | CVE-MC-006 | PDF Window Config | 6.5 | Low | Medium |
 | P2 | CVE-MC-008 | Inconsistent Settings | 5.5 | Low | Medium |
 | P2 | CVE-MC-007 | PlantUML Exfiltration | 5.3 | Medium | Medium |
 | P3 | CVE-MC-009 | External Tool Execution | 4.4 | Low | Low |
 | P3 | CVE-MC-010 | Dependency Versioning | 3.5 | Low | Low |
 ### 4.3 Risk Score Calculation
 ```
 Overall Application Risk Score: 7.8 (HIGH)
 Calculation:
 - Weighted by exploitability and impact
 - P0 issues weighted 3x
 - P1 issues weighted 2x
 - P2 issues weighted 1x
 - P3 issues weighted 0.5x
 Risk = (9.6*3 + 9.3*3 + 8.0*2 + 7.8*2 + 7.5*2 + 6.5 + 5.5 + 5.3 + 4.4*0.5 + 3.5*0.5) / 17
     = (28.8 + 27.9 + 16.0 + 15.6 + 15.0 + 6.5 + 5.5 + 5.3 + 2.2 + 1.75) / 17
     = 124.55 / 17
     = 7.33 (adjusted to 7.8 with environmental factors)
 ```
 ---
 ## 5. Business Impact Analysis
 ### 5.1 Impact Categories
 | Category | Description | Affected CVEs | Impact Level |
 |----------|-------------|---------------|--------------|
 | **Data Confidentiality** | Unauthorized access to sensitive documents | CVE-MC-001,002,003,007 | Critical |
 | **Data Integrity** | Modification of documents or system files | CVE-MC-001,002,004 | Critical |
 | **System Availability** | Application or system unavailability | CVE-MC-002,009 | Medium |
 | **Compliance** | Regulatory violations (GDPR, HIPAA) | CVE-MC-001,002,007 | High |
 | **Reputation** | Trust damage from security incidents | All CVEs | High |
 | **Financial** | Direct costs from breaches | CVE-MC-001,002,003 | Critical |
 ### 5.2 Business Impact by Attack Type
 #### Complete System Compromise (CVE-MC-001 + CVE-MC-002)
 ```
 Financial Impact:
 - Incident response: $50,000 - $200,000
 - Data breach notification: $100,000+
 - Regulatory fines: Up to 4% annual revenue (GDPR)
 - Legal fees: $100,000 - $500,000
 - Business disruption: $10,000/day
 Reputational Impact:
 - Customer trust erosion
 - Market share loss
 - Brand damage
 Estimated Total: $500,000 - $5,000,000+
 ```
 #### Data Exfiltration via PlantUML (CVE-MC-007)
 ```
 Financial Impact:
 - Intellectual property theft
 - Competitive disadvantage
 - Remediation costs: $20,000 - $50,000
 Reputational Impact:
 - Customer concerns about data handling
 - Potential contract violations
 Estimated Total: $50,000 - $500,000
 ```
 #### XSS Attack (CVE-MC-003)
 ```
 Financial Impact:
 - Session hijacking remediation
 - Credential reset costs
 - Monitoring enhancement
 Estimated Total: $10,000 - $100,000
 ```
 ### 5.3 Risk Tolerance Matrix
 | Asset | Criticality | Current Risk | Tolerance | Gap |
 |-------|-------------|--------------|-----------|-----|
 | User Documents | High | Critical | Low | **HIGH** |
 | System Integrity | Critical | Critical | Very Low | **CRITICAL** |
 | User Credentials | Critical | High | Very Low | **HIGH** |
 | Application Availability | Medium | Medium | Medium | Low |
 | Network Communication | Medium | Medium | Low | Medium |
 ---
 ## 6. MITRE ATT&CK Framework Mapping
 ### 6.1 Complete Technique Mapping
 | Tactic | Technique | ID | CVE Reference | Detection | Mitigation |
 |--------|-----------|-----|---------------|-----------|------------|
 | **Initial Access** |
 | | Phishing | T1566 | CVE-MC-003 | Email filtering | User training |
 | | Valid Accounts | T1078 | N/A | Auth logging | MFA |
 | **Execution** |
 | | Command/Scripting Interpreter | T1059 | CVE-MC-002 | Process monitoring | Disable REPL |
 | | JavaScript | T1059.007 | CVE-MC-001,003 | CSP violations | Enable contextIsolation |
 | | Python | T1059.006 | CVE-MC-002 | Process monitoring | Sandboxing |
 | | Bash | T1059.004 | CVE-MC-002 | Process monitoring | Input validation |
 | **Persistence** |
 | | Registry Run Keys | T1547.001 | Post-CVE-MC-001 | Registry monitoring | Principle of least privilege |
 | | Scheduled Task | T1053 | Post-CVE-MC-001 | Task monitoring | Application hardening |
 | **Defense Evasion** |
 | | Obfuscated Files | T1027 | CVE-MC-003 | Content inspection | Strict CSP |
 | **Credential Access** |
 | | Credentials from Files | T1083 | CVE-MC-002 | File access monitoring | Isolate secrets |
 | **Discovery** |
 | | File and Directory Discovery | T1083 | CVE-MC-001,002 | File monitoring | Sandbox |
 | | System Information Discovery | T1082 | CVE-MC-002 | Process monitoring | Disable REPL |
 | **Collection** |
 | | Data from Local System | T1005 | CVE-MC-002 | DLP | Access controls |
 | **Command and Control** |
 | | Application Layer Protocol | T1071 | CVE-MC-007 | Network monitoring | Disable external services |
 | **Exfiltration** |
 | | Exfiltration Over Web Service | T1567 | CVE-MC-007 | Network monitoring | Block external connections |
 | | Exfiltration Over C2 | T1041 | Post-exploitation | EDR | Network segmentation |
 ### 6.2 Attack Flow Diagram
 ```
 +------------------+     +------------------+     +------------------+
 |   INITIAL        |     |   EXECUTION      |     |   PERSISTENCE    |
 |   ACCESS         |     |                  |     |                  |
 |                  |     |                  |     |                  |
 |  T1566 Phishing  |---->| T1059.007 JS     |---->| T1547.001 Reg    |
 |  T1204 User Exec |     | T1059.004 Bash   |     | T1053 Sched Task |
 |                  |     | T1059.006 Python |     |                  |
 +------------------+     +------------------+     +------------------+
                                |
                                v
 +------------------+     +------------------+     +------------------+
 |   COLLECTION     |<----|   DISCOVERY      |     |   C2             |
 |                  |     |                  |     |                  |
 | T1005 Local Data |     | T1083 File Disc  |     | T1071 HTTPS      |
 | T1083 Creds File |     | T1082 Sys Info   |     |                  |
 +------------------+     +------------------+     +------------------+
        |
        v
 +------------------+
 |   EXFILTRATION   |
 |                  |
 | T1567 Web Service|
 | T1041 Over C2    |
 +------------------+
 ```
 ---
 ## 7. Security Requirements & Mitigations
 ### 7.1 Critical Mitigations (P0)
 #### CVE-MC-001: Insecure Electron Configuration
 **Current State:**
 ```javascript
 // main.js:328-331
 webPreferences: {
  nodeIntegration: true,
  contextIsolation: false,
  spellcheck: true
 }
 ```
 **Required Changes:**
 ```javascript
 webPreferences: {
  nodeIntegration: false,      // REQUIRED
  contextIsolation: true,       // REQUIRED
  sandbox: true,                // RECOMMENDED
  spellcheck: true
 }
 ```
 **Migration Path:**
 1. Update preload.js to expose all required APIs
 2. Update renderer.js to use exposed APIs instead of require()
 3. Test all functionality
 4. Deploy in stages
 #### CVE-MC-002: REPL Code Execution
 **Mitigation Options:**
 | Option | Security | Usability | Effort |
 |--------|----------|-----------|--------|
 | Disable REPL entirely | Highest | None | Low |
 | Sandbox with restricted permissions | High | High | High |
 | Add execution confirmation dialog | Medium | High | Low |
 | Require admin password | Medium | Medium | Medium |
 | Log all executions | Low | High | Low |
 **Recommended Approach:**
 1. Add user confirmation dialog with code preview
 2. Implement execution sandboxing (Docker/container)
 3. Add audit logging
 4. Restrict available modules
 ### 7.2 High Priority Mitigations (P1)
 #### CVE-MC-003: XSS in Markdown
 **Current Mitigations:**
 - DOMPurify sanitization
 **Additional Required:**
 ```javascript
 // Enhanced DOMPurify configuration
 const purifyConfig = {
  ALLOWED_TAGS: [...],
  ALLOWED_ATTR: [...],
  FORBID_TAGS: ['script', 'iframe', 'object', 'embed'],
  FORBID_ATTR: ['onerror', 'onload', 'onclick'],
  ADD_ATTR: ['target'],
  FORCE_BODY: true
 };
 ```
 #### CVE-MC-005: Weak CSP
 **Current CSP:**
 ```
 default-src 'self';
 script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net;
 style-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com;
 img-src 'self' data: blob: file:;
 font-src 'self' data:;
 connect-src 'self' https://www.plantuml.com;
 ```
 **Recommended CSP:**
 ```
 default-src 'self';
 script-src 'self';
 style-src 'self';
 img-src 'self' data:;
 font-src 'self';
 connect-src 'self';
 frame-src 'none';
 object-src 'none';
 base-uri 'self';
 form-action 'self';
 ```
 **Note:** This requires:
 - Bundling all dependencies locally
 - Removing PlantUML server dependency (use local rendering)
 - Removing unsafe-inline and unsafe-eval
 ### 7.3 Medium Priority Mitigations (P2)
 #### CVE-MC-006/008: Window Security Consistency
 **Affected Windows:**
 - PDF export window (main.js:2579-2585)
 - Hidden conversion window (main.js:3263-3268)
 **Fix:**
 ```javascript
 webPreferences: {
  nodeIntegration: false,
  contextIsolation: true,
  sandbox: true,
  preload: path.join(__dirname, 'preload-pdf.js')
 }
 ```
 #### CVE-MC-007: PlantUML Data Exfiltration
 **Options:**
 1. Use local PlantUML JAR file
 2. Use PlantUML npm package
 3. Add warning before sending to external server
 4. Allow configuration of PlantUML server URL
 ---
 ## 8. Attack Tree Summary
 ### 8.1 Primary Attack Tree - Full System Compromise
 ```
 GOAL: Full System Compromise via MarkdownConverter
 │
 ├── [BRANCH A] Exploit CVE-MC-001 (nodeIntegration)
 │   │
 │   ├── [A.1] XSS via malicious markdown
 │   │   ├── [A.1.1] HTML injection
 │   │   ├── [A.1.2] SVG script injection
 │   │   └── [A.1.3] DOMPurify bypass
 │   │
 │   ├── [A.2] Compromised CDN script
 │   │   ├── [A.2.1] jsdelivr compromise
 │   │   └── [A.2.2] cdnjs compromise
 │   │
 │   └── [A.3] PlantUML SVG injection
 │       └── [A.3.1] Compromised plantuml.com
 │
 ├── [BRANCH B] Exploit CVE-MC-002 (REPL)
 │   │
 │   ├── [B.1] Social engineering
 │   │   ├── [B.1.1] Malicious tutorial document
 │   │   └── [B.1.2] Phishing with "config file"
 │   │
 │   └── [B.2] Code execution
 │       ├── [B.2.1] JavaScript (Node.js)
 │       ├── [B.2.2] Python
 │       └── [B.2.3] Bash/Shell
 │
 └── [BRANCH C] Chain Exploits
    │
    ├── [C.1] XSS -> RCE (CVE-MC-003 + CVE-MC-001)
    │   └── Impact: CVSS 9.8
    │
    ├── [C.2] Path Traversal -> Privilege Escalation
    │   └── Impact: CVSS 8.5
    │
    └── [C.3] PlantUML -> XSS -> RCE
        └── Impact: CVSS 9.1
 ```
 ### 8.2 Attack Success Probability
 | Attack Path | Complexity | Privileges Required | User Interaction | Probability |
 |-------------|------------|---------------------|------------------|-------------|
 | A.1 XSS->RCE | Low | None | Required | 75% |
 | A.2 CDN Compromise | High | None | None | 15% |
 | A.3 PlantUML->RCE | Medium | None | Required | 40% |
 | B.1 REPL Social Eng | Low | None | Required | 60% |
 | C.1 Combined XSS-RCE | Low | None | Required | 70% |
 ---
 ## 9. Recommendations
 ### 9.1 Immediate Actions (0-30 days)
 1. **CVE-MC-001**: Enable `contextIsolation: true` and `nodeIntegration: false` for main window
 2. **CVE-MC-002**: Add confirmation dialog before REPL execution with code preview
 3. **CVE-MC-005**: Remove `unsafe-inline` and `unsafe-eval` from CSP
 4. **CVE-MC-006**: Fix PDF export window security settings
 ### 9.2 Short-term Actions (30-90 days)
 1. **CVE-MC-002**: Implement sandboxed code execution environment
 2. **CVE-MC-003**: Enhance DOMPurify configuration, add CSP reporting
 3. **CVE-MC-007**: Implement local PlantUML rendering option
 4. Add comprehensive security audit logging
 ### 9.3 Long-term Actions (90+ days)
 1. **CVE-MC-010**: Implement dependency pinning and SCA scanning
 2. Security awareness training for users
 3. Implement secure development lifecycle (SDL)
 4. Regular penetration testing schedule
 ---
 ## 10. Appendix
 ### A. Security Configuration Audit
 **Main Window (main.js:323-334)**
 ```javascript
 // CURRENT (INSECURE)
 webPreferences: {
  nodeIntegration: true,      // CRITICAL: Allows require() in renderer
  contextIsolation: false,    // CRITICAL: No isolation between contexts
  spellcheck: true
 }
 // RECOMMENDED
 webPreferences: {
  nodeIntegration: false,
  contextIsolation: true,
  sandbox: true,
  spellcheck: true,
  webSecurity: true,
  allowRunningInsecureContent: false
 }
 ```
 **CSP Configuration (index.html:5)**
 ```html
 <!-- CURRENT (WEAK) -->
 <meta http-equiv="Content-Security-Policy"
  content="default-src 'self';
           script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cdn.jsdelivr.net;
           ...">
 <!-- RECOMMENDED -->
 <meta http-equiv="Content-Security-Policy"
  content="default-src 'self';
           script-src 'self';
           style-src 'self';
           img-src 'self' data:;
           connect-src 'self';
           frame-src 'none';
           object-src 'none'">
 ```
 ### B. IPC Channel Security Review
 **High-Risk Channels:**
 | Channel | Risk | Recommendation |
 |---------|------|----------------|
 | `execute-code` | Critical | Remove or sandbox |
 | `save-file` | High | Add path validation |
 | `batch-convert` | Medium | Rate limiting exists |
 | `git-*` | Medium | Audit git operations |
 ### C. Dependency Security
 **Critical Dependencies:**
 | Package | Version | Known CVEs | Recommendation |
 |---------|---------|------------|----------------|
 | electron | 37.4.0 | None | Pin version |
 | dompurify | 3.3.1 | None | Keep updated |
 | marked | 17.0.3 | None | Keep updated |
 | mermaid | 11.12.3 | None | Review CSP impact |
 ---
 ## Document Control
 | Version | Date | Author | Changes |
 |---------|------|--------|---------|
 | 1.0 | 2026-03-15 | Security Team | Initial threat model |
 ---
 *This threat model should be reviewed and updated after any significant architectural changes or at minimum annually.*
@@ -1,502 +0,0 @@
 # MarkdownConverter v5.0 - React + Tauri + PWA Architecture Design
 **Date:** 2026-03-15
 **Status:** Approved
 **Target Platforms:** Desktop (Tauri), Web (PWA), Mobile (Future)
 ---
 ## Executive Summary
 This document outlines the architecture for MarkdownConverter v5.0, a complete rewrite using React, Tauri, and PWA technologies. The new architecture enables:
 - **Multi-platform support**: Single codebase for desktop, web, and future mobile
 - **Improved security**: Eliminates critical Electron vulnerabilities by design
 - **Reduced bundle size**: ~5-10MB desktop, ~137KB web (vs 150MB+ Electron)
 - **Better maintainability**: Component-based architecture with TypeScript
 - **Offline support**: Full PWA capabilities with IndexedDB storage
 ---
 ## 1. Project Structure
 ```
 markdown-converter-v5/
 ├── src/
 │   ├── components/
 │   │   ├── ui/                    # Shadcn/ui components (button, dialog, etc.)
 │   │   ├── editor/                # CodeMirror wrapper, toolbar
 │   │   ├── preview/               # Markdown preview, theme rendering
 │   │   ├── sidebar/               # Explorer, Git, Snippets, Templates panels
 │   │   ├── tabs/                  # Tab bar, tab management
 │   │   ├── dialogs/               # Export, batch converter, settings dialogs
 │   │   └── layout/                # Main layout, splitter panes
 │   │
 │   ├── hooks/
 │   │   ├── useEditor.ts           # Editor state & actions
 │   │   ├── useTheme.ts            # Theme management
 │   │   ├── useFileSystem.ts       # File operations (uses adapter)
 │   │   ├── useConversion.ts       # Conversion operations
 │   │   └── useKeyboardShortcuts.ts
 │   │
 │   ├── stores/
 │   │   ├── editorStore.ts         # Content, tabs, cursor position
 │   │   ├── settingsStore.ts       # User preferences
 │   │   ├── themeStore.ts          # Active theme, custom themes
 │   │   └── sidebarStore.ts        # Sidebar state, active panel
 │   │
 │   ├── adapters/
 │   │   ├── types.ts               # Interface definitions
 │   │   ├── tauri/
 │   │   │   ├── index.ts           # Tauri adapter implementation
 │   │   │   ├── fs.ts              # File system via Tauri
 │   │   │   ├── convert.ts         # Pandoc, FFmpeg via Tauri
 │   │   │   └── system.ts          # System info, paths
 │   │   ├── web/
 │   │   │   ├── index.ts           # Web adapter implementation
 │   │   │   ├── fs.ts              # IndexedDB + File System Access API
 │   │   │   ├── convert.ts         # WASM converters, cloud fallback
 │   │   │   └── system.ts          # Browser capabilities
 │   │   └── index.ts               # Platform detection & export
 │   │
 │   ├── wasm/
 │   │   ├── pdf.wasm               # PDF generation
 │   │   ├── marked.wasm            # Markdown parsing (if available)
 │   │   └── loader.ts              # WASM module loader
 │   │
 │   ├── lib/
 │   │   ├── markdown.ts            # Marked + plugins config
 │   │   ├── syntax.ts              # Highlight.js config
 │   │   ├── mermaid.ts             # Diagram rendering
 │   │   └── utils.ts               # Helper functions
 │   │
 │   ├── styles/
 │   │   ├── globals.css            # Tailwind imports, CSS variables
 │   │   ├── themes/                # Theme CSS files
 │   │   └── editor.css             # CodeMirror styling
 │   │
 │   ├── types/
 │   │   ├── editor.ts              # Editor-related types
 │   │   ├── conversion.ts          # Conversion options types
 │   │   └── platform.ts            # Platform capability types
 │   │
 │   ├── App.tsx                    # Root component
 │   ├── main.tsx                   # Entry point
 │   └── vite-env.d.ts
 │
 ├── src-tauri/                     # Tauri backend (Rust)
 │   ├── src/
 │   │   ├── main.rs                # Tauri entry
 │   │   ├── commands/              # IPC command handlers
 │   │   │   ├── fs.rs              # File system operations
 │   │   │   ├── convert.rs         # Pandoc, FFmpeg wrappers
 │   │   │   └── system.rs          # System utilities
 │   │   └── lib.rs
 │   ├── Cargo.toml
 │   └── tauri.conf.json
 │
 ├── public/
 │   ├── manifest.json              # PWA manifest
 │   ├── sw.js                      # Service worker
 │   ├── fonts/                     # JetBrains Mono, Inter
 │   └── icons/                     # App icons
 │
 ├── package.json
 ├── vite.config.ts
 ├── tailwind.config.ts
 ├── tsconfig.json
 └── components.json                # Shadcn/ui config
 ```
 ---
 ## 2. Component Architecture
 ```tsx
 // Component hierarchy
 <App>                              // Root layout, theme provider
 ├── <Layout>
 │   ├── <TitleBar />              // Draggable title bar (desktop only)
 │   ├── <TabBar />                // Document tabs
 │   ├── <MainContent>
 │   │   ├── <Sidebar>             // Collapsible sidebar
 │   │   │   ├── <ExplorerPanel />
 │   │   │   ├── <GitPanel />
 │   │   │   ├── <SnippetsPanel />
 │   │   │   └── <TemplatesPanel />
 │   │   ├── <EditorPane>          // Split view container
 │   │   │   ├── <CodeMirrorEditor />
 │   │   │   └── <PreviewPane>
 │   │   │       └── <MarkdownPreview />
 │   │   └── <BottomPanel>         // REPL, terminal, output
 │   └── <StatusBar />             // Line count, encoding, status
 │
 └── <Dialogs>                      // Portal-based dialogs
    ├── <ExportDialog />
    ├── <BatchConvertDialog />
    ├── <SettingsDialog />
    ├── <ThemeDialog />
    └── <PdfEditorDialog />
 ```
 **Key Components:**
 | Component | Props | Responsibility |
 |-----------|-------|----------------|
 | `CodeMirrorEditor` | `content`, `onChange`, `theme` | Wrap CodeMirror 6 with React |
 | `MarkdownPreview` | `content`, `theme` | Render sanitized HTML with themes |
 | `TabBar` | `tabs`, `activeId`, `onSelect`, `onClose` | Manage document tabs |
 | `Sidebar` | `activePanel`, `collapsed` | Collapsible sidebar container |
 | `ExportDialog` | `format`, `options` | Export configuration UI |
 ---
 ## 3. State Management (Zustand)
 ### Editor Store
 ```typescript
 interface Tab {
  id: string;
  title: string;
  content: string;
  filePath?: string;
  isDirty: boolean;
  cursorPosition: { line: number; column: number };
 }
 interface EditorState {
  tabs: Tab[];
  activeTabId: string | null;
  // Actions
  createTab: (title?: string) => string;
  closeTab: (id: string) => void;
  setActiveTab: (id: string) => void;
  updateContent: (id: string, content: string) => void;
  updateCursorPosition: (id: string, pos: { line: number; column: number }) => void;
  markSaved: (id: string, filePath?: string) => void;
 }
 ```
 ### Settings Store
 ```typescript
 interface SettingsState {
  theme: string;
  fontSize: number;
  fontFamily: string;
  previewMode: 'split' | 'editor' | 'preview';
  showLineNumbers: boolean;
  wordWrap: boolean;
  autoSave: boolean;
  autoSaveInterval: number;
 }
 ```
 **Stores Summary:**
 | Store | State | Persisted |
 |-------|-------|-----------|
 | `editorStore` | Tabs, content, cursor | Tab metadata only |
 | `settingsStore` | User preferences | Yes |
 | `themeStore` | Active theme, custom themes | Yes |
 | `sidebarStore` | Panel state, width | Yes |
 ---
 ## 4. Platform Adapters
 ### Adapter Interface
 ```typescript
 export interface PlatformAdapter {
  name: 'tauri' | 'web';
  // File System
  fs: {
    readFile: (path: string) => Promise<string>;
    writeFile: (path: string, content: string) => Promise<void>;
    deleteFile: (path: string) => Promise<void>;
    listDirectory: (path: string) => Promise<FileInfo[]>;
    exists: (path: string) => Promise<boolean>;
    watchDirectory?: (path: string, callback: WatchCallback) => () => void;
  };
  // Conversion
  convert: {
    toPdf: (content: string, options: PdfOptions) => Promise<Blob>;
    toDocx: (content: string, options: DocxOptions) => Promise<Blob>;
    toHtml: (content: string, options: HtmlOptions) => Promise<string>;
    batchConvert: (files: string[], format: string) => Promise<ConversionResult[]>;
  };
  // Capabilities
  capabilities: {
    hasPandoc: boolean;
    hasFfmpeg: boolean;
    hasLibreOffice: boolean;
    hasDirectFs: boolean;
    hasSystemNotifications: boolean;
  };
 }
 ```
 ### Platform Detection
 ```typescript
 // Auto-detect platform at startup
 const isTauri = typeof window !== 'undefined' &&
                '__TAURI__' in window;
 export const adapter: PlatformAdapter = isTauri
  ? tauriAdapter
  : webAdapter;
 ```
 ### Capability Differences
 | Feature | Tauri (Desktop) | Web (PWA) |
 |---------|-----------------|-----------|
 | File System | Direct access | IndexedDB + File System Access API |
 | PDF Export | Pandoc (native) | WASM converter |
 | DOCX Export | Pandoc (native) | Limited/not available |
 | Media Conversion | FFmpeg (native) | Cloud API or limited |
 | File Watching | Native events | Not available |
 | Offline | Always | Service Worker |
 ---
 ## 5. Build Configuration
 ### Vite Configuration
 - Target: ESNext
 - Minifier: esbuild
 - Code splitting by vendor chunks
 - Source maps enabled
 ### Tailwind Configuration
 - Dark mode: `class` strategy
 - Custom colors using CSS variables
 - Custom font families (JetBrains Mono, Inter)
 - Tailwindcss-animate plugin
 ### TypeScript Configuration
 - Target: ES2022
 - Strict mode enabled
 - All strict checks enabled
 - Path aliases (`@/*`)
 ### Bundle Sizes (Estimated)
 | Chunk | Size (gzipped) |
 |-------|----------------|
 | `vendor-react` | ~12KB |
 | `vendor-editor` | ~45KB |
 | `vendor-markdown` | ~35KB |
 | `vendor-ui` | ~15KB |
 | `app` (your code) | ~30KB |
 | **Total PWA** | **~137KB** |
 | Tauri desktop | ~5-10MB (with WebView) |
 ---
 ## 6. Tauri Backend (Rust)
 ### IPC Commands
 **File System:**
 - `read_file` - Read file content
 - `write_file` - Write file content
 - `delete_file` - Delete file
 - `list_directory` - List directory contents
 - `path_exists` - Check path existence
 - `watch_directory` - Watch for file changes
 **Conversion:**
 - `to_pdf` - Convert to PDF via Pandoc
 - `to_docx` - Convert to DOCX via Pandoc
 - `to_html` - Convert to HTML via Pandoc
 - `batch_convert` - Batch conversion
 **System:**
 - `check_dependencies` - Check for Pandoc, FFmpeg, LibreOffice
 - `get_config_dir` - Get config directory path
 ### Security Comparison
 | Aspect | Electron (Current) | Tauri |
 |--------|-------------------|-------|
 | `nodeIntegration` | `true` (CVE) | Not possible |
 | `contextIsolation` | `false` (CVE) | Always enforced |
 | Bundle size | ~150MB | ~5-10MB |
 | Memory usage | Higher | Lower |
 | IPC security | Manual whitelist | Compile-time verified |
 ---
 ## 7. PWA Configuration
 ### Web App Manifest
 - Name: Markdown Converter
 - Display: Standalone
 - Theme color: #5661b3
 - File handlers for .md, .markdown, .txt
 - Share target for receiving shared content
 ### Service Worker
 - Cache-first for static assets
 - Network-first for API calls
 - Stale-while-revalidate for dynamic content
 - Automatic update detection
 ### IndexedDB Storage
 **Stores:**
 - `files` - Offline file storage
 - `settings` - User preferences
 - `templates` - Custom templates
 ### PWA Features
 | Feature | Implementation |
 |---------|---------------|
 | Offline support | Service Worker + IndexedDB |
 | Install prompt | Web App Manifest |
 | File handling | File System Access API (Chrome) |
 | Share target | Share Target API |
 | Background sync | Background Sync API |
 ---
 ## 8. Migration Plan
 ### Timeline: 8 Weeks
 **Phase 1: Foundation (Week 1-2)**
 - Initialize new repo
 - Setup Vite + React + TypeScript
 - Configure Tailwind + Shadcn/ui
 - Setup Zustand stores
 - Create platform adapter interfaces
 - Setup Tauri project structure
 **Phase 2: Core Editor (Week 3-4)**
 - CodeMirrorEditor component
 - MarkdownPreview component
 - SplitPane layout
 - Theme system
 - Tab management
 - Keyboard shortcuts
 **Phase 3: Sidebar & Panels (Week 5)**
 - Sidebar container
 - ExplorerPanel
 - GitPanel
 - SnippetsPanel
 - TemplatesPanel
 - Bottom panel
 **Phase 4: Platform Adapters (Week 6)**
 - Web adapter implementation
 - Tauri adapter implementation
 - File system operations
 - PDF conversion
 - Capability detection
 **Phase 5: Export & Conversion (Week 7)**
 - ExportDialog
 - BatchConvertDialog
 - UniversalConverterDialog
 - ImageConverterDialog
 - AudioConverterDialog
 - VideoConverterDialog
 - PDF Editor Dialog
 **Phase 6: PWA & Polish (Week 8)**
 - Service Worker setup
 - Web App Manifest
 - IndexedDB storage
 - Offline mode indicator
 - Settings persistence
 - Accessibility audit
 - Performance optimization
 ### Parallel Development Strategy
 ```
 Current Electron App (v4.x)     New React+Tauri App (v5.0)
        │                               │
        │  Bug fixes only               │  Active development
        │  Security patches             │  Feature migration
        ▼                               ▼
   Stable release  ────────────>  Beta release
   (maintained)                    (new features)
 ```
 ---
 ## 9. Design Decisions Summary
 | Decision | Choice | Rationale |
 |----------|--------|-----------|
 | Code Structure | Single repo with platform adapters | Lightest weight, clean separation |
 | State Management | Zustand | Minimal (~1KB), simple API |
 | UI Library | Shadcn/ui + Tailwind | Copy-paste ownership, excellent DX |
 | Build Tool | Vite | Industry standard, fast HMR |
 | TypeScript | Strict mode | Maximum type safety |
 | Desktop Features | Hybrid (WASM core, desktop advanced) | Best of both worlds |
 | Migration | Parallel development | Zero disruption to stable release |
 ---
 ## 10. Success Criteria
 - [ ] All core editor features functional on both Tauri and PWA
 - [ ] Bundle size under 150KB for PWA
 - [ ] All 13 themes migrated and working
 - [ ] Export to PDF works on both platforms
 - [ ] Offline mode fully functional in PWA
 - [ ] WCAG 2.1 AA accessibility compliance
 - [ ] TypeScript strict mode with no `any` types
 - [ ] All IPC channels have TypeScript types
 - [ ] Security audit passes with no critical issues
 ---
 ## Appendix: Dependencies
 ### Production Dependencies
 - `react` - UI library
 - `react-dom` - React DOM renderer
 - `zustand` - State management
 - `@radix-ui/react-*` - Headless UI primitives
 - `@codemirror/*` - Code editor
 - `marked` - Markdown parser
 - `highlight.js` - Syntax highlighting
 - `mermaid` - Diagram rendering
 - `dompurify` - HTML sanitization
 - `class-variance-authority` - Component variants
 - `clsx` + `tailwind-merge` - Class utilities
 - `lucide-react` - Icons
 ### Development Dependencies
 - `@tauri-apps/cli` - Tauri CLI
 - `typescript` - TypeScript compiler
 - `vite` - Build tool
 - `tailwindcss` - CSS framework
 - `eslint` - Linting
 - `prettier` - Formatting
 ---
 *Document generated: 2026-03-15*
 *Next step: Invoke writing-plans skill to create detailed implementation plan*
@@ -1,202 +0,0 @@
 # Modal System Design
 **Date:** 2026-03-24
 **Version:** 4.0.0
 **Status:** Approved
 ## Overview
 Replace the existing dialog implementations with a unified modal system that provides:
 - Glassmorphism backdrop matching app aesthetic
 - Full accessibility (ARIA, focus trap, keyboard navigation)
 - Smooth fade + scale animations
 - Consistent API via `ModalManager` class
 ## Decisions Made
 | Decision | Choice | Rationale |
 |----------|--------|-----------|
 | Architecture | Unified `ModalManager` class | Cleaner, consistent behavior across all modals |
 | Backdrop style | Glassmorphism | Matches existing app design language |
 | Focus management | Focus first interactive element | Standard, predictable behavior |
 | Animation | Fade + scale (95% → 100%) | Modern, subtle effect |
 | Implementation | Custom (not native `<dialog>`) | Full control, no polyfill concerns |
 ## Architecture
 ### File Structure
 ```
 src/
 ├── utils/
 │   └── ModalManager.js    # Core modal logic (~150 lines)
 ├── styles/
 │   └── modal.css          # Unified modal styles (~200 lines)
 └── index.html             # Updated dialog markup
 ```
 ### ModalManager Class
 ```javascript
 class ModalManager {
  constructor(element, options = {})
  open()                    // Show modal with animation
  close()                   // Hide modal with animation
  destroy()                 // Cleanup event listeners
  on(event, callback)       // Event subscription
  // Internal
  #createBackdrop()         // Create glassmorphism backdrop
  #trapFocus()              // Manage focus within modal
  #handleKeydown(e)         // Escape key handler
  #getFocusableElements()   // Query focusable children
 }
 ```
 ### Events
 - `open` — Fired after open animation completes
 - `close` — Fired after close animation completes
 ## CSS Design
 ### Variables (from tokens.css)
 ```css
 --z-modal: 200;
 --transition-normal: 200ms cubic-bezier(0.4, 0, 0.2, 1);
 --shadow-xl: 0 20px 25px -5px rgb(0 0 0 / 0.1);
 --radius-lg: 0.5rem;
 ```
 ### Backdrop
 ```css
 .modal-backdrop {
  position: fixed;
  inset: 0;
  background: rgba(0, 0, 0, 0.4);
  backdrop-filter: blur(4px);
  -webkit-backdrop-filter: blur(4px);
  z-index: var(--z-modal);
 }
 ```
 ### Modal Container
 ```css
 .modal {
  position: fixed;
  inset: 0;
  display: flex;
  align-items: center;
  justify-content: center;
  z-index: calc(var(--z-modal) + 1);
  opacity: 0;
  visibility: hidden;
  transition: opacity var(--transition-normal),
              visibility var(--transition-normal);
 }
 .modal.open {
  opacity: 1;
  visibility: visible;
 }
 ```
 ### Modal Content (with animation)
 ```css
 .modal-content {
  background: hsl(var(--background));
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-xl);
  max-width: 90vw;
  max-height: 90vh;
  overflow: hidden;
  transform: scale(0.95);
  transition: transform var(--transition-normal);
 }
 .modal.open .modal-content {
  transform: scale(1);
 }
 ```
 ## HTML Structure
 All dialogs convert to unified structure:
 ```html
 <div id="export-dialog"
     class="modal"
     role="dialog"
     aria-modal="true"
     aria-labelledby="export-dialog-title">
  <div class="modal-backdrop" data-close></div>
  <div class="modal-content">
    <div class="modal-header">
      <h3 id="export-dialog-title">Export Options</h3>
      <button class="modal-close" aria-label="Close">&times;</button>
    </div>
    <div class="modal-body">
      <!-- Dialog-specific content -->
    </div>
    <div class="modal-footer">
      <button class="btn btn-secondary" data-close>Cancel</button>
      <button class="btn btn-primary">Confirm</button>
    </div>
  </div>
 </div>
 ```
 ### Key Attributes
 - `role="dialog"` — Screen reader identification
 - `aria-modal="true"` — Prevents screen reader from accessing background
 - `aria-labelledby` — References the dialog title
 - `data-close` — Click handler for closing (backdrop, cancel buttons)
 ## Accessibility Features
 1. **Focus trap** — Tab cycles within modal only
 2. **Focus first element** — Auto-focuses first input/button on open
 3. **Escape key** — Closes modal
 4. **Click outside** — Clicking backdrop closes modal
 5. **Focus restoration** — Returns focus to trigger element on close
 6. **ARIA attributes** — Proper screen reader support
 ## Dialogs to Migrate
 | Dialog ID | Current Class | Complexity |
 |-----------|--------------|------------|
 | `find-dialog` | `.find-dialog` | Simple |
 | `export-dialog` | `.export-dialog` | Complex (many sections) |
 | `print-preview-overlay` | `.export-dialog` | Medium |
 | `table-generator-dialog` | `.export-dialog` | Simple |
 | `ascii-art-dialog` | `.export-dialog` | Medium |
 | `universal-converter-dialog` | `.export-dialog` | Complex |
 | `batch-dialog` | `.batch-dialog` | Complex |
 | `pdf-editor-dialog` | `.export-dialog` | Complex |
 | `header-footer-dialog` | `.export-dialog` | Medium |
 | `field-picker-dialog` | `.export-dialog` | Simple |
 ## Migration Steps
 1. Create `src/utils/ModalManager.js`
 2. Create `src/styles/modal.css`
 3. Update `index.html` to include new stylesheet
 4. Convert each dialog HTML to new structure
 5. Initialize `ModalManager` instances in `renderer.js`
 6. Remove old CSS from `styles.css`
 7. Test all dialogs
 ## Out of Scope
 - Modal nesting (stacked modals) — can be added later if needed
 - Animated backdrop (currently static blur)
 - Modal size variants (small/large/fullscreen) — can use inline styles
@@ -1,326 +0,0 @@
 # V4 Enhancement + Flutter Exploration Design
 **Date:** 2026-03-24
 **Status:** Approved
 **Approach:** Incremental V4 Enhancement + Flutter Spike (70/30 split)
 ---
 ## Executive Summary
 This design outlines a two-track approach:
 1. **V4 Enhancement (70%)**: Fix critical bugs, optimize performance, add platform adapters, improve UI patterns
 2. **Flutter Exploration (30%)**: Build proof-of-concept for cross-platform evaluation (Windows, Mobile, Web)
 ---
 ## Goals & Scope
 ### Primary Goals
 1. **Fix critical bug**: PDF and markdown multitab functionality
 2. **Performance improvements**: Faster startup, smoother editing, responsive preview
 3. **Architecture improvements**: Platform adapters, cleaner state management
 4. **Flutter research**: Proof-of-concept for cross-platform evaluation
 ### Out of Scope
 - Full V5 migration
 - Complete UI redesign
 - New features (focus on optimization)
 ### Success Criteria
 | Metric | Current | Target |
 |--------|---------|--------|
 | Startup time | ~3-5s | <2s |
 | Editor typing latency | Noticeable lag | <16ms |
 | Preview render (1MB file) | ~500ms | <200ms |
 | Memory usage | ~300MB | <200MB |
 | Bundle size | ~150MB | <100MB |
 ---
 ## Section 1: V4 Critical Fixes & Performance Optimizations
 ### 1.1 Fix: PDF/Markdown Multitab Bug
 **Location:** `src/renderer.js` (TabManager class)
 **Investigation areas:**
 - `switchToTab()` - ensure proper state preservation
 - `closeTab()` - ensure EditorView cleanup
 - Add tab type tracking (markdown vs pdf)
 - Isolate PDF viewer state from editor state
 ### 1.2 Startup Performance Optimizations
 | Optimization | Implementation | Expected Gain |
 |--------------|----------------|---------------|
 | Defer Mermaid | Load only when diagram detected | ~500ms |
 | Defer PDF.js | Load on first PDF open | ~800ms |
 | Lazy load themes | Load active theme only | ~200ms |
 | Lazy sidebar panels | Load panel code when sidebar opens | ~300ms |
 | Preload optimization | Remove unused IPC channels | ~100ms |
 **Lazy loading pattern:**
 ```javascript
 // Current (loads everything upfront)
 const { dialog } = require('@electron/remote');
 // Optimized (load on demand)
 let _dialog;
 function getDialog() {
  if (!_dialog) _dialog = require('@electron/remote').dialog;
  return _dialog;
 }
 ```
 ### 1.3 Editor Performance
 | Issue | Solution |
 |-------|----------|
 | Typing lag with large files | Debounce preview updates (300ms) |
 | Syntax highlight overhead | Use highlight.js lazy mode |
 | Memory leaks | Clean up EditorView on tab close |
 | Theme switching lag | Pre-compile theme CSS |
 ### 1.4 Preview Rendering
 | Issue | Solution |
 |-------|----------|
 | Mermaid slow | Render on-demand, cache results |
 | Full re-render on keystroke | Debounced incremental updates |
 | Large documents | Viewport rendering (visible portion only) |
 ---
 ## Section 2: Platform Adapter Pattern
 ### 2.1 Architecture
 ```
 src/
 ├── adapters/
 │   ├── index.js              # Auto-detects and exports adapter
 │   ├── types.js              # Interface definitions (JSDoc)
 │   │
 │   ├── electron/             # Current Electron implementation
 │   │   ├── index.js          # Exports electronAdapter
 │   │   ├── fs.js             # File system operations
 │   │   ├── convert.js        # Pandoc, FFmpeg conversions
 │   │   ├── pdf.js            # PDF operations
 │   │   └── system.js         # System info, dialogs, notifications
 │   │
 │   └── mock/                 # For testing
 │       └── index.js          # Mock adapter for unit tests
 ```
 ### 2.2 Adapter Interface
 ```javascript
 /**
 * @typedef {Object} PlatformAdapter
 * @property {'electron'} name
 * @property {FileSystemAdapter} fs
 * @property {ConversionAdapter} convert
 * @property {PdfAdapter} pdf
 * @property {SystemAdapter} system
 */
 /**
 * @typedef {Object} FileSystemAdapter
 * @property {(path: string) => Promise<string>} readFile
 * @property {(path: string, content: string) => Promise<void>} writeFile
 * @property {(path: string) => Promise<void>} deleteFile
 * @property {(path: string) => Promise<FileInfo[]>} listDirectory
 * @property {(path: string) => Promise<boolean>} exists
 */
 ```
 ### 2.3 Migration Strategy
 | Phase | What | Files Affected |
 |-------|------|----------------|
 | 1 | Create adapter structure | New files only |
 | 2 | Migrate file operations | `renderer.js`, `sidebar/*.js` |
 | 3 | Migrate conversions | Export dialogs |
 | 4 | Migrate PDF operations | PDF viewer |
 | 5 | Remove old IPC calls | `preload.js` cleanup |
 ---
 ## Section 3: UI Improvements (Shadcn/ui Patterns)
 ### 3.1 Design Token System
 ```css
 /* src/styles/tokens.css */
 :root {
  /* Colors - Light mode */
  --background: 0 0% 100%;
  --foreground: 222.2 84% 4.9%;
  --primary: 227 44% 52%;
  --primary-foreground: 210 40% 98%;
  --secondary: 210 40% 96.1%;
  --secondary-foreground: 222.2 47.4% 11.2%;
  --muted: 210 40% 96.1%;
  --muted-foreground: 215.4 16.3% 46.9%;
  --destructive: 0 84.2% 60.2%;
  --border: 214.3 31.8% 91.4%;
  --ring: 227 44% 52%;
  /* Spacing & Radii */
  --radius: 0.5rem;
 }
 ```
 ### 3.2 Component Improvements
 | Component | Current Issue | Fix |
 |-----------|---------------|-----|
 | Buttons | Inconsistent hover/focus | Use `.btn` with variants |
 | Dialogs | Missing focus trap | Add focus trap, Escape key, aria-modal |
 | Tabs | No keyboard navigation | Add arrow key nav, aria-selected |
 | Sidebar | No collapse animation | CSS transitions |
 | Dropdowns | Missing click-outside | Add proper event handling |
 ### 3.3 Accessibility Improvements
 - Focus states with `:focus-visible`
 - Skip to content link
 - ARIA labels on interactive elements
 - Keyboard navigation for all components
 ---
 ## Section 4: Flutter Exploration (30% Effort)
 ### 4.1 Flutter Project Structure
 ```
 markdown-converter-flutter/
 ├── lib/
 │   ├── main.dart
 │   ├── app.dart
 │   ├── core/
 │   │   ├── theme/
 │   │   └── constants.dart
 │   ├── features/
 │   │   ├── editor/
 │   │   ├── preview/
 │   │   └── tabs/
 │   ├── services/
 │   │   ├── file_service.dart
 │   │   ├── export_service.dart
 │   │   └── platform_service.dart
 │   └── adapters/
 │       ├── file_adapter.dart
 │       ├── file_adapter_mobile.dart
 │       ├── file_adapter_web.dart
 │       └── file_adapter_desktop.dart
 ├── pubspec.yaml
 ├── windows/
 ├── web/
 └── lib/
 ```
 ### 4.2 Key Dependencies
 ```yaml
 dependencies:
  flutter_markdown: ^0.7.0
  flutter_code_editor: ^0.3.0
  provider: ^6.1.0
  file_picker: ^8.0.0
  path_provider: ^2.1.0
  pdf: ^3.10.0
  printing: ^5.12.0
 ```
 ### 4.3 Prototype Features
 | Feature | Priority |
 |---------|----------|
 | Basic markdown editor | Must have |
 | Live preview | Must have |
 | Light/dark theme | Must have |
 | Tab management | Should have |
 | File open/save | Should have |
 | PDF export | Nice to have |
 | Windows exe build | Must have |
 | Web build | Must have |
 | Mobile build | Should have |
 ### 4.4 Evaluation Criteria
 | Metric | Target |
 |--------|--------|
 | Windows exe size | <50MB |
 | Web initial load | <500KB |
 | Cold start time | <2s |
 | Editor typing latency | <16ms |
 ### 4.5 Flutter vs Tauri Comparison
 | Aspect | Flutter | Tauri + React |
 |--------|---------|---------------|
 | Mobile support | ✅ Excellent | ❌ Requires separate app |
 | Web performance | ⚠️ Good, larger | ✅ Excellent, small |
 | Desktop bundle | ⚠️ ~30-50MB | ✅ ~5-10MB |
 | Native feel | ⚠️ Custom rendering | ✅ System WebView |
 | Code reuse | ✅ 100% shared | ⚠️ Some platform-specific |
 ---
 ## Implementation Timeline
 ### Phase 1: V4 Critical Fixes (Week 1)
 - Fix PDF/markdown multitab bug
 - Implement startup optimizations
 - Add debounced preview rendering
 ### Phase 2: Platform Adapters (Week 2)
 - Create adapter structure
 - Migrate file operations
 - Migrate conversions
 ### Phase 3: UI Improvements (Week 3)
 - Add design tokens
 - Improve component accessibility
 - Add keyboard navigation
 ### Phase 4: Flutter Prototype (Weeks 2-4, parallel)
 - Set up Flutter project
 - Implement basic editor
 - Build Windows and Web versions
 - Document findings
 ---
 ## Risk Mitigation
 | Risk | Mitigation |
 |------|------------|
 | Multitab fix causes regressions | Comprehensive test suite before changes |
 | Performance optimizations break features | Incremental changes with benchmarks |
 | Flutter proves unsuitable | 30% effort limit, V4 remains primary |
 | Platform adapter migration too slow | Phased approach, each phase independent |
 ---
 ## Success Metrics
 - [ ] Multitab functionality working correctly
 - [ ] Startup time < 2 seconds
 - [ ] No perceived editor lag with files < 1MB
 - [ ] Preview renders in < 200ms
 - [ ] Bundle size reduced by 30%+
 - [ ] Platform adapters for fs, convert, pdf implemented
 - [ ] Design tokens applied to all components
 - [ ] Flutter prototype running on Windows + Web
 - [ ] Flutter evaluation documented with recommendation
 ---
 *Document generated: 2026-03-24*
 *Next step: Create detailed implementation plan*
@@ -1,335 +0,0 @@
 # Writer's Studio Feature Pack — Design Document
 **Date**: 2026-04-06
 **Version**: 4.2.0 target
 **Status**: Approved
 **Scope**: Three cohesive features to transform MarkdownConverter into a writing environment
 ---
 ## Overview
 The Writer's Studio Feature Pack adds three interconnected features to MarkdownConverter:
 1. **Zen Mode** — Distraction-free writing environment with typewriter scrolling
 2. **Document Outline** — Heading hierarchy sidebar panel for navigation
 3. **Writing Analytics** — Real-time readability and vocabulary analysis dashboard
 These features work together: Zen Mode creates the environment, Outline provides navigation, Analytics gives insight.
 ---
 ## Feature 1: Zen Mode
 ### Purpose
 Transform the app from a multi-tool into a focused writing environment. Inspired by iA Writer, Typora, and Bear.
 ### New Files
 - `src/zen-mode.js` — ZenMode class (~150 lines)
 - `src/styles-zen.css` — Zen mode specific styles (~120 lines)
 ### Integration Points
 - `src/renderer.js` — Initialize ZenMode, register F11 shortcut, add View > Zen Mode menu
 - `src/editor/codemirror-setup.js` — Export typewriter + dimming extensions
 ### Behavior
 **Toggle**: F11, View > Zen Mode, command palette "Toggle Zen Mode"
 **Exit**: Escape key, F11 again
 **What hides**:
 - Tab bar
 - Toolbar
 - Sidebar (collapsed)
 - Status bar
 - App header
 **What shows**:
 - Editor (full viewport)
 - Floating HUD (bottom-center, semi-transparent)
 ### Floating HUD
 ```
 ┌─────────────────────────────────────────┐
 │  847 words  •  ~4 min  •  23:45 session │
 │  ████████████████░░░░  85% of 1000      │
 └─────────────────────────────────────────┘
 ```
 - Word count (from existing status bar logic)
 - Estimated reading time (~200 wpm)
 - Session timer (starts when zen mode activates)
 - Optional progress bar toward word goal
 ### CodeMirror Extensions
 **Typewriter Scroll** (`ViewPlugin`):
 - Listens to `EditorView.update` for selection changes
 - Calls `editor.dispatch({ effects: EditorView.scrollIntoView(pos, { y: 'center' }) })`
 - Smooth scrolling with `scrollBehavior: 'smooth'` in CSS
 **Line Dimming** (`ViewPlugin` + `Decoration`):
 - Builds a `DecorationSet` mapping each line to an opacity value
 - Active line: opacity 1.0
 - 1-2 lines away: 0.7
 - 3-4 lines away: 0.5
 - 5+ lines away: 0.3
 - Uses `Decoration.line({ attributes: { style: 'opacity: X' } })`
 ### Centered Column
 CSS applied to `.zen-mode .cm-content`:
 ```css
 .zen-mode .cm-content {
    max-width: 700px;
    margin: 0 auto;
    font-size: 18px;
    line-height: 1.8;
 }
 ```
 ### State Management
 - `this.previousState` stores which UI elements were visible before zen mode
 - On exit, restores all elements to their previous visibility
 - Editor content, cursor position, and scroll state are never modified
 ---
 ## Feature 2: Document Outline Panel
 ### Purpose
 Provide always-visible heading navigation for documents of any length. The single most-requested navigation feature for multi-section documents.
 ### New Files
 - `src/sidebar/outline-panel.js` — `renderOutlinePanel` function (~100 lines)
 ### Modified Files
 - `src/index.html` — Add outline icon button in sidebar icons strip
 - `src/renderer.js` — Register 'outline' panel, provide editor reference
 ### Sidebar Integration
 Uses existing `SidebarManager.registerPanel()` API:
 ```javascript
 sidebarManager.registerPanel('outline', {
    title: 'Outline',
    render: (container) => renderOutlinePanel(container, editor, editorContent)
 });
 ```
 New icon button in sidebar strip (after templates icon):
 ```html
 <button class="sidebar-icon" data-panel="outline" title="Outline (Ctrl+Shift+O)">
    <!-- hierarchy/list icon SVG -->
 </button>
 ```
 ### Parsing Logic
 Parse headings from raw markdown content using regex:
 ```javascript
 const headingRegex = /^(#{1,6})\s+(.+)$/gm;
 ```
 Returns array of:
 ```javascript
 { level: 1-6, text: "Heading Text", line: 42 }
 ```
 Debounced at 300ms to avoid re-parsing on every keystroke.
 ### UI Structure
 ```
 ┌──────────────────────────────────────────┐
 │  OUTLINE                          ☰      │
 ├──────────────────────────────────────────┤
 │  ▸ Introduction                  (H1)    │
 │    ▸ Getting Started             (H2)    │
 │    ▸ Prerequisites               (H2)    │
 │      ▸ Node.js                   (H3) ◄  │
 │    ▸ Installation                (H2)    │
 │  ▸ Features                      (H1)    │
 │    ▸ Editor                      (H2)    │
 │    ▸ Export                      (H2)    │
 ├──────────────────────────────────────────┤
 │  9 headings  •  2 H1  •  4 H2  •  3 H3  │
 └──────────────────────────────────────────┘
 ```
 - Indentation based on heading level (H1 = 0px, H2 = 16px, H3 = 32px, etc.)
 - Current heading highlighted with accent color (◄ indicator)
 - Hover shows full heading text if truncated
 ### Click-to-Navigate
 ```javascript
 editor.dispatch({
    effects: EditorView.scrollIntoView(linePos, { y: 'center' })
 });
 ```
 Brief highlight animation on the target line (fades out over 500ms).
 ### Current Heading Sync
 On editor update (debounced 100ms):
 1. Get cursor line number
 2. Find the last heading whose line number <= cursor line
 3. Set that heading as active in the outline
 ### Empty State
 When no headings found:
 ```
 No headings found
 Use # to create headings:
 # Heading 1
 ## Heading 2
 ### Heading 3
 ```
 ---
 ## Feature 3: Writing Analytics
 ### Purpose
 Give writers real-time insight into their document's readability, structure, and vocabulary. This is the "surprise" feature most Markdown editors lack.
 ### New Files
 - `src/analytics/writing-analytics.js` — `WritingAnalytics` class (~180 lines)
 - `src/analytics/analytics-panel.js` — `renderAnalyticsPanel` function (~120 lines)
 ### Integration Points
 - `src/renderer.js` — Register Ctrl+Shift+A shortcut, command palette entry, View menu item
 ### Trigger
 - Keyboard: `Ctrl+Shift+A`
 - Command Palette: "Show Writing Analytics"
 - Menu: View > Writing Analytics
 ### Presentation
 Uses existing `ModalManager` to show a modal overlay with analytics dashboard.
 ```
 ┌─────────────────────────────────────────────────────┐
 │  Writing Analytics                              ✕   │
 ├─────────────────────────────────────────────────────┤
 │                                                      │
 │  ┌─ Readability ──────────────────────────────────┐ │
 │  │  Flesch Reading Ease:  67.3 (Standard)    ○   │ │
 │  │  Grade Level:          8.2              ○○○●○  │ │
 │  └─────────────────────────────────────────────────┘ │
 │                                                      │
 │  ┌─ Timing ───────────────────────────────────────┐ │
 │  │  Reading Time:   ~4 min                        │ │
 │  │  Speaking Time:  ~6 min                        │ │
 │  └─────────────────────────────────────────────────┘ │
 │                                                      │
 │  ┌─ Structure ────────────────────────────────────┐ │
 │  │  Sentences:  42  •  Paragraphs:  8            │ │
 │  │  Avg Sentence:  14.2 words                     │ │
 │  │  Longest:  38 words ("The quick brown fox...") │ │
 │  └─────────────────────────────────────────────────┘ │
 │                                                      │
 │  ┌─ Vocabulary ───────────────────────────────────┐ │
 │  │  Unique: 312 / 847 words (36.8%)               │ │
 │  │  Top: the(42) and(31) markdown(28) ...         │ │
 │  └─────────────────────────────────────────────────┘ │
 │                                                      │
 │  ┌─ Word Goal ────────────────────────────────────┐ │
 │  │  Target: [1000] words                          │ │
 │  │  ████████████████░░░░  847/1000 (85%)          │ │
 │  └─────────────────────────────────────────────────┘ │
 │                                                      │
 └─────────────────────────────────────────────────────┘
 ```
 ### Metrics Implementation
 **Readability (Flesch-Kincaid):**
 ```javascript
 // Flesch Reading Ease
 ease = 206.835 - 1.015 * (words / sentences) - 84.6 * (syllables / words);
 // Flesch-Kincaid Grade Level
 grade = 0.39 * (words / sentences) + 11.8 * (syllables / words) - 15.59;
 ```
 **Syllable Estimation:**
 ```javascript
 function countSyllables(word) {
    word = word.toLowerCase().replace(/(?:[^laeiouy]es|ed|[^laeiouy]e)$/, '');
    word = word.replace(/^y/, '');
    return word.match(/[aeiouy]{1,2}/g)?.length || 1;
 }
 ```
 **Reading/Speaking Time:**
 - Reading: 200 words/minute
 - Speaking: 130 words/minute
 **Lexical Diversity:**
 - Ratio of unique words to total words (excluding stop words)
 **Top Words:**
 - Frequency map, sorted descending, top 10
 - Excludes common stop words (the, a, an, is, are, etc.)
 ### Word Goal
 - Persisted in `electron-store` per document (or global default)
 - Progress bar with percentage
 - Celebration effect when goal is reached (brief confetti animation or green flash)
 ### Update Cadence
 - Re-analyzes on editor content change (debounced at 1000ms)
 - If modal is open, updates live
 - If modal is closed, no computation (zero overhead)
 ---
 ## File Summary
 | File | Action | Purpose |
 |------|--------|---------|
 | `src/zen-mode.js` | Create | ZenMode class with CM6 extensions |
 | `src/styles-zen.css` | Create | Zen mode styling |
 | `src/sidebar/outline-panel.js` | Create | Outline sidebar panel |
 | `src/analytics/writing-analytics.js` | Create | Analytics computation engine |
 | `src/analytics/analytics-panel.js` | Create | Analytics modal UI |
 | `src/index.html` | Modify | Add outline icon, zen mode button |
 | `src/renderer.js` | Modify | Initialize all three features |
 | `src/editor/codemirror-setup.js` | Modify | Export typewriter + dimming extensions |
 ## Keyboard Shortcuts
 | Shortcut | Feature | Action |
 |----------|---------|--------|
 | F11 | Zen Mode | Toggle on/off |
 | Escape | Zen Mode | Exit (when active) |
 | Ctrl+Shift+O | Outline | Open outline sidebar panel |
 | Ctrl+Shift+A | Analytics | Open analytics modal |
 ## Dependencies
 No new npm dependencies required. All features use:
 - Existing CodeMirror 6 APIs (ViewPlugin, Decoration, scrollIntoView)
 - Existing SidebarManager API
 - Existing ModalManager API
 - Pure JavaScript math for analytics
@@ -1,270 +0,0 @@
 # Packaging — All-Platform Build + GitHub Releases
 **Goal:** Make `npm run dist:all` produce Linux + Windows + macOS artifacts, and have the existing `.github/workflows/release.yml` create a GitHub Release on tag push with those artifacts. No code signing in this iteration.
 **Scope (user decisions 2026-06-06):**
 - Target platforms: **all three** (Linux .deb/AppImage/snap, Windows NSIS/portable/zip, macOS dmg/zip)
 - Distribution: **GitHub Releases** (no auto-update; static artifacts only)
 - Code signing: **skip for now** (unsigned binaries; Windows SmartScreen will warn, macOS Gatekeeper will quarantine)
 **Architecture:** This is mostly about completing the existing scaffold. `electron-builder` 26.0.12, `scripts/download-tools.js`, `scripts/generate-icons.js`, the `package.json` scripts, and `release.yml` are all already in place. We need to (1) close a real bug in the `files` config, (2) add the macOS job to the workflow, and (3) declare macOS targets in the package config.
 **Tech stack:** electron-builder 26.0.12, GitHub Actions `ubuntu-latest`/`windows-latest`/`macos-latest` runners, softprops/action-gh-release@v2 for the release creation.
 ---
 ## Task 1 — Fix the `files` config in `package.json`
 The current `files: ["src/**/*", ...]` matches `src/renderer/**/*.tsx` and ships dev source into the asar. The shipped renderer should be the built `dist/renderer/**/*` output, not TS source. asarUnpack for ffmpeg-static is correct and stays.
 **Files:** `package.json` (build.files, build.extraResources)
 ### Step 1.1 — Replace `files` block
 ```json
 "files": [
  "src/main/**/*",
  "src/preload.js",
  "src/plugins/**/*",
  "package.json"
 ],
 "extraResources": [
  {
    "from": "dist/renderer",
    "to": "renderer"
  }
 ]
 ```
 - `src/main/**/*` — main process source (entry point + all main-process modules)
 - `src/preload.js` — single preload file at the root of `src/`
 - `src/plugins/**/*` — built-in plugins (referenced from main process; the `extraFiles: []` line in the current config is empty, so this is the right pattern)
 - `package.json` — required for the asar `app.asar/package.json` lookup electron does at runtime
 - `dist/renderer` moves to `extraResources` because it should live alongside the asar (not inside it) — the asar is sealed and we want the renderer to be a separately-updatable resource path. Production main loads it via `loadFile(path.join(__dirname, '../../dist/renderer/index.html'))` which, in the packaged app, resolves to `process.resourcesPath/renderer/index.html`. **This requires changing the loadFile path in `src/main/window/index.js` too** — see Task 4.
 ### Step 1.2 — Verify
 - `npm run build:linux` should produce a working .AppImage
 - Inside the .AppImage (extract with `--appimage-extract`), check `resources/` has `app.asar` and a `renderer/` directory containing `index.html` and `assets/`
 - Inside `app.asar`, check `src/main/index.js` is present and `src/renderer/` is absent
 ---
 ## Task 2 — Add macOS targets + icon to `package.json` build config
 **Files:** `package.json`
 ### Step 2.1 — Replace the existing `mac` block
 ```json
 "mac": {
  "category": "public.app-category.productivity",
  "identity": null,
  "target": [
    { "target": "dmg", "arch": ["x64", "arm64"] },
    { "target": "zip", "arch": ["x64", "arm64"] }
  ],
  "icon": "assets/icon.icns",
  "darkModeSupport": true,
  "hardenedRuntime": false,
  "gatekeeperAssess": false,
  "entitlements": null
 }
 ```
 - `identity: null` is intentional for unsigned builds
 - `darkModeSupport: true` — the app already supports dark mode; this is just metadata
 - `hardenedRuntime: false` and `gatekeeperAssess: false` — without signing, these are the only way the build succeeds
 - `entitlements: null` — no entitlements file; some features (jit) won't work but Electron's main process doesn't need them in this app
 - **`.icns` is missing.** For this iteration we'll use the default Electron icon and add a follow-up to generate one. The build will succeed without it but the produced .app will have the default icon.
 ### Step 2.2 — Generate a placeholder `.icns` (optional, can be deferred)
 If we want a proper icon, the path is:
 1. `npm run generate-icons` to produce `assets/icons/*.png` (already done)
 2. Use `png2icns` (Linux) or `iconutil` (mac) to bundle them into `assets/icon.icns`
 3. We don't have either on this Linux container; defer to a follow-up plan
 For this iteration: ship without `.icns` and accept the default icon.
 ### Step 2.3 — Add `publish` config
 ```json
 "publish": {
  "provider": "github",
  "owner": "amitwh",
  "repo": "markdown-converter",
  "releaseType": "release"
 }
 ```
 Even without auto-update, this tells `electron-builder` to write `latest-mac.yml` / `latest-linux.yml` next to the artifacts. Useful for future auto-update wiring. CI passes `--publish=never` to override.
 ---
 ## Task 3 — Add macOS job to `.github/workflows/release.yml`
 **Files:** `.github/workflows/release.yml`
 ### Step 3.1 — Add a third job between `build-windows` and `release`
 Insert after the `build-windows` job (around line 96):
 ```yaml
  build-macos:
    runs-on: macos-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: npm
      - name: Install dependencies
        run: npm ci
      - name: Download external tools (pandoc)
        run: node scripts/download-tools.js
      - name: Run tests
        run: npm test
      - name: Build macOS packages (unsigned)
        env:
          CSC_IDENTITY_AUTO_DISCOVERY: 'false'
        run: npm run build:mac -- --publish=never
      - name: Upload macOS artifacts
        uses: actions/upload-artifact@v4
        with:
          name: macos-artifacts
          path: |
            dist/*.dmg
            dist/*.zip
          retention-days: 5
 ```
 ### Step 3.2 — Wire macOS into the `release` job's `needs` and downloads
 Change the `release` job:
 ```yaml
  release:
    needs: [build-linux, build-windows, build-macos]
    ...
 ```
 And add a third download step (after the Windows download):
 ```yaml
      - name: Download macOS artifacts
        uses: actions/download-artifact@v4
        continue-on-error: true
        with:
          name: macos-artifacts
          path: dist
 ```
 `continue-on-error: true` is intentional — a failed macOS build shouldn't block a release of working Linux+Windows artifacts.
 ---
 ## Task 4 — Update `src/main/window/index.js` for the resource path
 **Files:** `src/main/window/index.js`
 ### Step 4.1 — Update the loadFile path
 The current code (line 35):
 ```js
 const prodPath = path.join(__dirname, '../../dist/renderer/index.html');
 ```
 Inside the packaged app, `__dirname` points into the asar. `process.resourcesPath` points to the directory holding `app.asar` + the `renderer/` extraResources dir. Change to:
 ```js
 const rendererIndex = app.isPackaged
  ? path.join(process.resourcesPath, 'renderer', 'index.html')
  : path.join(__dirname, '../../dist/renderer/index.html');
 win.loadFile(rendererIndex);
 ```
 This needs to happen after the dev/prod branch is decided. The existing `if (!app.isPackaged && devServerUrl)` block already handles dev mode; the else branch needs this update.
 ### Step 4.2 — Add a guard for missing renderer in prod
 ```js
 if (app.isPackaged) {
  try {
    fs.accessSync(path.join(process.resourcesPath, 'renderer', 'index.html'));
  } catch {
    console.error('[WINDOW] Renderer not found at', process.resourcesPath, '— did you run `npm run build:renderer` before packaging?');
  }
 }
 ```
 Failure mode: someone runs `npm run build` without first building the renderer. Without this guard, the window opens blank and the user has no idea why.
 ---
 ## Task 5 — Test on this Linux box
 ### Step 5.1 — Local verification
 ```bash
 npm ci
 npm run download-tools   # idempotent; bin/linux/pandoc already exists
 npm run build:renderer
 npm run build:linux      # produces .deb, .AppImage in dist/
 ```
 Inspect the .AppImage:
 ```bash
 chmod +x dist/*.AppImage
 ./dist/MarkdownConverter-*.AppImage --appimage-extract
 ls squashfs-root/resources/
 # Expect: app.asar  renderer/
 ls squashfs-root/resources/renderer/
 # Expect: index.html  assets/
 ```
 ### Step 5.2 — Run the produced app
 ```bash
 ./dist/MarkdownConverter-*.AppImage
 ```
 The app should:
 - Launch with the AppShell, header, sidebar
 - Allow opening a folder / file
 - Export to PDF/DOCX/HTML work (pandoc bundled)
 ### Step 5.3 — Tag + push to test the release workflow (optional)
 Only do this if the user wants to verify the full pipeline. A dry-run on the CI side via `act` would be cleaner but `act` doesn't run macos-latest jobs locally. If the user wants to verify the workflow, push a `v5.0.1-rc1` tag and watch the Actions tab.
 ---
 ## Success criteria
 1. `npm run dist:all` produces all three platform families on this Linux box (or at least Linux + mac, since Windows is built on Windows)
 2. The .AppImage launches and the app works end-to-end
 3. `release.yml` runs all three jobs on a tag push and creates a GitHub release with the union of artifacts
 4. No regressions: 306/306 tests still pass, dev workflow still works
 5. The `files` bug is fixed: no `.tsx` in the packaged asar
 ## Known limitations (intentional, can be follow-ups)
 - **No `.icns`** — the macOS app will have the default Electron icon. Generating a proper `.icns` requires `iconutil` (mac) or `png2icns` (cross-platform); neither is on this Linux box.
 - **No code signing** — Windows SmartScreen will warn; macOS Gatekeeper will quarantine unsigned `.dmg`. Setting up signing later is a config-only change (no structural rework): add `CSC_LINK`/`CSC_KEY_PASSWORD` for Windows, `CSC_LINK` (Apple Developer ID) for mac.
 - **No auto-update** — user decisions for this iteration. Wiring `electron-updater` is a follow-up; the `publish` config from Task 2 puts metadata in the right place.
 - **Cross-build quirks** — building macOS from Linux produces a `.dmg` that is generally usable but may show a "this app is from an unidentified developer" prompt the first time. Right-click → Open to bypass once. Documented in the release notes.
 ## Out of scope
 - CHANGELOG.md updates (not part of packaging)
 - electron-updater wiring
 - Code signing cert procurement
 - Snap store / Microsoft Store / Mac App Store submission
@@ -1,426 +0,0 @@
 # MarkdownConverter v5.0 — Platform Design
 **Date:** 2026-04-14
 **Status:** Approved
 **Author:** Amit Haridas
 ## Overview
 Transform MarkdownConverter from a monolithic editor into an extensible platform with a plugin system and three feature packs, shipped together as v5.0.
 ## Subsystems
 1. **Plugin System** — Lightweight plugin registry with extension points (sidebar, commands, settings, status bar, export hooks, event bus)
 2. **Writing Studio Plugin** — Manuscript manager, goal tracking, writing sprints, snapshots, smart proofreading
 3. **AI Assistant Plugin** — Multi-provider AI writing assistant (Ollama, LMStudio, GGUF direct with GPU, Anthropic, OpenAI)
 4. **Collaboration Plugin** — Git-based async collaboration, comments/annotations, review requests
 ## Core Principle
 **Existing functionality is never replaced or broken.** The plugin system is additive. All existing keyboard shortcuts, features, and UI remain untouched. Plugin shortcuts use `Ctrl+Alt+` namespace.
 ---
 ## 1. Plugin System
 ### File Structure
 ```
 src/
  plugins/
    plugin-registry.js      # Load, register, lifecycle
    plugin-api.js            # Base class plugins extend
    plugin-loader.js         # Discovers and validates manifests
    built-in/
      writing-studio/
        manifest.json
        index.js
        panels/
        components/
      ai-assistant/
        manifest.json
        index.js
        providers/
      collaboration/
        manifest.json
        index.js
 ```
 ### Manifest Schema
 ```json
 {
  "id": "writing-studio",
  "name": "Writing Studio",
  "version": "1.0.0",
  "description": "Manuscript management, goal tracking, writing sprints",
  "icon": "pen-tool",
  "extensionPoints": {
    "sidebar": { "panel": "panels/manuscript-panel.js", "order": 30 },
    "settings": { "section": "settings/index.js" },
    "statusBar": { "indicators": ["sprint-timer", "word-goal"] },
    "commands": [
      { "id": "start-sprint", "label": "Start Writing Sprint", "shortcut": "Ctrl+Alt+S" },
      { "id": "take-snapshot", "label": "Take Snapshot", "shortcut": "Ctrl+Alt+N" }
    ],
    "exportHooks": {
      "preExport": "hooks/pre-export.js",
      "postExport": "hooks/post-export.js"
    }
  },
  "settings": [
    { "key": "dailyGoal", "type": "number", "default": 1000, "label": "Daily word goal" },
    { "key": "sprintDuration", "type": "number", "default": 25, "label": "Sprint duration (min)" }
  ]
 }
 ```
 ### Plugin Lifecycle
 1. PluginLoader discovers manifests in `built-in/` + user plugins directory
 2. PluginRegistry validates manifests
 3. Each plugin calls `Plugin.init(context)` receiving scoped API context
 4. Extension points registered (sidebar panels, commands, status bar items)
 5. Plugins activate lazily — sidebar panel loads JS when user clicks tab
 ### Plugin Context API
 Each plugin's `init()` receives:
 ```javascript
 {
  sidebar: {
    registerPanel(id, { icon, title, component })
  },
  commands: {
    register(id, label, handler, shortcut?)
  },
  statusBar: {
    registerIndicator(id, { position, render })
  },
  settings: {
    get(key),                    // plugin-scoped
    set(key, value),             // auto-persisted via electron-store
    onChanged(key, callback)
  },
  editor: {
    getContent(),                // current document
    getSelection(),              // selected text
    insertAtCursor(text),        // requires opt-in
    onContentChanged(callback)
  },
  events: {
    on(event, handler),
    emit(event, data)
  },
  exports: {
    registerPreHook(handler),
    registerPostHook(handler)
  },
  ipc: {
    invoke(channel, ...args),
    on(channel, handler)
  }
 }
 ```
 ### Event Bus Events
 Each event has a versioned payload schema. Breaking changes increment the version suffix.
 ```
 document:opened        → { filePath: string, tabId: string }
 document:saved         → { filePath: string, tabId: string }
 document:changed       → { tabId: string, content: string, wordCount: number }
 editor:selection-changed → { tabId: string, text: string, from: {line,ch}, to: {line,ch} }
 tab:switched           → { tabId: string, filePath: string }
 tab:closed             → { tabId: string, filePath: string }
 export:started         → { format: string, filePath: string }
 export:completed       → { format: string, filePath: string, outputPath: string }
 export:failed          → { format: string, error: string }
 plugin:loaded          → { pluginId: string, version: string }
 plugin:activated       → { pluginId: string }
 plugin:deactivated     → { pluginId: string }
 app:ready              → {}
 app:before-quit        → {}
 ```
 ### Design Rules
 - Built-in plugins use the same API as future third-party plugins
 - Lazy activation — sidebar panels don't load until clicked
 - Scoped settings: `plugins.<id>.<key>` in electron-store
 - Plugin commands globally unique — registry rejects duplicate command IDs at load time
 - **Plugin sandboxing**: each plugin handler is wrapped in try/catch. For CPU-intensive operations (AI inference, diff computation), plugins must delegate to main process via IPC. Handlers that block the renderer for >5s trigger a warning notification. Memory-hungry operations (GGUF inference) run in isolated child processes.
 - **Cross-plugin graceful degradation**: plugins check `context.events.hasHandler('ai:analyze')` before emitting cross-plugin requests. If no handler (AI plugin disabled), show a "this feature requires the AI plugin" prompt instead of failing silently. All cross-plugin calls have a 30s timeout with default fallback behavior.
 ---
 ## 2. Writing Studio Plugin
 ### 2A. Manuscript / Project Manager
 Folder-based project structure:
 ```
 ~/Manuscripts/
  my-novel/
    .project.json          # { title, targets, metadata }
    01-chapter-one.md
    02-chapter-two.md
    characters/
      protagonist.md
    research/
      world-building.md
    .snapshots/
      2026-04-14T10-30.json
 ```
 `.project.json`:
 ```json
 {
  "title": "My Novel",
  "type": "manuscript",
  "target": { "words": 80000, "deadline": "2026-09-01" },
  "chapters": [
    { "file": "01-chapter-one.md", "title": "The Beginning", "status": "draft" }
  ],
  "metadata": { "author": "", "genre": "", "synopsis": "" }
 }
 ```
 Sidebar panel shows project tree with drag-to-reorder, word counts per chapter, target progress bar. "Compile manuscript" exports all chapters as a single document.
 ### 2B. Goal Tracking & Writing Sprints
 - **Status bar**: daily progress bar + sprint timer
 - **Writing sprint**: configurable duration (15/25/30/45/60 min), word count delta, WPM at end
 - **Goal tracking**: daily/weekly word goals, streak tracking, 30-day bar chart
 - **Enhanced analytics**: session tracking, readability scores, productive time-of-day heatmap
 - Data stored in `plugins.writing-studio.history` as date-keyed map
 ### 2C. Snapshot & Versioning
 - `Ctrl+Alt+N` or toolbar button saves snapshot
 - Stored as JSON: `{ timestamp, content, wordCount, cursorPos, label }`
 - Snapshot panel in sidebar: Restore, Diff (side-by-side), auto-snapshot interval
 - Snapshots in `.snapshots/` inside project folder, or app data if no project
 ### 2D. Smart Proofreading
 Delegates to AI plugin via event bus. Writing Studio provides:
 - Right-click context menu: "Check grammar", "Suggest alternatives", "Analyze readability"
 - Inline wavy underline decorations for issues
 - Proofread panel: issues categorized by type with Accept/Dismiss
 ### Commands
 | Command | Shortcut | Action |
 |---------|----------|--------|
 | `start-sprint` | `Ctrl+Alt+S` | Start writing sprint |
 | `stop-sprint` | `Ctrl+Alt+Shift+S` | Stop sprint |
 | `take-snapshot` | `Ctrl+Alt+N` | Save snapshot |
 | `restore-last-snapshot` | `Ctrl+Alt+Z` | Restore latest snapshot |
 | `new-project` | — | Create manuscript project |
 | `compile-manuscript` | `Ctrl+Alt+E` | Export all chapters |
 | `proofread-document` | `Ctrl+Alt+G` | AI proofread |
 ---
 ## 3. AI Assistant Plugin
 ### Provider Architecture
 ```
 AI Plugin
  ├── Provider Interface
  │     ├── complete(prompt, options) → string
  │     ├── stream(prompt, options) → AsyncIterable
  │     └── analyze(text, type) → AnalysisResult
  │
  ├── Providers
  │     ├── OllamaProvider      — localhost:11434
  │     ├── LMStudioProvider    — localhost:1234/v1
  │     ├── GGUFProvider         — direct llama.cpp with GPU support
  │     ├── AnthropicProvider    — Claude API
  │     └── OpenAIProvider       — GPT API
  │
  └── Features
        ├── Grammar/style check
        ├── Inline auto-complete
        ├── AI chat panel (sidebar)
        ├── Document analysis
        └── Smart commands (command palette)
 ```
 ### Provider Details
 **Ollama:** `GET /api/tags` for models, `POST /api/generate` and `POST /api/chat` for inference.
 **LMStudio:** OpenAI-compatible API at `localhost:1234/v1`. `GET /v1/models`, standard chat completion format, SSE streaming.
 **GGUF Direct (with GPU):**
 - Ships bundled llama.cpp binaries per platform (CUDA, Vulkan, Metal, CPU variants)
 - Auto-detects GPU: CUDA (nvidia-smi), Vulkan driver, Metal (macOS)
 - GPU layer offloading: configurable, auto-suggests based on VRAM vs model size
 - Settings: GPU backend selection, layer count, context length, thread count
 - "Keep model loaded" option for faster repeated requests
 - WASM fallback for sandboxed environments (CPU-only)
 - External binary path for advanced users with custom builds
 - **Process isolation**: llama.cpp runs as a spawned child process (not in main process). If it crashes, detected via exit handler, auto-restarted with notification. GPU memory freed on crash. App remains stable.
 - Process management: spawn in server mode on localhost ephemeral port, clean up on app quit or model unload
 **Cloud (Anthropic/OpenAI):**
 - API key stored encrypted via electron safeStorage
 - Token usage tracking with estimated cost
 - Rate limit awareness with request queueing and backoff
 ### IPC Design
 All provider HTTP requests go through main process:
 - No CORS issues
 - API keys never in renderer
 - Main process enforces rate limiting
 - GGUF inference in isolated child process
 **Request/response lifecycle:**
 ```
 Renderer → ipc.invoke('ai:complete') → Main → HTTP to provider → result → Renderer
 ```
 **Streaming lifecycle with error handling:**
 ```
 Renderer → ipc.invoke('ai:stream', { requestId, prompt })
         ← Main assigns requestId, returns { requestId }
         ← ipc.on('ai:chunk', { requestId, text }) — repeated
         ← ipc.on('ai:done', { requestId }) — success
         ← ipc.on('ai:error', { requestId, error }) — failure
 // Cancellation
 Renderer → ipc.invoke('ai:cancel', { requestId })
         ← Main aborts HTTP request, emits 'ai:done'
 // Orphan cleanup: if renderer disconnects (crash/close),
 // main process detects via 'render-view-deleted' and aborts all active streams.
 // Heartbeat: if no chunk received in 30s, main emits 'ai:error' with timeout.
 ```
 ### Features
 1. **Inline suggestions**: ghost text after configurable delay, Tab to accept, Esc to dismiss
 2. **AI chat panel**: sidebar conversation, "Insert" / "Replace selection" buttons
 3. **Document analysis**: grammar, style, tone, with accept/reject per suggestion
 4. **Smart commands**: summarize, generate outline, find inconsistencies, translate, explain code
 ### Privacy
 - Local-first: default provider is Ollama
 - No telemetry: requests go direct to provider
 - Content gating: exclude file types from AI
 - Status bar shows "AI: processing..." with cancel option
 - Cloud usage stats in settings (tokens, cost)
 ### Cross-Plugin Integration
 ```javascript
 // Writing Studio calls AI Plugin
 context.events.emit('ai:analyze', { text, type: 'grammar', callback });
 ```
 ---
 ## 4. Collaboration Plugin
 ### 4A. Enhanced Git Panel
 Upgrades to existing git panel:
 - Remote management (add/remove remotes, push/pull)
 - Branch list and switching
 - Commit history with diff viewer (side-by-side or unified)
 - Conflict resolution UI (accept-ours/accept-theirs/per-edit)
 ### 4B. Shared Repository Workflow
 1. Writer A creates project + initializes git + pushes to shared repo
 2. Writer B clones repo from within MarkdownConverter
 3. Both write on their own branches
 4. Writer A creates review request (simplified PR)
 Review request: changed files, word count diff, commit messages. Reviewer can approve, request changes, leave inline comments. Reviews are git branches + comments as git notes.
 ### 4C. Comments & Annotations
 Inline comments stored as JSON in `.comments/` directory (git-tracked):
 ```json
 {
  "id": "uuid",
  "file": "03-chapter-three.md",
  "anchor": {
    "contextBefore": "The hero looked at the horizon and said,",
    "selectedText": "I will not go quietly into that dark night",
    "contextAfter": "He turned to face the army alone."
  },
  "line": 142,
  "text": "This dialogue feels unnatural",
  "author": "amit",
  "timestamp": "2026-04-14T14:30:00Z",
  "replies": [],
  "resolved": false
 }
 ```
 - **Anchor-based positioning**: comments store `contextBefore`, `selectedText`, and `contextAfter` (not absolute byte offsets). On file change, re-anchor by searching for the context text. If context no longer matches, mark comment as "detached" and show a warning. Falls back to `line` number as rough position.
 - Highlighted text in editor with tooltip on hover
 - Comment panel in sidebar: all unresolved comments across files
 - Resolution workflow: add → address → reply → resolve
 - Resolved comments dim but stay visible
 ### 4D. Change Notifications
 - Status bar indicator: `↓ 3 new commits`
 - Click to see changes, one-click pull
 - Conflicts trigger resolution UI
 - Push button only when local commits ahead of remote
 ### 4E. Offline-First
 All writing happens locally. Git is the sync mechanism. No internet required for writing, commenting, snapshots, or sprints. Push/pull on user action or auto-sync setting.
 ### Commands
 | Command | Shortcut | Action |
 |---------|----------|--------|
 | `collab:commit` | `Ctrl+Shift+G` | Commit with message |
 | `collab:push` | — | Push current branch |
 | `collab:pull` | — | Pull from remote |
 | `collab:add-comment` | `Ctrl+Alt+C` | Comment on selection |
 | `collab:next-comment` | `F8` | Next unresolved comment |
 | `collab:prev-comment` | `Shift+F8` | Previous comment |
 | `collab:create-review` | — | Create review request |
 ### Cross-Plugin Integration
 ```javascript
 context.events.emit('snapshot:created', { file, snapshotId });
 context.events.on('project:chapter-opened', (chapter) => { /* load comments */ });
 context.events.on('comment:added', (comment) => { /* AI could suggest fix */ });
 ```
 ---
 ## Bundle Size Impact
 - llama.cpp binaries: ~15MB per GPU variant. Only target platform shipped. GPU variants (CUDA/Vulkan/Metal) downloaded on demand if user enables GGUF direct loading — not bundled by default. Only CPU fallback bundled (~15MB).
 - Plugin system core: ~30KB
 - Each built-in plugin: ~50-100KB
 - Diff library (jsdiff): ~15KB
 - Total estimated increase: ~20-30MB (core), additional ~30-50MB per GPU variant (lazy download)
 ## Testing Strategy
 - Plugin system: unit tests for registry, loader, context API mocking
 - Each plugin: isolated unit tests, integration tests via plugin context
 - AI provider tests: mock HTTP responses, test streaming parsing
 - Git tests: use test repository fixture
 - E2E: verify plugin loading doesn't break existing features
@@ -1,399 +0,0 @@
 # Phase 7 — Modals Design
 > Companion to the parent plan: `docs/superpowers/plans/2026-06-05-react-ui-redesign.md` (Phases 7+8+9+10 are sketched there at high level; this spec locks Phase 7's architecture, file map, and contracts so it can be planned task-by-task.)
 **Date:** 2026-06-05
 **Phase:** 7 of 10 (React + shadcn/ui UI redesign)
 **Tag (on completion):** `phase-7-modals`
 ---
 ## 1. Goal & Non-Goals
 **Goal:** Add a layered modal system to the React renderer. Wire 7 modal types (SettingsSheet + 4 Export dialogs + About + Welcome + Confirm) to a single `<ModalLayer />`. Add a persisted `useSettingsStore` for user preferences. The modals are opened via the command store (Phase 6 pattern), and the modals themselves read/write settings via the new store.
 **Non-goals (Phase 7):**
 - Implement the actual export pipelines (PDF/DOCX/HTML/PNG generation) — those are main-process concerns, already implemented. Phase 7 only adds the renderer-side dialog UI.
 - Real plugin system — the Plugins tab is a placeholder ("Coming soon").
 - Toast notifications — Phase 8.
 - Advanced tools (Zen mode, REPL, ASCII/Table generators, Print preview) — Phase 9.
 ---
 ## 2. Architecture
 ### 2.1 Modal state lives in `useAppStore` (extended, not new store)
 `useAppStore` is already the "global UI" store (sidebar, preview, zen, paneSizes). It's the right home for modal state because:
 - It's already mounted.
 - It's already persisted (via `zustand persist` with `partialize` for pane sizes).
 - A separate `useUIStore` would be YAGNI.
 **Add to `AppState`:**
 - `modal: ModalState` (discriminated union — see §2.2)
 - `openModal: <K extends ModalKind>(kind: K, props?: ModalPropsFor<K>) => void`
 - `closeModal: () => void`
 **Persistence:** `modal` is **runtime-only**, like `userBindings` in `useCommandStore`. We add it to the `partialize` function so only the persisted fields (`sidebarVisible`, `previewVisible`, `zenMode`, `paneSizes`) are saved. The modal kind never needs to survive a reload.
 ### 2.2 Discriminated-union modal shape
 ```ts
 export type ModalState =
  | { kind: null }
  | { kind: 'export-pdf';     props: { sourcePath: string } }
  | { kind: 'export-docx';    props: { sourcePath: string } }
  | { kind: 'export-html';    props: { sourcePath: string } }
  | { kind: 'export-batch';   props: { sourcePaths: string[] } }
  | { kind: 'settings' }
  | { kind: 'about' }
  | { kind: 'welcome' }
  | { kind: 'confirm';        props: ConfirmProps };
 export interface ConfirmProps {
  title: string;
  body: string;
  confirmLabel?: string;       // default "Confirm"
  cancelLabel?: string;        // default "Cancel"
  destructive?: boolean;       // switches confirm button to red variant
  onConfirm: () => void | Promise<void>;
  onCancel?: () => void;
 }
 ```
 **Why a discriminated union:** every component that opens a modal must pass the right `props` shape for the `kind` — TypeScript catches mismatches at compile time. A generic `{ open: boolean, type: string }` shape would defer the error to runtime.
 ### 2.3 Single `<ModalLayer />`
 Mounted at the bottom of `App.tsx`. Reads `modal.kind` from `useAppStore`, renders the matching component (or `null`). Each child modal calls `closeModal()` on dismiss.
 ```tsx
 // src/renderer/components/modals/ModalLayer.tsx (sketch)
 export function ModalLayer() {
  const modal = useAppStore((s) => s.modal);
  switch (modal.kind) {
    case null: return null;
    case 'export-pdf':   return <ExportPdfDialog {...modal.props} />;
    // ... etc
  }
 }
 ```
 `<ModalLayer />` ensures only one modal is visible at a time (the store only holds one). This is correct for v1 — no need for stacking/replacement transitions in Phase 7.
 ### 2.4 Settings store (new, separate)
 A new `useSettingsStore` for user preferences. **Why separate from `useAppStore`:** settings is a different lifecycle. `useAppStore` is "current view configuration"; `useSettingsStore` is "user preferences that survive across sessions and are read by many features". Same precedent as `useFileStore` (file tree state) being separate from `useAppStore` (UI chrome state).
 **Persistence:** `zustand persist` with `partialize` to serialize only the leaf settings (matching the pattern in `useFileStore` and `useCommandStore`).
 ```ts
 interface SettingsState {
  // Editor
  fontSize: number;            // 12-20, default 14
  tabSize: number;             // 2 | 4 | 8, default 4
  lineNumbers: boolean;        // default true
  wordWrap: boolean;           // default true
  minimap: boolean;            // default true
  // Theme
  theme: 'light' | 'dark' | 'auto';  // default 'auto'
  accentColor: 'brand' | 'blue' | 'green' | 'purple' | 'orange';  // default 'brand'
  fontFamily: 'system' | 'jetbrains' | 'fira';  // default 'system'
  // Export
  pdfFormat: 'letter' | 'a4' | 'legal';  // default 'a4'
  pdfMargins: 'normal' | 'narrow' | 'wide';  // default 'normal'
  pdfEmbedFonts: boolean;       // default true
  docxTemplate: 'standard' | 'minimal' | 'modern';  // default 'standard'
  htmlHighlightStyle: 'github' | 'monokai' | 'nord' | 'none';  // default 'github'
  // ASCII table formatting — applies to all 3 single-file export formats
  renderTablesAsAscii: boolean;  // default false
  // First-launch / Welcome
  welcomeDismissed: boolean;    // default false
  // Actions
  setSetting: <K extends keyof Omit<SettingsState, ...>>(...);
  resetToDefaults: () => void;
 }
 ```
 **Template-based exports** (per user request): `docxTemplate` is one of `'standard' | 'minimal' | 'modern'`. The export dialog shows a Select with the available templates. The IPC layer (`ipc.export.docx`) already accepts a `template` field; Phase 7 just exposes it. The main process maps these template names to actual `.docx` template files bundled with the app.
 **ASCII table formatting** (per user request): `renderTablesAsAscii` is a toggle in the Settings sheet (Export tab) and in each of the 3 single-file export dialogs as an inline checkbox override. When true, the markdown AST's table nodes are converted to fixed-width monospace text (using a small `lib/ascii-table.ts` helper) *before* the export pipeline sees them. The preview pane is unaffected — this is export-time only.
 ### 2.5 WelcomeDialog trigger logic
 A small `useEffect` in `App.tsx`:
 ```ts
 useEffect(() => {
  if (!useSettingsStore.getState().welcomeDismissed) {
    useAppStore.getState().openModal('welcome');
  }
 }, []);  // run once on mount
 ```
 The Help menu registers a `help.welcome` command that simply calls `openModal('welcome')` — does NOT reset the `welcomeDismissed` flag. (Decision in §2.4 of the brainstorming.)
 ### 2.6 Commands trigger modals
 The command store (Phase 6) gets new commands. Registered in `src/renderer/lib/commands/register-menu-commands.ts`:
 | Command ID       | Handler                                              |
 |------------------|------------------------------------------------------|
 | `file.exportPdf`     | `openModal('export-pdf', { sourcePath: activePath })`  |
 | `file.exportDocx`    | `openModal('export-docx', { sourcePath: activePath })` |
 | `file.exportHtml`    | `openModal('export-html', { sourcePath: activePath })` |
 | `file.exportBatch`   | `openModal('export-batch', { sourcePaths: openFiles })` |
 | `settings.open`      | `openModal('settings')`                                  |
 | `help.welcome`       | `openModal('welcome')`                                   |
 | `help.about`         | `openModal('about')`                                     |
 | `file.confirmClose`  | opens confirm dialog before closing a dirty tab        |
 | `app.quit`           | opens confirm if dirty tabs exist, else quits          |
 `settings.open` and `help.about` also get buttons in `AppHeader` (already partly done in Phase 6 — we just add new icons and wire to the new commands).
 ---
 ## 3. File Map
 ### 3.1 shadcn primitives (manually created, per the shadcn-CLI-blocked memory)
 Created in `src/renderer/components/ui/`:
 - `dialog.tsx`         — Radix Dialog wrapper with motion preset
 - `sheet.tsx`          — Radix Dialog (side variant) for SettingsSheet
 - `tabs.tsx`           — Radix Tabs for the 5-tab SettingsSheet
 - `input.tsx`          — text input
 - `textarea.tsx`       — multi-line input (for confirm body, welcome copy)
 - `select.tsx`         — Radix Select for theme/font/template pickers
 - `switch.tsx`         — Radix Switch for boolean settings
 - `checkbox.tsx`       — Radix Checkbox for "don't show again" toggles
 - `slider.tsx`         — Radix Slider for fontSize
 - `label.tsx`          — Radix Label (always pair with form fields)
 - `form.tsx`           — react-hook-form glue components (FormField, FormItem, FormLabel, FormControl, FormDescription, FormMessage)
 - `radio-group.tsx`    — Radix RadioGroup for accent color / template
 ### 3.2 Modals (`src/renderer/components/modals/`)
 - `ModalLayer.tsx`               — root, mounted by `App.tsx`
 - `ExportPdfDialog.tsx`          — PDF options (format, margins, embed fonts, ascii tables)
 - `ExportDocxDialog.tsx`         — DOCX options (template picker: standard/minimal/modern, ascii tables)
 - `ExportHtmlDialog.tsx`         — HTML options (standalone, highlight style, ascii tables)
 - `ExportBatchDialog.tsx`        — batch queue (format, concurrency, file list)
 - `SettingsSheet.tsx`            — 5-tab sheet (side="right", 480px wide)
  - `EditorSettings.tsx`         — font size, tab size, line numbers, word wrap, minimap
  - `ThemeSettings.tsx`          — light/dark/auto, accent color, font family
  - `ExportSettings.tsx`         — pdf format, margins, embed fonts, docx template, html highlight, ascii tables
  - `PluginsSettings.tsx`        — "Coming soon" placeholder
  - `AboutSettings.tsx`          — app version, links, acknowledgements
 - `AboutDialog.tsx`              — simple read-only dialog with version + GitHub link
 - `WelcomeDialog.tsx`            — first-launch dialog with quick-start cards
 - `ConfirmDialog.tsx`            — generic confirmation (title, body, destructive, onConfirm)
 - `ExportDialogFooter.tsx`       — shared Cancel / Export button row used by the 4 export dialogs
 - `useExportSource.ts`           — shared hook: reads active buffer, validates, returns source string + path
 ### 3.3 Stores
 - **Modify** `src/renderer/stores/app-store.ts` — add `modal` + `openModal` + `closeModal`; update `partialize` to exclude `modal`
 - **Create** `src/renderer/stores/settings-store.ts` — new
 ### 3.4 Lib
 - **Create** `src/renderer/lib/validators.ts` — zod schemas:
  - `settingsSchema` (whole settings object)
  - `exportPdfSchema` (format, margins, embedFonts, renderTablesAsAscii)
  - `exportDocxSchema` (template, renderTablesAsAscii)
  - `exportHtmlSchema` (standalone, highlightStyle, renderTablesAsAscii)
  - `exportBatchSchema` (format, concurrency, file list)
  - `confirmPropsSchema` (for the confirm dialog)
 - **Create** `src/renderer/lib/ascii-table.ts` — `toAsciiTable(rows: string[][]): string` (the small helper that converts a 2D string array to a fixed-width ASCII table)
 - **Create** `src/renderer/lib/modal-triggers.ts` — small helpers: `useWelcomeTrigger()`, `useQuitGuard()`
 ### 3.5 Modified files
 - **Modify** `src/renderer/App.tsx` — mount `<ModalLayer />` at the bottom; add the `useWelcomeTrigger` `useEffect` for first-launch
 - **Modify** `src/renderer/lib/commands/register-menu-commands.ts` — add the 9 new commands (4 export + settings + welcome + about + confirmClose + quit)
 - **Modify** `src/renderer/components/layout/AppHeader.tsx` — add Settings (gear) and About (info) icon buttons that dispatch the new commands
 - **Modify** `src/main.js` (verify) — no changes expected; menu items already wire to `menu:action` channels that flow through `useBridgeNativeMenu`. If any new menu items need IPC channels, add them in the main process mirror.
 ### 3.6 Tests
 **Unit (`tests/unit/`):**
 - `stores/settings-store.test.ts` (5-6 tests: defaults, setSetting, resetToDefaults, persistence/partialize)
 - `stores/app-store.test.ts` extended (3 tests: openModal sets state, closeModal clears, only one modal at a time)
 - `lib/validators.test.ts` (3 tests: each schema rejects bad input)
 - `lib/ascii-table.test.ts` (3 tests: simple table, alignment, empty input)
 **Component (`tests/component/modals/`):**
 - `ExportPdfDialog.test.tsx` (4 tests: renders with default settings, submit calls ipc.export.pdf with merged opts, error renders inline, ascii-table toggle flows through)
 - `ExportDocxDialog.test.tsx` (3 tests: renders, submit includes template, ascii-table toggle)
 - `ExportHtmlDialog.test.tsx` (3 tests: renders, highlight style select, ascii-table toggle)
 - `ExportBatchDialog.test.tsx` (3 tests: renders file list, format selector, concurrency)
 - `SettingsSheet.test.tsx` (6 tests: renders 5 tabs, each tab shows correct fields, settings change persists)
 - `AboutDialog.test.tsx` (2 tests: renders version, links open external)
 - `WelcomeDialog.test.tsx` (3 tests: renders, dismiss sets welcomeDismissed, "don't show again" checked)
 - `ConfirmDialog.test.tsx` (3 tests: confirm calls onConfirm and closes, cancel calls closeModal, destructive variant)
 - `ModalLayer.test.tsx` (3 integration tests: null kind renders nothing, switching kinds replaces modal, modal unmounts on close)
 **Integration (`tests/integration/`):**
 - `phase7-modals-smoke.test.tsx` (4 tests: dispatch command opens modal, command store + settings store + IPC all wired, app.tsx mount triggers welcome on first launch, modal layer end-to-end)
 ---
 ## 4. Data Flow
 ### 4.1 Open a modal
 ```ts
 // From any command handler in register-menu-commands.ts:
 useAppStore.getState().openModal('export-pdf', { sourcePath: activePath });
 ```
 ### 4.2 The dialog reads source
 ```ts
 // ExportPdfDialog.tsx
 const { source, path } = useExportSource();
 if (!source) return <EmptySourceFallback />;
 ```
 `useExportSource` is a small hook that:
 1. Reads `useFileStore.activeTabId` + `useEditorStore.buffers`
 2. If no active buffer, prompts the user to open a file (uses confirm dialog)
 3. Returns `{ source: string, path: string } | null`
 ### 4.3 Settings change
 ```ts
 // EditorSettings.tsx — switches/inputs call setSetting
 const [fontSize, setFontSize] = useSettingsStore(s => [s.fontSize, s.setSetting]);
 // or
 setSetting('fontSize', 16);
 ```
 Editor and preview subscribe to specific slices. The `useTheme` hook from `next-themes` is augmented to read `theme: 'light' | 'dark' | 'auto'` from `useSettingsStore` (replacing the standalone next-themes default).
 ### 4.4 Export flow
 ```ts
 // ExportPdfDialog on submit:
 const settings = useSettingsStore.getState();
 const result = await ipc.export.pdf({
  inputPath: path,
  outputPath: chosenOutputPath,
  format: dialogFormat ?? settings.pdfFormat,
  margins: MARGIN_PRESETS[dialogMargins ?? settings.pdfMargins],
  embedFonts: dialogEmbed ?? settings.pdfEmbedFonts,
  renderTablesAsAscii: dialogAscii ?? settings.renderTablesAsAscii,
 });
 if (!result.ok) setError(result.error.message);
 else { closeModal(); /* toast in Phase 8 */ }
 ```
 The dialog-level overrides fall through to settings defaults when not explicitly chosen.
 ### 4.5 ASCII table transformation
 The transformation happens in the **renderer** (pre-IPC), so the main process doesn't need to know about ASCII mode:
 ```ts
 // In ExportPdfDialog before submitting:
 const finalSource = renderTablesAsAscii
  ? applyAsciiTransform(source)   // walks AST, replaces <table> blocks
  : source;
 ```
 `applyAsciiTransform` is a small function (10-20 lines) that:
 1. Parses markdown source for `|...|` table syntax via a small regex
 2. Replaces each table block with a fenced code block containing the ASCII table
 3. Returns the modified source
 (No AST walker needed — markdown tables are line-based and a regex per line + simple width calc is sufficient.)
 ### 4.6 DOCX template selection
 The dialog shows a Select with 3 options (standard, minimal, modern). The main process maps these names to bundled `.docx` template files. The IPC contract is unchanged — `DocxOptions.template: string` was already defined in `types/ipc.ts` during Phase 1.
 ### 4.7 Confirm flow
 ```ts
 // In a command handler:
 const activeTab = ...;
 if (activeTab?.dirty) {
  useAppStore.getState().openModal('confirm', {
    title: 'Discard unsaved changes?',
    body: `"${activeTab.title}" has unsaved changes. Close without saving?`,
    confirmLabel: 'Discard',
    destructive: true,
    onConfirm: () => doCloseTab(),
  });
 } else {
  doCloseTab();
 }
 ```
 ### 4.8 Welcome first-launch
 `useEffect` in `App.tsx` (run once on mount) checks `welcomeDismissed` from `useSettingsStore`. If false, calls `openModal('welcome')`. The Welcome dialog has a "Don't show again" checkbox that sets `welcomeDismissed: true` and closes.
 ---
 ## 5. Error Handling
 - **IPC errors in export dialogs:** inline error banner below the submit button. `IpcResult<T>` discriminated union makes this easy. Banner shows `result.error.message` and a "Try again" button that re-submits.
 - **Settings validation:** zod schemas in `validators.ts`. Each form field shows `aria-invalid` + red border on error. Form-level errors via react-hook-form's `formState.errors`.
 - **Confirm dialog cancel:** just calls `closeModal()`. No state mutation. Optional `onCancel` callback for "remember my choice" patterns (not used in Phase 7).
 - **Welcome "don't show again":** persists `welcomeDismissed: true`. Help menu can re-open Welcome (without resetting the flag).
 - **Settings corruption on load (bad localStorage data):** `useSettingsStore` is built with a `partialize` that also acts as a whitelist — only known fields are deserialized. Unknown fields are dropped. If a persisted value fails zod validation, fall back to defaults (logged as a warning).
 ---
 ## 6. Testing Strategy
 TDD per the established pattern (Phases 1-6). Every component test:
 - Renders with empty/default state
 - One happy-path interaction (form submit, button click)
 - One error/edge case (validation fail, IPC error, cancel)
 Store tests focus on pure logic (state transitions, persistence, partialize). Settings store test specifically verifies:
 - Defaults match schema
 - `setSetting` works for leaf keys
 - `resetToDefaults` clears to initial state
 - Persisted payload (from `partialize`) contains exactly the leaf fields
 - Hydration from a partial/corrupt payload doesn't throw
 Component tests use `render` + `userEvent`, mock `window.electronAPI` for IPC.
 ModalLayer integration test verifies:
 1. Mounting with `kind: null` renders nothing (query container, expect empty)
 2. Mounting with `kind: 'about'` renders `<AboutDialog>` (aria-label match)
 3. Switching from `kind: 'about'` to `kind: 'settings'` unmounts About, mounts Settings (verified by role/aria-label transitions)
 4. Confirm dialog calls `onConfirm` and `closeModal` on success
 ---
 ## 7. Risks & Open Questions
 **Risks:**
 - **Form library complexity.** react-hook-form + zod is powerful but adds learning curve. Mitigation: a single shared `<SettingsForm>` wrapper reduces cognitive load; export dialogs use simple `useState` (no need for the full form infra).
 - **shadcn Dialog animation jank with our motion presets.** Radix Dialog has its own `data-state` attributes for open/closed. We compose with our `modalPop` preset via `forceMount` + Motion. Need to verify no double-animation.
 - **Settings store hydration race.** If a component reads a setting on first render before hydration completes, it gets the default. For Phase 7 this is fine — defaults are sensible.
 **Open questions (deferrable):**
 - Should the "ascii table" output include alignment row separators (`+---+---+`) or just be a `| a | b |`-style table? → Decision: use the `|---|` separator form (more compact, common in plain-text email).
 - Should ExportBatchDialog be a Sheet (queue progress) or a Dialog (form)? → Decision: Dialog with a form; progress is shown inline (not a streaming queue). Phase 9 could revisit.
 - Should `welcomeDismissed` be per-user-account or per-install? → Per-install (localStorage). No multi-user concept in v1.
 ---
 ## 8. Out of Scope (deferred to later phases)
 - Phase 8: Toast notifications on export success/failure (the dialog's inline error is v1; toasts are a follow-up).
 - Phase 9: ASCII art generator (figlet) is separate from ASCII table rendering. This spec is about table formatting.
 - Phase 9: Word export uses a `.docx` template *generation* step (WordExportDialog), not the IPC `ipc.export.docx` path. Distinct.
 - Phase 10: Delete legacy `src/print-preview.js`, `src/wordTemplateExporter.js`, etc.
 ---
 ## 9. Success Criteria
 Phase 7 is complete when:
 - All listed shadcn primitives exist in `src/renderer/components/ui/` with tests
 - `useSettingsStore` is implemented, tested, and persisted
 - `useAppStore` extended with `modal` discriminated union and tested
 - All 7 modal components implemented, tested, and accessible (aria-labels, keyboard nav)
 - 4 export dialogs (PDF/DOCX/HTML/Batch) all submit through the command store and call IPC correctly
 - `ModalLayer` mounted in `App.tsx` and integrated with command triggers
 - Welcome dialog shows on first launch, dismissible, re-openable from Help menu
 - Confirm dialog used by quit-with-dirty and close-with-dirty flows
 - ASCII table rendering works (toggle in settings, override in export dialogs)
 - DOCX template picker in ExportDocxDialog submits the correct `template` field
 - `npx vite build` succeeds, `npx vitest run` shows **all tests green** (target: +50 new tests, total ~220)
 - Branch tagged `phase-7-modals` and pushed to origin
@@ -1,250 +0,0 @@
 # Phase 8 — Toasts Design
 > Companion to the parent plan: `docs/superpowers/plans/2026-06-05-react-ui-redesign.md` (Phases 8+9+10 are sketched at high level; this spec locks Phase 8's architecture, file map, and contracts so it can be planned task-by-task.)
 **Date:** 2026-06-05
 **Phase:** 8 of 10 (React + shadcn/ui UI redesign)
 **Tag (on completion):** `phase-8-toasts`
 ---
 ## 1. Goal & Non-Goals
 **Goal:** Add a toast notification layer to the React renderer using sonner (already installed). Surface user-initiated async action results (file save, file/folder open, exports) as transient toasts in the bottom-right of the window. The error banner pattern in export dialogs stays — toasts are a complementary global channel.
 **Non-goals (Phase 8):**
 - Undo/redo support (Phase 9)
 - Custom toast actions/buttons (Phase 9, if needed)
 - Persistent notification history
 - Toast queueing/throttling for rapid-fire events
 - Replacing inline error banners (they stay as per-dialog context)
 **Scope decision:** Toast on user-initiated actions only. Skip silent background operations (loadChildren, etc.) to avoid noise. 4 wire points total: save (success+error), open file/folder (error only), 4 export dialogs (success+error).
 ---
 ## 2. Architecture
 ### 2.1 Toast helpers in `lib/toast.ts`
 A thin typed layer over sonner. The helpers exist to:
 - Give us a single import surface (instead of scattering `import { toast } from 'sonner'` across the codebase)
 - Provide a place to add brand colors, formatting, or analytics later without touching call sites
 - Make mocking easier in tests (one module to mock)
 ```ts
 // src/renderer/lib/toast.ts (sketch)
 import { toast as sonnerToast } from 'sonner';
 export const toast = {
  success: (message: string) => sonnerToast.success(message),
  error: (message: string) => sonnerToast.error(message),
  info: (message: string) => sonnerToast.info(message),
  warning: (message: string) => sonnerToast.warning(message),
  promise: <T>(
    promise: Promise<T>,
    msgs: { loading: string; success: string | ((data: T) => string); error: string | ((err: unknown) => string) }
  ) => sonnerToast.promise(promise, msgs),
  dismiss: (id?: string | number) => sonnerToast.dismiss(id),
 };
 ```
 ### 2.2 `<Toaster />` mounted in App.tsx
 A canonical shadcn Toaster wrapper (manual paste per memory `shadcn-cli-blocked-manual-primitives`). Mounts alongside `<ModalLayer />`:
 ```tsx
 // src/renderer/App.tsx (sketch)
 import { Toaster } from '@/components/ui/sonner';
 function App() {
  useWelcomeTrigger();
  return (
    <>
      <AppShell />
      <ModalLayer />
      <Toaster />
    </>
  );
 }
 ```
 The Toaster uses sonner's `<Toaster />` component with:
 - `theme={resolvedTheme}` from `useTheme()` (so toasts match the user's light/dark preference)
 - `richColors` for semantic success/error/info/warning colors
 - `position="bottom-right"` (sonner default; explicit for clarity)
 - `closeButton` (so users can dismiss)
 ### 2.3 Inline wiring at 4 wire points
 **Pattern choice — inline in stores/dialogs, NOT middleware.** Matches the Phase 7 precedent of inline error banners in export dialogs. Middleware would be DRY but harder to debug and harder to control granularity (we want errors on save, but NOT on silent loadChildren).
 **Wire points:**
 1. **`useFileStore.saveActiveBuffer`** — wrap the existing logic:
   ```ts
   saveActiveBuffer: async () => {
     // ... existing logic to get buffer ...
     const writeResult = await ipc.file.write(activeTabId, buffer.content);
     if (!writeResult.ok) {
       toast.error(`Failed to save: ${writeResult.error.message}`);
       return false;
     }
     // ... existing markSaved/markTabClean ...
     toast.success(`Saved ${title}`);
     return true;
   }
   ```
 2. **`useFileStore.openFile`** — error only:
   ```ts
   openFile: async (filePath) => {
     // ... existing logic to check existing tab ...
     const result = await ipc.file.read(filePath);
     if (!result.ok) {
       toast.error(`Failed to open file: ${result.error.message}`);
       return;
     }
     // ... existing logic ...
   }
   ```
 3. **`useFileStore.openFolder`** — error only:
   ```ts
   openFolder: async (path) => {
     const result = await ipc.file.list(path);
     if (!result.ok) {
       toast.error(`Failed to open folder: ${result.error.message}`);
       return;
     }
     // ... existing logic ...
   }
   ```
 4. **4 export dialogs** — both success and error (error complements the inline banner):
   ```ts
   if (!result.ok) {
     toast.error(`Export failed: ${result.error.message}`);
     setError(result.error.message);
     setSubmitting(false);
   } else {
     toast.success(`Exported ${source.title} to ${result.data?.outputPath ?? 'file'}`);
     closeModal();
   }
   ```
 ---
 ## 3. File Map
 ### 3.1 Created files
 - `src/renderer/lib/toast.ts` — typed wrappers (re-export of sonner with our naming)
 - `src/renderer/components/ui/sonner.tsx` — canonical shadcn Toaster wrapper (manual paste)
 - `tests/unit/lib/toast.test.ts` — ~5 unit tests
 - `tests/component/ui/sonner.test.tsx` — 1 smoke test
 - `tests/integration/phase8-toasts-smoke.test.tsx` — ~4 integration tests
 ### 3.2 Modified files
 - `src/renderer/App.tsx` — mount `<Toaster />` alongside `<ModalLayer />`
 - `src/renderer/stores/file-store.ts` — add 3 toast calls (save, openFile, openFolder)
 - `src/renderer/components/modals/ExportPdfDialog.tsx` — toast on submit result
 - `src/renderer/components/modals/ExportDocxDialog.tsx` — toast on submit result
 - `src/renderer/components/modals/ExportHtmlDialog.tsx` — toast on submit result
 - `src/renderer/components/modals/ExportBatchDialog.tsx` — toast on submit result
 ---
 ## 4. Data Flow
 User action → store action OR export dialog submit → IPC call → result →
 - if error: `toast.error(message)` → sonner renders in bottom-right portal
 - if success: `toast.success(message)` → sonner renders
 - inline error banner in dialog stays as per-dialog context (NOT removed)
 Theme comes from `useTheme()` in the Toaster component, not from individual toasts. The Toaster is mounted once at the app level.
 For the 4 export dialogs: the existing inline error banner stays (it's contextual to the dialog), AND a toast is fired. This gives the user both immediate context (in the dialog) and persistent notification (toast in corner).
 For file save: ONLY a toast (no inline error UI in the editor pane — keeps the editor clean). Errors still show the toast.
 ---
 ## 5. Error Handling
 - **Toast helpers never throw.** They are thin re-exports of sonner, which handles its own error cases (e.g., render failures, missing portal target).
 - **In tests**, the `toast` module is mocked so calls don't render real toasts. Mock signature: `vi.mock('@/lib/toast', () => ({ toast: { success: vi.fn(), error: vi.fn(), ... } }))`.
 - **Theme fallback:** If `useTheme()` is loading or `resolvedTheme` is undefined, Toaster uses `'system'` as a fallback (sonner's default behavior).
 - **Sonner missing:** If for some reason sonner fails to load, the toast calls become no-ops. The user still sees inline error banners in the export dialogs.
 - **Inline error banners stay.** They are not replaced by toasts — they complement them.
 ---
 ## 6. Testing Strategy
 ### 6.1 Unit tests (`tests/unit/lib/toast.test.ts`)
 5 tests:
 - `toast.success` calls sonner `toast.success` with the message
 - `toast.error` calls sonner `toast.error` with the message
 - `toast.info` calls sonner `toast.info`
 - `toast.warning` calls sonner `toast.warning`
 - `toast.promise` forwards the promise and messages to sonner
 All tests mock the sonner module and verify the forwarded call.
 ### 6.2 Component test (`tests/component/ui/sonner.test.tsx`)
 1 smoke test: `<Toaster />` renders without crashing inside a ThemeProvider.
 ### 6.3 Integration test (`tests/integration/phase8-toasts-smoke.test.tsx`)
 ~4 tests:
 - Saving a file → `toast.success` called with `"Saved test.md"`
 - Opening a non-existent file (ipc returns error) → `toast.error` called with file path in message
 - Export success (ipc returns ok) → `toast.success` called + dialog closes
 - Export failure (ipc returns error) → `toast.error` called + inline banner shown + dialog stays open
 TDD throughout. Mocks for `ipc.*` and `lib/toast`.
 ### 6.4 Existing tests must still pass
 - All 243 tests from Phase 7 must remain green
 - Export dialog tests will need updates to verify the new toast calls (the dialog tests currently check for inline banner; they should ALSO verify the toast call)
 ---
 ## 7. Risks & Open Questions
 **Risks:**
 - **Sonner theme switching:** If `useTheme()` returns `'system'` and the OS preference changes mid-session, sonner will re-render. This is the correct behavior; just confirm in test.
 - **Toast spam:** If user holds Cmd+S, the save could fire many times. Sonner deduplicates by default for similar messages? → Decision: rely on sonner's default behavior. If spam becomes an issue, add a `toast.dismiss()` debounce in v2.
 **Open questions (deferrable):**
 - Should we add a custom toast for "undo last close" (Phase 9's undo feature)? → Decision: out of scope for Phase 8. Phase 9 will handle undo toasts.
 - Should the export dialog inline banner be removed once toasts are wired? → Decision: NO — keep both. The inline banner is contextual to the dialog; the toast is global. They serve different purposes.
 ---
 ## 8. Out of Scope (deferred to later phases)
 - Phase 9: Undo toasts ("Tab closed — Undo" with action button)
 - Phase 9: Long-running operation progress toasts (e.g., batch export queue)
 - Phase 9: Custom toast variants for advanced tools (ASCII generator, table generator)
 - Phase 10: Cleanup of inline error banners (will evaluate in Phase 10 if redundant)
 ---
 ## 9. Success Criteria
 Phase 8 is complete when:
 - `lib/toast.ts` exists with typed wrappers
 - `<Toaster />` is mounted in `App.tsx` and renders toasts
 - `useFileStore.saveActiveBuffer` calls `toast.success`/`toast.error` on result
 - `useFileStore.openFile` calls `toast.error` on failure
 - `useFileStore.openFolder` calls `toast.error` on failure
 - 4 export dialogs call `toast.success`/`toast.error` on result
 - All tests pass: ~+10 new tests, total ~253
 - `npx vite build` succeeds
 - Branch tagged `phase-8-toasts` and pushed to origin
@@ -1,303 +0,0 @@
 # Phase 9 — Advanced Tools Design
 > Companion to the parent plan: `docs/superpowers/plans/2026-06-05-react-ui-redesign.md` (Phase 9 is sketched at high level; this spec locks architecture, file map, and contracts so it can be planned task-by-task.)
 **Date:** 2026-06-05
 **Phase:** 9 of 10 (React + shadcn/ui UI redesign)
 **Tag (on completion):** `phase-9-advanced-tools`
 ---
 ## 1. Goal & Non-Goals
 **Goal:** Add 10 advanced tools to the React renderer. Group 1: Standalone dialogs (ASCII generator, Table generator, Word export, Find-in-files). Group 2: Global overlays (Zen mode, REPL, Print preview). Group 3: Editor/sidebar integrations (Minimap, Breadcrumbs-with-symbols, Git status). All triggered via the Phase 6 command store.
 **Non-goals (Phase 9):**
 - True undo/redo stack (still not in scope)
 - Snippet/template library
 - Custom REPL with full JS eval (we chose markdown snippet preview for safety)
 - Custom diff/merge UI (just shows git status, no in-app diffing)
 - Plug-in extensions
 - Multi-cursor editing
 - LSP / language server integration
 **Decision summary (from brainstorming):**
 - REPL = **markdown snippet preview** (no JS eval — safe in renderer)
 - Word export = **`.docx` via `docx` lib in renderer**, with both Standard and Custom .dotx template modes
 - Find-in-files = **recursive search with result navigation** (new IPC, regex support)
 ---
 ## 2. Architecture
 ### 2.1 Three mount strategies
 | Category | Mount | Examples |
 |---|---|---|
 | **Dialogs** | `<ModalLayer />` (Phase 7 pattern) | ASCII gen, Table gen, Word export, Find-in-files |
 | **Global overlays** | Top-level in `App.tsx` (like `<Toaster />`) | Zen mode, REPL panel, Print preview |
 | **Editor/sidebar integrations** | Extend existing components | Minimap, Breadcrumbs, Git status |
 The ModalLayer is the dispatcher for dialogs. The global overlays are mounted directly in `App.tsx` because they need to participate in the top-level layout (full-window, or pinned to the bottom).
 ### 2.2 ModalState union extension
 The Phase 7 `ModalState` discriminated union (9 kinds) gets 4 new kinds for the new dialogs:
 ```ts
 export type ModalState =
  | { kind: null }
  | { kind: 'export-pdf'; props: { sourcePath: string } }
  | { kind: 'export-docx'; props: { sourcePath: string } }
  | { kind: 'export-html'; props: { sourcePath: string } }
  | { kind: 'export-batch'; props: { sourcePaths: string[] } }
  | { kind: 'export-word'; props: { sourcePath: string } }   // NEW
  | { kind: 'ascii-generator' }                                  // NEW
  | { kind: 'table-generator' }                                  // NEW
  | { kind: 'find-in-files' }                                    // NEW
  | { kind: 'settings' }
  | { kind: 'about' }
  | { kind: 'welcome' }
  | { kind: 'confirm'; props: ConfirmProps };
 ```
 Three of the four new kinds (ascii, table, find-in-files) take no props — they read from the active buffer via `useExportSource` (for ascii/table) or from `useFileStore.rootPath` (for find-in-files). `export-word` takes `sourcePath` like the other export dialogs.
 ### 2.3 New commands in command store
 | Command ID | Trigger | Opens |
 |---|---|---|
 | `tools.ascii` | new | `AsciiGeneratorDialog` |
 | `tools.table` | new | `TableGeneratorDialog` |
 | `tools.exportWord` | new | `WordExportDialog` |
 | `tools.findInFiles` | new | `FindInFilesDialog` |
 | `tools.repl` | new | toggles REPL panel |
 | `view.zenMode` | existing (Phase 6) | toggles Zen mode overlay |
 | `file.print` | new | opens `PrintPreview` overlay |
 | `git.refresh` | new | re-fetches git status |
 All registered in `src/renderer/lib/commands/register-menu-commands.ts`.
 ### 2.4 New IPC surface
 ```ts
 // src/renderer/lib/ipc.ts (additions)
 ipc.file.search({ rootPath, query, isRegex, caseSensitive }: {
  rootPath: string;
  query: string;
  isRegex: boolean;
  caseSensitive: boolean;
 }): Promise<IpcResult<Array<{ filePath: string; line: number; content: string }>>>;
 ipc.file.gitStatus({ rootPath }: { rootPath: string }): Promise<IpcResult<Array<{ filePath: string; status: 'modified' | 'added' | 'deleted' | 'untracked' }>>>;
 ipc.file.print({ html }: { html: string }): Promise<IpcResult<void>>;
 ipc.file.writeBuffer({ path, buffer }: { path: string; buffer: Uint8Array }): Promise<IpcResult<void>>;
 ```
 The main process counterparts are added to `src/main.js` (or a new `src/main/files-search.js`, etc.). For Phase 9, the spec covers the renderer-side design; main-process IPC handlers are assumed to follow the same `ipcMain.handle` pattern as the existing handlers.
 ### 2.5 Settings additions (`useSettingsStore`)
 ```ts
 // zod schema additions:
 docxCustomTemplatePath: z.string().nullable().default(null),  // path to user .dotx file
 replOpen: z.boolean().default(false),                         // REPL panel visibility
 breadcrumbSymbols: z.boolean().default(true),                  // breadcrumbs show code symbols
 // minimap already exists from Phase 7 (useSettingsStore.minimap: z.boolean().default(true))
 ```
 The `minimap` setting from Phase 7 is now wired (not just stored).
 ---
 ## 3. File Map
 ### 3.1 Created files
 **Dialogs (in `src/renderer/components/modals/`):**
 - `AsciiGeneratorDialog.tsx` — input textarea, font select, output preview with copy button
 - `TableGeneratorDialog.tsx` — rows × cols inputs, header checkbox, output preview
 - `WordExportDialog.tsx` — template select (Standard / Custom .dotx), options, preview, export
 - `FindInFilesDialog.tsx` — query input, regex/case toggles, results list with click-to-navigate
 **Global overlays (in `src/renderer/components/tools/`):**
 - `ReplPanel.tsx` — bottom-pinned, textarea + rendered preview
 - `PrintPreview.tsx` — full-window print preview
 **Editor/sidebar integrations:**
 - `src/renderer/components/layout/ZenMode.tsx` — wraps/controls the editor in zen mode (or modify `AppShell.tsx` to hide chrome)
 - `src/renderer/components/sidebar/GitStatusPanel.tsx` — file list with status badges
 **Lib:**
 - `src/renderer/lib/docx-export.ts` — renderer-side `docx` lib integration (markdown → Blob)
 - `src/renderer/hooks/use-zen-mode.ts` — small hook that reads `useSettingsStore.zenMode`
 **Modifications:**
 - `src/renderer/App.tsx` — mount `<ReplPanel />` and `<PrintPreview />` alongside `<ModalLayer />` and `<Toaster />`
 - `src/renderer/components/layout/AppShell.tsx` — when `zenMode === true`, hide all chrome except the editor
 - `src/renderer/components/editor/CodeMirrorEditor.tsx` — add `@codemirror/minimap` (or `@replit/codemirror-minimap`) when `useSettingsStore.minimap` is true
 - `src/renderer/components/layout/Breadcrumb.tsx` — extend to show symbols (headings, code blocks) using `@codemirror/langs-data` or a simple markdown AST walk
 - `src/renderer/components/sidebar/Sidebar.tsx` — add a "Git" tab to the existing tab list
 - `src/renderer/stores/settings-store.ts` — add 3 new fields
 - `src/renderer/lib/validators.ts` — add 3 new fields to `settingsSchema`
 - `src/renderer/lib/ipc.ts` — add 4 new IPC methods
 - `src/renderer/lib/commands/register-menu-commands.ts` — add 8 new commands
 - `src/main.js` (or split files) — add 4 main-process IPC handlers
 **Tests:**
 - `tests/component/tools/ReplPanel.test.tsx` — smoke test
 - `tests/component/tools/PrintPreview.test.tsx` — smoke test
 - `tests/component/modals/AsciiGeneratorDialog.test.tsx` — 3 tests
 - `tests/component/modals/TableGeneratorDialog.test.tsx` — 3 tests
 - `tests/component/modals/WordExportDialog.test.tsx` — 4 tests
 - `tests/component/modals/FindInFilesDialog.test.tsx` — 4 tests
 - `tests/component/sidebar/GitStatusPanel.test.tsx` — 3 tests
 - `tests/component/layout/Breadcrumb.test.tsx` — extend with symbols test
 - `tests/integration/phase9-tools-smoke.test.tsx` — 6 tests (one per command-triggered tool)
 ---
 ## 4. Data Flow
 ### 4.1 Word export (most complex)
 1. User triggers `tools.exportWord` → `registerMenuCommands` opens the export-word modal via `useAppStore.openModal('export-word', { sourcePath: activeTabId })`
 2. **Wait** — we need a new modal kind `export-word` in the `ModalState` union. Add it.
 3. `WordExportDialog` (mounted by ModalLayer) shows:
   - Template select: "Standard (bundled)" or "Custom .dotx (your file)" — pre-populated with `useSettingsStore.docxCustomTemplatePath`
   - "Choose custom template..." button (file picker, saves to settings)
   - Options: embed images (checkbox), include front matter (checkbox)
   - Preview area: shows the generated docx structure (sizes, table of contents)
 4. On submit:
   - Renderer calls `lib/docx-export.ts#generateDocx(source, templatePath, options)` which uses the `docx` lib
   - The lib takes a `Document` AST and produces a Blob
   - ASCII tables are converted to monospace `<w:r>` runs (using `applyAsciiTransform` from Phase 7)
   - Images are extracted from markdown and embedded as base64
   - If a custom .dotx path is set, the renderer reads it via `ipc.file.read` and applies its styles (via `docx` lib's style support)
   - User picks output path via `ipc.app.showSaveDialog`
   - Writes Blob via `ipc.file.writeBuffer` (new)
   - Toast success/failure
 ### 4.2 Find-in-files
 1. User triggers `tools.findInFiles` → ModalLayer opens `FindInFilesDialog`
 2. User types query, picks regex/literal, case-sensitive toggle
 3. On submit: `ipc.file.search({ rootPath: useFileStore.rootPath, query, isRegex, caseSensitive })`
 4. Backend walks the disk recursively, applies regex/literal match, returns `Array<{ filePath, line, content }>`
 5. Dialog shows result list (file:line:content, clickable)
 6. Click a result:
   - `useFileStore.openFile(filePath)` if not already open
   - Set the cursor in the editor to the matched line
 7. Close the dialog
 ### 4.3 REPL (markdown snippet preview)
 1. User triggers `tools.repl` → toggles `useSettingsStore.replOpen` (or a new dedicated `useReplStore`)
 2. `ReplPanel` (mounted in App.tsx) is visible when `replOpen === true`
 3. The panel has:
   - Top half: textarea (user types/pastes markdown)
   - Bottom half: rendered preview (uses `lib/markdown.ts` from Phase 1 + DOMPurify)
 4. Updates are debounced (300ms) for the preview
 5. Pure renderer-side, no IPC
 ### 4.4 Zen mode
 1. User triggers `view.zenMode` → toggles `useSettingsStore.zenMode`
 2. `AppShell` reads `zenMode` from store; when true, hides all chrome (header, tabs, toolbar, breadcrumb, status bar, sidebar)
 3. Editor goes fullscreen
 4. Pressing Esc exits zen mode (keydown listener in `use-zen-mode` hook)
 ### 4.5 Print preview
 1. User triggers `file.print` → opens `PrintPreview` (full-window overlay)
 2. The preview renders the current buffer's content as it would appear in print
 3. Two buttons: "Print" (calls `ipc.file.print({ html })` which opens native print dialog) and "Close"
 ### 4.6 Minimap
 1. `useSettingsStore.minimap` (existing setting) is read by `CodeMirrorEditor`
 2. When true, the editor's extension includes `@replit/codemirror-minimap` (or a simpler custom implementation)
 3. The minimap shows a shrunk version of the document on the right side of the editor
 4. Toggling the setting adds/removes the extension dynamically
 ### 4.7 Breadcrumbs-with-symbols
 1. The current `Breadcrumb` shows the file path. Extend it to also show markdown symbols (headings, code blocks)
 2. Use a simple AST walk of the current buffer to extract heading levels
 3. Show as a path-like navigation: `file.md > H1: Title > H2: Section > #line`
 4. The `useSettingsStore.breadcrumbSymbols` toggle (default true) controls whether symbols are shown
 ### 4.8 Git status
 1. On sidebar Git tab open, fetch `ipc.file.gitStatus({ rootPath: useFileStore.rootPath })`
 2. The main process runs `git status --porcelain` (or equivalent) and returns the list
 3. Show file list with status badges (M, A, D, ?)
 4. Click a file opens it via `useFileStore.openFile`
 5. `git.refresh` re-fetches
 ---
 ## 5. Error Handling
 - **Word export failures:** `lib/docx-export.ts` catches `docx` lib errors → toast.error
 - **Word export missing .dotx:** if custom template path is set but file doesn't exist, show inline banner in the dialog
 - **Find-in-files failures:** if `ipc.file.search` throws (regex syntax error, IO error), show inline banner in the dialog
 - **REPL:** no IPC, no error handling needed
 - **Git status:** if folder isn't a git repo, return empty array. Panel shows "Not a git repository" message
 - **Print:** if `ipc.file.print` fails (no printer, user cancels), toast.error or silent close
 - **Minimap, Breadcrumbs:** renderer-side, no errors
 ---
 ## 6. Testing Strategy
 - **Unit tests:** `lib/docx-export.ts` (markdown → docx conversion, ASCII handling), `lib/ascii-table.ts` (already tested)
 - **Component tests:** 1-2 smoke tests per new component
 - **Integration test:** `phase9-tools-smoke.test.tsx` covering the 6 command-triggered tools (dispatch opens correct modal/overlay)
 - **Editor integrations:** minimap toggle, breadcrumbs render with symbols, git status panel render
 - **Target: +30-40 new tests**, total ~290
 ---
 ## 7. Risks & Open Questions
 **Risks:**
 - **`docx` lib bundle size (~500KB).** Acceptable for a desktop app but worth noting. Lazy-load if it becomes a concern.
 - **Word export custom template parsing** — the `.dotx` format is a zip with XML inside. The `docx` lib may not fully support reading existing templates. v1 may need a simpler "styles only" extraction.
 - **Find-in-files regex compilation** — invalid regex would throw. Validate on the renderer before calling IPC.
 - **Minimap performance** — for large files, the minimap can slow down scrolling. CodeMirror's built-in minimap has performance options to configure.
 **Open questions (deferrable):**
 - **REPL persistence** — should the textarea content survive across modal close/reopen? → Decision: NO for v1. Keep simple.
 - **Git status auto-refresh** — should it auto-refresh every N seconds? → Decision: NO for v1. Manual via `git.refresh` command.
 - **Find-in-files result count limit** — what if there are 10,000 matches? → Decision: limit to 500 results for v1, show "X more matches" message.
 ---
 ## 8. Out of Scope (deferred to Phase 10 or later)
 - Custom undo/redo (still not in scope)
 - Snippet/template library
 - Multi-cursor editing
 - LSP / language server
 - Phase 10 will delete legacy files including the old `src/print-preview.js`, `src/wordTemplateExporter.js`, `src/welcome.js`, `src/zen-mode.js`, etc.
 ---
 ## 9. Success Criteria
 Phase 9 is complete when:
 - All 10 features implemented and accessible via the command store
 - `lib/docx-export.ts` generates valid `.docx` files
 - Find-in-files returns results from a recursive disk walk
 - REPL renders markdown snippet previews
 - Zen mode hides all chrome and Esc exits
 - Print preview opens native print dialog
 - Minimap appears when `useSettingsStore.minimap` is true
 - Breadcrumbs show symbols by default
 - Git status panel shows modified/added/deleted/untracked files
 - ~+30-40 new tests, total ~290
 - `npx vite build` succeeds
 - Branch tagged `phase-9-advanced-tools` and pushed to origin
@@ -1,361 +0,0 @@
 # MarkdownConverter — React + shadcn/ui UI Redesign
 **Date:** 2026-06-05
 **Status:** Design (awaiting user approval)
 **Branch:** `react-electron`
 **Author:** Brainstormed with user via superpowers:brainstorming
 ## Summary
 Replace the legacy vanilla JS renderer (`src/renderer.js` is 213 KB; `src/styles.css` is 74 KB) with a modern React 19 + Vite + TypeScript + shadcn/ui renderer that achieves visual feature parity while delivering a Polished + Glassy (Raycast/Arc-style) aesthetic. The Electron main process, preload bridge, and IPC contracts stay unchanged. Work proceeds via vertical slices — each PR ships a demoable feature.
 ## Goals
 1. Replace every render-time feature of the legacy renderer with an idiomatic React + shadcn/ui implementation.
 2. Adopt the "Polished + Glassy" visual language (subtle shadows, 8–12 px radii, gradient accents, gentle depth) on top of the existing ConcreteInfo brand tokens and design system.
 3. Use a single component foundation (shadcn/ui) and a single motion library (Motion / Framer Motion) to keep the dependency surface narrow and the design coherent.
 4. Keep the main process, preload, and IPC contracts untouched. The renderer is the only surface being rewritten.
 5. Keep the app runnable at every commit. No "big bang" merge.
 ## Non-Goals
 - Migrating the main process to TypeScript (out of scope for this spec).
 - Adding new features the legacy renderer does not have (plugin system, AI features, etc. — those are future specs).
 - Replacing Pandoc/FFmpeg/ImageMagick orchestration.
 - Changing the packaging pipeline (electron-builder config stays).
 - Replacing the CodeMirror 6 editor — it is the right tool and is already wired up.
 ## Decisions Locked During Brainstorming
 | Decision | Choice | Why |
 |---|---|---|
 | Scope | Full feature parity with legacy renderer | User-selected option. Renderer is one cohesive surface; splitting it across specs would force premature contracts. |
 | Visual style | **B — Polished + Glassy** (Raycast/Arc aesthetic) | "Fancy" comes from elevation, gradient accents, and material depth — not over-designed visuals. |
 | Layout | **2 — IDE-style** (equal editor/preview, draggable divider, collapsible sidebar) | Power-user markdown apps converge on this. Draggable divider + keyboard reset. |
 | Modal patterns | **A (Centered Dialog), B (Right Side-Sheet), D (Toasts)** | No command palette. |
 | Command palette | **No** — full menus, no ⌘K | Power users can use the OS-level launcher. App stays focused on writing. |
 | Animation | **Motion (Framer Motion)** | Best for layout transitions, modal/drawer enter/exit, drag. Sparingly used. |
 | Component library | **shadcn/ui** | Tailwind + Radix primitives, copy-paste ownership, perfect fit for the "glassy" aesthetic and the HSL-CSS-variable foundation that is already in place. |
 | Implementation strategy | **Vertical slices** — one feature end-to-end per PR | App stays runnable. Each PR is reviewable. |
 ## Defaults (Used Unless Overridden Later)
 | Item | Default | Why |
 |---|---|---|
 | State management | Zustand (already in deps) + Immer for nested patches | Already in `package.json`; perfect for editor state. |
 | Theming | shadcn `next-themes`, dark default + light, system-aware | shadcn canonical pattern. Brand colors already in CSS vars. |
 | Icons | `lucide-react` (already in deps) | 1000+ tree-shakable icons. |
 | Forms | `react-hook-form` + `zod` | Standard for shadcn forms. |
 | Drag/drop (sortable lists) | `@dnd-kit/core` | De facto React drag lib (file tree reordering, plugin list reorder). |
 | Pane resize (split layout) | `react-resizable-panels` | Canonical React lib for resizable pane groups; handles drag, arrow keys, snap, persisted sizes. |
 | Testing | Vitest + RTL + Playwright (E2E + visual regression) | Standard for React + Electron. |
 | TypeScript | Strict mode (already wired) | Already in deps and `vite.renderer.config.ts`. |
 ## Architecture
 The Electron app keeps its existing process model. Only the renderer is rewritten.
 ```
 ┌──────────────────────────────────────────────────────────┐
 │  Electron Main (UNCHANGED)                                │
 │  - BrowserWindow, IPC handlers, file/fs ops               │
 │  - Pandoc, FFmpeg, ImageMagick orchestration              │
 └────────────┬─────────────────────────────────────────────┘
             │ contextBridge (UNCHANGED preload.js)
 ┌────────────▼─────────────────────────────────────────────┐
 │  React Renderer (REWRITTEN)                                │
 │  ┌────────────────────────────────────────────────────┐  │
 │  │  AppShell (layout)                                  │  │
 │  │  ├─ MenuBar (native)                                │  │
 │  │  ├─ AppHeader (logo, breadcrumbs, theme toggle)     │  │
 │  │  ├─ TabBar (open files)                             │  │
 │  │  ├─ Toolbar (formatting)                            │  │
 │  │  ├─ ResizablePaneGroup (sidebar | editor | preview) │  │
 │  │  │   ├─ Sidebar (file tree, outline)                │  │
 │  │  │   ├─ EditorPane (CodeMirror 6)                   │  │
 │  │  │   └─ PreviewPane (marked + KaTeX + Mermaid)      │  │
 │  │  ├─ StatusBar (word count, encoding, cursor pos)    │  │
 │  │  └─ ModalLayer (Dialog, SideSheet, Toaster)         │  │
 │  └────────────────────────────────────────────────────┘  │
 │  ┌────────────────────────────────────────────────────┐  │
 │  │  Feature Modules (each owns UI + state slice)       │  │
 │  │  ├─ editor/    CodeMirror wrapper, syntax, themes   │  │
 │  │  ├─ preview/   markdown→html, KaTeX, Mermaid       │  │
 │  │  ├─ tabs/      open files, dirty state              │  │
 │  │  ├─ sidebar/   file tree, outline, search results   │  │
 │  │  ├─ modals/    export, settings, about, etc.        │  │
 │  │  ├─ tools/     zen, repl, ascii-gen, table-gen      │  │
 │  │  └─ export/    pdf, docx, html, image batch         │  │
 │  └────────────────────────────────────────────────────┘  │
 │  ┌────────────────────────────────────────────────────┐  │
 │  │  Shared Infrastructure                              │  │
 │  │  ├─ stores/  Zustand slices per feature             │  │
 │  │  ├─ hooks/   useFile, useEditor, useTheme, etc.     │  │
 │  │  ├─ lib/     cn, ipc, formatters, validators        │  │
 │  │  ├─ ui/      shadcn primitives: button, dialog…     │  │
 │  │  └─ types/   shared TS types                        │  │
 │  └────────────────────────────────────────────────────┘  │
 └──────────────────────────────────────────────────────────┘
 ```
 ### Architectural Rules
 - **Shell components** (`AppHeader`, `TabBar`, `StatusBar`) subscribe only to `useAppStore`.
 - **Feature components** subscribe to their own feature's store.
 - **Cross-feature access** goes through hooks, not direct store imports (e.g., `useFileTree()` wraps `useFileStore`).
 - **Feature modules are self-contained** — each owns its components, its Zustand slice, and its types. Safe to develop in parallel later.
 - **No direct `window.electronAPI` calls** from feature code. All IPC goes through `lib/ipc.ts` for type safety and error normalization.
 ## State Management
 ```
 stores/
 ├─ useAppStore        // global UI: theme, sidebar, pane sizes, modals open
 ├─ useFileStore       // file system: tree, open files, active tab
 ├─ useEditorStore     // editor: per-file content, cursor, selection, dirty
 ├─ usePreviewStore    // preview: scroll sync, zoom, theme
 ├─ useSettingsStore   // user prefs (persisted to electron-store)
 └─ useCommandStore    // menu actions registry, recent actions
 ```
 **Why slices instead of one mega-store?** Editor content can be megabytes. Keeping it in its own slice lets React avoid re-rendering the preview when only the editor changes — components subscribe with selectors.
 **Persistent state** (auto-saved to electron-store via Zustand `persist` middleware): theme, sidebar visibility, last open files, pane divider positions, settings.
 **Ephemeral state** (lost on quit): active modal, hover states, search query, current file content (saved to disk on idle).
 ## Visual Design System
 ### Color Tokens
 The existing `globals.css` HSL variables stay. Additions for the "glassy" aesthetic:
 ```css
 --shadow-sm: 0 1px 2px rgba(13, 11, 9, 0.06);
 --shadow-md: 0 4px 12px rgba(13, 11, 9, 0.08), 0 0 0 1px rgba(13, 11, 9, 0.04);
 --shadow-lg: 0 12px 32px rgba(13, 11, 9, 0.12), 0 0 0 1px rgba(13, 11, 9, 0.06);
 --shadow-glow-brand: 0 0 24px rgba(229, 70, 31, 0.25);
 --glass-bg-light: rgba(255, 255, 255, 0.72);
 --glass-bg-dark:  rgba(13, 11, 9, 0.72);
 --glass-border-light: rgba(255, 255, 255, 0.4);
 --glass-border-dark:  rgba(255, 255, 255, 0.08);
 ```
 ### shadcn Components
 Install via `npx shadcn@latest add`:
 **Primitives** (need all of these): `button`, `dialog`, `sheet`, `popover`, `tooltip`, `select`, `dropdown-menu`, `tabs`, `separator`, `scroll-area`, `toggle`, `switch`, `slider`, `input`, `textarea`, `label`, `form`, `skeleton`, `sonner`, `command`.
 **Composite** (custom-built on top of primitives): `file-tree`, `pane-group`, `divider`, `status-bar`, `menu-bar`, `toast`.
 ### Typography
 - Body: Plus Jakarta Sans 15 px / line-height 1.6
 - Code: JetBrains Mono 13.5 px
 - Display: Barlow Condensed 700/800 — used sparingly (page titles, big metrics)
 - Headings: Plus Jakarta Sans 600/700 with tight letter-spacing
 - Labels (`.label`): Plus Jakarta Sans 500, 12 px, uppercase, 0.05 em letter-spacing
 ### Motion Choreography
 | Element | Motion | Duration | Easing |
 |---|---|---|---|
 | Modal (Dialog A) | Scale 0.96→1, opacity 0→1 | 200 ms | `ease-out` |
 | Side sheet (B) | TranslateX 100%→0, opacity 0→1 | 300 ms | `cubic-bezier(0.16, 1, 0.3, 1)` |
 | Toast | TranslateY 100%→0, opacity | 250 ms | spring(stiffness: 300, damping: 30) |
 | Sidebar toggle | Width 264 px↔72 px, content fade | 250 ms | `ease-in-out` |
 | Divider drag | Live width update | 0 ms | none (instant) |
 | Theme switch | CSS variables, opacity overlay | 300 ms | `ease-in-out` |
 | Tab switch | Underline slide | 200 ms | `ease-out` |
 | Hover (buttons) | `bg` + `shadow` shift | 150 ms | `ease-out` |
 | Focus ring | Outline grow | 100 ms | `ease-out` |
 **Rules:** Every motion has a purpose. No gratuitous animation. Respects `prefers-reduced-motion` (Motion handles this automatically).
 ### Empty / Loading / Error States
 Every async surface ships all three. Sonner toasts for ephemeral feedback. Skeleton screens for content areas. Empty-state components with icon + message + primary CTA.
 ## Modal/Overlay Patterns
 | Use case | Pattern | Why |
 |---|---|---|
 | Export (PDF/DOCX/HTML) | A — Centered Dialog | Focused decision, ~3–5 fields, "do one thing" |
 | Settings | B — Right Side-Sheet | Long form, tabbed sections, stays open while editing |
 | Find/Replace | Inline toolbar (not modal) | Always-visible utility |
 | About | A — Centered Dialog | Tiny info dump |
 | Confirm destructive (delete, close unsaved) | A — Centered Dialog | Forces attention |
 | File save error | D — Toast | Non-blocking info |
 | Pandoc/FFmpeg progress | D — Toast → sticky on >3 s | Background work feedback |
 | Plugin manager | B — Right Side-Sheet | Lists + per-item actions |
 | ASCII/Table generators | A — Centered Dialog | Tool-style focused input → output |
 | Print preview | A — Centered Dialog | Full-screen-ish modal overlay |
 | Welcome (first launch) | A — Centered Dialog | One-time onboarding |
 | Word export | A — Centered Dialog | Template selection |
 | Zen mode | Full-viewport toggle (no modal) | Replaces the editor entirely |
 | REPL | Bottom-pinned panel (split-pane) | Persistent terminal-like UI |
 | Quick file open | B — Right Side-Sheet | File tree, search, recent |
 ### Dialog A Anatomy (Export as example)
 ```
 ┌─ Backdrop (rgba(13,11,9,0.45) + backdrop-blur 4px) ─────────┐
 │                                                            │
 │   ┌──── Modal (max-w-md, rounded-2xl, shadow-lg) ─────┐    │
 │   │ ┌── Header ────────────────────────────────────┐  │    │
 │   │ │ [Icon] Export as PDF                  [×]    │  │    │
 │   │ │ Choose format options                       │  │    │
 │   │ └─────────────────────────────────────────────┘  │    │
 │   │ ┌── Body ──────────────────────────────────────┐  │    │
 │   │ │ Format: [Letter] [A4] [Legal]                │  │    │
 │   │ │ Margins: ────●────                           │  │    │
 │   │ │ ☐ Include table of contents                  │  │    │
 │   │ │ ☐ Embed fonts                                │  │    │
 │   │ └─────────────────────────────────────────────┘  │    │
 │   │ ┌── Footer ────────────────────────────────────┐  │    │
 │   │ │                       [Cancel] [Export →]    │  │    │
 │   │ └─────────────────────────────────────────────┘  │    │
 │   └──────────────────────────────────────────────────┘    │
 │                                                            │
 └────────────────────────────────────────────────────────────┘
 ```
 ### Side-Sheet B Anatomy (Settings as example)
 Slides in from right, ~50 % width (max 560 px). Backdrop is `rgba(13,11,9,0.2)` with `backdrop-blur(2 px)` (lighter than dialog — the sheet is the focus). Tab navigation in the sheet header (Editor / Theme / Export / Plugins / About).
 ### Toast D Anatomy (Sonner)
 Stacked bottom-right, max 3 visible. Glass background. Color-coded 3 px left border — success `#1a7a56`, error `#ef4444`, info `#0ea5e9`, warning `#eab308`. Icon + title + description. Optional action button. Auto-dismiss 4 s for success, sticky for error.
 ## Data Flow (Editor → Preview Pipeline)
 ```
 User types
  ↓
 CodeMirror onChange
  ↓
 useEditorStore.updateContent(tabId, content)  ← debounced 50 ms
  ↓
 ┌─ Persist to electron-store on idle (1 s) ─┐
 │                                            │
 └─ Publish to usePreviewStore (subscribed) ─┘
  ↓
 marked(content) → sanitized HTML
  ↓
 PreviewPane renders HTML
  KaTeX post-processes $...$
  Mermaid post-processes ```mermaid
  Highlight.js post-processes ```lang
  ↓
 useEffect: scroll-sync editor cursor → preview position
 ```
 **Bidirectional scroll sync:** editor scroll → preview (primary), preview click → editor cursor (secondary). Throttled to 60 fps via `requestAnimationFrame`.
 ## IPC Contract
 The preload bridge stays unchanged. A new `src/renderer/lib/ipc.ts` wraps every channel with TypeScript types and normalizes errors to a discriminated union:
 ```ts
 type IpcResult<T> =
  | { ok: true; data: T }
  | { ok: false; error: { code: string; message: string } };
 export const ipc = {
  file: {
    open: (): Promise<IpcResult<FileResult>>,
    read: (path: string): Promise<IpcResult<string>>,
    write: (path: string, content: string): Promise<IpcResult<void>>,
    list: (dir: string): Promise<IpcResult<FileEntry[]>>,
    onChange: (cb: (path: string) => void) => () => void,
  },
  export: {
    pdf: (opts: PdfOptions): Promise<IpcResult<ExportResult>>,
    docx: (opts: DocxOptions): Promise<IpcResult<ExportResult>>,
    html: (opts: HtmlOptions): Promise<IpcResult<ExportResult>>,
    batch: (items: BatchItem[], opts: BatchOptions): Promise<IpcResult<BatchResult>>,
  },
  app: {
    getVersion: (): Promise<IpcResult<string>>,
    openExternal: (url: string): Promise<IpcResult<void>>,
    showItemInFolder: (path: string): Promise<IpcResult<void>>,
  },
 };
 ```
 ## Error Handling
 Layered defense — no single failure can crash the app:
 1. **IPC errors** → caught in `lib/ipc.ts` wrapper, returned as `IpcResult<T>` discriminated union. Components show toast on error.
 2. **Component errors** → React error boundary per feature area (one for editor, one for preview, one for modals). On error: show inline error UI with "Reload this panel" + "Copy details" actions.
 3. **Async operations** (export, file ops) → loading state on button + toast on completion. Long ops (>2 s) get a sticky toast with cancel.
 4. **Validation errors** (settings, export options) → inline form errors via `react-hook-form` + `zod`. shadcn `Form` component for consistent error display.
 5. **Pandoc/FFmpeg missing** → detected at startup, banner + disable export menu items. Don't surprise-fail at export time.
 ## Testing Strategy
 - **Unit (Vitest):** stores, hooks, lib utilities, formatters, validators
 - **Component (Vitest + RTL):** shadcn wrappers, dialog interactions, sidebar toggle, divider drag, theme toggle
 - **Integration (Vitest + RTL):** editor ↔ preview flow, file open → tab add → content display, settings change persists
 - **E2E (Playwright):** app launches, file opens, markdown renders, export to PDF works
 - **Visual regression (Playwright snapshots):** locked-in screenshots for header, sidebar, dialogs, toasts — catch accidental style drift
 - **Target coverage:** stores/hooks/lib ≥ 90 %, components ≥ 75 %, E2E covers all critical paths
 ## Accessibility (WCAG 2.1 AA)
 Baked in via shadcn + Radix:
 - All dialogs focus-trap, Esc to close, return focus to trigger
 - All interactive elements keyboard-reachable
 - Visible focus rings (2 px brand ring)
 - 4.5:1 contrast minimum (already met by brand colors)
 - `aria-label` on icon buttons, `role="alert"` on toasts
 - Respects `prefers-reduced-motion` (Motion handles this automatically)
 ## Implementation Phases (Vertical Slices)
 Each phase is a shippable PR that keeps the app runnable. The legacy `renderer.js` is gradually replaced; until each phase is complete, the old renderer code still runs the missing parts.
 | # | Phase | Output | Acceptance |
 |---|---|---|---|
 | 1 | **Foundation** | shadcn installed; `next-themes`, `motion`, `react-hook-form`, `zod`, `@dnd-kit/core`, `react-resizable-panels`, `sonner` installed; design tokens finalized; `lib/utils.ts` (`cn`), `lib/ipc.ts` typed wrappers, `lib/motion.ts` preset transitions, `App.tsx` shell skeleton renders | `npm run build` succeeds; dev server shows the new shell with theme toggle working |
 | 2 | **App shell + layout** | `AppHeader`, `TabBar`, `Toolbar`, `Breadcrumb`, `StatusBar`, `ResizablePaneGroup` with sidebar toggle and draggable divider. Empty editor/preview panes. | Resize divider with mouse and arrow keys; sidebar collapses; pane sizes persist. |
 | 3 | **Editor pane** | CodeMirror 6 wrapped, dark/light themes wired to shadcn theme, syntax highlighting, line numbers, search, autocomplete | Open `.md` file → renders in editor; can edit and save. |
 | 4 | **Preview pane** | marked + DOMPurify + KaTeX + Mermaid + highlight.js. Bidirectional scroll sync with editor. | Open file → preview renders, follows cursor. |
 | 5 | **File tree + tabs** | Sidebar file tree (read directory on demand, lazy-expand children only on click). Tabs for open files. Dirty state indicator. File content is read from disk only when the tab is activated. | Open folder → root populates; click folder → children load; click file → opens in tab; close tab reverts dirty. |
 | 6 | **Native menus + toolbar** | Replace the legacy `CommandPalette` with full menus (File / Edit / View / Insert / Format / Tools / Help) bound to keyboard shortcuts. Toolbar buttons. | All menu items invoke the right action; shortcuts work; toolbar reflects active state. |
 | 7 | **Modals** | Export dialog (PDF/DOCX/HTML/batch), Settings side-sheet (Editor/Theme/Export/Plugins/About tabs), About dialog, Confirm-destructive dialog | All dialogs and sheet render with proper motion; settings persist; export works end-to-end. |
 | 8 | **Toasts** | Sonner wired into all async operations (save, export, errors, tool missing) | All operations give appropriate feedback; no silent failures. |
 | 9 | **Advanced tools** | Zen mode (full-viewport toggle), REPL (bottom-pinned panel), ASCII generator, Table generator, Word export template picker, Print preview | Each tool is feature-complete vs. legacy version. |
 | 10 | **Polish + delete legacy** | Visual regression snapshots locked; remove `renderer.js` and old `styles*.css` references from build; `npm run build:linux` produces a working installer | Final PR ships an installer with no legacy code paths. |
 ## Risks and Mitigations
 | Risk | Mitigation |
 |---|---|
 | shadcn CLI requires Vite (not vanilla Electron renderer) | Vite is already configured for the renderer in `vite.renderer.config.ts`; the CLI works against the same project. |
 | shadcn CLI assumes Tailwind is at project root; we have it in renderer/ only | Point the CLI at `src/renderer/components.json` and set `tailwind.css` to the right path. |
 | Marked + KaTeX + Mermaid + highlight.js together is heavy | Lazy-load Mermaid (only when `mermaid` code block encountered). KaTeX is loaded once, cached. |
 | Editor content state can be megabytes → re-render storms | Editor content lives in its own slice; preview subscribes to a derived/cached HTML string; components use `useShallow` / selector subscriptions. |
 | Bidirectional scroll sync loops | `useEffect` debounce + ignore if cursor/selection is the sync source. |
 | CodeMirror 6 doesn't ship a Tailwind theme by default | Use `@codemirror/theme-one-dark` for dark; build a custom theme that pulls from CSS variables for light. |
 | The legacy `renderer.js` and `styles*.css` are referenced from `index.html` (now `src/renderer/index.html`) | Phase 10 deletes the references; until then, both run side-by-side and the new React app sits in a known root div. |
 | Electron `nodeIntegration` is off; we use contextBridge | Already the case. Document the contract clearly in `lib/ipc.ts`. |
 ## Open Questions (to confirm before implementation)
 None. All major decisions are locked. Defaults will be used unless the user overrides them when reviewing the implementation plan.
 ## References
 - `src/renderer.js` (213 KB) — legacy renderer being replaced
 - `src/styles.css` (74 KB), `src/styles-modern.css` (71 KB), `src/styles-concreteinfo.css` (21 KB) — legacy styles being replaced
 - `src/renderer/styles/globals.css` — already shadcn-compatible (HSL CSS variables)
 - `src/renderer/App.tsx` — empty skeleton that references components we will build
 - `tailwind.config.js` — brand colors and fonts already defined
 - `vite.renderer.config.ts` — Vite + React plugin already configured
 - `package.json` — CodeMirror 6, TanStack Table, lucide-react, cva, clsx, tailwind-merge, tailwindcss-animate already installed
@@ -1,333 +0,0 @@
 # Phase 10 — Polish + Delete Legacy Design
 > Companion to the parent plan: `docs/superpowers/plans/2026-06-05-react-ui-redesign.md` (Phase 10 is sketched at high level; this spec locks architecture, file map, deletion targets, and version strategy.)
 **Date:** 2026-06-06
 **Phase:** 10 of 10 (React + shadcn/ui UI redesign) — **FINAL**
 **Tag (on completion):** `v5.0.0` (the first release tag, all prior phases were `phase-N-*` working tags)
 ---
 ## 1. Goal & Non-Goals
 **Goal:** Finalize the React UI redesign. Decompose the legacy 146KB `src/main.js` into a feature-first modular structure under `src/main/`, remove the legacy vanilla-JS renderer and all dead IPC bridges, then ship **v5.0.0** with a CHANGELOG.
 **Non-goals (Phase 10):**
 - Adding new features (Phases 1-9 shipped all of them)
 - A full main-process test suite (the existing main process is largely untested; adding tests is Phase 11+)
 - Backwards compat shims for the legacy renderer
 - Renderer-side refactor (already done)
 - Migrating the renderer build pipeline further (vite configs are in place)
 **Success criteria:**
 - `src/main.js` is gone; `src/main/index.js` is the new entrypoint
 - `package.json#main` points to `src/main/index.js`
 - All 12 legacy renderer files are deleted
 - All 9 dead IPC channels are removed from `preload.js` and `main.js`
 - `src/index.html` is reduced to ~50 lines (just the Vite bootstrap)
 - `package.json#version` is `5.0.0`
 - `CHANGELOG.md` exists in Keep a Changelog 1.1.0 format
 - `git grep -E "renderer\.js|command-palette|print-preview|welcome\.js|zen-mode|wordTemplate|ascii-generator|table-generator|styles\.css"` returns zero results
 - All 305 tests still pass
 - `npx vite build --config vite.renderer.config.ts` succeeds
 - `npx electron .` launches and main window renders
 - Tag `v5.0.0` pushed to origin
 ---
 ## 2. Target Architecture
 ### 2.1 `src/main/` (feature-first decomposition)
 ```
 src/main/
 ├── index.js              # entrypoint: bootstraps store, app, window, ipc
 ├── store.js              # electron-store wrapper (preferences + wordTemplatePath)
 ├── ipc.js                # ipcMain.handle registration (composes from modules)
 ├── files/
 │   ├── index.js          # file ops facade (read/write/list/pickFolder/pickFile)
 │   ├── search.js         # recursive regex search (used by find-in-files)
 │   ├── git.js            # git status porcelain parser
 │   └── binary.js         # writeBuffer helper (Uint8Array → file)
 ├── menu/
 │   ├── index.js          # buildMenu() — composes the app menu
 │   └── items.js          # individual menu items (File, Edit, View, etc.)
 ├── window/
 │   ├── index.js          # createMainWindow ONLY (createAsciiWindow/createTableWindow are DEAD)
 │   └── state.js          # window state persistence
 ├── word-template/
 │   ├── index.js          # WordTemplateExporter facade
 │   ├── parser.js         # .dotx parsing
 │   ├── converter.js      # markdown → docx
 │   └── apply.js          # apply template styles to converted docx
 └── utils/
    ├── paths.js          # path helpers
    ├── logger.js         # structured logging
    └── download.js       # tool downloader
 ```
 **Module rules:**
 - Each file has one clear responsibility (no god files; CLAUDE.md says >300 lines is the cap)
 - `index.js` is the public face of a folder; deeper files are private
 - `src/main/index.js` (top-level) wires everything together
 - Cross-folder imports go through `index.js`, not directly to internals
 ### 2.2 Entry point change
 **Before:**
 ```json
 // package.json
 "main": "src/main.js"
 ```
 **After:**
 ```json
 // package.json
 "main": "src/main/index.js"
 ```
 The new `src/main/index.js` runs the same `app.whenReady().then(...)` flow that the current `src/main.js` does, but composes the decomposed modules.
 ### 2.3 What becomes dead code (removed during decomposition)
 When the legacy renderer files are deleted, these main-process functions become orphaned and are removed too:
 | Function | File | Why dead |
 |---|---|---|
 | `createAsciiWindow()` | `src/main/window/index.js` | Loads deleted `src/ascii-generator.html` |
 | `createTableWindow()` | `src/main/window/index.js` | Loads deleted `src/table-generator.html` |
 | `ipcMain.on('open-ascii-generator', ...)` | `src/main/index.js` (after decomposition) | Replaced by React `<AsciiGeneratorDialog>` |
 | `ipcMain.on('open-table-generator', ...)` | `src/main/index.js` (after decomposition) | Replaced by React `<TableGeneratorDialog>` |
 | `webContents.send('print-preview')` | `src/main/menu/items.js` | Replaced by React `<PrintPreview>` |
 | `webContents.send('print-preview-styled')` | `src/main/menu/items.js` | Replaced by React `<PrintPreview>` |
 | `webContents.send('toggle-command-palette')` | `src/main/menu/items.js` | Replaced by `useCommandStore` |
 | `require('./wordTemplateExporter')` | `src/main/index.js` (after decomposition) | Replaced by `src/main/word-template/` + renderer-side `lib/docx-export.ts` |
 ---
 ## 3. Legacy Deletion Map
 ### 3.1 Files to delete from `src/` (12 files, ~14,426 lines)
 | File | Size | Lines | Replaced by |
 |---|---|---|---|
 | `src/renderer.js` | 213KB | 5319 | `src/renderer/` (Phases 1-9) |
 | `src/styles.css` | 74KB | 3723 | `src/renderer/index.css` + Tailwind |
 | `src/styles-modern.css` | 71KB | 2625 | Tailwind + shadcn/ui |
 | `src/styles-concreteinfo.css` | 21KB | 969 | Tailwind theme tokens |
 | `src/styles-sidebar.css` | 9.7KB | 304 | `<Sidebar>` component |
 | `src/styles-zen.css` | 2.1KB | 102 | Zen mode in AppShell |
 | `src/styles-welcome.css` | 2.2KB | 24 | Welcome dialog |
 | `src/fonts.css` | 1.8KB | (imported elsewhere) | Tailwind font config |
 | `src/command-palette.js` | (small) | 109 | `useCommandStore` |
 | `src/print-preview.js` | (small) | 138 | `<PrintPreview>` |
 | `src/welcome.js` | (small) | 78 | `<Welcome>` modal |
 | `src/zen-mode.js` | (small) | 292 | `use-zen-mode` hook + AppShell |
 | `src/wordTemplateExporter.js` | (small) | 743 | `src/main/word-template/` + renderer `lib/docx-export.ts` |
 | `src/ascii-generator.html` | 34KB | (HTML) | `<AsciiGeneratorDialog>` |
 | `src/table-generator.html` | 18KB | (HTML) | `<TableGeneratorDialog>` |
 | `src/index.html` | 103KB | 1667 | `src/renderer/index.html` (already exists, Vite root) |
 **Total: 13 files = ~16,093 lines / ~548KB**
 `src/renderer/index.html` (the live Vite template) is NOT deleted.
 ### 3.2 Dead IPC channels to remove from `src/preload.js`
 - `toggle-command-palette` (line 238)
 - `open-ascii-generator` (line 89)
 - `open-table-generator` (line 92)
 - `print-preview` (line 173)
 - `print-preview-styled` (line 174)
 - `show-table-generator` (line 180)
 - `show-ascii-generator-window` (line 217)
 - `show-ascii-generator` (line 218)
 - `show-table-generator-window` (line 221)
 And from the exposed API surface:
 - `openAscii: () => ipcRenderer.send('open-ascii-generator')` (line 445)
 - `openTable: () => ipcRenderer.send('open-table-generator')` (line 446)
 **9 channel names + 2 API entries to remove.**
 ### 3.3 Legacy references in `src/index.html` (16 places) — **the LEGACY file at project root, 1667 lines**
 - `<link rel="stylesheet" href="styles.css">` (line ~6)
 - `<link rel="stylesheet" href="styles-welcome.css">` (line ~7)
 - `<div id="print-preview-overlay" class="modal hidden" ...>` block (~10 lines)
 - `<div class="command-palette-overlay hidden" id="command-palette-overlay">` block (~5 lines)
 - `<script src="renderer.js"></script>` (final script tag)
 **All of these are removed by deleting the file `src/index.html` entirely.**
 The CURRENT live renderer template is **`src/renderer/index.html`** (already correct: minimal, CSP, Plus Jakarta Sans font, `<script type="module" src="./main.tsx">`). This file is **NOT touched** in Phase 10. Vite's `root` is set to `src/renderer/` in `vite.renderer.config.ts`, so `src/renderer/index.html` is the HTML template Vite uses. The `src/index.html` at the project root is an orphan from the pre-Vite era.
 **Verification:** after deleting `src/index.html`, the renderer build still works because Vite doesn't look at the project root — it uses `src/renderer/index.html`.
 ### 3.4 Main process rewiring
 - Remove `require('./wordTemplateExporter')` from main entrypoint
 - Remove `webContents.send('print-preview*')` and `webContents.send('toggle-command-palette')` from menu items
 - Remove `ipcMain.on('open-ascii-generator', ...)` and `ipcMain.on('open-table-generator', ...)` handlers
 - Remove `asciiGeneratorWindow` and `tableGeneratorWindow` global state (and any references to `loadFile(...ascii-generator.html)` / `loadFile(...table-generator.html)`)
 ---
 ## 4. `src/index.html` — DELETE (not rewrite)
 The current `src/index.html` is 1667 lines of legacy markup and is **DELETED** (not rewritten). The renderer is already correctly served by `src/renderer/index.html` (the Vite root). Deleting the legacy root-level `src/index.html` is the action — no replacement file is needed.
 `src/renderer/index.html` (already correct) is NOT modified:
 ```html
 <!DOCTYPE html>
 <html lang="en">
 <head>
  <meta charset="UTF-8">
  <meta http-equiv="Content-Security-Policy" content="default-src 'self'; ...">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>MarkdownConverter</title>
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
  <link href="https://fonts.googleapis.com/css2?family=Plus+Jakarta+Sans:..." rel="stylesheet">
 </head>
 <body class="font-sans antialiased">
  <div id="root"></div>
  <script type="module" src="./main.tsx"></script>
 </body>
 </html>
 ```
 ---
 ## 5. Version Bump + CHANGELOG
 ### 5.1 `package.json`
 ```diff
 -  "version": "4.4.2",
 +  "version": "5.0.0",
 ```
 Major version bump because the legacy renderer removal is a breaking change for anyone who had plugins/integrations pointing at `src/renderer.js`.
 ### 5.2 `CHANGELOG.md` (new file, Keep a Changelog 1.1.0 format)
 ```markdown
 # Changelog
 All notable changes to markdown-converter will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 ## [5.0.0] - 2026-06-06
 ### Added
 - **Complete React 19 + Vite + TypeScript renderer** replacing the legacy vanilla-JS UI
 - Native macOS/Windows/Linux menus with command palette and keyboard shortcuts
 - Settings sheet (5 tabs: editor, theme, keybindings, advanced, about)
 - Modal layer with 13 modal kinds (export PDF/DOCX/HTML/Word, batch, settings, about, welcome, confirm, ASCII gen, table gen, find in files)
 - 10 advanced tools: ASCII generator, table generator, Word export, find-in-files, REPL, print preview, zen mode, minimap, breadcrumbs-with-symbols, git status
 - Sonner toast notifications at 4 wire points
 - 3 mount strategies: ModalLayer dialogs, App.tsx overlays, editor/sidebar integrations
 - `ipc.file.writeBuffer` for renderer-side binary output
 - `ipc.file.search` (recursive regex), `ipc.file.gitStatus`, `ipc.print.show`, `ipc.app.showSaveDialog`
 - 305 unit + integration tests (vitest + React Testing Library)
 - Per-package @radix-ui primitives
 - shadcn/ui (new-york style) primitives
 ### Changed
 - **BREAKING**: Renderer is now React-only.
 - Main process decomposed from 146KB `src/main.js` into feature-first modules under `src/main/`
 - `src/index.html` reduced from 1667 to ~50 lines
 - IPC contract: handlers throw, `safeCall` catches → `{ ok, error }`
 - Settings store: `useSettingsStore` (zustand persist with zod)
 - Modal state: `useAppStore.modal: ModalState` discriminated union
 ### Removed
 - `src/renderer.js` (legacy vanilla-JS renderer, 5319 lines) — and `src/index.html` (1667 lines of legacy markup, replaced by `src/renderer/index.html` which is already the live Vite template)
 - 7 legacy stylesheets (styles.css, styles-modern.css, styles-concreteinfo.css, styles-sidebar.css, styles-zen.css, styles-welcome.css, fonts.css)
 - 5 legacy scripts (command-palette.js, print-preview.js, welcome.js, zen-mode.js, wordTemplateExporter.js)
 - 2 legacy HTMLs (ascii-generator.html, table-generator.html)
 - 9 dead IPC channels (toggle-command-palette, open-*/show-* ascii/table, print-preview*)
 ```
 ---
 ## 6. Task Decomposition
 **10 tasks** (each independently verifiable, one feature per commit, no bundling):
 1. **Decompose main.js — `src/main/files/`** (file ops facade, search, git, binary)
 2. **Decompose main.js — `src/main/menu/`** (buildMenu + items, with dead sends removed)
 3. **Decompose main.js — `src/main/window/`** (createMainWindow ONLY — ascii/table windows removed)
 4. **Decompose main.js — `src/main/word-template/`** (WordTemplateExporter split into parser/converter/apply)
 5. **Decompose main.js — `src/main/utils/` + `store.js` + `ipc.js` + `index.js`** (glue + new entrypoint)
 6. **Trim preload.js** — remove 9 dead IPC channels + 2 exposed API entries
 7. **Delete legacy renderer files** (13 files: renderer.js, 7 styles, fonts.css, 4 scripts, 3 htmls)
 8. **Verify src/renderer/index.html is the live template** (no action needed if it's already correct)
 9. **Bump package.json version to 5.0.0 + write CHANGELOG.md**
 10. **Final verification + tag v5.0.0** (build, tests, grep, electron smoke)
 Tasks 1-5 are subagent-driven (decomposition is mechanical given a clear target structure). Tasks 6-9 are direct edits. Task 10 is a verification gate.
 ---
 ## 7. Verification Strategy
 **Per task:**
 - After each decomposition step: `npx vitest run` (305 still green)
 - After main.js decomposition: `npx electron .` smoke — app starts, opens a file
 - After deletions: `git grep -E "renderer\.js|command-palette|print-preview|welcome\.js|zen-mode|wordTemplate|ascii-generator|table-generator|styles\.css"` returns ZERO results
 **Final (Task 10):**
 - `npx vitest run` — 305 passing
 - `npx vite build --config vite.renderer.config.ts` — succeeds
 - `npx vite build --config vite.preload.config.ts` — succeeds
 - `npx electron .` — app launches, main window renders
 - Manual smoke: open a `.md` file, edit it, export to PDF/DOCX, use the command palette
 - `git tag -a v5.0.0 -m "..."` and `git push origin v5.0.0`
 ---
 ## 8. Risks & Open Questions
 **Risks:**
 - **Decomposition regressions.** Splitting a 146KB main.js into 7+ files has surface area for missed imports / circular deps. Mitigation: tests stay green; electron smoke after each step.
 - **Hidden legacy references.** `git grep` won't catch references inside minified bundles or in node_modules. Mitigation: vite build will fail if there's a dangling import.
 - **`src/main/index.js` entrypoint change.** Anything in the build pipeline (electron-builder, scripts) that hardcodes `src/main.js` needs to be updated. Mitigation: grep all of `package.json`, `scripts/`, `vite.*.config.ts` for `main.js`.
 **Open questions (resolved during brainstorming):**
 - ~~Main process scope~~ → Full rewrite
 - ~~Folder shape~~ → Feature-first
 - ~~IPC migration~~ → Delete dead channels
 - ~~Version strategy~~ → v5.0.0 with Keep a Changelog format
 - ~~Order of work~~ → Decompose first, delete last
 ---
 ## 9. Out of Scope (deferred to Phase 11+)
 - Main process test suite
 - Renderer-side further refactor
 - New features
 - Migration to tauri (separate plan in `docs/plans/2026-03-15-react-tauri-pwa.md`)
 ---
 ## 10. Success Criteria
 Phase 10 is complete when:
 - All 10 tasks are committed, one per commit, no bundling
 - `src/main/index.js` is the new entrypoint
 - All 12 legacy files are deleted
 - All 9 dead IPC channels are removed
 - `package.json#version` is `5.0.0`, `package.json#main` is `src/main/index.js`
 - `CHANGELOG.md` exists with a complete v5.0.0 entry
 - 305 tests still pass
 - `npx vite build` succeeds for both renderer and preload configs
 - `npx electron .` launches and the app works end-to-end
 - `git grep` for legacy references returns zero results
 - Tag `v5.0.0` is created and pushed to origin
 - Phase 10 is the LAST phase of the React UI redesign
@@ -1,295 +0,0 @@
 # Production polish — v5 shippable build
 **Date:** 2026-06-07
 **Branch:** `react-electron`
 **Status:** Draft, pending implementation plan
 **Author:** Claude (brainstormed with Amit Haridas)
 ## 1. Goals & non-goals
 ### Goals
 v5 is reliably shippable to two distribution channels:
 - **GitHub Releases** (public, free, existing workflow).
 - **ConcreteInfo update server** at `https://updates.concreteinfo.co.in/v5/` (self-hosted, for ConcreteInfo's own users).
 Concretely:
 - A non-blocking update banner surfaces "v5.0.2 is available" with a user-confirmed restart-to-install flow. No silent background installs.
 - A light first-run wizard (theme + update channel + starter template), all skippable.
 - One-shot auto-migration from v4.4.1 settings, with a v4 backup file and a toast on success/failure.
 - Local crash dump capture (no third-party). CrashReportModal lets the user open the dump folder and copy/delete dumps.
 - GitHub Actions CI that builds + uploads artifacts on tag and runs the test suite on every PR.
 ### Non-goals (deferred to v5.1+)
 - **Code signing.** macOS Gatekeeper and Windows SmartScreen will warn. Re-evaluated for v5.1.
 - **Sentry or any third-party crash reporting.** Local dumps only.
 - **Auto-install on quit.** Always user-confirmed.
 - **Delta updates** (full downloads only in v5).
 - **Plugin system, cloud/licensing, perf/a11y** — each is its own subsequent spec.
 ## 2. Architecture
 ```
 GitHub Releases (public)        ConcreteInfo (CI feed)
  └── *.zip, *.dmg, *.exe,        └── *.zip, *.dmg, *.exe,
      *.deb, *.rpm,                  *.deb, *.rpm,
      latest.yml, latest-           latest.yml, latest-
      mac.yml, latest-              mac.yml, latest-
      linux.yml, latest-            linux.yml, latest-
      windows.yml                   windows.yml
        ▲                              ▲
        │                              │
        └──────┬───────────────────────┘
               │ electron-updater reads
               │ the channel chosen in
               │ Settings (default: GitHub)
               ▼
 ┌─────────────────────────────────────────────────────┐
 │  Main process (src/main/updater/)                  │
 │   - Updater service: wraps electron-updater         │
 │   - Channel resolver: returns feed URL from setting │
 │   - State machine: idle → checking → available →    │
 │     downloading → ready → installing                │
 │   - Crash writer: catches process.on('uncaught…)   │
 │   - Migration runner: idempotent, runs on app start│
 └─────────────────────────────────────────────────────┘
        ▲                              ▲
        │ IPC (renderer→main,           │ IPC (renderer→main,
        │ allowlisted SEND)             │ allowlisted SEND)
        │ updater:check,                │ crash:read,
        │ updater:install,              │ crash:open-dir,
        │ updater:get-state             │ crash:delete
        │                               │
        │ IPC (main→renderer,           │
        │ allowlisted RECEIVE)          │
        │ updater:status                │
        ▼                              ▼
 ┌─────────────────────────────────────────────────────┐
 │  Renderer (preload bridge + React)                  │
 │   - Update banner: "v5.0.2 available"               │
 │   - Settings: Update channel radio                  │
 │   - First-run wizard: skip-links, all optional      │
 │   - Crash dialog: open dump dir, copy file          │
 │   - Migration: first-launch indicator in settings   │
 └─────────────────────────────────────────────────────┘
 ```
 ### Key boundaries
 - **`src/main/updater/`** is a single new directory. `updater-service.js` owns the `electron-updater` lifecycle, never the renderer.
 - **Renderer talks to updater over IPC only.** No direct `autoUpdater` import in preload. Channels must be in `ALLOWED_SEND_CHANNELS` / `ALLOWED_RECEIVE_CHANNELS`.
 - **Channel switching is a settings change.** No restart required; the next `checkForUpdates()` reads the new feed URL.
 - **Migration is idempotent.** Stores a `migration.version` key; skips if already at v5.
 - **Crash writer never blocks startup.** Initialized in main entry, but a write failure is non-fatal.
 ## 3. Component breakdown
 | Unit | What it does | How it's used | Depends on |
 |---|---|---|---|
 | `main/updater/updater-service.js` | Owns `electron-updater`; exposes check/download/install; emits status events | Main process singleton; started after `app.whenReady()` | `electron-updater`, `electron` |
 | `main/updater/feed-config.js` | Maps channel setting → feed URL; reads from `app.getPath('userData')/settings.json` | Called by updater-service on each check | settings store |
 | `main/updater/crash-writer.js` | Hooks `process.on('uncaughtException', …)`; writes minidump + stack to `app.getPath('userData')/crashDumps/{timestamp}.json` | Initialized in main entry, before anything else | `electron`, `app.getPath` |
 | `main/updater/migration-runner.js` | Reads v4 settings; transforms to v5 schema; writes backup; updates `migration.version` | Run from main entry on `app.whenReady()` | `fs`, settings store |
 | `main/ipc/updater-handlers.js` | IPC handlers: `updater:check`, `updater:install`, `updater:get-state` | Registered in main entry | updater-service |
 | `main/ipc/crash-handlers.js` | IPC handlers: `crash:read`, `crash:open-dir` | Registered in main entry | crash-writer |
 | `preload.js` (extension) | Add `updater.check()`, `updater.install()`, `crash.read()`, `crash.openDir()` to `electronAPI`; add channels to allowlist | Preload runs at boot | existing preload |
 | `renderer/lib/updater-store.ts` | Zustand store mirroring updater state; subscribes to `updater:status` events | Renderer; consumed by banner, settings, modals | `zustand`, IPC bridge |
 | `renderer/components/UpdateBanner.tsx` | Non-blocking banner shown when `updater-store.status` is `available | downloading | ready` | Mounted in `App.tsx` next to header | updater-store, sonner |
 | `renderer/components/FirstRunWizard.tsx` | 3-step modal with skip links; opens on first launch when `app-store.firstRun === true` | Mounted in `App.tsx` | app-store, settings-store, command-store |
 | `renderer/components/modals/SettingsModal.tsx` (extend) | Add "Updates" section: channel radio, "Check now" button, auto-check toggle | Mounted via `useAppStore.modal` | updater-store, settings-store |
 | `renderer/components/modals/CrashReportModal.tsx` | List local crash dumps; "Open dump folder", "Copy to clipboard", "Delete" actions | Mounted via `useAppStore.modal` | crash ipc, sonner |
 | `renderer/lib/migrations/v4-to-v5.ts` | Pure function: `(v4Settings) => v5Settings` | Called from `migration-runner` | zod schemas |
 ### Data flow — "user clicks Check for updates"
 1. Settings panel: `useSettingsStore.getState().setSetting('updateChannel', 'github' | 'concreteinfo')`.
 2. `SettingsModal` calls `await ipc.updater.check()`.
 3. Preload `safeCall` → `window.electronAPI.updater.check()` → `ipcRenderer.invoke('updater:check')`.
 4. Main handler asks `updater-service` to `autoUpdater.checkForUpdates()` with the channel's feed URL.
 5. `updater-service` emits `'updater:status', { state: 'available', version: '5.0.2' }`.
 6. Preload forwards to `updater-store` via `window.electronAPI.on('updater:status', cb)`.
 7. `updater-store` state flips to `available`; `UpdateBanner` renders.
 8. User clicks "View release notes" → opens `https://github.com/.../releases/tag/v5.0.2` via `ipc.app.openExternal`.
 9. User clicks "Restart to update" → calls `ipc.updater.install()`. `updater-service` calls `autoUpdater.quitAndInstall()`. App quits, relaunches into v5.0.2.
 ## 4. Error handling
 ### Updater
 - **No network:** `autoUpdater.checkForUpdates()` rejects with `ENOTFOUND` / `ETIMEDOUT`. We catch, log to main log, emit `updater:status { state: 'error', code: 'NETWORK' }`. Banner shows "Couldn't check for updates. Try again." Toast fires inline at the wire point in `UpdateBanner` / `SettingsModal` on retry, matching the existing pattern (`toasts-inline-at-wire-points`).
 - **Feed 404 / signature missing (N/A in v5 since unsigned):** Treat as configuration error. Log to main log with full URL. Banner shows "Update feed is misconfigured. Report this on GitHub." Crash-log-style entry is written.
 - **Update available but download fails:** Banner flips to "Download failed. Try again." Clicking "Try again" re-invokes `autoUpdater.downloadUpdate()`. Three consecutive failures show a "Report issue" link in the banner.
 - **Update installs but launch fails:** Worst case. We catch the post-`quitAndInstall` crash via `crash-writer` and write a marker file `app.getPath('userData')/update-failed.json` with the previous version. On next boot, the user is offered to revert manually by re-downloading from the GitHub release page (a "rolled back" banner instead of the wizard).
 - **Concurrent checks:** Debounce 60s. A second `checkForUpdates()` within 60s is a no-op; returns the current state. The Check-Now button is disabled during a check.
 ### Migration
 - **v4 settings file missing/corrupt:** Treat as "nothing to migrate." App starts with v5 defaults. Toast: "Welcome to v5 — using default settings."
 - **Migration throws mid-transform:** Original v4 file is preserved as `settings.v4.bak.json` (already on disk). App starts with v5 defaults. Toast: "Couldn't migrate v4 settings — your old settings are preserved at {path}."
 - **`migration.version === 5`:** Skip entirely. No-op.
 ### Crash writer
 - **Dump write fails (disk full, permissions):** Print to stderr; do not crash the app. Recovery is "user's problem" — we never block app startup on the crash writer.
 - **No dumps in dir:** CrashReportModal shows empty state: "No crashes recorded — nice work!"
 ### First-run wizard
 - **Skip clicked at any step:** Sets `app-store.firstRun = false` and proceeds. All defaults already match the unselected choice, so this is non-destructive.
 - **Wizard cannot reach settings (corrupt store):** Falls back to defaults silently. Wizard still closes.
 ## 5. Testing
 ### Unit (Vitest, renderer-side)
 - `useUpdaterStore`: state transitions on each `updater:status` event; debounce on `check()`; reject on missing channel.
 - `FirstRunWizard`: each step's CTA writes the right slice; "Skip" leaves defaults; "Skip at step 1" still closes the wizard and sets `firstRun = false`.
 - `migrations/v4-to-v5`: golden-file tests — every v4 shape we ship transforms to expected v5 output. Idempotency: running twice yields identical v5 settings.
 - `feed-config`: each channel setting resolves to the right feed URL; missing/unknown channel falls back to GitHub.
 ### Component (Vitest + RTL)
 - `UpdateBanner`: hidden when state is `idle` or `error-network`; visible with the right copy in `available`/`downloading`/`ready`; Restart button calls `ipc.updater.install()`; "View release notes" opens the right URL via `ipc.app.openExternal`.
 - `FirstRunWizard`: skip links work; theme picker updates the store; channel picker persists; template picker inserts into the new buffer.
 - `CrashReportModal`: lists dumps from the IPC response; "Open folder" invokes `crash.openDir`; delete removes the file.
 - `SettingsModal > Updates`: channel radio flips `settings-store.updateChannel`; "Check now" fires `ipc.updater.check`; auto-check toggle persists.
 ### Integration (Vitest, full app)
 - **Migration end-to-end:** pre-seed a v4 settings file in `app.getPath('userData')/settings.json`, launch the app, verify v5 file is written, v4 backup exists, `migration.version === 5`, and the wizard opens on first run.
 - **Update flow mock:** stub `electron-updater` to emit `available` → `downloading` → `ready`; verify the banner appears, Restart click triggers `quitAndInstall`, and the IPC sequence matches the allowlist.
 ### E2E (Playwright + Electron, runs the live app)
 - Open the app, verify the FirstRun wizard renders. Skip. Verify the editor is visible.
 - Open Settings, switch update channel from GitHub to ConcreteInfo, click Check now. Stub the feed response. Verify the banner appears with the right version.
 - Click Restart. Verify the app calls `quitAndInstall` (assert on a mocked `autoUpdater.quitAndInstall`).
 - Trigger an unhandled rejection in the renderer. Verify a dump is written to `crashDumps/`. Open the CrashReportModal, verify it appears in the list.
 ### Coverage targets
 - Updater service: ≥ 90% (small surface, hot path).
 - Migration runner: 100% of branches (idempotency, corrupt file, missing file, transform failure).
 - FirstRunWizard: ≥ 80%.
 - Component tests above any preset.
 ## 6. Distribution feed contracts
 ### GitHub Releases (default)
 Feed URL pattern:
 ```
 https://github.com/{owner}/{repo}/releases/download/v{version}/
 ```
 For v5.0.2:
 ```
 https://github.com/{owner}/{repo}/releases/download/v5.0.2/latest-mac.yml
 https://github.com/{owner}/{repo}/releases/download/v5.0.2/latest-linux.yml
 https://github.com/{owner}/{repo}/releases/download/v5.0.2/latest-windows.yml
 ```
 `electron-updater` reads these automatically given the GitHub owner/repo config. The release workflow already exists at `.github/workflows/release.yml` and builds `.dmg`, `.zip`, `.exe`, `.deb`, `.rpm`. We add `latest.yml` generation via `electron-builder --publish always` in the CI.
 ### ConcreteInfo feed
 Feed URL:
 ```
 https://updates.concreteinfo.co.in/v5/latest.yml
 https://updates.concreteinfo.co.in/v5/latest-mac.yml
 https://updates.concreteinfo.co.in/v5/latest-linux.yml
 https://updates.concreteinfo.co.in/v5/latest-windows.yml
 ```
 CI mirrors the GitHub Release artifacts to this path on every release. ConcreteInfo infra is documented in `~/.claude-mmax/CLAUDE.md`; the coolify server is `localhost:8000`. The mirror is a static-file route — no auth, just version-prefixed.
 ## 7. First-run wizard contract
 Three steps. Each step has "Skip" and "Back" links. Final step is "Done."
 1. **Theme:** Light / Dark / System. Default: System. Persists to `settings-store.theme`.
 2. **Update channel:** GitHub Releases / ConcreteInfo. Default: GitHub Releases. Persists to `settings-store.updateChannel`.
 3. **Starter template:** Blank / README / Meeting notes / Blog post. Default: Blank. On "Done," creates an untitled buffer with the chosen template content.
 `firstRun` lives in `app-store` (not persisted across app data resets) and is checked on every launch. Setting it to `false` either explicitly (skip/done) or implicitly (v4 migration succeeded) prevents re-showing.
 ## 8. Settings migration contract (v4.4.1 → v5.0.0)
 `migration-runner` runs once on first v5 launch. It:
 1. Reads `app.getPath('userData')/settings.json` if it exists.
 2. Validates the v4 shape with a zod schema (`v4SettingsSchema`).
 3. If valid: transforms via `migrations/v4-to-v5.ts` and writes the v5 settings to `settings.json`. Backs up v4 to `settings.v4.bak.json`. Sets `migration.version = 5` in the v5 file.
 4. If missing or invalid: writes a fresh v5 settings file with defaults. `migration.version = 5`.
 5. If transform throws: leaves v4 file in place as the "backup." App starts with defaults. Toast warns the user.
 The transform handles:
 - v4 `theme` ('light' | 'dark' | 'auto') → v5 `theme` ('light' | 'dark' | 'system').
 - v4 `customCss` string → v5 `customCssPath` file path or `null`.
 - v4 `recentFiles: string[]` → v5 `recentFiles` (unchanged shape).
 - v4 `editorFontSize: number` → v5 `editorFontSize` (unchanged shape).
 - v4 `keyBindings: object` → v5 `userBindings` (keymap).
 - v4 `snippets: array` → v5 `snippets` (unchanged shape).
 - v4 `pdfExportOptions` etc. → v5 schema for the new export pipeline.
 Anything not in the v4 schema is dropped. Defaults are taken from the v5 zod schema.
 ## 9. IPC allowlist additions
 `src/preload.js` adds these to `ALLOWED_SEND_CHANNELS`:
 ```js
 'updater:check',
 'updater:install',
 'updater:get-state',
 'crash:read',
 'crash:open-dir',
 'crash:delete',
 ```
 `ALLOWED_RECEIVE_CHANNELS`:
 ```js
 'updater:status',
 ```
 The `electronAPI` object gets:
 ```js
 updater: {
  check: () => ipcRenderer.invoke('updater:check'),
  install: () => ipcRenderer.invoke('updater:install'),
  getState: () => ipcRenderer.invoke('updater:get-state'),
  onStatus: (cb) => ipcRenderer.on('updater:status', (_, payload) => cb(payload)),
 },
 crash: {
  read: () => ipcRenderer.invoke('crash:read'),
  openDir: () => ipcRenderer.send('crash:open-dir'),
  delete: (filename) => ipcRenderer.invoke('crash:delete', filename),
 },
 ```
 ## 10. Risks & mitigations
 | Risk | Mitigation |
 |---|---|
 | First-run wizard is annoying to long-time users | Skippable; only shows on first launch. `firstRun = false` is set permanently on first skip/done. |
 | Auto-migration corrupts settings | Original v4 file is preserved as `settings.v4.bak.json`. Transform errors fall back to defaults and toast the user. |
 | Crash writer fills disk | Cap at 20 dumps; oldest auto-pruned. |
 | Update feed mirror drift between GitHub and CI | Mirror runs in CI on every release; manual `npm run publish:concreteinfo` available as fallback. |
 | `electron-updater` is unsigned, so anyone can publish a "v5.0.2" to a mirror | We do not enable auto-install in v5 — every install is user-confirmed via the release-notes page. v5.1 adds signing. |
 | First-run wizard blocks app start on a slow renderer | Wizard is non-blocking. App shell mounts and is interactive behind the modal. |
 | Debounced `checkForUpdates()` may mask real errors | "Check now" button bypasses the debounce; debounce only applies to automatic checks. |
 | CI release workflow is on a tag — broken tags must be re-tagged manually | Documented in CONTRIBUTING.md; pre-release tag re-runs the workflow. |
 ## 11. Out of scope (deferred)
 - Code signing.
 - Delta updates.
 - Per-channel pre-release / beta tracks (only stable feeds in v5).
 - Crash analytics / Sentry.
 - Squirrel.Windows-specific quirks (we publish NSIS only).
@@ -1,258 +0,0 @@
 # Monospace Font Embedding + Naming Differentiation
 **Date:** 2026-07-22
 **Branch:** react-electron
 **Goal:** Bring `react-electron` to feature parity with `master` by porting the v4.5.0 "embedded monospace font" feature, and differentiate the dev build identity from the installed `markdown-converter` deb so the two can coexist on the same machine.
 ---
 ## Context
 The `react-electron` branch is the active development branch — a major rewrite of the renderer in React 19 + TypeScript + Tailwind/shadcn while keeping the main process in CommonJS. As of commit `bb4e874` it is **ahead** of `master` in nearly every dimension (auto-updater, crash writer, migration runner, command palette, first-run wizard, updates settings, crash report modal, 30+ React modals, large-file mode, scoped CSS).
 A repo-wide diff (`git diff --stat master..react-electron`) shows 301 files changed, +38,293/-26,786 lines. Master is **behind** react-electron.
 The **only** feature present in `master` and absent in `react-electron` is the monospace-font-embedding feature added in master v4.5.0 (commits `3f8679c` through `b218c76`, 19 commits). It bundles JetBrains Mono + Fira Code TTFs and embeds them into PDF/DOCX/EPUB/HTML exports so ASCII art and code blocks render with the exact font the user sees in the preview.
 A second concern: the user has `markdown-converter` installed as a `.deb`. Running `npm run dev` from this repo currently uses the same `appId` (`com.concreteinfo.markdownconverter`) and `productName` (`MarkdownConverter`), which triggers Electron's single-instance lock and confuses file-association routing. We rename this branch's identity to `Markdown Converter React` / `markdown-converter-react` to coexist.
 ---
 ## Scope
 ### In scope
 1. Port the monospace font embedding feature from `master` v4.5.0 into the react-electron branch:
   - All five `src/main/*.js` modules (`MonospaceFontConfig`, `PdfFontHeader`, `DocxFontEmbedder`, `EpubFontEmbedder`, `ExportCss`)
   - Settings schema module (`src/main/settings/monospaceSettings.js`)
   - Two new IPC handlers (`get-monospace-settings`, `set-monospace-settings`) plus preload allowlist and TypeScript declaration
   - Renderer body-class toggle and CSS tokens (`--font-mono-active`, `--font-mono-feature`)
   - Bundled font assets: `JetBrainsMono-{Regular,Bold}.ttf`, `FiraCode-{Regular,Bold}.ttf` plus LICENSE files
   - `asarUnpack` directive for `assets/fonts/**`
   - `download-tools.js` extension to fetch Fira Code
   - Wire `buildMonospaceExportCss`, `buildPdfFontHeader`, `DocxFontEmbedder.embed`, `EpubFontEmbedder.embed` into `src/main/index.js` export pipelines (PDF, DOCX, EPUB, HTML paths)
   - Print-preview font integration (`src/renderer/components/preview/PrintPreviewFrame.tsx` or equivalent)
   - Tests: one test file per new module mirroring master's coverage plus an E2E smoke test
 2. Rename branch identity:
   - `package.json` `name` → `markdown-converter-react`
   - `package.json` `build.productName` → `Markdown Converter React`
   - `package.json` `build.appId` → `com.concreteinfo.markdownconverter.react`
   - `package.json` `build.linux.executableName` → `markdown-converter-react`
   - Window title prefix → `Markdown Converter — React Dev` in dev mode (use `process.env.VITE_DEV_SERVER_URL` as the gate)
   - Settings file path remains `userData/settings.json` (no migration needed) — but add a new key `appVariant: "react"` so the renderer can show the correct title
 ### Out of scope
 - React renderer rewrites (already ahead of master)
 - Auto-updater, crash, migration (already ahead of master)
 - Tauri / Web migration
 - Pandoc version bump
 - Documentation beyond this spec, the implementation plan, and the changelog entry
 - Changes to v4-to-v5 settings migration (we leave the existing runner alone)
 ---
 ## Design
 ### Module layout (new files)
 ```
 src/main/
  MonospaceFontConfig.js          # path resolver — finds bundled TTF
  PdfFontHeader.js                # builds .tex fontspec header for xelatex/lualatex
  DocxFontEmbedder.js             # injects TTF into pandoc DOCX output (post-process)
  EpubFontEmbedder.js             # EPUB --epub-embed-font + manifest patch
  ExportCss.js                    # builds CSS string with woff2 embedded as base64
  settings/
    monospaceSettings.js          # schema, defaults, family map
  ipc/
    monospace-handlers.js         # IPC handler registration
  utils/
    (existing)                    # no change
 src/renderer/
  hooks/
    use-monospace-classes.ts      # toggles body.mono-{jetbrains,fira}{,-ligatures} classes
  components/preview/
    PrintPreviewFrame.tsx         # wire print preview to monospace settings via IPC
  styles/globals.css              # add --font-mono-active/--font-mono-feature declarations
  types/electron.d.ts             # extend ElectronAPI with monospace.{getSettings,saveSettings}
 src/preload.js                    # add monospace channels to ALLOWED_SEND_CHANNELS + expose on window.electronAPI.monospace
 assets/fonts/
  JetBrainsMono-Regular.ttf       # bundled, ~270 KB
  JetBrainsMono-Bold.ttf          # bundled, ~278 KB
  JetBrainsMono-LICENSE.txt
  FiraCode-Regular.ttf            # bundled, ~300 KB
  FiraCode-Bold.ttf               # bundled, ~300 KB
  FiraCode-LICENSE.txt
 scripts/download-tools.js         # extend to fetch Fira Code
 tests/
  unit/main/monospace/
    MonospaceFontConfig.test.js
    monospaceSettings.test.js
    PdfFontHeader.test.js
    DocxFontEmbedder.test.js
    EpubFontEmbedder.test.js
    ExportCss.test.js
    monospace-handlers.test.js
  smoke-e2e-monospace.js          # e2e: convert ASCII-art Markdown → PDF/DOCX/EPUB/HTML, assert TTF references appear in output
 ```
 ### Key interfaces (TypeScript-style for clarity)
 ```ts
 // src/main/settings/monospaceSettings.js
 type MonoFont = 'jetbrains-mono' | 'fira-code';
 const FAMILY_BY_KEY: Record<MonoFont, string> = {
  'jetbrains-mono': 'JetBrains Mono',
  'fira-code': 'Fira Code',
 };
 function getActiveMonoFont(settings): string;
 function isLigaturesEnabled(settings): boolean;
 function safeMonospaceSettings(input): { monospaceFont: MonoFont; monospaceLigatures: boolean };
 // src/main/MonospaceFontConfig.js
 function getMonoFontTtfPath(familyKey, weight = 400): string | null;  // null if asset missing
 function ligaturesEnabled(settings): boolean;
 function getActiveFamily(settings): string;
 // src/main/PdfFontHeader.js
 function buildPdfFontHeader(settings, ttfPath, fontFamily): { headerPath: string; familyName: string };
 // src/main/DocxFontEmbedder.js
 async function embedDocxFont(inputDocxPath, outputDocxPath, ttfPath, fontFamily): Promise<void>;
 async function buildDocxWithEmbeddedFont(pandocArgs, settings): Promise<{args, postProcess}>;
 // src/main/EpubFontEmbedder.js
 async function embedEpubFont(epubPath, ttfPath, fontFamily): Promise<void>;
 function withEpubEmbedFontArgs(pandocArgs, ttfPath, fontFamily): string[];
 // src/main/ExportCss.js
 function buildExportCss(settings, { woff2Base64, family, ligatures }): string;
 function buildFontFaceBlock(familyKey, woff2Base64): string;
 // src/main/ipc/monospace-handlers.js
 function register({ getMainWindow }): void;
 //   ipcMain.handle('get-monospace-settings', () => ({ monospaceFont, monospaceLigatures }))
 //   ipcMain.handle('set-monospace-settings', (_e, partial) => safeMonospaceSettings(partial) → persist + broadcast)
 ```
 ### Renderer integration
 - `use-monospace-classes.ts` hook runs once on mount, calls `electronAPI.monospace.getSettings()`, applies `document.body.classList` of:
  - `mono-jetbrains-mono` | `mono-fira-code`
  - `mono-ligatures-on` | `mono-ligatures-off`
 - CSS in `globals.css`:
  ```css
  :root {
    --font-mono-active: 'JetBrains Mono', 'SF Mono', Monaco, 'Courier New', monospace;
    --font-mono-feature: 'liga' 0, 'calt' 0;
  }
  body.mono-fira-code { --font-mono-active: 'Fira Code', 'JetBrains Mono', 'SF Mono', monospace; }
  body.mono-ligatures-on { --font-mono-feature: 'liga' 1, 'calt' 1; }
  ```
 - All existing `font-family: monospace` and `font-family: var(--font-mono)` usages continue to work; the new tokens sit above them.
 ### Wiring into export pipelines
 In `src/main/index.js` `exportWithPandoc` (PDF branch):
 - Read `monospaceFont` + `monospaceLigatures` from settings
 - Resolve TTF path via `MonospaceFontConfig.getMonoFontTtfPath`
 - If path exists: build font header via `PdfFontHeader.buildPdfFontHeader`, pass `--include-in-header=…`
 - If path missing: log warning, fall back to existing `-V monofont=Consolas` behavior
 In DOCX branch: invoke `DocxFontEmbedder.embedDocxFont` post-pandoc.
 In EPUB branch: prepend `--epub-embed-font=…` to pandoc args; call `EpubFontEmbedder.embedEpubFont` to patch manifest.
 In HTML branch: write CSS via `ExportCss.buildExportCss` (embed woff2 as base64) and reference in `<style>`.
 ### Naming differentiation
 `package.json` changes:
 ```diff
 - "name": "markdown-converter"
 + "name": "markdown-converter-react"
 - "productName": "MarkdownConverter"
 + "productName": "Markdown Converter React"
 - "appId": "com.concreteinfo.markdownconverter"
 + "appId": "com.concreteinfo.markdownconverter.react"
 + "linux": {
 +   "executableName": "markdown-converter-react",
 +   "synopsis": "Markdown editor (React build)",
 +   "description": "Markdown editor and universal file converter — React build"
 + }
 ```
 `src/main/window/index.js`:
 ```js
 const isDev = !!process.env.VITE_DEV_SERVER_URL;
 const titleSuffix = isDev ? ' — React Dev' : '';
 mainWindow = new BrowserWindow({
  title: `Markdown Converter${titleSuffix}`,
  ...
 });
 ```
 ### Settings impact
 Add two keys to `migration-transform.js` v5 schema with safe defaults:
 - `monospaceFont: z.enum(['jetbrains-mono', 'fira-code']).default('jetbrains-mono')`
 - `monospaceLigatures: z.boolean().default(false)`
 - `appVariant: z.enum(['classic', 'react']).default('react')`
 Existing user settings remain valid; the migration just fills in the new defaults.
 ---
 ## Testing strategy (TDD)
 For each new module: red-green-refactor.
 1. `MonospaceFontConfig.test.js` — uses tmpdir + mocked `process.resourcesPath` to assert resolution from `assets/fonts/JetBrainsMono-Regular.ttf`. Covers missing-file fallback.
 2. `monospaceSettings.test.js` — schema validation: rejects unknown fonts, coerces ligatures boolean, fills defaults.
 3. `PdfFontHeader.test.js` — writes a temp `.tex` file, asserts `\setmonofont{JetBrainsMono-Regular.ttf}[...]` lines match.
 4. `DocxFontEmbedder.test.js` — given a minimal DOCX zip, asserts `word/fonts/` contains the TTF and `word/_rels/fontTable.xml.rels` references it.
 5. `EpubFontEmbedder.test.js` — asserts `META-INF/container.xml` and `content.opf` updated after `--epub-embed-font`.
 6. `ExportCss.test.js` — base64 round-trip: `atob(css.match(/base64,([A-Za-z0-9+/=]+)/)[1])` returns the original woff2 bytes.
 7. `monospace-handlers.test.js` — invokes the registered handlers against `ipcMain` mock; asserts settings persistence + broadcast.
 8. `smoke-e2e-monospace.js` — runs `pandoc` end-to-end against a fixture markdown with ASCII art; greps output for font references.
 Coverage threshold maintained: jest at 15%, vitest at v8 + renderer lines.
 ---
 ## Risks
 - **TTF download license** — Fira Code is OFL-1.1; JetBrains Mono is OFL-1.1. Both allow redistribution; LICENSE files ship alongside TTFs. No risk.
 - **Pandoc version sensitivity** — `--epub-embed-font` requires pandoc ≥ 2.19. The download-tools script pins to 3.9.0.2; check `pandocVersion` and gracefully fall back if older.
 - **asarUnpack size** — adding ~1.2 MB of TTFs to packaged builds. Acceptable; matches master.
 - **Dev/prod appId split** — if a user installs both `markdown-converter` and `markdown-converter-react` debs, their settings files are separate (`userData/com.concreteinfo.markdownconverter.react/settings.json`). Documented in README.
 - **Test environment** — the e2e smoke test requires pandoc available locally. We'll `test.skip` if `which pandoc` fails.
 ---
 ## Definition of done
 - [ ] All planned steps implemented, not just the first/easiest ones
 - [ ] No forbidden markers (`TODO`, `FIXME`, `XXX`, `HACK`, `not implemented`, `placeholder`, `stub`, `coming soon`) in changed source
 - [ ] New test suites pass; existing 638 tests still pass
 - [ ] `npm run build:linux` produces a `.deb` artifact named `markdown-converter-react_*_amd64.deb`
 - [ ] App launches in dev mode with title `Markdown Converter — React Dev`
 - [ ] E2E smoke test confirms TTF references in PDF/DOCX/EPUB/HTML output
 - [ ] CHANGELOG.md updated with a "5.1.0 — react-electron parity" entry
 - [ ] No unrelated refactors; every changed line traces to the request
 ---
 ## Learning collaboration
 Per the project's learning-mode preference, the user will be asked to contribute two 5-10 line decisions during implementation:
 1. **Default monospace family** in `monospaceSettings.js` (`jetbrains-mono` vs `fira-code` vs `system-fallback`).
 2. **Body-class gating strategy** in `use-monospace-classes.ts` (apply on every settings change vs debounce vs once-on-mount).
 These choices shape the feature's behavior in ways that benefit from the user's domain knowledge.
@@ -1,112 +0,0 @@
 /**
 * ESLint Configuration for PanConverter
 * Uses flat config format (ESLint 9+)
 */
 module.exports = [
  {
    // Global ignores
    ignores: [
      'node_modules/**',
      'dist/**',
      'coverage/**',
      '*.min.js'
    ]
  },
  {
    // JavaScript files
    files: ['**/*.js'],
    languageOptions: {
      ecmaVersion: 2022,
      sourceType: 'module',
      globals: {
        // Node.js
        require: 'readonly',
        module: 'readonly',
        exports: 'readonly',
        __dirname: 'readonly',
        __filename: 'readonly',
        process: 'readonly',
        Buffer: 'readonly',
        console: 'readonly',
        setTimeout: 'readonly',
        setInterval: 'readonly',
        clearTimeout: 'readonly',
        clearInterval: 'readonly',
        // Browser
        window: 'readonly',
        document: 'readonly',
        localStorage: 'readonly',
        alert: 'readonly',
        prompt: 'readonly',
        confirm: 'readonly',
        Event: 'readonly',
        CustomEvent: 'readonly',
        HTMLElement: 'readonly',
        MutationObserver: 'readonly',
        TextEncoder: 'readonly',
        FileReader: 'readonly',
        requestAnimationFrame: 'readonly',
        cancelAnimationFrame: 'readonly',
        navigator: 'readonly',
        location: 'readonly',
        fetch: 'readonly',
        URL: 'readonly',
        Blob: 'readonly',
        Image: 'readonly',
        DragEvent: 'readonly',
        ClipboardEvent: 'readonly',
        KeyboardEvent: 'readonly',
        MouseEvent: 'readonly',
        NodeList: 'readonly',
        HTMLInputElement: 'readonly',
        HTMLTextAreaElement: 'readonly',
        getComputedStyle: 'readonly',
        // Electron
        electronAPI: 'readonly',
        // Libraries
        marked: 'readonly',
        DOMPurify: 'readonly',
        hljs: 'readonly',
        mermaid: 'readonly',
        // Node.js global object
        global: 'writable',
        // Jest
        jest: 'readonly',
        describe: 'readonly',
        test: 'readonly',
        it: 'readonly',
        expect: 'readonly',
        beforeEach: 'readonly',
        afterEach: 'readonly',
        beforeAll: 'readonly',
        afterAll: 'readonly'
      }
    },
    rules: {
      // Error prevention
      'no-unused-vars': ['warn', { argsIgnorePattern: '^_', varsIgnorePattern: '^_', caughtErrorsIgnorePattern: '^_' }],
      'no-undef': 'error',
      'no-console': 'off', // Allow console for Electron apps
      // Code quality
      'eqeqeq': ['warn', 'always'],
      'no-var': 'warn',
      'prefer-const': 'warn',
      // Style (handled by Prettier)
      'semi': 'off',
      'quotes': 'off',
      'indent': 'off',
      // Async handling
      'no-async-promise-executor': 'warn',
      'require-await': 'off',
      // Security
      'no-eval': 'error',
      'no-implied-eval': 'error',
      'no-new-func': 'error'
    }
  }
 ];
@@ -1,73 +0,0 @@
 /**
 * Jest Configuration for PanConverter
 * @version 2.2.0
 */
 module.exports = {
  // Test environment
  testEnvironment: 'jsdom',
  // Root directory
  rootDir: '.',
  // Test file patterns — scoped to ./tests/ only so dist/ artifacts like
  // .snap packages don't get matched as test suites.
  testMatch: [
    '<rootDir>/tests/**/*.test.js',
    '<rootDir>/tests/**/*.spec.js'
  ],
  // Ignore build outputs so .snap packages and bundled .asar contents
  // never enter jest's file discovery.
  testPathIgnorePatterns: [
    '/node_modules/',
    '/dist/',
    '/\\.git/'
  ],
  modulePathIgnorePatterns: [
    '/node_modules/',
    '/dist/'
  ],
  // Coverage configuration
  collectCoverageFrom: [
    'src/**/*.js',
    '!src/main/**', // Main process needs electron-mock
    '!src/preload.js', // Electron preload requires contextBridge
    '!**/node_modules/**'
  ],
  // Coverage thresholds (raised with expanded test suite)
  coverageThreshold: {
    global: {
      branches: 10,
      functions: 15,
      lines: 15,
      statements: 15
    }
  },
  // Transform settings (no transpilation needed for vanilla JS)
  transform: {},
  // Module paths
  moduleDirectories: ['node_modules', 'src'],
  // Setup files
  setupFilesAfterEnv: ['<rootDir>/tests/setup.js'],
  // Ignore patterns
  testPathIgnorePatterns: [
    '/node_modules/',
    '/dist/'
  ],
  // Verbose output
  verbose: true,
  // Clear mocks between tests
  clearMocks: true,
  // Reset modules between tests
  resetModules: true
 };
@@ -1,318 +0,0 @@
 {
  "name": "markdown-converter-react",
  "version": "5.0.1",
  "description": "Professional Markdown editor and universal file converter with PDF editing, batch processing, and syntax highlighting (React build)",
  "main": "src/main/index.js",
  "scripts": {
    "start": "electron .",
    "dev:renderer": "vite --config vite.renderer.config.ts",
    "dev:electron": "wait-on tcp:5173 && cross-env VITE_DEV_SERVER_URL=http://localhost:5173 ELECTRON_DISABLE_SANDBOX=1 electron . -- --no-sandbox --disable-gpu --disable-software-rasterizer --disable-dev-shm-usage",
    "dev": "concurrently -k -n vite,electron -c blue,green \"npm:dev:renderer\" \"npm:dev:electron\"",
    "build:renderer": "vite build --config vite.renderer.config.ts",
    "preview": "npm run build:renderer && electron .",
    "test": "jest",
    "test:watch": "jest --watch",
    "test:coverage": "jest --coverage",
    "test:renderer": "vitest run",
    "test:renderer:watch": "vitest",
    "test:renderer:coverage": "vitest run --coverage",
    "lint": "eslint src tests",
    "lint:fix": "eslint src tests --fix",
    "format": "prettier --write src tests",
    "format:check": "prettier --check src tests",
    "build": "electron-builder",
    "build:win": "electron-builder --win",
    "build:win-signed": "cross-env CSC_LINK=code-signing-cert.pfx electron-builder --win",
    "build:win-unsigned": "cross-env CSC_IDENTITY_AUTO_DISCOVERY=false electron-builder --win",
    "create-cert": "powershell -ExecutionPolicy Bypass -File scripts/create-selfsigned-cert.ps1",
    "build:mac": "electron-builder --mac",
    "build:linux": "electron-builder --linux",
    "build:linux-ci": "electron-builder --linux deb AppImage",
    "build:local": "electron-builder --linux --win",
    "dist": "electron-builder --publish=never",
    "dist:all": "electron-builder -mwl",
    "download-tools": "node scripts/download-tools.js",
    "generate-icons": "node scripts/generate-icons.js",
    "build:icon-icns": "node scripts/build-icon-icns.js",
    "publish:concreteinfo": "node scripts/publish-concreteinfo.js"
  },
  "keywords": [
    "markdown",
    "pandoc",
    "converter",
    "editor",
    "pdf",
    "audio",
    "video",
    "image"
  ],
  "author": "ConcreteInfo <amit.wh@gmail.com>",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/amitwh/markdown-converter"
  },
  "devDependencies": {
    "@playwright/test": "^1.60.0",
    "@testing-library/dom": "^10.4.1",
    "@testing-library/jest-dom": "^6.9.1",
    "@testing-library/react": "^16.3.2",
    "@testing-library/user-event": "^14.6.1",
    "@types/figlet": "^1.7.0",
    "@types/node": "^25.9.1",
    "@types/react": "^19.2.16",
    "@types/react-dom": "^19.2.3",
    "@vitejs/plugin-react": "^6.0.2",
    "@vitest/ui": "^4.1.8",
    "autoprefixer": "^10.5.0",
    "class-variance-authority": "^0.7.1",
    "clsx": "^2.1.1",
    "concurrently": "^10.0.3",
    "cross-env": "^10.0.0",
    "electron": "^41.1.1",
    "electron-builder": "^26.0.12",
    "eslint": "^9.39.2",
    "eslint-config-prettier": "^10.1.8",
    "eslint-plugin-prettier": "^5.5.4",
    "jest": "^30.2.0",
    "jest-environment-jsdom": "^30.2.0",
    "jsdom": "^29.1.1",
    "lucide-react": "^1.17.0",
    "postcss": "^8.5.15",
    "prettier": "^3.7.4",
    "sharp": "^0.34.3",
    "tailwind-merge": "^3.6.0",
    "tailwindcss": "^3.4.19",
    "tailwindcss-animate": "^1.0.7",
    "typescript": "^6.0.3",
    "vite": "^8.0.16",
    "vitest": "^4.1.8",
    "wait-on": "^9.0.10"
  },
  "dependencies": {
    "@codemirror/autocomplete": "^6.20.1",
    "@codemirror/commands": "^6.10.2",
    "@codemirror/lang-css": "^6.3.1",
    "@codemirror/lang-html": "^6.4.11",
    "@codemirror/lang-javascript": "^6.2.5",
    "@codemirror/lang-json": "^6.0.2",
    "@codemirror/lang-markdown": "^6.5.0",
    "@codemirror/lang-python": "^6.2.1",
    "@codemirror/language": "^6.12.2",
    "@codemirror/lint": "^6.9.5",
    "@codemirror/search": "^6.6.0",
    "@codemirror/state": "^6.5.4",
    "@codemirror/theme-one-dark": "^6.1.3",
    "@codemirror/view": "^6.39.16",
    "@dnd-kit/core": "^6.3.1",
    "@dnd-kit/sortable": "^10.0.0",
    "@dnd-kit/utilities": "^3.2.2",
    "@hookform/resolvers": "^5.4.0",
    "@radix-ui/react-checkbox": "^1.3.3",
    "@radix-ui/react-collapsible": "^1.1.12",
    "@radix-ui/react-context-menu": "^2.2.16",
    "@radix-ui/react-dialog": "^1.1.15",
    "@radix-ui/react-label": "^2.1.8",
    "@radix-ui/react-radio-group": "^1.3.8",
    "@radix-ui/react-scroll-area": "^1.2.10",
    "@radix-ui/react-select": "^2.2.6",
    "@radix-ui/react-slider": "^1.3.6",
    "@radix-ui/react-slot": "^1.2.4",
    "@radix-ui/react-switch": "^1.2.6",
    "@radix-ui/react-tabs": "^1.1.13",
    "@tanstack/react-table": "^8.21.3",
    "codemirror": "^6.0.2",
    "core-util-is": "^1.0.3",
    "docx": "^9.7.1",
    "docx4js": "^2.0.1",
    "dompurify": "^3.3.1",
    "electron-store": "^10.1.0",
    "electron-updater": "^6.8.9",
    "ffmpeg-static": "^5.3.0",
    "figlet": "^1.11.0",
    "highlight.js": "^11.11.1",
    "html2pdf.js": "^0.14.0",
    "immer": "^11.1.8",
    "marked": "^17.0.3",
    "marked-footnote": "^1.4.0",
    "marked-highlight": "^2.2.3",
    "mermaid": "^11.12.3",
    "motion": "^12.40.0",
    "next-themes": "^0.4.6",
    "pdf-lib": "^1.17.1",
    "pdfjs-dist": "^5.5.207",
    "pdfkit": "^0.17.2",
    "pizzip": "^3.2.0",
    "react": "^19.2.7",
    "react-dom": "^19.2.7",
    "react-hook-form": "^7.77.0",
    "react-resizable-panels": "^4.11.2",
    "simple-git": "^3.32.3",
    "sonner": "^2.0.7",
    "tslib": "^2.8.1",
    "zod": "^4.4.3",
    "zustand": "^5.0.14"
  },
  "overrides": {
    "jszip": "^3.10.1",
    "nth-check": "^2.1.1",
    "lodash.pick": "npm:lodash@^4.17.21",
    "lodash-es": "^4.18.1",
    "lodash": "^4.17.21"
  },
  "build": {
    "appId": "com.concreteinfo.markdownconverter.react",
    "productName": "Markdown Converter React",
    "copyright": "Copyright (C) 2024-2025 ConcreteInfo",
    "directories": {
      "output": "dist"
    },
    "icon": "assets/icon",
    "files": [
      "src/main/**/*",
      "src/preload.js",
      "src/plugins/**/*",
      "assets/fonts/**",
      "package.json"
    ],
    "asarUnpack": [
      "node_modules/ffmpeg-static/**",
      "assets/fonts/**"
    ],
    "extraResources": [
      {
        "from": "dist/renderer",
        "to": "renderer"
      }
    ],
    "extraFiles": [],
    "fileAssociations": [
      {
        "ext": "md",
        "name": "Markdown Document",
        "description": "Markdown Document",
        "mimeType": "text/markdown",
        "role": "Editor"
      },
      {
        "ext": "markdown",
        "name": "Markdown Document",
        "description": "Markdown Document",
        "mimeType": "text/markdown",
        "role": "Editor"
      },
      {
        "ext": "pdf",
        "name": "PDF Document",
        "description": "PDF Document",
        "mimeType": "application/pdf",
        "role": "Editor"
      }
    ],
    "mac": {
      "category": "public.app-category.productivity",
      "identity": null,
      "target": [
        {
          "target": "dmg",
          "arch": [
            "x64",
            "arm64"
          ]
        },
        {
          "target": "zip",
          "arch": [
            "x64",
            "arm64"
          ]
        }
      ],
      "icon": "assets/icon.icns",
      "darkModeSupport": true,
      "hardenedRuntime": false,
      "gatekeeperAssess": false,
      "entitlements": null
    },
    "win": {
      "target": [
        {
          "target": "nsis",
          "arch": [
            "x64"
          ]
        },
        {
          "target": "portable",
          "arch": [
            "x64"
          ]
        },
        {
          "target": "zip",
          "arch": [
            "x64"
          ]
        }
      ],
      "artifactName": "${productName}-${version}-${arch}.${ext}",
      "requestedExecutionLevel": "asInvoker",
      "legalTrademarks": "Copyright (C) 2024-2025 ConcreteInfo",
      "verifyUpdateCodeSignature": false,
      "signAndEditExecutable": false,
      "extraFiles": [
        {
          "from": "bin/win32/pandoc.exe",
          "to": "bin/pandoc.exe"
        }
      ]
    },
    "nsis": {
      "oneClick": false,
      "perMachine": false,
      "allowToChangeInstallationDirectory": true,
      "displayLanguageSelector": true,
      "createDesktopShortcut": true,
      "createStartMenuShortcut": true,
      "shortcutName": "MarkdownConverter",
      "runAfterFinish": true,
      "menuCategory": "Productivity",
      "license": "LICENSE",
      "warningsAsErrors": false,
      "artifactName": "${productName}-Setup-${version}.${ext}",
      "deleteAppDataOnUninstall": false,
      "differentialPackage": true
    },
    "linux": {
      "target": [
        "deb",
        "AppImage",
        "snap"
      ],
      "category": "Utility",
      "maintainer": "ConcreteInfo <amit.wh@gmail.com>",
      "executableName": "markdown-converter-react",
      "synopsis": "Markdown editor and converter (React build)",
      "extraFiles": [
        {
          "from": "bin/linux/pandoc",
          "to": "bin/pandoc"
        }
      ]
    },
    "deb": {
      "depends": [
        "imagemagick",
        "libreoffice-common"
      ],
      "description": "Professional Markdown editor and universal file converter",
      "maintainer": "ConcreteInfo <amit.wh@gmail.com>"
    },
    "publish": {
      "provider": "github",
      "owner": "amitwh",
      "repo": "markdown-converter",
      "releaseType": "release"
    }
  }
 }
@@ -1,6 +0,0 @@
 module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
 }
@@ -1,83 +0,0 @@
 #!/bin/bash
 echo "=========================================="
 echo "Pan Converter - GitHub Push Helper"
 echo "=========================================="
 echo ""
 echo "Before running this script, please ensure:"
 echo "1. You have created a repository named 'pan-converter' on GitHub"
 echo "2. The repository is empty (no README, .gitignore, or license)"
 echo "3. You have set up authentication (SSH key or Personal Access Token)"
 echo ""
 read -p "Have you completed the above steps? (y/n): " -n 1 -r
 echo ""
 if [[ ! $REPLY =~ ^[Yy]$ ]]; then
    echo "Please complete the setup first:"
    echo "1. Go to https://github.com/new"
    echo "2. Create a new repository named 'pan-converter'"
    echo "3. DO NOT initialize with README, .gitignore, or license"
    echo "4. Set up SSH key or Personal Access Token for authentication"
    exit 1
 fi
 echo ""
 echo "Choose authentication method:"
 echo "1. SSH (Recommended if you have SSH keys set up)"
 echo "2. HTTPS (Requires Personal Access Token)"
 read -p "Enter your choice (1 or 2): " AUTH_CHOICE
 if [ "$AUTH_CHOICE" = "1" ]; then
    echo "Using SSH authentication..."
    git remote set-url origin git@github.com:amitwh/pan-converter.git
 elif [ "$AUTH_CHOICE" = "2" ]; then
    echo "Using HTTPS authentication..."
    echo "You'll need to enter your GitHub username and Personal Access Token"
    git remote set-url origin https://github.com/amitwh/pan-converter.git
 else
    echo "Invalid choice. Exiting."
    exit 1
 fi
 echo ""
 echo "Pushing branches to GitHub..."
 echo "=============================="
 # Push master branch with upstream tracking
 echo "Pushing master branch..."
 if git push -u origin master; then
    echo "✓ Master branch pushed successfully"
 else
    echo "✗ Failed to push master branch"
    echo "Please check your authentication and try again"
    exit 1
 fi
 # Push other branches
 echo "Pushing linux branch..."
 if git push origin linux; then
    echo "✓ Linux branch pushed successfully"
 else
    echo "✗ Failed to push linux branch"
 fi
 echo "Pushing macos branch..."
 if git push origin macos; then
    echo "✓ macOS branch pushed successfully"
 else
    echo "✗ Failed to push macos branch"
 fi
 echo "Pushing windows branch..."
 if git push origin windows; then
    echo "✓ Windows branch pushed successfully"
 else
    echo "✗ Failed to push windows branch"
 fi
 echo ""
 echo "=========================================="
 echo "Push complete!"
 echo "Your repository is available at:"
 echo "https://github.com/amitwh/pan-converter"
 echo "=========================================="
@@ -1,718 +0,0 @@
 # Repository Structure Map
 Auto-generated by `~/.claude-shared/scripts/repo-map.sh` (universal-ctags).
 Signatures only — classes, functions, methods, interfaces, enums, types, namespaces, traits.
 Regenerate after structural changes. Languages: `JavaScript,Sh,TypeScript`.
 ```
 scripts/download-tools.js:
  L28  function  findFile
  L46  method  extract (PANDOC_CONFIG.linux)
  L61  method  extract (PANDOC_CONFIG.win32)
  L77  method  extract (PANDOC_CONFIG.darwin)
  L90  function  download
  L97  function  get (download)
  L136  function  downloadPandoc
 scripts/generate-icons.js:
  L17  function  generateIcons
 scripts/verify-open-export.mjs:
  L60  function  showSaveDialogSync (dialog)
 src/adapters/electron/fs.js:
  L20  method  readFile (electronFsAdapter)
  L30  method  writeFile (electronFsAdapter)
  L39  method  deleteFile (electronFsAdapter)
  L48  method  ensureDir (electronFsAdapter)
  L57  method  listDirectory (electronFsAdapter)
  L77  method  exists (electronFsAdapter)
  L86  method  isDirectory (electronFsAdapter)
  L96  method  copy (electronFsAdapter)
  L106  method  move (electronFsAdapter)
 src/analytics/analytics-panel.js:
  L7  function  showAnalyticsModal
  L105  function  escHandler (showAnalyticsModal)
  L116  function  escapeHtml
 src/analytics/writing-analytics.js:
  L77  function  countSyllables
  L83  function  extractWords
  L87  function  getReadabilityLabel
  L95  function  analyze
 src/editor/codemirror-setup.js:
  L46  function  createEditor
  L61  function  onChange (createEditor)
  L118  function  getLanguageExtension
  L120  method  javascript (getLanguageExtension.loaders)
  L124  method  html (getLanguageExtension.loaders)
  L128  method  css (getLanguageExtension.loaders)
  L132  method  json (getLanguageExtension.loaders)
  L136  method  python (getLanguageExtension.loaders)
 src/main/GitOperations.js:
  L3  function  getGitInstance
  L7  function  getStatus
  L31  function  stage
  L56  function  commit
  L66  function  log
  L84  function  diff
 src/main/PDFOperations.js:
  L5  function  parsePageRanges
  L28  function  hexToRgb
  L39  function  pdfMerge
  L59  function  pdfSplit
  L126  function  pdfCompress
  L152  function  pdfRotate
  L182  function  pdfDeletePages
  L208  function  pdfReorder
  L233  function  pdfWatermark
  L319  function  pdfEncrypt
  L353  function  pdfDecrypt
  L370  function  pdfSetPermissions
  L404  function  executeOperation
  L431  function  getPageCount
 src/main/files/binary.js:
  L6  function  register
 src/main/files/git.js:
  L6  function  register
 src/main/files/index.js:
  L9  function  register
 src/main/index.js:
  L28  function  getPandocPath
  L46  function  getFFmpegPath
  L65  function  sanitizeErrorMessage
  L74  function  createRateLimiter
  L76  function  canProceed (createRateLimiter)
  L86  function  convertDataToMarkdown
  L108  function  runPandocCmd
  L124  function  parseCommand
  L319  function  checkPandocAvailability
  L334  function  showAboutDialog
  L437  function  showDependenciesDialog
  L550  function  openFile
  L580  function  openPdfFile
  L599  function  saveAsFile
  L614  function  exportFile
  L624  function  showExportOptionsDialog
  L628  function  showBatchConversionDialog
  L633  function  selectWordTemplate
  L654  function  showTemplateSettings
  L847  function  processDynamicFields
  L868  function  setDocxPageSize
  L927  function  addHeaderFooterToDocx
  L1060  function  exportWordWithTemplate
  L1100  function  exportPDFViaWordTemplate
  L1180  function  showUniversalConverterDialog
  L1185  function  showPDFEditorDialog
  L1195  function  checkConverterAvailable
  L1336  function  collectFiles
  L1431  function  convertWithLibreOffice
  L1466  function  convertWithImageMagick
  L1475  function  convertWithFFmpeg
  L1483  function  convertWithPandoc
  L1490  function  performExportWithOptions
  L1741  function  tryPdfFallback
  L1818  function  showExportSuccess
  L1828  function  exportWithPandoc
  L1907  function  exportToHTML
  L2026  function  exportToPDFElectron
  L2174  function  exportSpreadsheet
  L2184  function  importDocument
  L2280  function  setTheme
  L2488  function  extractTablesFromMarkdown
  L2530  function  performBatchConversion
  L2552  function  findMarkdownFiles (performBatchConversion)
  L2579  function  processNextFile (performBatchConversion)
  L2855  function  handleCLIConversion
  L2883  function  showConversionDialog
  L2932  function  performCLIConversion
  L2974  function  buildPandocCommand
  L3152  method  transform (anonymousObject0b93a19c6805)
  L3273  function  openFileFromPath
  L3468  function  loadSnippets
  L3479  function  saveSnippetsFile
 src/main/ipc/crash-handlers.js:
  L3  function  register
 src/main/ipc/updater-handlers.js:
  L4  function  register
 src/main/menu/index.js:
  L16  function  buildMenu
  L30  function  register
 src/main/menu/items.js:
  L9  function  buildRecentFilesMenu
  L18  method  click (buildRecentFilesMenu.anonymousObject59dd54ea0305)
  L27  method  click (anonymousObject59dd54ea0505)
  L40  function  fileItems
  L143  method  click (fileItems.anonymousObject59dd54ea1005)
  L150  method  click (fileItems.anonymousObject59dd54ea1105)
  L157  method  click (fileItems.anonymousObject59dd54ea1205)
  L165  method  click (fileItems.anonymousObject59dd54ea1305)
  L172  method  click (fileItems.anonymousObject59dd54ea1405)
  L180  method  click (fileItems.anonymousObject59dd54ea1505)
  L187  method  click (fileItems.anonymousObject59dd54ea1605)
  L194  method  click (fileItems.anonymousObject59dd54ea1705)
  L201  method  click (fileItems.anonymousObject59dd54ea1805)
  L209  method  click (fileItems.anonymousObject59dd54ea1a05)
  L216  method  click (fileItems.anonymousObject59dd54ea1b05)
  L224  method  click (fileItems.anonymousObject59dd54ea1d05)
  L232  method  click (fileItems.anonymousObject59dd54ea1f05)
  L239  method  click (fileItems.anonymousObject59dd54ea2005)
  L246  method  click (fileItems.anonymousObject59dd54ea2105)
  L254  method  click (fileItems.anonymousObject59dd54ea2305)
  L261  method  click (fileItems.anonymousObject59dd54ea2405)
  L300  function  editItems
  L326  function  viewItems
  L372  method  click (viewItems.anonymousObject59dd54ea2a05)
  L379  method  click (viewItems.anonymousObject59dd54ea2b05)
  L386  method  click (viewItems.anonymousObject59dd54ea2c05)
  L393  method  click (viewItems.anonymousObject59dd54ea2d05)
  L400  method  click (viewItems.anonymousObject59dd54ea2e05)
  L407  method  click (viewItems.anonymousObject59dd54ea2f05)
  L414  method  click (viewItems.anonymousObject59dd54ea3005)
  L421  method  click (viewItems.anonymousObject59dd54ea3105)
  L428  method  click (viewItems.anonymousObject59dd54ea3205)
  L435  method  click (viewItems.anonymousObject59dd54ea3305)
  L443  method  click (viewItems.anonymousObject59dd54ea3505)
  L450  method  click (viewItems.anonymousObject59dd54ea3605)
  L457  method  click (viewItems.anonymousObject59dd54ea3705)
  L464  method  click (viewItems.anonymousObject59dd54ea3805)
  L471  method  click (viewItems.anonymousObject59dd54ea3905)
  L478  method  click (viewItems.anonymousObject59dd54ea3a05)
  L485  method  click (viewItems.anonymousObject59dd54ea3b05)
  L492  method  click (viewItems.anonymousObject59dd54ea3c05)
  L499  method  click (viewItems.anonymousObject59dd54ea3d05)
  L506  method  click (viewItems.anonymousObject59dd54ea3e05)
  L513  method  click (viewItems.anonymousObject59dd54ea3f05)
  L520  method  click (viewItems.anonymousObject59dd54ea4005)
  L527  method  click (viewItems.anonymousObject59dd54ea4105)
  L534  method  click (viewItems.anonymousObject59dd54ea4205)
  L541  method  click (viewItems.anonymousObject59dd54ea4305)
  L602  function  batchItems
  L631  function  convertItems
  L644  function  pdfEditorItems
  L712  method  click (pdfEditorItems.anonymousObject59dd54ea4905)
  L719  method  click (pdfEditorItems.anonymousObject59dd54ea4a05)
  L726  method  click (pdfEditorItems.anonymousObject59dd54ea4b05)
  L744  function  toolsItems
  L757  function  helpItems
 src/main/store.js:
  L11  method  get (store)
  L20  method  set (store)
 src/main/updater/crash-writer.js:
  L5  class  CrashWriter
  L6  method  constructor (CrashWriter)
  L12  method  handleUncaught (CrashWriter)
  L28  method  _prune (CrashWriter)
  L40  method  list (CrashWriter)
  L54  method  delete (CrashWriter)
  L59  method  path (CrashWriter)
 src/main/updater/feed-config.js:
  L1  function  feedConfigFor
 src/main/updater/migration-runner.js:
  L4  class  MigrationRunner
  L5  method  constructor (MigrationRunner)
  L12  method  run (MigrationRunner)
  L36  method  _writeDefaults (MigrationRunner)
 src/main/updater/migration-transform.js:
  L49  function  isAlreadyV5
  L56  function  normalizeAlreadyV5
  L95  function  migrateV4ToV5
 src/main/updater/updater-service.js:
  L4  class  UpdaterService
  L5  method  constructor (UpdaterService)
  L13  method  _wire (UpdaterService)
  L27  method  _emit (UpdaterService)
  L32  method  check (UpdaterService)
  L38  method  install (UpdaterService)
 src/main/utils/paths.js:
  L7  function  getAllowedDirectories
  L23  function  validatePath
  L58  function  resolveWritablePath
  L88  function  isPathAccessible
 src/main/window/index.js:
  L10  function  createMainWindow
 src/main/window/state.js:
  L10  function  load
  L18  function  save
 src/main/word-template/index.js:
  L11  class  WordTemplateExporter
  L12  method  constructor (WordTemplateExporter)
  L21  method  convert (WordTemplateExporter)
  L58  method  setPageSize (WordTemplateExporter)
  L111  method  insertContentAfterPage (WordTemplateExporter)
  L140  method  markdownToWordXml (WordTemplateExporter)
  L251  method  createHeadingXml (WordTemplateExporter)
  L266  method  createParagraphXml (WordTemplateExporter)
  L280  method  createQuoteXml (WordTemplateExporter)
  L294  method  createListItemXml (WordTemplateExporter)
  L315  method  createCodeBlockXml (WordTemplateExporter)
  L352  method  createHorizontalRuleXml (WordTemplateExporter)
  L366  method  createTableXml (WordTemplateExporter)
  L502  method  isAsciiArt (WordTemplateExporter)
  L606  method  createAsciiArtXml (WordTemplateExporter)
  L715  method  parseInlineFormatting (WordTemplateExporter)
  L776  method  createRunXml (WordTemplateExporter)
  L797  method  escapeXml (WordTemplateExporter)
 src/plugins/built-in/_sample/index.js:
  L3  class  SamplePlugin
  L4  method  init (SamplePlugin)
 src/plugins/built-in/writing-studio/goal-tracker.js:
  L3  class  GoalTracker
  L7  method  constructor (GoalTracker)
  L11  method  _getHistory (GoalTracker)
  L16  method  _setHistory (GoalTracker)
  L20  method  _setHistoryDay (GoalTracker)
  L26  method  addWords (GoalTracker)
  L37  method  getDailyProgress (GoalTracker)
  L44  method  getStreak (GoalTracker)
  L61  method  getLast30Days (GoalTracker)
  L74  method  getWeeklyTotal (GoalTracker)
 src/plugins/built-in/writing-studio/index.js:
  L7  class  WritingStudioPlugin
  L8  method  init (WritingStudioPlugin)
  L34  method  _registerCommands (WritingStudioPlugin)
  L112  method  _registerStatusBar (WritingStudioPlugin)
  L123  method  deactivate (WritingStudioPlugin)
  L127  method  getEngines (WritingStudioPlugin)
 src/plugins/built-in/writing-studio/panels/goals-panel.js:
  L1  function  renderGoalsPanel
 src/plugins/built-in/writing-studio/panels/manuscript-panel.js:
  L1  function  renderManuscriptPanel
 src/plugins/built-in/writing-studio/panels/proofread-panel.js:
  L1  function  renderProofreadPanel
  L41  method  callback (anonymousObjectd036aefd0105)
  L50  function  renderIssues
 src/plugins/built-in/writing-studio/panels/snapshots-panel.js:
  L1  function  renderSnapshotsPanel
 src/plugins/built-in/writing-studio/project-manager.js:
  L1  class  ProjectManager
  L5  method  constructor (ProjectManager)
  L9  method  createProject (ProjectManager)
  L21  method  loadProject (ProjectManager)
  L27  method  _saveProject (ProjectManager)
  L31  method  addChapter (ProjectManager)
  L38  method  updateChapter (ProjectManager)
  L45  method  compileManuscript (ProjectManager)
  L56  method  getStats (ProjectManager)
 src/plugins/built-in/writing-studio/snapshot-manager.js:
  L1  class  SnapshotManager
  L6  method  constructor (SnapshotManager)
  L11  method  _getAll (SnapshotManager)
  L16  method  _saveAll (SnapshotManager)
  L20  method  create (SnapshotManager)
  L34  method  list (SnapshotManager)
  L38  method  getById (SnapshotManager)
  L42  method  restore (SnapshotManager)
  L48  method  delete (SnapshotManager)
  L53  method  diff (SnapshotManager)
  L71  method  prune (SnapshotManager)
 src/plugins/built-in/writing-studio/sprint-engine.js:
  L1  class  SprintEngine
  L6  method  constructor (SprintEngine)
  L14  method  start (SprintEngine)
  L22  method  stop (SprintEngine)
  L33  method  tick (SprintEngine)
  L43  method  isActive (SprintEngine)
  L47  method  getRemaining (SprintEngine)
 src/plugins/event-bus.js:
  L1  class  EventBus
  L2  method  constructor (EventBus)
  L6  method  on (EventBus)
  L13  method  off (EventBus)
  L25  method  emit (EventBus)
  L37  method  hasHandler (EventBus)
 src/plugins/plugin-api.js:
  L1  class  PluginAPI
  L7  method  init (PluginAPI)
  L12  method  activate (PluginAPI)
  L15  method  deactivate (PluginAPI)
  L18  method  getManifest (PluginAPI)
 src/plugins/plugin-context.js:
  L1  class  PluginContext
  L14  method  constructor (PluginContext)
  L23  method  register (PluginContext.constructor.commands)
  L24  function  safeHandler (PluginContext.constructor.commands.register)
  L65  method  registerPreHook (PluginContext.constructor.exports)
  L68  method  registerPostHook (PluginContext.constructor.exports)
 src/plugins/plugin-loader.js:
  L4  class  PluginLoader
  L8  method  constructor (PluginLoader)
  L17  method  discoverPlugins (PluginLoader)
  L66  method  validateManifest (PluginLoader)
 src/plugins/plugin-registry.js:
  L4  class  PluginRegistry
  L5  method  constructor (PluginRegistry)
  L15  method  register (PluginRegistry)
  L49  method  getPlugin (PluginRegistry)
  L53  method  getAll (PluginRegistry)
  L57  method  activate (PluginRegistry)
  L68  method  deactivate (PluginRegistry)
 src/plugins/settings-store.js:
  L1  class  SettingsStore
  L5  method  constructor (SettingsStore)
  L9  method  get (SettingsStore)
  L13  method  set (SettingsStore)
  L17  method  onChanged (SettingsStore)
 src/preload.js:
  L275  method  send (anonymousObject04f5e4370105)
  L289  method  invoke (anonymousObject04f5e4370105)
  L308  method  on (anonymousObject04f5e4370105)
  L310  function  subscription (anonymousObject04f5e4370105.on)
  L328  method  once (anonymousObject04f5e4370105)
  L340  method  removeAllListeners (anonymousObject04f5e4370105)
  L488  function  subscription
 src/renderer/hooks/use-export-source.ts:
  L4  interface  ExportSource
  L14  function  useExportSource
 src/renderer/hooks/use-file-shortcuts.ts:
  L15  function  useFileShortcuts
 src/renderer/hooks/use-menu-action.ts:
  L6  alias  Transform
  L17  function  useMenuAction
 src/renderer/hooks/use-restore-last-folder.ts:
  L9  function  useRestoreLastFolder
 src/renderer/hooks/use-scroll-sync.ts:
  L3  interface  Options
  L8  function  useScrollSync
 src/renderer/hooks/use-shortcut.ts:
  L20  function  useShortcut
  L44  interface  ComboSpec
  L53  function  parseCombo
  L71  function  matchCombo
 src/renderer/hooks/use-welcome-trigger.ts:
  L9  function  useWelcomeTrigger
 src/renderer/hooks/use-zen-mode.ts:
  L8  function  useZenMode
 src/renderer/hooks/useAutoUpdateCheck.ts:
  L5  function  useAutoUpdateCheck
 src/renderer/lib/ascii-table.ts:
  L5  function  toAsciiTable
  L36  function  applyAsciiTransform
 src/renderer/lib/commands/register-menu-commands.ts:
  L24  alias  HeadingItem
  L26  alias  OpenModal
  L28  function  confirmCloseFlow
  L45  function  registerMenuCommands
  L411  function  useRegisterMenuCommands
  L421  function  useBridgeNativeMenu
 src/renderer/lib/docx-export.ts:
  L4  interface  DocxOptions
  L10  function  generateDocx
 src/renderer/lib/editor-commands.ts:
  L18  function  setActiveView
  L22  function  getActiveView
  L27  function  wrap
  L57  function  setLineHeading
  L76  function  toggleLinePrefix
  L103  function  toggleBold
  L107  function  toggleItalic
  L111  function  toggleCode
  L115  function  toggleCodeBlock
  L143  function  toggleUnorderedList
  L147  function  toggleOrderedList
  L151  function  insertLink
  L167  function  setHeadingLevel
  L171  function  scrollToLine
  L185  function  undo
  L192  function  redo
  L199  function  selectCurrentLine
  L210  function  insertSnippet
 src/renderer/lib/figlet.ts:
  L13  alias  FigletFont
  L15  function  figletText
 src/renderer/lib/headings.ts:
  L1  interface  HeadingItem
  L13  function  extractHeadings
 src/renderer/lib/html-export.ts:
  L11  interface  HtmlExportOptions
  L101  function  generateHtml
  L125  function  escapeHtml
 src/renderer/lib/ipc.ts:
  L14  alias  ChannelMissing
  L16  function  wrap
 src/renderer/lib/markdown.ts:
  L11  function  renderMarkdown
 src/renderer/lib/migrations/v4-to-v5.ts:
  L16  function  isAlreadyV5
  L22  function  normalizeAlreadyV5
  L37  function  migrateV4ToV5
 src/renderer/lib/pdf-export.ts:
  L13  interface  PdfExportOptions
  L28  function  generatePdf
 src/renderer/lib/updater-store.ts:
  L4  alias  State
  L6  interface  UpdaterState
 src/renderer/lib/utils.ts:
  L1  alias  ClassValue
  L4  function  cn
 src/renderer/lib/validators.ts:
  L30  alias  Settings
  L38  alias  ExportPdfOptions
  L44  alias  ExportDocxOptions
  L51  alias  ExportHtmlOptions
  L58  alias  ExportBatchOptions
 src/renderer/lib/writing-analytics.ts:
  L115  function  countSyllables
  L122  function  extractWords
  L126  function  getReadabilityLabel
  L134  interface  WritingMetrics
  L151  function  analyzeText
 src/renderer/stores/app-store.ts:
  L4  interface  PaneSizes
  L10  interface  ConfirmProps
  L20  alias  ModalState
  L42  alias  ModalKind
  L44  interface  AppState
  L57  method  openModal (AppState)
 src/renderer/stores/command-store.ts:
  L4  alias  CommandId
  L6  alias  CommandHandler
  L13  alias  UserBindings
  L15  interface  CommandState
 src/renderer/stores/editor-store.ts:
  L7  interface  Buffer
  L15  interface  EditorState
 src/renderer/stores/file-store.ts:
  L12  interface  FileNode
  L21  interface  OpenTab
  L28  interface  FileState
  L50  function  entryToNode
  L60  function  updateNode
 src/renderer/stores/preview-store.ts:
  L3  interface  PreviewState
 src/renderer/stores/settings-store.ts:
  L3  alias  Settings
  L5  alias  Omit
  L5  alias  SettingsLeaf
  L7  interface  SettingsState
  L8  method  setSetting (SettingsState)
 src/renderer/test/setup.ts:
  L7  interface  Window
  L119  class  ResizeObserver
  L120  method  observe (ResizeObserver)
  L121  method  unobserve (ResizeObserver)
  L122  method  disconnect (ResizeObserver)
  L141  class  DOMMatrix
 src/renderer/types/electron.d.ts:
  L1  interface  ElectronAPI
  L134  interface  Window
 src/renderer/types/ipc.ts:
  L1  alias  IpcResult
  L5  interface  FileEntry
  L13  interface  FileResult
  L18  interface  PdfOptions
  L27  interface  DocxOptions
  L34  interface  HtmlOptions
  L41  interface  ExportResult
  L47  interface  BatchItem
  L52  interface  BatchOptions
  L57  interface  BatchResult
 src/repl/repl-panel.js:
  L1  class  ReplPanel
  L2  method  constructor (ReplPanel)
  L8  method  setupEventListeners (ReplPanel)
  L13  method  toggle (ReplPanel)
  L19  method  show (ReplPanel)
  L25  method  clear (ReplPanel)
  L29  method  appendOutput (ReplPanel)
  L42  method  escapeHtml (ReplPanel)
 src/sidebar/explorer-panel.js:
  L1  function  renderExplorerPanel
  L40  function  renderTree
  L79  function  getFileIcon
 src/sidebar/git-panel.js:
  L1  function  renderGitPanel
  L24  function  loadGitStatus (renderGitPanel)
 src/sidebar/outline-panel.js:
  L6  function  renderOutlinePanel
  L18  function  parseHeadings (renderOutlinePanel)
  L36  function  findActiveHeading (renderOutlinePanel)
  L48  function  renderHeadings (renderOutlinePanel)
  L89  function  escapeHtml (renderOutlinePanel)
  L95  function  refresh (renderOutlinePanel)
  L100  function  setActiveHeading (renderOutlinePanel)
 src/sidebar/sidebar-manager.js:
  L1  class  SidebarManager
  L2  method  constructor (SidebarManager)
  L11  method  setupEventListeners (SidebarManager)
  L20  method  registerPanel (SidebarManager)
  L24  method  togglePanel (SidebarManager)
  L32  method  expand (SidebarManager)
  L45  method  collapse (SidebarManager)
 src/sidebar/snippets-panel.js:
  L1  function  renderSnippetsPanel
  L14  function  loadSnippets (renderSnippetsPanel)
  L19  function  renderList (renderSnippetsPanel)
 src/sidebar/templates-panel.js:
  L18  function  renderTemplatesPanel
 src/utils/ModalManager.js:
  L5  class  ModalManager
  L16  method  constructor (ModalManager)
  L31  method  init (ModalManager)
  L47  method  setupCloseTriggers (ModalManager)
  L51  function  handler (ModalManager.setupCloseTriggers)
  L65  function  handler
  L74  method  getFocusableElements (ModalManager)
  L89  method  trapFocus (ModalManager)
  L111  method  handleKeydown (ModalManager)
  L119  method  open (ModalManager)
  L141  function  keydownHandler (ModalManager.open)
  L164  method  close (ModalManager)
  L182  function  addHidden (ModalManager.close)
  L188  function  onTransitionEnd (ModalManager.close)
  L223  method  isOpen (ModalManager)
  L227  method  destroy (ModalManager)
 tests/git-operations.test.js:
  L26  function  asyncFn
  L35  function  asyncFnWithError
 tests/main-utils.test.js:
  L7  function  sanitizeErrorMessage
  L49  function  createRateLimiter
  L51  function  canProceed (createRateLimiter)
 tests/markdown-extensions.test.js:
  L83  method  start (extension)
  L86  method  tokenizer (extension)
  L102  method  renderer (extension)
  L151  function  plantumlEncode
  L176  function  slugify
  L203  function  scopeCSS
 tests/modal-manager.test.js:
  L11  function  createModalElement
 tests/plugin-api.test.js:
  L18  class  MyPlugin
  L19  method  init (MyPlugin)
 tests/plugin-context.test.js:
  L39  function  badHandler
 tests/plugin-loader.test.js:
  L17  function  writeManifest
 tests/plugin-registry.test.js:
  L5  class  TestPlugin
  L6  method  init (TestPlugin)
  L10  method  activate (TestPlugin)
  L13  method  deactivate (TestPlugin)
  L69  class  BadPlugin
  L70  method  init (BadPlugin)
 tests/setup.js:
  L96  function  error (console)
 tests/sidebar.test.js:
  L41  method  render (anonymousObject7c2818c30105)
  L52  method  render (anonymousObject7c2818c30205)
  L62  method  render (anonymousObject7c2818c30305)
  L68  method  render (anonymousObject7c2818c30405)
  L80  method  render (anonymousObject7c2818c30505)
  L88  method  render (anonymousObject7c2818c30605)
  L96  method  render (anonymousObject7c2818c30705)
  L120  method  render (anonymousObject7c2818c30905)
  L130  method  render (anonymousObject7c2818c30a05)
 tests/unit/hooks/use-menu-action.test.ts:
  L6  alias  Cleanup
  L27  function  fireMenu
 tests/unit/main/updater/crash-writer.test.js:
  L6  function  tmpDir
 tests/unit/main/updater/migration-runner.test.js:
  L6  function  tmpDir
  L47  method  transform (anonymousObject196c14410c05)
  L63  method  transform (anonymousObject196c14410d05)
 tests/unit/stores/file-store.test.ts:
  L26  function  fakeFileEntry
 tests/utils.test.js:
  L9  function  parseCommand
  L78  function  hexToRgb
  L121  function  getExtension
  L133  function  replaceExtension
 ```
@@ -1,116 +0,0 @@
 # PanConverter Windows Explorer Context Menu Integration
 This directory contains scripts to add PanConverter to the Windows Explorer context menu, allowing you to right-click on files and convert them directly without opening the full application.
 ## Features
 ### Context Menu Options
 - **Convert with PanConverter**: Shows a format selection dialog for any supported file
 - **PanConverter > Convert to...**: Direct conversion options (for Markdown files)
  - PDF
  - HTML  
  - DOCX
  - LaTeX
  - PowerPoint
 ### Supported File Types
 - **Markdown**: `.md`, `.markdown`
 - **HTML**: `.html`, `.htm`
 - **Documents**: `.docx`, `.odt`, `.rtf`
 - **LaTeX**: `.tex`
 - **PDF**: `.pdf`
 - **Presentations**: `.pptx`, `.ppt`, `.odp`
 ## Installation Methods
 ### Method 1: Automatic (During PanConverter Installation)
 When installing PanConverter using the Windows installer, you'll be prompted to install context menu integration automatically.
 ### Method 2: Manual Installation
 #### Using PowerShell (Recommended)
 1. Right-click on `install-context-menu.ps1`
 2. Select "Run with PowerShell"
 3. Follow the prompts (will request administrator privileges)
 #### Using Batch File
 1. Right-click on `install-context-menu.bat`
 2. Select "Run as administrator"
 3. Follow the prompts
 #### Using Registry File Directly
 1. Right-click on `install-context-menu.reg`
 2. Select "Merge" 
 3. Confirm the registry modification
 ## Uninstallation
 ### Using PowerShell
 ```powershell
 .\install-context-menu.ps1 -Uninstall
 ```
 ### Using Batch File
 Run `uninstall-context-menu.bat` as administrator
 ### Using Registry File
 Run `uninstall-context-menu.reg`
 ## How It Works
 ### Command Line Interface
 The context menu integration works by passing command line arguments to PanConverter:
 - `--convert <file>`: Shows conversion dialog for the specified file
 - `--convert-to <format> <file>`: Directly converts to the specified format
 ### Examples
 ```batch
 # Show conversion dialog
 PanConverter.exe --convert "document.md"
 # Direct conversion to PDF
 PanConverter.exe --convert-to pdf "document.md"
 ```
 ### Conversion Process
 1. PanConverter reads the input file
 2. Creates a temporary file if needed
 3. Uses Pandoc to convert to the target format
 4. Saves the output in the same directory as the input file
 5. Shows a Windows notification when complete
 ## Requirements
 - PanConverter must be installed in the default location: `%LOCALAPPDATA%\Programs\PanConverter\`
 - Pandoc must be installed and accessible from the command line
 - Administrator privileges required for registry modifications
 ## Troubleshooting
 ### Context Menu Not Appearing
 1. Ensure you ran the installation script as administrator
 2. Try logging out and back in, or restart Windows Explorer
 3. Check if PanConverter is installed in the expected location
 ### Conversion Failures
 1. Verify Pandoc is installed: `pandoc --version`
 2. Check if the input file is not corrupted or locked
 3. Ensure you have write permissions in the output directory
 ### Permission Errors
 - The installation scripts require administrator privileges to modify the registry
 - If you get permission errors, right-click and "Run as administrator"
 ## File Descriptions
 - `install-context-menu.reg`: Registry entries for context menu
 - `uninstall-context-menu.reg`: Registry entries removal
 - `install-context-menu.ps1`: PowerShell installation script
 - `install-context-menu.bat`: Batch installation script  
 - `uninstall-context-menu.bat`: Batch uninstallation script
 - `nsis-installer.nsh`: NSIS installer integration script
 ## Security Note
 The scripts modify the Windows registry to add context menu entries. Only run these scripts if you trust the source and understand the changes being made to your system.
@@ -1,75 +0,0 @@
 /**
 * Build assets/icon.icns from the PNGs in assets/icons/.
 *
 * ICNS file format (Apple Icon Image):
 *   Header:  'icns' (4 bytes) + total file length (uint32 BE, includes header)
 *   For each size:
 *     Type tag (4 bytes) + length (uint32 BE, includes the 8-byte entry header) + PNG data
 *
 * Standard PNG type tags we'll include:
 *   icp4 = 16x16,    icp5 = 32x32,    icp6 = 64x64
 *   ic07 = 128x128,  ic08 = 256x256,  ic09 = 512x512,  ic10 = 1024x1024
 *   icsb = 48x48 (small)
 *   ic11 = 16x16@2x (32x32 retina),  ic12 = 32x32@2x (64x64 retina)
 *   ic13 = 128x128@2x (256x256 retina), ic14 = 256x256@2x (512x512 retina)
 */
 const fs = require('fs');
 const path = require('path');
 const iconsDir = path.join(__dirname, '..', 'assets', 'icons');
 const outFile = path.join(__dirname, '..', 'assets', 'icon.icns');
 // (size-in-pixels, icns type tag) — we skip sizes we don't have on disk
 const sizes = [
  { size: 16,  type: 'icp4' },
  { size: 32,  type: 'icp5' },
  { size: 64,  type: 'icp6' },
  { size: 128, type: 'ic07' },
  { size: 256, type: 'ic08' },
  { size: 512, type: 'ic09' },
  { size: 1024, type: 'ic10' },
  { size: 48,  type: 'icsb' },
  { size: 32,  type: 'ic11' }, // 16@2x
  { size: 64,  type: 'ic12' }, // 32@2x
  { size: 256, type: 'ic13' }, // 128@2x
  { size: 512, type: 'ic14' }, // 256@2x
 ];
 const entries = [];
 for (const { size, type } of sizes) {
  const pngPath = path.join(iconsDir, `${size}x${size}.png`);
  if (!fs.existsSync(pngPath)) continue;
  const png = fs.readFileSync(pngPath);
  // ICNS requires 8-byte alignment per entry. paddedLen is the TOTAL entry size
  // (8-byte type+length header + PNG + padding), rounded up to a multiple of 8.
  const paddedLen = 8 + Math.ceil(png.length / 8) * 8;
  entries.push({ type, png, paddedLen });
  console.log(`  ${type} (${size}x${size}) — ${png.length} bytes`);
 }
 if (entries.length === 0) {
  console.error('No source PNGs found in', iconsDir);
  process.exit(1);
 }
 const totalLen = 8 + entries.reduce((s, e) => s + e.paddedLen, 0);
 const buf = Buffer.alloc(totalLen);
 let off = 0;
 // Header
 buf.write('icns', off, 4, 'ascii'); off += 4;
 buf.writeUInt32BE(totalLen, off); off += 4;
 // Entries
 for (const { type, png, paddedLen } of entries) {
  buf.write(type, off, 4, 'ascii'); off += 4;
  buf.writeUInt32BE(paddedLen, off); off += 4;
  png.copy(buf, off);
  off += png.length;
  // Pad to 8-byte boundary within the entry. paddedLen already includes the 8-byte header.
  const pad = paddedLen - 8 - png.length;
  if (pad > 0) off += pad;
 }
 fs.writeFileSync(outFile, buf);
 console.log(`\nWrote ${outFile} (${buf.length} bytes, ${entries.length} sizes)`);
@@ -1,59 +0,0 @@
 # create-selfsigned-cert.ps1
 # Generates a self-signed code-signing certificate for local/development builds.
 #
 # Usage:
 #   powershell -ExecutionPolicy Bypass -File scripts/create-selfsigned-cert.ps1
 #   npm run create-cert
 #
 # Then build with:
 #   $env:CSC_LINK="code-signing-cert.pfx"; $env:CSC_KEY_PASSWORD="YourPassword"; npm run build:win-signed
 #
 # NOTE: Self-signed certificates will still show a SmartScreen warning for end users.
 # For production releases, obtain an OV or EV certificate from a trusted CA
 # (DigiCert, Sectigo, Certum, etc.). EV certificates bypass SmartScreen immediately.
 # Open-source projects can apply for free signing at https://signpath.io/
 param(
    [string]$CertPassword = "MarkdownConverter2025",
    [string]$OutputFile   = "code-signing-cert.pfx",
    [string]$Subject      = "CN=ConcreteInfo, O=ConcreteInfo, L=India, C=IN"
 )
 Write-Host "Creating self-signed code-signing certificate..." -ForegroundColor Cyan
 # Create the certificate in the current user's certificate store
 $cert = New-SelfSignedCertificate `
    -Type CodeSigningCert `
    -Subject $Subject `
    -CertStoreLocation "Cert:\CurrentUser\My" `
    -NotAfter (Get-Date).AddYears(3) `
    -HashAlgorithm SHA256 `
    -KeyLength 4096 `
    -KeyUsage DigitalSignature
 if (-not $cert) {
    Write-Error "Failed to create certificate."
    exit 1
 }
 Write-Host "Certificate created: $($cert.Thumbprint)" -ForegroundColor Green
 # Export to PFX
 $securePassword = ConvertTo-SecureString -String $CertPassword -Force -AsPlainText
 $exportPath = Join-Path (Get-Location) $OutputFile
 Export-PfxCertificate -Cert $cert -FilePath $exportPath -Password $securePassword | Out-Null
 if (Test-Path $exportPath) {
    Write-Host "Certificate exported to: $exportPath" -ForegroundColor Green
    Write-Host ""
    Write-Host "To build a signed release:" -ForegroundColor Yellow
    Write-Host '  $env:CSC_LINK="code-signing-cert.pfx"' -ForegroundColor White
    Write-Host "  `$env:CSC_KEY_PASSWORD=`"$CertPassword`"" -ForegroundColor White
    Write-Host "  npm run build:win-signed" -ForegroundColor White
    Write-Host ""
    Write-Host "IMPORTANT: Add code-signing-cert.pfx to .gitignore!" -ForegroundColor Red
 } else {
    Write-Error "Export failed."
    exit 1
 }
@@ -1,215 +0,0 @@
 #!/usr/bin/env node
 /**
 * Downloads pandoc binary for the current build platform.
 * Run automatically via `npm run download-tools` before building.
 * Skips download if binary already exists (idempotent).
 */
 const https = require('https');
 const http = require('http');
 const fs = require('fs');
 const path = require('path');
 const os = require('os');
 const { execSync } = require('child_process');
 const PANDOC_VERSION = '3.9.0.2';
 /**
 * Pandoc's archive inner layout has shifted across releases and platforms:
 *   linux  tarball: pandoc-3.9.0.2/bin/pandoc
 *   win32  zip:     pandoc-3.9.0.2/pandoc.exe
 *   darwin zip:     pandoc-3.9.0.2-x86_64/bin/pandoc   (arch-suffixed inner dir)
 *                   pandoc-3.9.0.2-arm64/bin/pandoc    (on Apple Silicon builds)
 * Rather than hard-coding the intermediate path — which has already broken
 * once when pandoc 3.9 added the arch suffix to the macOS archive — we walk
 * the extracted tree and find the binary by name. This is robust to future
 * layout shifts (e.g., universal binaries renaming the inner dir).
 */
 function findFile(rootDir, targetName) {
  const entries = fs.readdirSync(rootDir, { withFileTypes: true });
  for (const entry of entries) {
    const full = path.join(rootDir, entry.name);
    if (entry.isFile() && entry.name === targetName) return full;
    if (entry.isDirectory()) {
      const found = findFile(full, targetName);
      if (found) return found;
    }
  }
  return null;
 }
 const PANDOC_CONFIG = {
  linux: {
    url: `https://github.com/jgm/pandoc/releases/download/${PANDOC_VERSION}/pandoc-${PANDOC_VERSION}-linux-amd64.tar.gz`,
    archiveExt: '.tar.gz',
    destFile: 'pandoc',
    extract(archivePath, destDir) {
      const tmpDir = path.join(os.tmpdir(), `pandoc-${Date.now()}`);
      fs.mkdirSync(tmpDir, { recursive: true });
      execSync(`tar -xzf "${archivePath}" -C "${tmpDir}"`);
      const src = findFile(tmpDir, 'pandoc');
      if (!src) throw new Error(`pandoc binary not found under ${tmpDir}`);
      fs.copyFileSync(src, path.join(destDir, 'pandoc'));
      fs.chmodSync(path.join(destDir, 'pandoc'), 0o755);
      fs.rmSync(tmpDir, { recursive: true, force: true });
    },
  },
  win32: {
    url: `https://github.com/jgm/pandoc/releases/download/${PANDOC_VERSION}/pandoc-${PANDOC_VERSION}-windows-x86_64.zip`,
    archiveExt: '.zip',
    destFile: 'pandoc.exe',
    extract(archivePath, destDir) {
      const tmpDir = path.join(os.tmpdir(), `pandoc-${Date.now()}`);
      fs.mkdirSync(tmpDir, { recursive: true });
      execSync(
        `powershell -Command "Expand-Archive -Force '${archivePath}' '${tmpDir}'"`,
      );
      const src = findFile(tmpDir, 'pandoc.exe');
      if (!src) throw new Error(`pandoc.exe not found under ${tmpDir}`);
      fs.copyFileSync(src, path.join(destDir, 'pandoc.exe'));
      fs.rmSync(tmpDir, { recursive: true, force: true });
    },
  },
  darwin: {
    url: `https://github.com/jgm/pandoc/releases/download/${PANDOC_VERSION}/pandoc-${PANDOC_VERSION}-x86_64-macOS.zip`,
    archiveExt: '.zip',
    destFile: 'pandoc',
    extract(archivePath, destDir) {
      const tmpDir = path.join(os.tmpdir(), `pandoc-${Date.now()}`);
      fs.mkdirSync(tmpDir, { recursive: true });
      execSync(`unzip -o "${archivePath}" -d "${tmpDir}"`);
      const src = findFile(tmpDir, 'pandoc');
      if (!src) throw new Error(`pandoc binary not found under ${tmpDir}`);
      fs.copyFileSync(src, path.join(destDir, 'pandoc'));
      fs.chmodSync(path.join(destDir, 'pandoc'), 0o755);
      fs.rmSync(tmpDir, { recursive: true, force: true });
    },
  },
 };
 function download(url, destPath) {
  return new Promise((resolve, reject) => {
    const file = fs.createWriteStream(destPath);
    let received = 0;
    let total = 0;
    let lastPct = -1;
    function get(redirectUrl) {
      const client = redirectUrl.startsWith('https://') ? https : http;
      client
        .get(redirectUrl, (res) => {
          if (res.statusCode === 301 || res.statusCode === 302) {
            get(res.headers.location);
            return;
          }
          if (res.statusCode !== 200) {
            reject(new Error(`HTTP ${res.statusCode} for ${redirectUrl}`));
            return;
          }
          total = parseInt(res.headers['content-length'] || '0', 10);
          res.on('data', (chunk) => {
            received += chunk.length;
            if (total > 0) {
              const pct = Math.floor((received / total) * 100);
              if (pct !== lastPct && pct % 10 === 0) {
                process.stdout.write(`  ${pct}%\r`);
                lastPct = pct;
              }
            }
          });
          res.pipe(file);
          file.on('finish', () => {
            file.close();
            process.stdout.write('  100%\n');
            resolve();
          });
        })
        .on('error', (err) => {
          fs.unlink(destPath, () => {});
          reject(err);
        });
    }
    get(url);
  });
 }
 async function downloadPandoc() {
  const platform = process.platform;
  const config = PANDOC_CONFIG[platform];
  if (!config) {
    console.log(`[download-tools] No pandoc config for platform "${platform}" — skipping.`);
    return;
  }
  const destDir = path.join(__dirname, '..', 'bin', platform);
  const destFile = path.join(destDir, config.destFile);
  if (fs.existsSync(destFile)) {
    console.log(`[download-tools] pandoc already present at ${destFile} — skipping.`);
    return;
  }
  fs.mkdirSync(destDir, { recursive: true });
  const tmpArchive = path.join(os.tmpdir(), `pandoc-download${config.archiveExt}`);
  console.log(`[download-tools] Downloading pandoc ${PANDOC_VERSION} for ${platform}...`);
  await download(config.url, tmpArchive);
  console.log(`[download-tools] Extracting to ${destDir}...`);
  config.extract(tmpArchive, destDir);
  try {
    fs.unlinkSync(tmpArchive);
  } catch (_) {
    /* ignore */
  }
  console.log(`[download-tools] pandoc ready: ${destFile}`);
 }
 async function downloadFiraCode() {
  const targetDir = path.resolve(__dirname, '..', 'assets', 'fonts');
  fs.mkdirSync(targetDir, { recursive: true });
  // Pinned to an immutable release tag with explicit SHA-256 digests so the
  // build fails loudly on any upstream tampering or accidental change.
  // Update the version + digests together when bumping Fira Code.
  const FIRA_CODE_VERSION = '6.2';
  const baseUrl = `https://github.com/tonsky/FiraCode/releases/download/${FIRA_CODE_VERSION}`;
  const files = [
    { url: `${baseUrl}/FiraCode-Regular.ttf`, out: 'FiraCode-Regular.ttf', sha256: '3c79d234a9161c790410ebb2a80de7efb7c15f581062c130e0fa78503ccdd0da' },
    { url: `${baseUrl}/FiraCode-Bold.ttf`, out: 'FiraCode-Bold.ttf', sha256: '975f26779fac1029c2cbdac1e9fac7e9ddeec05e064675e4aac63bffa121742f' },
    { url: `${baseUrl}/FiraCode-LICENSE.txt`, out: 'FiraCode-LICENSE.txt', sha256: null },
  ];
  for (const f of files) {
    const dest = path.join(targetDir, f.out);
    if (fs.existsSync(dest)) {
      console.log(`[download-tools] Fira Code asset already present at ${dest} — skipping.`);
      continue;
    }
    if (!f.sha256 || !/^[a-f0-9]{64}$/i.test(f.sha256)) {
      throw new Error(
        `[download-tools] Refusing to download ${f.url}: SHA-256 digest not pinned. ` +
          'Update scripts/download-tools.js with the digest from the official Fira Code release before building.'
      );
    }
    const tmp = `${dest}.tmp`;
    console.log(`[download-tools] Downloading ${f.url}...`);
    await download(f.url, tmp);
    const actual = require('crypto').createHash('sha256').update(fs.readFileSync(tmp)).digest('hex');
    if (actual !== f.sha256) {
      fs.unlinkSync(tmp);
      throw new Error(
        `[download-tools] SHA-256 mismatch for ${f.url}: expected ${f.sha256}, got ${actual}`
      );
    }
    fs.renameSync(tmp, dest);
  }
  console.log('[download-tools] Fira Code ready');
 }
 Promise.all([downloadPandoc(), downloadFiraCode()]).catch((err) => {
  console.error('[download-tools] FAILED:', err.message);
  process.exit(1);
 });
@@ -1,82 +0,0 @@
 /**
 * Icon Generator for MarkdownConverter
 * Generates all required icon sizes from NewIcon.jpg
 */
 const sharp = require('sharp');
 const fs = require('fs');
 const path = require('path');
 // Source image
 const sourceImage = path.join(__dirname, '..', 'assets', 'docico1.png');
 const assetsDir = path.join(__dirname, '..', 'assets');
 // Icon sizes needed for different platforms
 const iconSizes = [16, 24, 32, 48, 64, 128, 256, 512, 1024];
 async function generateIcons() {
  console.log('Generating icons from docico1.png...');
  // Check if source exists
  if (!fs.existsSync(sourceImage)) {
    console.error('Source image not found:', sourceImage);
    process.exit(1);
  }
  try {
    // Generate main icon.png (512x512)
    await sharp(sourceImage)
      .resize(512, 512, { fit: 'contain', background: { r: 255, g: 255, b: 255, alpha: 0 } })
      .png()
      .toFile(path.join(assetsDir, 'icon.png'));
    console.log('Generated icon.png (512x512)');
    // Generate icon@2x.png (1024x1024)
    await sharp(sourceImage)
      .resize(1024, 1024, { fit: 'contain', background: { r: 255, g: 255, b: 255, alpha: 0 } })
      .png()
      .toFile(path.join(assetsDir, 'icon@2x.png'));
    console.log('Generated icon@2x.png (1024x1024)');
    // Create icons directory for multi-size icons
    const iconsDir = path.join(assetsDir, 'icons');
    if (!fs.existsSync(iconsDir)) {
      fs.mkdirSync(iconsDir, { recursive: true });
    }
    // Generate all sizes
    for (const size of iconSizes) {
      await sharp(sourceImage)
        .resize(size, size, { fit: 'contain', background: { r: 255, g: 255, b: 255, alpha: 0 } })
        .png()
        .toFile(path.join(iconsDir, `${size}x${size}.png`));
      console.log(`Generated icons/${size}x${size}.png`);
    }
    // Generate favicon
    await sharp(sourceImage)
      .resize(32, 32, { fit: 'contain', background: { r: 255, g: 255, b: 255, alpha: 0 } })
      .png()
      .toFile(path.join(assetsDir, 'favicon.png'));
    console.log('Generated favicon.png (32x32)');
    // Generate tray icon (smaller, for system tray)
    await sharp(sourceImage)
      .resize(24, 24, { fit: 'contain', background: { r: 255, g: 255, b: 255, alpha: 0 } })
      .png()
      .toFile(path.join(assetsDir, 'tray-icon.png'));
    console.log('Generated tray-icon.png (24x24)');
    console.log('\nIcon generation complete!');
    console.log('\nFor Windows .ico file, use an online converter or:');
    console.log('  magick convert assets/icons/*.png assets/icon.ico');
    console.log('\nFor macOS .icns file, use:');
    console.log('  iconutil -c icns assets/icon.iconset -o assets/icon.icns');
  } catch (error) {
    console.error('Error generating icons:', error);
    process.exit(1);
  }
 }
 generateIcons();
@@ -1,48 +0,0 @@
@echo off
 echo PanConverter Context Menu Installation
 echo =====================================
 echo.
 REM Check for administrator privileges
 net session >nul 2>&1
 if %errorLevel% == 0 (
    echo Running with administrator privileges...
 ) else (
    echo This script requires administrator privileges.
    echo Please right-click and select "Run as administrator"
    echo.
    pause
    exit /b 1
 )
 REM Check if PanConverter is installed
 if not exist "%LOCALAPPDATA%\Programs\PanConverter\PanConverter.exe" (
    echo Warning: PanConverter not found at the expected location.
    echo Please ensure PanConverter is installed before continuing.
    echo Expected location: %LOCALAPPDATA%\Programs\PanConverter\PanConverter.exe
    echo.
    set /p continue="Continue anyway? (y/N): "
    if /i not "%continue%"=="y" exit /b 1
 )
 echo Installing context menu entries...
 reg import "%~dp0install-context-menu.reg"
 if %errorLevel% == 0 (
    echo.
    echo Context menu integration installed successfully!
    echo.
    echo You can now right-click on supported files and select:
    echo • "Convert with PanConverter" - Shows conversion dialog  
    echo • "PanConverter > Convert to..." - Direct conversion ^(for Markdown^)
    echo.
    echo Supported file types:
    echo .md .markdown .html .htm .docx .odt .rtf .tex .pdf .pptx .ppt .odp
 ) else (
    echo.
    echo Failed to install context menu entries.
    echo Please check that the registry file exists and try again.
 )
 echo.
 pause
@@ -1,67 +0,0 @@
 # PanConverter Context Menu Installation Script
 # This script installs PanConverter context menu integration for Windows Explorer
 param(
    [switch]$Uninstall = $false
 )
 # Check if running as administrator
 if (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
    Write-Host "This script requires Administrator privileges. Restarting with elevated permissions..." -ForegroundColor Yellow
    Start-Process PowerShell -Verb RunAs "-File `"$PSCommandPath`" $(if ($Uninstall) { '-Uninstall' })"
    exit
 }
 $scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
 $appPath = "${env:LOCALAPPDATA}\Programs\PanConverter\PanConverter.exe"
 if ($Uninstall) {
    Write-Host "Uninstalling PanConverter context menu integration..." -ForegroundColor Yellow
    $regFile = Join-Path $scriptDir "uninstall-context-menu.reg"
    if (Test-Path $regFile) {
        reg import $regFile
        if ($LASTEXITCODE -eq 0) {
            Write-Host "PanConverter context menu has been successfully removed!" -ForegroundColor Green
        } else {
            Write-Host "Failed to remove context menu entries." -ForegroundColor Red
        }
    } else {
        Write-Host "Uninstall registry file not found: $regFile" -ForegroundColor Red
    }
 } else {
    Write-Host "Installing PanConverter context menu integration..." -ForegroundColor Yellow
    # Check if PanConverter is installed
    if (-not (Test-Path $appPath)) {
        Write-Host "Warning: PanConverter executable not found at: $appPath" -ForegroundColor Yellow
        Write-Host "Please make sure PanConverter is installed before running this script." -ForegroundColor Yellow
        $continue = Read-Host "Continue anyway? (y/N)"
        if ($continue -ne 'y' -and $continue -ne 'Y') {
            exit
        }
    }
    $regFile = Join-Path $scriptDir "install-context-menu.reg"
    if (Test-Path $regFile) {
        reg import $regFile
        if ($LASTEXITCODE -eq 0) {
            Write-Host "PanConverter context menu has been successfully installed!" -ForegroundColor Green
            Write-Host "" 
            Write-Host "You can now right-click on supported files (MD, HTML, DOCX, PDF, etc.) and select:" -ForegroundColor Cyan
            Write-Host "• 'Convert with PanConverter' - Shows conversion dialog" -ForegroundColor Cyan
            Write-Host "• 'PanConverter > Convert to...' - Direct conversion options (for Markdown files)" -ForegroundColor Cyan
            Write-Host ""
            Write-Host "Supported file types: .md, .markdown, .html, .htm, .docx, .odt, .rtf, .tex, .pdf, .pptx, .ppt, .odp" -ForegroundColor Gray
        } else {
            Write-Host "Failed to install context menu entries." -ForegroundColor Red
        }
    } else {
        Write-Host "Install registry file not found: $regFile" -ForegroundColor Red
    }
 }
 Write-Host ""
 Write-Host "Press any key to exit..."
 $null = $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
@@ -1,134 +0,0 @@
 Windows Registry Editor Version 5.00
 ; PanConverter Context Menu Integration
 ; This registry file adds context menu options for converting files using PanConverter
 ; Add context menu for Markdown files (.md, .markdown)
 [HKEY_CLASSES_ROOT\.md\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 [HKEY_CLASSES_ROOT\.markdown\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.markdown\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for HTML files
 [HKEY_CLASSES_ROOT\.html\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.html\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 [HKEY_CLASSES_ROOT\.htm\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.htm\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for DOCX files
 [HKEY_CLASSES_ROOT\.docx\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.docx\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for ODT files
 [HKEY_CLASSES_ROOT\.odt\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.odt\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for RTF files
 [HKEY_CLASSES_ROOT\.rtf\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.rtf\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for LaTeX files
 [HKEY_CLASSES_ROOT\.tex\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.tex\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for PDF files
 [HKEY_CLASSES_ROOT\.pdf\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.pdf\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for PowerPoint files
 [HKEY_CLASSES_ROOT\.pptx\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.pptx\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 [HKEY_CLASSES_ROOT\.ppt\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.ppt\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add context menu for OpenDocument Presentation files
 [HKEY_CLASSES_ROOT\.odp\shell\PanConverter]
@="Convert with PanConverter"
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 [HKEY_CLASSES_ROOT\.odp\shell\PanConverter\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert \"%1\""
 ; Add submenu with specific conversion options for Markdown files
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu]
@="PanConverter"
 "MUIVerb"="Convert to..."
 "Icon"="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\""
 "SubCommands"=""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\PDF]
@="PDF"
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\PDF\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert-to pdf \"%1\""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\HTML]
@="HTML"
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\HTML\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert-to html \"%1\""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\DOCX]
@="DOCX"
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\DOCX\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert-to docx \"%1\""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\LaTeX]
@="LaTeX"
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\LaTeX\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert-to latex \"%1\""
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\PPTX]
@="PowerPoint"
 [HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu\shell\PPTX\command]
@="\"%LOCALAPPDATA%\\Programs\\PanConverter\\PanConverter.exe\" --convert-to pptx \"%1\""
@@ -1,145 +0,0 @@
 ; PanConverter NSIS Installer Include File
 ; Handles context menu installation and uninstallation
 !include "LogicLib.nsh"
 !include "MUI2.nsh"
 ; Custom installation page for context menu option
 Var ContextMenuCheckbox
 Var ContextMenuState
 Function ContextMenuPage
    !insertmacro MUI_HEADER_TEXT "Additional Options" "Choose additional installation options"
    nsDialogs::Create 1018
    Pop $0
    ${If} $0 == error
        Abort
    ${EndIf}
    ${NSD_CreateLabel} 0 0 100% 20u "Select additional features to install:"
    Pop $0
    ${NSD_CreateCheckbox} 20u 30u 280u 15u "Add PanConverter to Windows Explorer context menu"
    Pop $ContextMenuCheckbox
    ${NSD_SetState} $ContextMenuCheckbox ${BST_CHECKED}
    ${NSD_CreateLabel} 20u 50u 280u 30u "This will allow you to right-click on supported files and convert them directly using PanConverter."
    Pop $0
    nsDialogs::Show
 FunctionEnd
 Function ContextMenuPageLeave
    ${NSD_GetState} $ContextMenuCheckbox $ContextMenuState
 FunctionEnd
 ; Install context menu entries
 Function InstallContextMenu
    ${If} $ContextMenuState == ${BST_CHECKED}
        DetailPrint "Installing context menu integration..."
        ; Create registry entries for context menu
        WriteRegStr HKCR ".md\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".md\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".md\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        WriteRegStr HKCR ".markdown\shell\PanConverter" "" "Convert with PanConverter"  
        WriteRegStr HKCR ".markdown\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".markdown\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for HTML files
        WriteRegStr HKCR ".html\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".html\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".html\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        WriteRegStr HKCR ".htm\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".htm\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".htm\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for DOCX files
        WriteRegStr HKCR ".docx\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".docx\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".docx\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for ODT files
        WriteRegStr HKCR ".odt\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".odt\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".odt\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for RTF files
        WriteRegStr HKCR ".rtf\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".rtf\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".rtf\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for LaTeX files
        WriteRegStr HKCR ".tex\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".tex\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".tex\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for PDF files
        WriteRegStr HKCR ".pdf\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".pdf\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".pdf\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for PowerPoint files
        WriteRegStr HKCR ".pptx\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".pptx\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".pptx\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        WriteRegStr HKCR ".ppt\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".ppt\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".ppt\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Context menu for ODP files
        WriteRegStr HKCR ".odp\shell\PanConverter" "" "Convert with PanConverter"
        WriteRegStr HKCR ".odp\shell\PanConverter" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".odp\shell\PanConverter\command" "" '"$INSTDIR\PanConverter.exe" --convert "%1"'
        ; Submenu for Markdown files with direct conversion options
        WriteRegStr HKCR ".md\shell\PanConverterMenu" "" "PanConverter"
        WriteRegStr HKCR ".md\shell\PanConverterMenu" "MUIVerb" "Convert to..."
        WriteRegStr HKCR ".md\shell\PanConverterMenu" "Icon" "$INSTDIR\PanConverter.exe"
        WriteRegStr HKCR ".md\shell\PanConverterMenu" "SubCommands" ""
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\PDF" "" "PDF"
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\PDF\command" "" '"$INSTDIR\PanConverter.exe" --convert-to pdf "%1"'
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\HTML" "" "HTML"
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\HTML\command" "" '"$INSTDIR\PanConverter.exe" --convert-to html "%1"'
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\DOCX" "" "DOCX"
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\DOCX\command" "" '"$INSTDIR\PanConverter.exe" --convert-to docx "%1"'
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\LaTeX" "" "LaTeX"
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\LaTeX\command" "" '"$INSTDIR\PanConverter.exe" --convert-to latex "%1"'
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\PPTX" "" "PowerPoint"
        WriteRegStr HKCR ".md\shell\PanConverterMenu\shell\PPTX\command" "" '"$INSTDIR\PanConverter.exe" --convert-to pptx "%1"'
        DetailPrint "Context menu integration installed successfully!"
    ${EndIf}
 FunctionEnd
 ; Uninstall context menu entries
 Function un.RemoveContextMenu
    DetailPrint "Removing context menu integration..."
    ; Remove context menu entries for all file types
    DeleteRegKey HKCR ".md\shell\PanConverter"
    DeleteRegKey HKCR ".md\shell\PanConverterMenu"
    DeleteRegKey HKCR ".markdown\shell\PanConverter"
    DeleteRegKey HKCR ".html\shell\PanConverter"
    DeleteRegKey HKCR ".htm\shell\PanConverter"
    DeleteRegKey HKCR ".docx\shell\PanConverter"
    DeleteRegKey HKCR ".odt\shell\PanConverter"
    DeleteRegKey HKCR ".rtf\shell\PanConverter"
    DeleteRegKey HKCR ".tex\shell\PanConverter"
    DeleteRegKey HKCR ".pdf\shell\PanConverter"
    DeleteRegKey HKCR ".pptx\shell\PanConverter"
    DeleteRegKey HKCR ".ppt\shell\PanConverter"
    DeleteRegKey HKCR ".odp\shell\PanConverter"
    DetailPrint "Context menu integration removed successfully!"
 FunctionEnd
@@ -1,49 +0,0 @@
 #!/usr/bin/env node
 const fs = require('fs');
 const path = require('path');
 const version = process.argv[2] || require('../package.json').version;
 const hook = process.env.CONCRETEINFO_DEPLOY_HOOK;
 if (!hook) {
  console.error('CONCRETEINFO_DEPLOY_HOOK not set');
  process.exit(1);
 }
 const candidates = [
  'latest-mac.yml',
  'latest-linux.yml',
  'latest-windows.yml',
  `MarkdownConverter-${version}.dmg`,
  `markdown-converter_${version}_amd64.deb`,
  `MarkdownConverter-Setup-${version}.exe`,
 ];
 const dist = path.resolve(__dirname, '..', 'dist');
 for (const f of candidates) {
  if (!fs.existsSync(path.join(dist, f))) {
    console.error(`missing ${f} — run electron-builder first`);
    process.exit(1);
  }
 }
 const form = new FormData();
 form.append('version', version);
 for (const f of candidates) {
  if (fs.existsSync(path.join(dist, f))) {
    form.append('artifacts', fs.createReadStream(path.join(dist, f)), f);
  }
 }
 fetch('https://updates.concreteinfo.co.in/api/v1/ingest', {
  method: 'POST',
  headers: { Authorization: `Bearer ${hook}` },
  body: form,
 })
  .then((r) => {
    console.log('ingest status', r.status);
    process.exit(r.ok ? 0 : 1);
  })
  .catch((e) => {
    console.error('ingest failed:', e);
    process.exit(1);
  });
@@ -1,32 +0,0 @@
@echo off
 echo PanConverter Context Menu Uninstallation
 echo ========================================
 echo.
 REM Check for administrator privileges
 net session >nul 2>&1
 if %errorLevel% == 0 (
    echo Running with administrator privileges...
 ) else (
    echo This script requires administrator privileges.
    echo Please right-click and select "Run as administrator"
    echo.
    pause
    exit /b 1
 )
 echo Removing context menu entries...
 reg import "%~dp0uninstall-context-menu.reg"
 if %errorLevel% == 0 (
    echo.
    echo Context menu integration removed successfully!
    echo PanConverter entries have been removed from the Windows Explorer context menu.
 ) else (
    echo.
    echo Failed to remove context menu entries.
    echo Please check that the registry file exists and try again.
 )
 echo.
 pause
@@ -1,36 +0,0 @@
 Windows Registry Editor Version 5.00
 ; PanConverter Context Menu Uninstall Script
 ; This registry file removes PanConverter context menu entries
 ; Remove context menu for Markdown files (.md, .markdown)
 [-HKEY_CLASSES_ROOT\.md\shell\PanConverter]
 [-HKEY_CLASSES_ROOT\.md\shell\PanConverterMenu]
 [-HKEY_CLASSES_ROOT\.markdown\shell\PanConverter]
 ; Remove context menu for HTML files
 [-HKEY_CLASSES_ROOT\.html\shell\PanConverter]
 [-HKEY_CLASSES_ROOT\.htm\shell\PanConverter]
 ; Remove context menu for DOCX files
 [-HKEY_CLASSES_ROOT\.docx\shell\PanConverter]
 ; Remove context menu for ODT files
 [-HKEY_CLASSES_ROOT\.odt\shell\PanConverter]
 ; Remove context menu for RTF files
 [-HKEY_CLASSES_ROOT\.rtf\shell\PanConverter]
 ; Remove context menu for LaTeX files
 [-HKEY_CLASSES_ROOT\.tex\shell\PanConverter]
 ; Remove context menu for PDF files
 [-HKEY_CLASSES_ROOT\.pdf\shell\PanConverter]
 ; Remove context menu for PowerPoint files
 [-HKEY_CLASSES_ROOT\.pptx\shell\PanConverter]
 [-HKEY_CLASSES_ROOT\.ppt\shell\PanConverter]
 ; Remove context menu for OpenDocument Presentation files
 [-HKEY_CLASSES_ROOT\.odp\shell\PanConverter]
@@ -1,148 +0,0 @@
 import { _electron as electron } from 'playwright-core';
 import * as fs from 'node:fs';
 import * as path from 'node:path';
 const APP_DIR = '/home/amith/apps/markdown-converter';
 const electronBin = path.join(APP_DIR, 'node_modules/electron/dist/electron');
 const testMd = '/tmp/verify-test.md';
 const outputDocx = '/tmp/verify-output.docx';
 const outputHtml = '/tmp/verify-output.html';
 // Cleanup previous outputs
 if (fs.existsSync(testMd)) fs.unlinkSync(testMd);
 if (fs.existsSync(outputDocx)) fs.unlinkSync(outputDocx);
 if (fs.existsSync(outputHtml)) fs.unlinkSync(outputHtml);
 // Write test Markdown file
 fs.writeFileSync(
  testMd,
  '# Test Document\n\nThis is a verification test for opening and exporting.\n\n- Point A\n- Point B\n'
 );
 console.log('Launching Electron...');
 const app = await electron.launch({
  executablePath: electronBin,
  args: [
    '--no-sandbox',
    '--disable-gpu',
    '--disable-software-rasterizer',
    '--disable-dev-shm-usage',
    '.',
  ],
  env: {
    ...process.env,
    DISPLAY: ':0',
    ELECTRON_DISABLE_SANDBOX: '1',
    VITE_DEV_SERVER_URL: 'http://localhost:5173',
  },
  cwd: APP_DIR,
 });
 app.process().stdout.on('data', (data) => console.log('[MAIN-OUT]', data.toString().trim()));
 app.process().stderr.on('data', (data) => console.log('[MAIN-ERR]', data.toString().trim()));
 const win = await app.firstWindow();
 await win.waitForLoadState('domcontentloaded');
 await win.waitForSelector('.cm-editor, [role="toolbar"]', { timeout: 10000 });
 console.log('App loaded.');
 // Dismiss welcome wizard if present
 const wizardCount = await win.locator('[data-testid="first-run-wizard"]').count();
 if (wizardCount > 0) {
  console.log('Dismissing first run wizard...');
  await win.click('[data-testid="first-run-wizard"] >> text=Skip');
  await new Promise((r) => setTimeout(r, 300));
 }
 // Stub dialog.showSaveDialogSync in main process to automatically return output paths
 await app.evaluate(({ dialog }, { outputDocx, outputHtml }) => {
  dialog.showSaveDialogSync = (window, options) => {
    const filters = options?.filters || [];
    if (filters.some(f => f.extensions.includes('docx'))) {
      return outputDocx;
    }
    return outputHtml;
  };
 }, { outputDocx, outputHtml });
 // Simulate opening the test Md file by sending IPC from main
 console.log('Opening test markdown file...');
 const fileContent = fs.readFileSync(testMd, 'utf-8');
 await app.evaluate(({ BrowserWindow }, { filePath, content }) => {
  const wins = BrowserWindow.getAllWindows();
  const main = wins.find((w) => !w.isDestroyed());
  if (!main) throw new Error('No main window');
  main.webContents.send('file-opened', { path: filePath, content });
 }, { filePath: testMd, content: fileContent });
 // Wait for editor to display the content
 await win.waitForFunction(
  (content) => {
    const editor = document.querySelector('.cm-content');
    return editor && editor.textContent.includes('Test Document');
  },
  fileContent,
  { timeout: 5000 }
 );
 console.log('File successfully opened in editor.');
 // Let's wait a moment for currentFile synchronization to trigger in the main process
 await new Promise((r) => setTimeout(r, 500));
 // Trigger DOCX Export (calls performExportWithOptions under the hood)
 console.log('Exporting to DOCX...');
 await win.evaluate(() => {
  window.electronAPI.export.withOptions('docx', {});
 });
 // Wait for file to be written to disk
 let docxExported = false;
 for (let i = 0; i < 20; i++) {
  if (fs.existsSync(outputDocx) && fs.statSync(outputDocx).size > 0) {
    docxExported = true;
    break;
  }
  await new Promise((r) => setTimeout(r, 250));
 }
 if (docxExported) {
  console.log('✅ DOCX exported successfully.');
 } else {
  console.error('❌ DOCX export failed (file not created or empty).');
 }
 // Wait 2.5 seconds to bypass the conversion rate limiter (2000ms debounce)
 console.log('Waiting for rate limiter...');
 await new Promise((r) => setTimeout(r, 2500));
 // Trigger HTML Export
 console.log('Exporting to HTML...');
 await win.evaluate(() => {
  window.electronAPI.export.withOptions('html', {});
 });
 let htmlExported = false;
 for (let i = 0; i < 20; i++) {
  if (fs.existsSync(outputHtml) && fs.statSync(outputHtml).size > 0) {
    htmlExported = true;
    break;
  }
  await new Promise((r) => setTimeout(r, 250));
 }
 if (htmlExported) {
  console.log('✅ HTML exported successfully.');
 } else {
  console.error('❌ HTML export failed (file not created or empty).');
 }
 await app.close();
 console.log('Verification completed.');
 if (docxExported && htmlExported) {
  process.exit(0);
 } else {
  process.exit(1);
 }
--- a/Show More
+++ b/Show More