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

20 KiB

Step 13 — COMPLETE: 0.1.1 LM Studio recovery / precise-riff patch acceptance
Date: 2026-10-20

RESULT
PASS: authoritative version 0.1.1, refreshed editable application metadata,
final wheel/sdist, EXACT persisted-wheel stdio acceptance outside checkout,
text-only recovery, original phrase/native/MIDI verification, full checks.
Ready for the orchestrator's final user-file-generation request after review.
The Step13 worker created no user-facing output. Final orchestrator acceptance
is recorded below. No unresolved implementation blocker.
Live LM Studio/model/UI and plugin/Cubase/audio acceptance remain UNRUN.

PATH DEFINITIONS
R = D:\_Repos\Code\GAJ3T\MCPs\MusicGen\GAJ3T.MusicGen.Riff-Groove-Builder
A = D:\_Repos\Code\GAJ3T\MCPs\MusicGen\GAJ3T.MusicGen.Riff-Groove-Builder\.test-artifacts\lmstudio-fix-0.1.1
All R\ and A\ references below expand to these exact absolute Windows paths.
Outside-checkout launch/independent-verifier cwd:
  D:\_Repos\Code\GAJ3T\MCPs\MusicGen
Interpreter: R\.venv\Scripts\python.exe
Report: R\prompts\report_13.md

IMPLEMENTED
- Only src\riff_groove_builder\__init__.py authors the package version: 0.1.1.
  pyproject.toml continues deriving setuptools metadata from that attribute.
  Runtime MCP initialization uses that same source. Tests now require 0.1.1
  package/metadata agreement and assert real source/wheel handshake versions.
- Refreshed ONLY the editable application, offline:
    python -m pip install --disable-pip-version-check --no-cache-dir --no-index
      --no-deps --no-build-isolation -e .
  Existing 0.1.0 application metadata was replaced with 0.1.1; runtime/dev
  dependencies were NOT reinstalled. No dependency manifest/ranges changed.
  No global install, dependency restore, new tool or dependency was required.
- Distribution tests accept RIFF_RELEASE_DIST for an exact already-persisted
  pair under R\dist, without rebuilding/substituting another wheel. Normal
  unset-variable behavior still builds its own offline wheel from its sdist.
  Installation remains noneditable, no-index/no-deps/no-cache-dir.
- Retained current source/wheel original phrase and simple-recovery evidence
  under the new version-specific A path, not by replacing Step12 evidence.
  Original phrase acceptance now sends ONLY description and basename.
  Nearby/error cases additionally exercise allow_midi_fallback=false.
  Numeric event assertions remain independent of the composing code; original
  phrase hashes are also pinned to independently recorded Step12 baselines.
- README now documents LM Studio mcpServers, not VS Code servers/type,
  absolute Python/args, required already-existing output root, actual suffixes,
  exact verbatim minimal original JSON, defaults, grammar/interpretation limits,
  no invented profiles/CC91, and restart plus fresh-chat remediation.
  Updated current compatibility documentation; old reports remain history.
  Official configuration reference checked:
    https://lmstudio.ai/docs/app/mcp
  All seven README JSON blocks parse and pass their executable checks:
  one LM Studio config, four tool requests, two output payloads.
  Requests pass actual JSON schemas, typed resolution, mapping and compilation.
  LM Studio config is checked separately as launch configuration, not falsely
  passed to the generate_music schema or claimed as a live-client test.

FINAL DISTRIBUTIONS — DO NOT CONFUSE WITH OLD 0.1.0 ARTIFACTS
Wheel:
  D:\_Repos\Code\GAJ3T\MCPs\MusicGen\GAJ3T.MusicGen.Riff-Groove-Builder\dist\lmstudio-fix-20261020\gaj3t_musicgen_riff_groove_builder-0.1.1-py3-none-any.whl
  82175 bytes
  SHA256 1d72dce98c775f958288049fde008e4d2bb4bab12bf858bf53f8b0231781b540
Sdist:
  D:\_Repos\Code\GAJ3T\MCPs\MusicGen\GAJ3T.MusicGen.Riff-Groove-Builder\dist\lmstudio-fix-20261020\gaj3t_musicgen_riff_groove_builder-0.1.1.tar.gz
  97774 bytes
  SHA256 04ec8bda391d7170b69c7bbd6309f68277d8081f98f6c44cba953a229d7258ae

