Cubase-MCP-GAJ3T.MusicGen.R.../prompts/step_15_fix.md

45 lines
2.7 KiB
Markdown

# Step 15 fix: Resolve impossible D2 fixture; complete hybrid implementation
## Authoritative correction after report review
The orchestrator read report_15.md in full and independently confirmed the
physical contradiction: MIDI38 and42 each require AME string6. The requirement
for simultaneous native D2-major [38,42,45] was an ERROR IN THE WORKER PROMPT,
not a reason to abandon hybrid notation or the user's actual E2 phrase.
No change to tuning, native validation or user-explicit pitch is authorized.
Apply these surgical overrides to step_15.md:
1. The CANONICAL NATIVE chord example uses D3, not D2:
Chords: F#2 F#2 D3 D3 Bb2 Bb2 - - -
Its two D-major pitch sets are [50,54,57]; other attacks/times unchanged.
All21 tones now have real physical string assignments. Require source AND
installed native/MIDI acceptance with fallback=false for THIS example.
2. Retain the old explicit D2 example as a NEGATIVE NATIVE / POSITIVE MIDI
exactness test: allowed fallback preserves every [38,42,45] pitch; disabled
fallback errors before publishing. Do not transpose, drop or call that native.
3. Original user's E2-only two-measure phrase remains required unchanged and
fully native-capable. The final prompt primarily uses this original phrase.
4. Restore/implement the complete Step15 hybrid parser and tests under this
correction. A single unplayable chord cannot block generic notation. Do not
remove working public parser code/tests merely because a negative native
test demonstrates expected fallback.
All OTHER Step15 requirements remain: actual public prose+lanes, reusable
count math, o/x/^/-/~, explicit notes/octaves/major-minor/add4/slash bass/voicings,
visible interpretation, correct rests/holds, ambiguity/conflict errors, slides
reserved with guidance, no key retuning, no timing from spacing width and no
factory/user-app changes. Preserve old0.1.1 outputs and strict/privacy/atomic/CC
behaviors. No commits/delegation/later prompts/version changes here.
Read report14/15/current foundation and execute step15 under the corrected
acceptance above. Rebuild no release until Step16. Run new focused tests,
full current suite, Ruff lint/format, strict mypy/pip and installed acceptance.
When complete, write your end-of-step report to ./prompts/report_15_fix.md including: what was implemented, test results (pass/fail with details), any issues encountered, and whether you're ready for the next step
One plain triple-backtick fence for the entire report. Preserve original
report15 as history, not a current unsupported-parser claim. Include actual
playable D3 chord/native tests, honest D2 fallback, original E2 exactness, grammar/
interpretation and Step16 readiness. Do not create the next prompt.