CRITICAL USER EXPERIENCE DISASTER: Build system complexity creates insurmountable barriers for new users

[krystophny]

Build system generates cryptic hash-based directory structures that make manual compilation impossible for users.

BRUTAL USER IMPACT:

• Advanced users cannot figure out compilation without extensive trial and error
• Students/researchers abandon library due to build complexity
• No documentation explains hash-based build directory structure
• Professional adoption blocked by unusable build experience

BUILD COMPLEXITY EVIDENCE:

• Modules in: build/gfortran_1FD0EBF408CEEB1F/
• Libraries in: build/gfortran_27353C317BE38399/fortplot/
• Users must guess different hash directories for includes vs libraries
• Hash values change unpredictably making instructions obsolete

WORKFLOW FAILURE PATTERN:

1. User runs 'make build' (succeeds)
2. User attempts standard compilation patterns (fails)
3. User explores build/ directory (confused by hashes)
4. User abandons library (cannot compile basic examples)

COMPARISON WITH SUCCESSFUL LIBRARIES:

• Most Fortran libraries: build/lib/, build/include/
• FortPlot: build/gfortran_RANDOMHASH1/, build/gfortran_RANDOMHASH2/fortplot/

SOLUTION REQUIRED:
Provide standard library/include directory structure or comprehensive compilation guide

[krystophny]

Consolidated into Sprint #2 Issues #979 and #980 - Build system and documentation system recovery