Built offline using existing tools:
  python -I -B -m build --no-isolation --outdir dist\lmstudio-fix-20261020
The default build produced the wheel FROM the sdist, not just directly from
the checkout. A\build.txt records the successful final build.
Independent audit: wheel26 entries, sdist31 files, six production JSON profiles.
Every packaged source/profile byte matches current source; README/pyproject
in the sdist match current files. Other members are packaging metadata only.
No private template, chat, kit/song, factory music, licensed manual, audio,
generated MIDI/native output, venv, test artifact or report is packaged.

EXACT PERSISTED-WHEEL ACCEPTANCE
The full final pytest run set:
  RIFF_RELEASE_DIST=R\dist\lmstudio-fix-20261020
Thus both isolated wheel imports and the real server test installed the exact
wheel path/hash above; no alternate generated wheel satisfied these checks.
Wheel SHA256 was checked unchanged after the real server run and independently.
Evidence: A\installed-wheel\distribution-acceptance.json

- Fresh separate venv imports verified package file, metadata version 0.1.1,
  silent import and no server/MCP import side effects, outside the checkout.
- Real installed server reused existing dev-venv dependencies but loaded ALL
  16 package/module entry locations and all six resources from its noneditable
  install target, not R\src or the editable package.
  Launch used -I -B with cwd D:\_Repos\Code\GAJ3T\MCPs\MusicGen.
  This is not a fresh full dependency-installation certification.
- Actual newline-delimited JSON-RPC initialize negotiated 2025-11-25, named
  riff-groove-builder/version0.1.1; tools/list returned exactly
  list_instrument_profiles and generate_music with actual input/output schemas.
- Text-only decisions used json.loads(content[0].text), including readable
  profile IDs and safe field/reason/correction messages. For success and all
  exercised domain/validation failures, exactly one complete TextContent JSON
  equals structuredContent and passes the actual output schema.
- Wrong lead sd3p/mid request returned INVALID_REQUEST / formats / format_parts
  with explicit guitar-vs-drum format correction. No files were published.
  Removing wrong formats and unsolicited CC91 exposed PROFILE_REQUIRED with
  safe list-profiles/default guidance, no echoed invented profile value.
  Arbitrary unsupported triplet prose returned UNSUPPORTED_DESCRIPTION.
  Selecting the visible real AME ID and key Em recovered to complete
  mid+griff; key normalized to E minor, no fallback, four musical notes and
  one keyswitch, zero CC91. Old simple-output hashes remain exact.
- Source recovery also used a real independently launched stdio child,
  version0.1.1, six valid stdout messages, exit0, empty stderr.
  Source original phrase: five valid stdout messages, exit0, empty stderr.
  Source transport records:
    A\source\text-transport.json
    A\source\phrase-transport.json
- Installed no-template/main process: 20 valid protocol stdout messages, exit0;
  intentionally malformed-protocol privacy case emits only its expected
  sanitized SDK diagnostic, never private input. Uninitialized EOF also exits0.
  Installed native/CC/original-phrase process: 23 valid stdout messages,
  exit0, EMPTY stderr. It also exercised original-template native sets,
  aliases/actual suffixes, MIDI-only, exact CC, fallback and no-overwrite.
  Temporary install/venv/output workspaces were cleaned after acceptance.
  JSON origins/paths under distribution-70726b2645ec41ed921c5400fc9331db describe
  that completed transient run, not currently retained installations.

VERBATIM ORIGINAL PHRASE — NO CORRECTIVE MUSICAL OVERRIDES
Description sent exactly, with these line breaks:
Please produce a 4/4 riff in Em. With Chugging palm muting 8th notes from 1 to 3&;
and triplets on 4&A with the A as a pinch harmonic that carries over a whole note
in the 2nd measure.

Only other argument: basename="phrase-original".
No explicit parts, format, profile, key, tempo, bars or CC. Automatic result:
complete; lead only; default ample.ame.4.0.1.riffer.v1; E minor; two bars;
120 quarter-note BPM; mid+griff; no fallback/drum file/control/program event.

