Add THE CANONICAL 100: Complete Lucidia language definition through examples

This commit introduces the foundational specification for Lucidia v1.0 - a set
of 100 working example programs that DEFINE the language through demonstration
rather than formal grammar.

Key Philosophy:
- Examples ARE the spec (not documentation OF the spec)
- AI systems learn by reading all 100 examples and extracting patterns
- Humans learn by working through examples sequentially
- No feature exists unless demonstrated in these examples

Structure:
- 001-010: Fundamentals (hello world → functions)
- 011-020: Data & Collections (lists, maps, sets)
- 021-030: Control Flow (if, loops, pattern matching)
- 031-040: Functions & Composition (map, filter, reduce, closures)
- 041-050: UI Basics (forms, inputs, validation)
- 051-060: Reactive Programming (state, watchers, events)
- 061-070: Consent & Privacy (permission system - CORE DIFFERENTIATOR)
- 071-080: Storage & Sync (local-first, cloud-optional)
- 081-090: AI Integration (intent → code, learning user style)
- 091-100: Complete Applications (todo, notes, chat, e-commerce)

Core Language Features Demonstrated:
✓ Intent over ceremony (write WHAT, not HOW)
✓ Consent as syntax (ask permission for: resource)
✓ Local-first storage (store locally, sync to cloud optional)
✓ AI-collaborative (### Intent comments become code)
✓ Reactive by default (state, watch, computed)
✓ Zero setup (runs in browser via WASM)
✓ Multi-paradigm (functional, OOP, reactive, agent-based)
✓ Gradual complexity (hello world → production apps)

Files Created:
- README.md - Learning philosophy and path
- INDEX.md - Complete reference table
- 001-100.lucidia - All example programs

Total: 102 files, ~3,500+ lines of example code

Why This Matters:
This is not just documentation. This IS Lucidia. Every parser, compiler,
AI assistant, and developer tool will be trained on these examples. They
are the permanent, immutable foundation of the language.

Next Steps:
1. Build parser that learns from these examples
2. Train AI to recognize and generate Lucidia patterns
3. Create browser playground with these as gallery
4. Use for academic paper and conference presentations

Designed by: Cece (Principal Language & Runtime Architect)
For: BlackRoad Operating System / Lucidia Programming Language
Status: Complete foundation for implementation

docs/examples/canonical/080-storage-encryption.lucidia

@@ -0,0 +1,62 @@
+# 080: Storage Encryption
+# Encrypt sensitive data before storing
+
+# Encrypt by default
+sensitive_data = {
+  password: "secret123",
+  api_key: "sk_live_xxxx",
+  ssn: "123-45-6789"
+}
+
+store sensitive_data locally as "credentials"
+  encrypt: true
+  # Uses device key or user-provided password
+
+# Encrypted storage is automatic for sensitive field names
+# (password, ssn, credit_card, api_key, etc.)
+
+# User-provided encryption key
+save_encrypted_diary(entry):
+  ask "Enter encryption password:" -> password
+    type: "password"
+
+  store entry locally as "diary/{entry.id}"
+    encrypt: true
+    key: password
+
+  show "Diary entry saved (encrypted)"
+
+# Load encrypted data
+load_encrypted_diary(entry_id):
+  ask "Enter encryption password:" -> password
+    type: "password"
+
+  entry = load "diary/{entry_id}" locally
+    decrypt: true
+    key: password
+
+  if entry == null:
+    show "Wrong password or entry doesn't exist"
+  else:
+    show entry.text
+
+# Automatic encryption for regulated data
+store_medical_record(record):
+  # Medical data automatically encrypted (HIPAA compliance)
+  store record locally as "medical_records/{record.id}"
+  # encryption: true is implicit for medical data
+
+# Sync encrypted
+sync_encrypted_data():
+  # Data synced to cloud remains encrypted
+  # Cloud never sees unencrypted data
+  encrypted_notes = load "private_notes" locally
+    encrypt: true
+
+  sync encrypted_notes to cloud
+    # Still encrypted in transit and at rest
+
+  show "Private notes synced (encrypted)"
+
+# Everything sensitive is encrypted by default
+# Lucidia assumes privacy, not surveillance