chore: prepare repository for open source release

Add README, MIT and Apache 2.0 licenses, update .gitignore to exclude
build artifacts and unused FreeRouting versions. Include new example
files, planning docs, and pending source changes.

Author: FlightCore Dev

.gitignore

@@ -25,3 +25,15 @@ crates/cypcb-parser/grammar/package-lock.json
 
 # Local cargo config (machine-specific)
 .cargo/config.toml
+
+# Unused FreeRouting versions
+freerouting-1.9.0.jar
+freerouting-2.0.1.jar
+
+# Compiled Rust artifacts (loose files outside /target)
+*.rlib
+*.o
+
+# Runtime artifacts
+logs/
+export-test/

.planning/debug/parser-current-syntax.md

@@ -0,0 +1,74 @@
+---
+status: diagnosed
+trigger: "Diagnose why the parser rejects `current 500mA` syntax in net blocks"
+created: 2026-01-22T00:00:00Z
+updated: 2026-01-22T00:02:00Z
+symptoms_prefilled: true
+goal: find_root_cause_only
+---
+
+## Current Focus
+
+hypothesis: CONFIRMED - Syntax mismatch between user expectation and grammar design
+test: Verified with both syntaxes
+expecting: N/A - Root cause found
+next_action: Report findings
+
+## Symptoms
+
+expected: Parser accepts `current 500mA` syntax inside net blocks
+actual: Parser returns "Syntax error: unexpected token: 'current 500mA'"
+errors: "Syntax error: unexpected token: 'current 500mA'"
+reproduction: Add `current 500mA` inside a net definition block
+started: Unknown - 05-01-SUMMARY claims it was implemented
+
+## Eliminated
+
+## Evidence
+
+- timestamp: 2026-01-22T00:01:00Z
+  checked: grammar.js lines 150-171 (net_definition and net_constraint_block)
+  found: |
+    Net constraints use square bracket syntax BEFORE the braces:
+    - net_definition: seq('net', name, optional(net_constraint_block), '{', pin_ref_list, '}')
+    - net_constraint_block: seq('[', repeat(net_constraint), ']')
+    - current_constraint rule EXISTS at lines 186-189
+
+    Expected syntax: net VCC [current 500mA] { ... }
+    User's syntax:   net VCC { ... current 500mA }
+  implication: User is placing constraint inside braces; grammar only accepts constraints in square brackets before braces
+
+- timestamp: 2026-01-22T00:02:00Z
+  checked: Ran parser test with both syntaxes
+  found: |
+    User syntax (inside braces): FAILS with "unexpected token: 'current 500mA'"
+    Correct syntax (square brackets): PASSES
+  implication: Confirms grammar design, not a bug - documentation/syntax mismatch
+
+## Resolution
+
+root_cause: |
+  NOT A BUG - SYNTAX MISMATCH
+
+  The grammar is implemented correctly. The `current` constraint IS supported,
+  but it must appear in square brackets BEFORE the net body braces, not inside them.
+
+  Grammar design (grammar.js lines 150-158):
+    net_definition: seq('net', name, optional(net_constraint_block), '{', pin_ref_list, '}')
+
+  CORRECT SYNTAX:
+    net VCC [current 500mA] {
+        R1.1
+        C1.1
+    }
+
+  INCORRECT (user's attempt):
+    net VCC {
+        R1.1
+        C1.1
+        current 500mA   // ERROR - constraints go in [ ] before braces
+    }
+
+fix: N/A - This is a documentation issue, not a code bug
+verification: N/A
+files_changed: []

.planning/phases/03-validation/03-09-SUMMARY.md

@@ -0,0 +1,67 @@
+---
+phase: 03-validation
+plan: 09
+status: complete
+completed: 2026-01-22
+---
+
+# Summary: 03-09 Visual Verification Checkpoint
+
+## What Was Verified
+
+Human verification of complete DRC system working end-to-end.
+
+## Verification Results
+
+### DRC Detection
+- **Clearance violations:** Detected - "Clearance violation: 0.00mm actual, 0.15mm required"
+- **Unconnected pins:** Detected - All unconnected pins reported (R1.1, R1.2, R2.1, R2.2, etc.)
+- **Multiple violation types:** Working correctly
+
+### Visual Display
+- **Error badge:** Shows in status bar with violation count
+- **Error panel:** Lists all violations with [kind] message format
+- **Markers:** Red ring markers visible at violation locations
+
+### Hot Reload
+- **File watch:** Working - changes trigger re-render
+- **DRC update:** Violations recalculated on reload
+- **Example tested:** blink.cypcb (12 violations), drc-test.cypcb (clearance + unconnected)
+
+## Test Files Used
+
+- `examples/blink.cypcb` - 12 unconnected-pin violations (3 components, 8-pin IC)
+- `examples/drc-test.cypcb` - Intentional clearance violation between R1/R2
+
+## Console Output Verified
+
+```
+WASM module loaded successfully
+Loaded snapshot: {board: {...}, components: Array(3), nets: Array(0), violations: Array(12)}
+[HotReload] WebSocket connected
+[HotReload] Reloaded snapshot
+```
+
+## Issues Found & Fixed During Phase
+
+- **DRC WASM empty violations:** Fixed in commit 9252017
+  - Root cause: `WasmPcbEngineAdapter.get_snapshot()` returned cached JS snapshot instead of WASM engine result
+  - Fix: Changed to return `this.wasmEngine.get_snapshot()`
+
+## Phase 3 Completion Status
+
+All 10 plans complete:
+- 03-01: DRC crate setup ✓
+- 03-02: IC footprints ✓
+- 03-03: Manufacturer presets ✓
+- 03-04: Custom footprint DSL ✓
+- 03-05: Clearance checking ✓
+- 03-06: Drill/trace/connectivity rules ✓
+- 03-07: DRC integration ✓
+- 03-08: Violation display ✓
+- 03-09: Visual verification ✓
+- 03-10: Zones and keepouts ✓
+
+## Next Phase
+
+Phase 4: Export - Gerber X2, Excellon drill, BOM generation

.planning/phases/12-tauri-desktop-foundation/12-05-PLAN.md

@@ -2,8 +2,8 @@
 phase: 12-tauri-desktop-foundation
 plan: 05
 type: execute
-wave: 1
-depends_on: []
+wave: 4
+depends_on: ['12-03']
 files_modified: [viewer/src/main.ts]
 autonomous: true
 gap_closure: true
@@ -60,8 +60,8 @@ Add these 5 event listeners:
 1. **desktop:open-file** - Receives `{ path: string, content: string }` in event.detail.
    - Call `engine.load_source(detail.content)` to parse the content
    - Update `snapshot = engine.get_snapshot()`
-   - If snapshot.board exists, call `fitBoard()` and update viewport/interactionState.viewport
-   - Update error badge via `updateErrorBadge(snapshot.violations || [])`
+   - Update error badge via `updateErrorBadge(snapshot.violations || [])` (AFTER snapshot is assigned)
+   - If snapshot.board exists, call `viewport = fitBoard(viewport, snapshot.board.width_nm, snapshot.board.height_nm)` and update `interactionState.viewport = viewport`
    - Set `currentFilePath = detail.path` (the local variable, for routing)
    - Update statusText with filename (extract from path using split)
    - Set `dirty = true`
@@ -79,18 +79,18 @@ Add these 5 event listeners:
 
 3. **desktop:viewport** - Receives `{ action: 'zoom-in' | 'zoom-out' | 'fit' }` in event.detail.
    - For 'zoom-in': multiply viewport.scale by 1.5, update viewport and interactionState.viewport, set dirty = true
-   - For 'zoom-out': multiply viewport.scale by (1/1.5), update viewport and interactionState.viewport, set dirty = true
+   - For 'zoom-out': divide viewport.scale by 1.5 (i.e., multiply by 0.6667), update viewport and interactionState.viewport, set dirty = true
    - For 'fit': if snapshot?.board exists, call `fitBoard(viewport, snapshot.board.width_nm, snapshot.board.height_nm)`, update viewport and interactionState.viewport, set dirty = true
 
 4. **desktop:toggle-theme** - No detail payload.
-   - Cycle theme exactly like the themeToggle click handler: get current from themeManager.getTheme(), compute next (light->dark->auto->light), call themeManager.setTheme(next), call updateThemeIcon().
+   - Cycle theme exactly like the themeToggle click handler: get current from themeManager.getTheme(), compute next (light->dark->auto->light), call themeManager.setTheme(next), call updateThemeIcon() (the existing function defined at ~line 244 in main.ts, accessible within init() scope).
 
 5. **desktop:new-file** - No detail payload.
    - Call `engine.load_source('')` to clear
    - Update `snapshot = engine.get_snapshot()`
    - Set `currentFilePath = null`
    - Set `lastLoadedSource = null`
-   - Set statusText to 'Ready (WASM) - Open a file' or 'Ready (Mock) - Open a file'
+   - Set statusText using the existing `usingWasm` variable: `statusText = usingWasm ? 'Ready (WASM) - Open a file' : 'Ready (Mock) - Open a file'`
    - Set `dirty = true`
 
 Also add `let lastLoadedSource: string | null = null;` near the top of init() alongside the other state variables.
@@ -112,7 +112,7 @@ All 5 desktop custom events (open-file, content-request, viewport, toggle-theme,
 
 <verification>
 1. `grep -c "desktop:" viewer/src/main.ts` returns at least 5 (one per event type)
-2. `grep "lastLoadedSource" viewer/src/main.ts` shows the variable is set in reload, handleFileLoad, and desktop:open-file handler
+2. `grep -n "lastLoadedSource\s*=" viewer/src/main.ts` shows assignments in at least 4 locations: declaration, reload() (~line 483), handleFileLoad() (~line 317), and desktop:open-file handler
 3. `cd viewer && npx tsc --noEmit` passes
 </verification>