Both source and installed-wheel original files persist:
  A\source\phrase-original\phrase-original.mid
  A\source\phrase-original\phrase-original_lead.griff
  A\installed-wheel\phrase-original\phrase-original.mid
  A\installed-wheel\phrase-original\phrase-original_lead.griff
Each directory also contains independently checked evidence.json.

Source and installed bytes are IDENTICAL, and unchanged from Step12:
  phrase-original.mid — 168 bytes
  SHA256 c1967e698a50b8c22a22e458c3e2dd02d04407d1ad1d61f8a462d790b0810e62
  phrase-original_lead.griff — 1701 bytes
  SHA256 e8195e74c60ac93b1a4c92967a0834a64b2a2ebd74f453d6d3640ea465c4104c

Independent saved MIDI/XML numeric results:
Index Art MIDI960 on/off Native480 Begin/End Pitch Velocity
1     PM     0 / 480        0 / 240          40    80
2     PM   480 / 960      240 / 480          40    80
3     PM   960 / 1440     480 / 720          40    64
4     PM  1440 / 1920     720 / 960          40    80
5     PM  1920 / 2400     960 / 1200         40    96
6     PM  2400 / 2880    1200 / 1440         40    80
7     PM  2880 / 3200    1440 / 1600         40    80
8     PM  3200 / 3520    1600 / 1760         40    80
9     PH  3520 / 7680    1760 / 3840         40    80

Exactly eight PM plus one PH; no MIDI3840/native1920 onset/bar2 retrigger.
Six straight eighths then three triplet attacks; final PH duration4160 MIDI
ticks = 13/3 quarter beats. Native uses exactly half every MIDI time.
MIDI type1, PPQ960, Conductor/Lead, 4/4, tempo500000us, both EOT7680.
Keyswitches: PM26 on0/off30; PH31 on3520/off3550, channel0/velocity100,
each ordered before its corresponding musical note. Eleven total note-ons
INCLUDE the two switches; there are NINE musical note-ons, not eleven.
Native Riff/AME/PPQBase480/Measures2/KeyEm/loopEnd3840, all string6/fret4,
eight actual PM labels and one actual PH label. No fabricated native CC lane.
The existing MIDI writer has no key-signature meta event; resolved/native Em
and actual pitch40 verify tonic/key, not an invented MIDI meta-event claim.

Independence beyond producer read-back:
  A\verify_release.py ran with -I -B from the outside-checkout cwd above,
  using Mido/ElementTree/hashlib, WITHOUT importing riff_groove_builder.
  It checked the retained actual files, exact build bytes/provenance, source
  versus installed equality, selector ordering and preservation snapshots.
  PASS; A\independent-verification.json and .txt retain results.
Nearby computed 2-to-3& range and overlap/too-short rejection also pass through
both real transports, without stray stage directories or error publications.

RETURNED ASSUMPTIONS / LIMITS
- count-A is the FINAL COUNT of the eighth-note triplet, not the pitch A.
- The final PH is ONE continuous note through ALL of measure2, no retrigger.
- Register is the playable low tonic nearest MIDI40 within profile range/
  tuning; default Em/AME is E2/MIDI40, not an invented melody/transposition.
- Omitted tempo is 120 quarter-note BPM; omitted bars resolve to two here
  because the phrase implies the measure2 hold, not the ordinary four-bar default.
- PM/PH selector zero lead and positive30-tick pulse gates are explicit generator
  policy, not a promise about plugin response. No profile/effect/CC is inferred.
- Bounded lead-only 4/4 range-plus-triplet/PH grammar, not arbitrary prose,
  melodies, arbitrary triplets, changing tempo/meter, sections, audio or legato.
  Only AME has evidenced PH; bass/SD3/standard profiles have not gained PH.
  griff/briff/sd3p are actual native suffixes; agp/sdp are request aliases.
  A matching operator-local SD3 template is necessary only for native drums.

OLD SIMPLE / NO-PHRASE MUSICAL BYTES PRESERVED
Source AND installed text-recovery originals:
  A\source\text-recovered\ and A\installed-wheel\text-recovered\
  text-recovered.mid — 117 bytes
    SHA256 922d4c30e4618b6cce61a2ecebb36193773ca3884e56db80f7c18fe18e813f26
  text-recovered_lead.griff — 1014 bytes
    SHA256 213adde1c4785dccd2289e6888328c16bca720fb8d2786edb4df34f3863d1c2f
  Four native/musical quarter notes, one MIDI keyswitch, no controls.
