Architecture: Audit and catalog all duplicated theme definitions between curses-java and curses-themes

[sfloess]

Part of #233: Architecture: Unify curses-java and curses-themes with shared implementation

Scope

Create a comprehensive audit of what is duplicated between curses-java (Java) and curses-themes (Python) to establish the exact scope of unification work.

Tasks

• List all themes in curses-java with their source files
• List all themes in curses-themes with their source files
• For each theme, document: name, border chars, color definitions, shadow/highlight/lowlight values, 3D rendering parameters
• Identify rendering logic that is duplicated (e.g., draw_box_3d() ~125 lines)
• Identify rendering logic that differs between implementations
• Document the Theme3D interface in both languages side by side
• Quantify: lines of pure data vs lines of rendering logic

Deliverable

A comparison document (or issue comment) showing exactly what can be extracted as shared data vs what remains as language-specific rendering.

Acceptance Criteria

• All 11+ themes cataloged with their properties
• Data vs logic split clearly quantified
• Any differences between Java and Python implementations identified