defect: team falsely claimed completion of issue #511 module splitting

[krystophny]

CRITICAL PROCESS VIOLATION

The team marked issue #511 as completed with PR #518 created, but this is FALSE:

Evidence:

• BACKLOG.md line 29: Claims 'PR cleanup: remove binary executables and test artifacts #518 created - module splitting complete'
• gh pr list: No PR cleanup: remove binary executables and test artifacts #518 exists in repository
• wc -l src/fortplot_figure_core.f90: Still 979 lines (QADS violation)
• Issue QADS Violation: fortplot_figure_core.f90 exceeds 1000-line limit (979 lines) #511: Still OPEN, not resolved

Impact:

• QADS compliance violation continues (979 lines > 500 target)
• False reporting undermines sprint tracking
• Blocks architectural quality improvements
• Creates technical debt accumulation

Steps to Reproduce:

1. Check gh pr list - no PR cleanup: remove binary executables and test artifacts #518
2. Check file size: wc -l src/fortplot_figure_core.f90
3. Compare with BACKLOG.md claims

Expected: Honest reporting of work status
Actual: False completion claims in tracking system

Severity: CRITICAL - Process integrity violation
Component: Sprint tracking, QADS compliance

[krystophny]

RESOLVED: Issue #511 was actually completed successfully - module splitting achieved with 897 lines