Ordinary installed three-part standard request, explicit/default/native-fallback:
  324-byte MIDI SHA256
    7d61b8d4a8c42a19091126ce7301b159744bbae4e78456b0cd1894f6269aea4b
Ordinary native-target no-control baselines still match Step10:
  MIDI336bytes:
    8fc4cfbe66c0706f223ec33a61692ead046a56a9dba51c6566f967690cee186c
  griff1296bytes:
    fe7a2a5c98d0ae16f6894e681e7f001a658c90d11b3f1beb313d5c98b6c810c9
  briff1282bytes:
    5da9b05e92e6989366f41f8abf22a0f8b88ae14591bc8b544e4c7c0cf47827c4
  synthetic-template sd3p1491bytes:
    8bee8a86a7e60320d02c4404e36d818639af1d8f4ebce27f6c23a25e7ebd0589
Existing tests assert the native-target no-control baselines; no weakened
assertions, blanket skips or unsupported approximations were introduced.

FINAL EXECUTED VALIDATION
Windows11/build10.0.26200/AMD64; repository CPython3.13.13.
Only this runtime was executed; declared Python>=3.11 is not multi-runtime
certification. Existing runtime mcp1.30.0 / pydantic2.14.1 / mido1.3.3.
1. Focused version/docs/source recovery/phrase checks:
   python -m pytest tests\unit\test_package.py tests\unit\test_readme.py
     tests\integration\test_text_feedback.py tests\integration\test_phrase_stdio.py -q
   PASS: 15 tests in1.98s; A\focused-suite.txt.
2. FINAL full current suite: python -m pytest -q
   RIFF_RELEASE_DIST=R\dist\lmstudio-fix-20261020
   RIFF_SD3_TEMPLATE=C:\Users\g3\Documents\Toontrack\Superior Drummer 3\sd3-demo.sd3p
   PASS: 1503 passed in61.86s, ZERO failures/skips; A\full-suite.txt.
   Includes all current parser/normalization/text-only, native/MIDI/CC/template,
   privacy/sanitization, corruption, event-budget, filesystem/root/junction,
   concurrency/atomic publication and installed-wheel regressions.
3. python -m ruff check . — PASS, all checks passed.
4. python -m ruff format --check . — PASS, 94 files already formatted.
5. python -m mypy --strict src tests — PASS, 50 source files/no issues.
6. python -m pip check — PASS, no broken requirements.
   Static/dependency results retained in A\checks.txt.
7. Editor diagnostics for release-touched Python files — no errors.
8. git diff --check — PASS.
9. Independent isolated outside-checkout persisted-file/archive/preservation
   verification — PASS, no application-package import.

PRESERVATION / PRIVACY / CLEANUP
Independent before/after check: ALL25 snapshotted files unchanged in hash,
size, identity and mtime: 17 pre-existing historical reports, seven source
fixtures/templates, and the genuine local SD3 reference below.
  C:\Users\g3\Documents\Toontrack\Superior Drummer 3\sd3-demo.sd3p
  size75393; inode166633186213030518; mtime_ns1788614183091903900
  SHA256 06f54b02079e4b32d532ecc232b813c3fe1865799e6f5b2b21b5ddf398b0533d
Local-template tests were opt-in-enabled and READ-ONLY. They preserve non-song
kit/mixer/tracker state; none enters source or distributions.
Other local musical/factory references were not modified or copied. No private
chat, manual or factory asset was read/exported as part of this release work.
Accepted Step11/12 implementation remains present; previous reports were
NOT rewritten and their original Step12 evidence was not overwritten.

A\preservation-before.json retains the25-file baseline.
A\source-manifest.json covers71 current package/test/fixture/docs/README/
pyproject/.gitignore files, excluding reports and ignored build/test artifacts.
SHA256 of sorted compact JSON path->file-SHA256:
  f6d73d0a3a6ad6c3d72398f8fbe34dcf317baf4a22d228a7b8d2a2ca7e9d1a66
Final build/module/resource provenance is independently checked against source.
Owned failed/intermediate initial distributions were removed. Test stdio
children exited0 and transient installation/build/output workspaces were
cleaned by fixtures. Final distributions, clearly named original evidence,
logs/verifier/manifests and this report remain.
No unrelated files were deleted; no user output file was replaced.

