Restructure student tracks by cross-reference chains, add project rules

Student tracks restructured based on document cross-reference analysis:
- Track 1 "Gemalen & CRC Keten": Grace→Kevin→Robin→Adriaan (chain)
- Track 2 "Condition Monitoring": Kevin→Yamai (fork from Track 1)
- Track 3 "Zuivering & Beluchting": Noa‖Elise (parallel, same problem)
- Track 4 "EVOLV Reactor Model": Pieter (standalone, no student cross-refs)
- Track 5 "IoT & ICT Infra": Bart→Fontys ICT→Fontys TOGAF (chain)

Inter-student dependencies added (7 new):
- Grace→Kevin, Kevin→Robin, Robin→Adriaan (Track 1 chain)
- Kevin→Yamai (Track 2 fork)
- Bart→Fontys ICT→Fontys TOGAF (Track 5 chain)

CLAUDE.md: Added "Metro Map Data Rules" section documenting:
- Thema=line, Project=station, speerpunt=track grouping
- Student work rules: cross-references determine track sharing
- Identified chains with evidence (reference counts from source docs)
- Grid alignment requirements

MetroCanvas: Truncate long station labels to prevent overlap (max ~20 chars
based on grid spacing, with ellipsis)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -59,6 +59,37 @@ The project wiki lives in `wiki/` and follows the wiki-template schema. It is th
 
 **After making significant changes:** update relevant wiki pages, `knowledge-graph.yaml`, and `wiki/log.md`.
 
+## Metro Map Data Rules
+
+The metro map is the primary navigation and knowledge structure. These rules govern how content maps to the visual metro metaphor.
+
+### Thema = Metro Line (Dim 1)
+Each thema is a horizontal metro line at the strategy level. Keep themas to major organizational concerns:
+- **R&D Planning 2026** themes (Architectuur, Productiewaardig, Lab, Governance)
+- **Onderzoek** — all research work (R&D-driven and student)
+
+### Project = Station (Dim 1)
+Each project is a station on its thema's line. Stations are zoomable into Dim 2.
+
+### Student Work Rules
+Student projects live under the **Onderzoek** thema. Structure:
+1. **Each student gets their own track (metro line) within the Onderzoek thema** — unless they build on another student's work
+2. **Students who build on each other share a track** — chronological stations on the same line, earlier work first
+3. **Cross-references determine track grouping**, not topic similarity. Evidence: explicit mentions of another student's work, reuse of their system/data, or continuation of their project
+4. **Identified chains** (from cross-reference analysis of source documents):
+   - **Gemalen & CRC track**: Grace van Geel (pump curves) → Kevin Haest (CRC/IOT2050, references Grace) → Robin van Weelie (D.R.A.I.N., references CRC) → Adriaan Sol (pilot 3, references D.R.A.I.N.)
+   - **Monitoring branch** (forks from Kevin): Kevin Haest → Yamai van Rooij (CRC 78x, MCSA, references Kevin)
+   - **Zuivering track**: Noa de Groot (beluchting) ‖ Elise Nouws (algen, parallel approach to same problem)
+   - **EVOLV Reactor**: Pieter van der Wilt (standalone — EVOLV ASM model, no student cross-refs)
+   - **IoT & Infra track**: Bart van Gool (IoT-hub) → Fontys ICT (Docker/CI-CD/SOC) → Fontys TOGAF (security)
+5. **Dependencies to 2026 projects** are tracked as `Afhankelijkheid` records (type: technisch/data/infrastructuur)
+
+### Kennis Artikelen
+Standalone knowledge articles extracted from research. Not tied to a project lifecycle. Used by the AI/search engine for semantic retrieval.
+
+### Grid Alignment
+All node positions must be multiples of GRID=50. Server-side: `MapDataService::snapToGrid()`. Client-side: `gridConstants.js`.
+
 ## What Requires Human Validation
 - Architecture decisions
 - Domain model changes