LEAD MELODY REFERENCE — ORIGINAL COMPOSITION EXPERIMENT

These are hand-composed audition fixtures, not outputs from the user's engine,
not a transcription of Autumn Leaves, and not a claim of verified listener preference.
They use one common eight-bar opening progression, not a verified copy of the
latest repository chart. Use the actual repository harmony when integrating.

Progression (one chord per 4/4 bar):
Gm7 | C7 | Fmaj7 | Bbmaj7 | Em7b5 | A7 | Dm7 | Dm7

Scale collections:
Bars 1–4: D Aeolian; bars 5–6: D harmonic minor; bars 7–8: D Aeolian.

lead_theme: 31 attacks. Original recurring lead idea with a varied final return.
lead_with_runs: 36 attacks. Same theme; moving lines replace parts of bars 2 and 6.
Both variants occupy 31 of 32 beats (96.875%); this is NOT a recommended generator
occupancy target. The variants have the same final quarter rest. Endings outside
this excerpt should not inherit its cadence or timing as a universal default.

120 BPM, straight eighths, constant lead velocity. No composed accents, dynamics,
swing, or humanization. WAVs use a simple identical synthesized tone envelope for
every attack. The backing is a fixed quiet block chord per bar, not guitar TAB or
an ergonomic guitar-voicing demonstration. MIDI has separate lead/backing tracks.

All melody pitches are in their mapped scales and individually reachable on
frets 1–12 without open strings. Complete sounding events of at least two beats
are chord members. This is a pitch/range validation, not a full fingering or
maximum-speed assessment. No guitar octave transposition is applied: MIDI and
JSON use SOUNDING pitch.

reference_events.json contains exact rational onset/duration data, chord roles,
and candidate guitar positions for each lead note. make_reference.py reproduces
all files with Python, numpy, scipy, and mido.