ISSUES ENCOUNTERED AND RESOLVED
- Editor test discovery returned no tests; actual pytest CLI supplied focused
  and full execution. No success was inferred from editor discovery.
- Initial new test string/assertion layout needed Ruff line wrapping.
  Fixed before the final build, then rebuilt the final pair and passed all
  static/full checks. Superseded owned build pair was removed.
- Independent archive probe initially assumed LF-only wheel METADATA. Actual
  metadata uses platform line endings; switched to the standard email metadata
  parser. Verified actual Version=0.1.1; no package-byte alteration was needed.
- No unresolved implementation, dependency, musical-event or privacy blocker.

OPERATOR-REQUIRED STARTUP / FINAL GENERATION HANDOFF
Do NOT treat an already-running MCP process or existing LM Studio chat as proof
that the new package/schema is in use. The operator must:
1. Use LM Studio's Program -> Install -> Edit mcp.json if configuration is needed;
   use README's mcpServers example with the repository venv Python and an
   already-existing output root. Do not substitute VS Code servers/type JSON.
2. RESTART the LM Studio MCP SERVER after this update.
3. START A FRESH CHAT; rediscover tools/profiles and verify initialization
   version0.1.1. Old chats may retain cached schema/description/failed assumptions.
4. Only after review, issue the final original request using minimal supported
   arguments. Do not invent aggressive_rock, lead sd3p, CC91 or other effects.
The operator/orchestrator performs those actions; this task did NOT restart,
edit or manipulate LM Studio, any active chat/config/process, Cubase or DAW.
Software stdio/filesystem success is NOT live LM Studio/model, audible
plugin/native import/play/save/reload, routing or Cubase acceptance.

READY: final user-file generation can proceed on the verified 0.1.1 build
after orchestrator review and the operator's restart/fresh-chat requirement.
No files were generated under D:\MusicGenOutput in Step13.
Stopped here: no commits, delegation, later prompts, user-output generation
or application/configuration/process/DAW manipulation.

ORCHESTRATOR FINAL USER-FILE ACCEPTANCE

After reviewing the complete report, independently reran the full current suite
against the exact persisted 0.1.1 release pair:
  1503 passed in 60.82s, zero failures/skips.
Ruff lint/format, strict mypy and pip check also independently passed.
Source and installed metadata both report version 0.1.1.

A NEW real stdio child, launched outside the checkout with the user's configured
output root and unchanged optional SD3 template, initialized as 0.1.1.
TextContent JSON matched structuredContent for profile discovery, a deliberate
lead+sd3p error, and the actual successful original-description request.
Wrong format identified formats with a correction; it published no directory.
The original description was sent verbatim, without invented profile/format/
CC parameters; allow_midi_fallback=false ensured actual native success.

Actual user-facing outputs, exclusively created and independently reopened:
D:\MusicGenOutput\em_chug_triplet_ph_20261020_030601\
  em_chug_triplet_ph_20261020_030601.mid
    168 bytes
    SHA256 c1967e698a50b8c22a22e458c3e2dd02d04407d1ad1d61f8a462d790b0810e62
  em_chug_triplet_ph_20261020_030601_lead.griff
    1701 bytes
    SHA256 e8195e74c60ac93b1a4c92967a0834a64b2a2ebd74f453d6d3640ea465c4104c

Independent Mido/ElementTree checks confirmed:
  E minor, E2/MIDI40, 120 BPM default, 4/4, two measures.
  9 musical notes = 8 PM + 1 PH; no bar2 retrigger.
  MIDI onsets 0,480,960,1440,1920,2400,2880,3200,3520; PHoff7680.
  PM26 and PH31 selectors ordered before musical onsets.
  Native PPQ480, exact half-timings, PM/PH labels, string6/fret4, PHend3840.
  No CC91, other CC/program events, fabricated drum artifact or sidecar.
The source SD3 template's identity/size/mtime/hash remained unchanged.
The test child was closed cleanly. The existing LM Studio server/chat,
configuration, model and Cubase session were NOT manipulated or restarted.
Operator restart plus a fresh LM Studio chat remain required to use 0.1.1 there.