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

56 KiB

STEP 4 REPORT — Generic profiles and articulation event intentions
Date: 2026-10-19

INFRASTRUCTURE IMPLEMENTATION/TEST STATUS: PASS.
FULL STEP 4 PRODUCTION READINESS: FALSE / BLOCKED.
READY FOR STEP 5: FALSE. No authorized real product mapping evidence exists.
Synthetic passing tests do not satisfy the approved Step 4 production exit gate.

IMPLEMENTED
- Added immutable Core profile/rule/evidence models, validation, typed MIDI
  event intentions, complete-or-failed planning results and diagnostics.
  Core has no project/package references and remains independent of DryWetMIDI.
- Profiles identify role, exact product/version, mapping version, authorized
  provenance/verification record, inclusive playable range, zero-based channel,
  initial state, explicit final resets and supported rules.
- Validation rejects invalid IDs/identity/evidence/status/roles, MIDI ranges,
  velocity layers, advances/durations, duplicate rules/CC numbers, ambiguous
  layers, incomplete/conflicting state and playable/keyswitch collisions.
  Drum mappings are logical-voice-to-absolute-pitch data, with explicit CC state;
  no GM/SD3 pitches or real instrument mappings were inferred.
- Planner revalidates composition and explicitly selected matching profiles.
  Unsupported articulation, unmapped voice, invalid velocity/pitch, missing/
  unverified profile, track channel collision, conflicting channel-wide state,
  overlapping pitch ownership or timing overflow returns diagnostics and no
  partial usable plan. Source musical data is preserved.
- Added embedded Generation catalog, loaded from its assembly rather than cwd.
  Production resource content is exactly []: zero production profiles/defaults.
  Unknown/default selection fails actionably, with no synthetic fallback.
  Public loading is embedded-only; internal stream parsing is unit-testable.
  Malformed/invalid resources fail explicitly, including missing constructor
  fields, null required values, integer enums, unknown/duplicate JSON properties,
  duplicate profile IDs and synthetic/unverified entries.
- IntegrationTests now references Generation to exercise the actual catalog.
  Its existing Server-only apphost copy target remains unchanged. Refreshed
  IntegrationTests' generated dependency lock; no new PackageReference/version.
- Added mapping contract and updated README/compatibility inventory to separate
  generic infrastructure from missing production evidence. Server source/tool
  registration is unchanged: production MCP tools remain empty.

MECHANISM, VELOCITY AND STATE DECISIONS
- Reused existing role/articulation/drum-voice enums and exact 960-PPQ timing.
  Control advances/durations are explicit signed-Int64 integer ticks.
  Events are typed note-on/note-off/CC intentions, not MIDI-library objects,
  handwritten MIDI encoding, file output or native serialization.
- Keyswitch-only, velocity-only, CC-only and combined rules are supported.
  All pitches are absolute MIDI numbers, independent of octave-label naming.
- Velocity layer bounds are inclusive requested-velocity constraints, 1..127.
  Outside-layer input fails, never clamps. Null outputVelocity preserves
  dynamics; an explicit fixed output must lie inside the layer. It changes only
  emitted velocity, not source dynamics. Identical control states need disjoint
  velocity intervals for distinct articulations.
- Latched state includes keyswitch pitch AND switch velocity plus the complete
  CC vector. Redundant state actions are suppressed; sustain restoration is an
  explicit supported rule, not guessed. Latched switch duration is pulse length.
- Momentary actions retrigger per note. Switch release occurs after both the
  musical end and the minimum switch duration measured from switch-on, including
  advance. CC release restores explicitly declared initial values. No guessed
  sustain switch, all-notes-off or unspecified final reset is emitted.
- Initial CC values emit at tick zero. The declared initial pitched articulation
  is known resting state, not an unnecessary initial switch trigger.
  Explicit final resets occur after musical extent and any later release;
  reset pulse tails extend EndTick when necessary.
- Bounded supported state schemes reject mixed latched/momentary controls on
  one channel and ambiguous overlapping momentary retriggers. Drums use voice
  pitches and CC state, not pitched-articulation keyswitches. Incompatible
  simultaneous/overlapping control windows fail without channel-per-note tricks.
  Nonzero-advance transitions cannot change incompatible prior sustained notes.
- One shared LeadInTicks is the maximum configured switch advance among
  requested rules on selected tracks. Every musical start/end shifts equally.
  No negative control time is clamped and no single role shifts independently.
- Same-tick stable priorities: note-offs (0), initial/release/reset CCs (1),
  new CC/switch state (2), musical note-ons (3); ties retain deterministic order.
  MusicalExtentTicks preserves all declared bars/trailing rests; MusicalEndTick
  adds lead-in; EndTick also includes final control releases/reset pulses.

TEST EVIDENCE
- 158 new articulation unit cases cover profile validation/ranges/layers,
  independent and combined mechanisms, exact event values/channels/timing,
  latching/retriggers/sustain/reset state, pairing/order, velocity-coded switch
  state, immutable deterministic output, source preservation, unsupported inputs,
  drum CC conflicts, channel collisions, fractional timing and checked overflow
  including final reset pulses. Catalog cases cover unrelated cwd, honest empty
  content, selection failures and malformed/invalid resources.
- 9 new in-process integration cases exercise description -> composition ->
  validation -> synthetic profile validation -> event planning, role subsets,
  production-catalog absence and explicit failures without partial plans.
- The full documented three-role example uses TEST-ONLY invented mappings:
  shared lead-in 240 ticks (lead advance 240, bass advance 120, drums zero);
  musical extent 15,360; shifted musical end/plan end 15,600.
  Lead has 32 musical notes plus one matched switch pulse; bass has four notes
  plus one matched switch pulse; drums have 48 mapped hits plus initial, active
  and final CC values. Total: 175 event intentions. Exact switch positions,
  output velocity, drum notes/CCs, shifted note starts/ends and pairing are
  asserted. Reversed profile enumeration yields identical event sequences.
- These are synthetic in-memory pipeline checks, NOT MIDI-file, native-file,
  public MCP generation, Cubase or actual instrument acceptance tests.

CHANGED FILES (20 deliverables, including this report)
  README.md
  docs\articulation-mappings.md
  docs\format-compatibility.md
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\InstrumentProfile.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\ArticulationRule.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\InstrumentProfileValidator.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\ArticulationPlanner.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\ArticulationPlanningResult.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\PlannedMidiEvent.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\Profiles\InstrumentProfileCatalog.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\Profiles\instrument-profiles.json
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\GAJ3T.MusicGen.RiffGrooveBuilder.Generation.csproj
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\SyntheticProfiles.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\InstrumentProfileValidatorTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\ArticulationPlannerTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\InstrumentProfileCatalogTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\Articulations\ArticulationPipelineTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests.csproj
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\packages.lock.json
  prompts\report_4.md

EXACT VALIDATION COMMANDS AND RESULTS
All dotnet commands ran from the repository root with process-local settings:
  $env:PATH = 'C:\Program Files\dotnet;' + $env:PATH
  $env:DOTNET_CLI_TELEMETRY_OPTOUT = '1'
  $env:DOTNET_NOLOGO = '1'
SDK executable: C:\Program Files\dotnet\dotnet.exe.
Output-only PowerShell formatting shortened repeated repository paths in
development logs; it did not change commands, selectors or test behavior.

1. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx
   PASS, exit 0, all five projects, after project-reference/resource edits.
   Repeated after the friend-test assembly manifest edit:
   dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --verbosity quiet
   PASS, exit 0.

2. Development compilation/test iterations:
   dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore
   Initial run: exit 1, 0 warnings, 3 CS8752 errors. Corrected ambiguous
   target-typed new expressions passed through a params diagnostic array.
   dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --filter FullyQualifiedName~Articulation
   Initial run: exit 1 before tests; new test helper name conflicted with an
   existing Composition namespace, and xUnit analyzers required predicate
   Assert.Single/DoesNotContain overloads. Fixed the new tests without weakening
   assertions or suppressing analyzers.
   dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --filter FullyQualifiedName~Articulation --verbosity quiet
   One diagnostic retry: exit 1 before fixes.
   dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --verbosity quiet
   Diagnostic build: exit 1, 0 warnings, 18 test compile/analyzer errors.
   Corrected focused runs with the quiet test command above:
     144 unit + 9 integration passed, exit 0, 0 failed/skipped;
     151 unit + 9 integration passed, exit 0, 0 failed/skipped;
     160 unit + 9 integration passed, exit 0, 0 failed/skipped.
   This broad selector includes TWO retained composition tests whose method
   names contain Articulation; do not count them as new Step 4 tests.

FINAL REQUIRED ACCEPTANCE
3. dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore
   PASS, exit 0. All five projects built; 0 warnings, 0 errors (0.63 s).

4. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build
   PASS, exit 0. Both assemblies discovered and executed:
     UnitTests:        452 passed, 0 failed, 0 skipped (812 ms).
       158 new articulation cases + all 294 retained cases.
     IntegrationTests:  33 passed, 0 failed, 0 skipped (1 s).
       9 new articulation pipeline cases + all 24 retained cases.
     TOTAL:            485 passed, 0 failed, 0 skipped.
       167 new cases + all 318 prior cases.

5. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --locked-mode
   PASS, exit 0. All five projects restored against generated locks.

6. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build --filter FullyQualifiedName~.Articulations. --verbosity quiet
   PASS, exit 0. Exact new namespace count: 158 unit + 9 integration =
   167 new tests; 0 failed, 0 skipped.

ADDITIONAL CHECKS
- Editor runTests over all four new test files: "No tests found".
  Used the prescribed CLI fallback; empty editor discovery was not called a pass.
- Final editor problems check over src/tests: no errors found.
- git --no-pager diff --check: PASS, exit 0.
- In-memory trailing-whitespace audit of all 19 Step 4 files preceding this
  report: PASS, exit 0; no scratch files created.
- Core project XML audit: PASS, zero project/package references.
- Production resource audit: PASS, exact empty list []; registry remains
  new McpToolRegistry() with no production tools.
- SHA256 preservation audit: PASS, all eight pre-existing orchestration files
  unchanged: plan.md, step_1..4.md and report_1..3.md. The already-modified plan
  was preserved, not reset or edited.
- Source/test output-file audit: PASS, no .mid/.midi/.agp/.sdp files.

BLOCKERS, UNRUN CHECKS AND STOP DECISION
- Development compile/analyzer issues are resolved. No unresolved generic
  infrastructure build/test failure remains. Infrastructure is ready for review.
- FULL STEP 4 REMAINS BLOCKED; readiness false. Required actual evidence:
  exact installed Eclips/Ray product names/versions/settings; SD3 version,
  content library, chosen MIDI map and overrides; authorized versioned mapping
  provenance/rights; verified absolute playable/switch/drum pitches, switch
  velocities, velocity layers/transformations, CC values/combinations, timing,
  durations, channel behavior, initial state, latching, momentary release/reset
  semantics and actual application verification for all three targets.
- Native schemas/metadata, authorized minimal fixtures/template permissions,
  confirmed AGP/SDP extensions/entity semantics/load workflows and actual
  native/plugin/Cubase acceptance evidence also remain absent. Generic MIDI
  intentions and test-created numbers establish none of those facts.
- No actual instrument/Cubase imports, MIDI/native writing/read-back,
  self-contained publication or public generation-tool acceptance was run:
  these require unavailable evidence and/or later authorized steps.
- No production profile, guessed mapping, tool exposure, native/MIDI writer,
  new package, later-step prompt, orchestrator edit, commit or delegation.
  No personal/vendor-directory search, network evidence fabrication or
  application automation was performed.
- Stopping after this report. Do not proceed to Step 5 without actual evidence
  and orchestrator/owner resolution of the blocked production gate.

Correction iteration 2: instrument catalog extension
Date: 2026-10-20

CATALOG-EXTENSION IMPLEMENTATION/TEST READINESS: PASS; ready for review.
FULL STEP 4 PRODUCTION MAPPING READINESS: FALSE / BLOCKED.
READY FOR STEP 5: FALSE. Stopping for orchestrator review.
This section updates current scope/status; the infrastructure history above
is retained unchanged.

IMPLEMENTED AND CONTRACT MIGRATION
- Added immutable vendor-neutral InstrumentDefinition with six metadata fields:
  ID, vendor string, product code, display name, existing role and documentation
  URL. No vendor/product enum, per-instrument subclass or fabricated version,
  playable range, mapping controls, installed/native capability was added.
- Embedded Instruments\instruments.json declares exactly seven identities:
  ample-abj / ABJ / Ample Bass J / Bass;
  ample-aglp / AGLP / Ample Guitar LP / Lead;
  ample-agm / AGM / Ample Guitar M / Lead;
  ample-agt / AGT / Ample Guitar T / Lead;
  ample-ame / AME / Ample Metal Eclipse / Lead;
  ample-amr / AMR / Ample Metal Ray5 / Bass;
  toontrack-sd3 / SD3 / Superior Drummer 3 / Drums.
  Vendor/manual URLs match the approved correction's official sources.
  Four Lead, two Bass, one Drums; acoustic guitars reuse the Lead slot.
- InstrumentCatalog supports embedded-only loading, exact ID lookup, immutable
  role filtering and deterministic ordinal-ID ordering independent of cwd.
  Invalid/missing/null/unknown/duplicate JSON fields, null entries, invalid
  IDs/codes/identity strings, URLs, undefined/numeric/composite roles, duplicate
  IDs and duplicate vendor/code or vendor/name identities fail explicitly.
  A malformed resource cannot return a successful empty catalog.
- Added required constructor/property InstrumentId to InstrumentProfile, after
  profile ID. JSON requires instrumentId; missing/null values fail rather than
  acquiring implicit binding. Core validates its stable ASCII ID shape.
  Updated existing synthetic unit/pipeline factories and profile-copy calls.
  No planner/event-generation behavior or rules were changed.
- InstrumentProfileCatalog validates every binding against a declared
  instrument, its existing role and exact ProductName == DisplayName identity.
  Dangling IDs, mismatches, duplicate profile IDs and synthetic/unverified
  mappings are rejected. Shared internal CatalogJson retains strict parsing;
  profile and definition resource failures remain InvalidDataException.
- Preserved Select(role, profileId), requiring explicit role/profile IDs with
  no authorized role defaults. Wrong-role profiles now have a distinct failure.
  Added SelectInstrument(role, instrumentId, profileId?); only a single matching
  verified candidate can resolve without a profile ID. Multiple versions require
  explicit choice. No first-candidate selection or cross-product substitution.
  Diagnostics distinguish unknown_instrument, instrument_role_mismatch,
  mapping_unavailable, unknown_profile, profile_role_mismatch,
  profile_instrument_mismatch, ambiguous_profile, no_default_profile and
  invalid_role.
- Joined immutable InstrumentProfileCatalog.Instruments entries expose metadata,
  matching profiles and derived mapping_unavailable/profile_available status.
  These describe mapping admission, not native compatibility or installation.
  Current production state: SEVEN identities, ZERO verified mapping profiles,
  SEVEN mapping_unavailable entries, ZERO playable production targets.
- Profiles\instrument-profiles.json remains exactly []; no production mapping
  was fabricated or changed. Server source/registry is unchanged and empty;
  discovery/generation tools remain unexposed, with final integration in Step 8.

DATA-ONLY EXTENSIBILITY AND REGRESSION EVIDENCE
- Unit-only JSON fixtures add four invented identities from arbitrary vendor
  strings, including synthetic-extra with two product/mapping versions.
  They are embedded only in UnitTests, never in the production assembly.
  Their intentionally invented Verified flags exercise catalog admission, not
  vendor mapping truth or actual application verification. Production continues
  rejecting actual Synthetic/Unverified status even with complete valid bindings.
- Both extra-target versions bind/select through the same catalog APIs, then
  the UNCHANGED ArticulationPlanner produces the expected test-only velocity:
  v1 preserves requested 96; v2 emits explicit 110 without mutating source 96.
  Ambiguous selection fails; exact version IDs succeed. A single-version
  extra instrument resolves explicitly by instrument ID without substitution.
- A data-only combined catalog joins all seven production identities with the
  four test identities: 11 metadata entries, four fixture profiles. Existing
  seven targets stay mapping_unavailable while the extra target becomes
  profile_available. Reversing JSON order yields identical ordered catalog
  output and never selects an arbitrary version.
- Tests cover exact seven names/codes/vendors/roles/manual URLs, immutable
  collections/filtering, unrelated-cwd loading, malformed/null/duplicate and
  invalid data, required profile binding, product/role/reference validation,
  verification rejection and all explicit selection/availability outcomes.
- New integration test loads both actual embedded catalogs from the unrelated
  existing OS directory, inspects/join-checks all seven targets, rejects missing
  mappings actionably, and proves no usable event plan is produced.
  Existing synthetic articulation pipeline and real MCP process regressions
  remain intact. No MIDI/native file or real application acceptance is implied.
- README and existing mapping/compatibility documents list the expanded scope,
  official source links, identity versus mapping/native acceptance, strict APIs,
  data-only extension/admission and rebuild/publish requirement. No runtime
  directories, scanning/loading, hot reload, external services, new packages,
  product-specific switches, writer hierarchy or export implementation.

CHANGED FILES (22 deliverables including this report)
  README.md
  docs\articulation-mappings.md
  docs\format-compatibility.md
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Instruments\InstrumentDefinition.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\InstrumentProfile.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Core\Articulations\InstrumentProfileValidator.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\CatalogJson.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\Instruments\InstrumentCatalog.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\Instruments\instruments.json
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\Profiles\InstrumentProfileCatalog.cs
  src\GAJ3T.MusicGen.RiffGrooveBuilder.Generation\GAJ3T.MusicGen.RiffGrooveBuilder.Generation.csproj
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Instruments\InstrumentCatalogTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Instruments\CatalogFixtures.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Instruments\Fixtures\instruments.json
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Instruments\Fixtures\profiles.json
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\SyntheticProfiles.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\InstrumentProfileValidatorTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\Articulations\InstrumentProfileCatalogTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests\GAJ3T.MusicGen.RiffGrooveBuilder.UnitTests.csproj
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\Instruments\InstrumentCatalogPipelineTests.cs
  tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\Articulations\ArticulationPipelineTests.cs
  prompts\report_4.md

EXACT VALIDATION COMMANDS / RESULTS
Repository root; process-local settings for every dotnet shell:
  $env:PATH = 'C:\Program Files\dotnet;' + $env:PATH
  $env:DOTNET_CLI_TELEMETRY_OPTOUT = '1'
  $env:DOTNET_NOLOGO = '1'
Executable: C:\Program Files\dotnet\dotnet.exe.

1. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --locked-mode
   Initial post-manifest validation: PASS, exit 0, all five projects up to date.
   No package/version/project-reference or lock-file changes were necessary.

2. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --filter 'FullyQualifiedName~.Articulations.|FullyQualifiedName~.Instruments.'
   Development attempts:
   - Exit 1: unit compilation stopped on one xUnit2029 assertion-style error;
     integration assembly still ran: 10 passed, 0 failed/skipped.
     Replaced filtered Assert.Empty with predicate Assert.DoesNotContain.
   - Exit 1: shared role-converter insertion had a misplaced method brace
     (CS1513/CS1022); corrected structure without suppressing validation.
   - Exit 0: 237 unit + 10 integration = 247 passed, 0 failed/skipped.
   FINAL after the combined production-plus-fixture extension test:
     PASS, exit 0; 238 unit + 10 integration = 248 passed, 0 failed/skipped.

3. dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore
   FINAL PASS, exit 0; five projects, 0 warnings, 0 errors (0.94 s).

4. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build
   FINAL PASS, exit 0:
     UnitTests:        532 passed, 0 failed, 0 skipped (692 ms).
     IntegrationTests:  34 passed, 0 failed, 0 skipped (1 s).
     TOTAL:            566 passed, 0 failed, 0 skipped.
   Increase over reviewed baseline: 80 unit + 1 integration = 81 new cases.
   All 485 reviewed baseline cases are retained and pass.

5. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --locked-mode
   FINAL PASS, exit 0; all five projects up to date against existing locks.

ADDITIONAL CHECKS / PRESERVATION
- Editor runTests over the six relevant test files: "No tests found".
  Prescribed CLI fallback above executed the tests; editor absence is not a pass.
- Final editor problems(src/tests): no errors found; CLI compilation is the
  authoritative build evidence.
- git --no-pager diff --check: PASS, exit 0.
- Core XML reference audit: zero PackageReference/ProjectReference elements.
- Production mapping resource remains []; Program still constructs an empty
  McpToolRegistry. No .mid/.midi/.agp/.sdp files exist under src/tests.
- SHA256 comparison of all nine non-report-4 orchestration files: unchanged
  from this worker's entry state, including the owner's already-modified
  plan.md and current step_4_fix.md; neither was reset or edited.
- Existing report history is preserved; the entire report uses exactly one
  plain triple-backtick fence. No scratch files, commits or delegation.

EVIDENCE, BLOCKERS AND STOP
- Identity references: official per-product Ample manual URLs in
  Instruments\instruments.json and docs\articulation-mappings.md, as supplied by
  the approved correction, plus the official SD3 manual URL. Earlier documented
  Eclipse/Ray5 manual and owner screenshot findings remain partial evidence.
  This iteration did not perform a new vendor/manual or local installation scan.
- ACTUAL PRODUCTION MAPPING VERIFICATION THIS ITERATION: NONE.
  The folder screenshot establishes no product versions, filesystem paths or
  maps. Do not assume all Ample products share articulations or native formats.
- Catalog-extension readiness is PASS despite missing maps. No unresolved
  metadata, selection, compilation or automated-test blocker remains.
- Full Step 4 readiness is FALSE / BLOCKED: ABJ, AGLP, AGM, AGT, AME, AMR and SD3
  still lack complete authorized exact-installed-version/settings mapping
  contracts and actual application verification. Required evidence includes
  absolute playable/control/drum pitches, switch velocity/advance/duration,
  velocity layers/transformations, CC combinations/state, channels, initial/
  latched/momentary/release/reset behavior; SD3 also requires its exact
  content library, chosen MIDI map and custom overrides.
- Native schemas/fixture/template rights, requested AGP/SDP extension/entity/load
  semantics and actual instrument/Cubase acceptance remain separate unresolved
  gates. No MIDI/native writing/read-back, product/Cubase import, publication,
  runtime-free or public generation-tool acceptance was run.
- No later step, new tool exposure, export implementation, runtime scanning,
  orchestrator prompt/plan edit, package addition, commit or delegation.
  STOP after this report for orchestrator review; do not start Step 5.

===============================================================================
Correction iteration 3: documentation-backed profiles
Date: 2026-10-20
Baseline: accepted Step 5 infrastructure, 663 tests.

BOUNDED CORRECTION STATUS: PASS for the supported, source-backed subset.
ADMITTED: 2 Documented profiles (AGLP and AME); 0 application-Verified profiles.
UNAVAILABLE: ABJ, AGM, AGT, AMR and SD3; all seven identities remain declared.
FULL REQUESTED-PRODUCT / APPLICATION READINESS: FALSE / BLOCKED.
READY FOR NEXT STEP: only for orchestrator review of this bounded subset.
No subsequent step, public tool, native writer or deployment was started.
Earlier report entries above are preserved historical results, not current counts.

IMPLEMENTATION
- Added MappingVerification.Documented without changing existing enum values:
  Unverified=0, Verified=1, Synthetic=2. Documented means cited published defaults;
  Verified continues to mean application-verified. Both are production-admissible;
  Unverified and Synthetic remain rejected, with only explicit test-only synthetic
  opt-in. No documentation-only mapping is called Verified.
- Added immutable MappingCompatibilityNotes: VersionScope,
  ConfigurationRequirements, RoutingPolicy and TimingPolicy. The optional final
  constructor argument preserves existing constructor/serialized fixture use.
  Documented profiles must supply notes; missing/null notes fail explicitly.
  Present fields must be nonempty, trimmed and free of control characters.
  Serialized nested fields are required; no compatibility policy is defaulted.
  Documented primary Source must be an absolute HTTP(S) URL without credentials.
- ProductVersion honestly states "documented defaults; installed version unknown".
  MappingVersion is the independent data revision published-defaults-2026-10-20.1.
  Evidence records manual sections, source HTTP revisions/hashes, retrieval date,
  vendor demo numeric anchors, authorization scope and application-check limits.
- Retained strict InstrumentId/role/exact product-name binding, explicit selection,
  immutable catalog data and actionable unsupported-profile diagnostics.
  No automatic Lead default or product substitution was introduced.
- Enabled null InitialArticulation for unknown receiver articulation. Planning
  explicitly begins with no assumed switch state: the first requested Sustain
  OR PalmMute alone is selected. Repeats latch without duplicate pulses.
  Existing explicit known-state behavior, complete initial CC initialization,
  conflict rejection, source immutability and musical timing are preserved.
  Unsupported non-null known initial articulations remain invalid.
- Existing MIDI construction/serialization, pinned library, projects/packages,
  track roles, articulations and pattern grammar were not changed.
  README and both mapping/compatibility documents explain the current subset.

EXACT ADMITTED PROFILES / FACTS
1. ample-aglp-documented-defaults-2026-10-20
   Binding: ample-aglp / Lead / Ample Guitar LP.
   Sustain switch 24, PalmMute switch 26, playable inclusive range 40-86.
   Sustain musical velocity 1-126; 127 is settings-dependent Pop/Pinch Harmonic.
   PalmMute preserves velocities 1-127; lower velocity means greater mute depth.
2. ample-ame-documented-defaults-2026-10-20
   Binding: ample-ame / Lead / Ample Metal Eclipse.
   Sustain switch 24, PalmMute switch 26, playable inclusive range 36-84.
   Sustain musical velocity 64-126 only. Manual's 1-15 full mute, 16-31 3/4
   mute, 32-63 half mute and 127 Pop/Pinch Harmonic are NOT accepted as Sustain.
   PalmMute preserves velocities 1-127; lower velocity means greater mute depth.
Out-of-range pitches/layers fail before writing; no clamping or hidden transform.

PRIMARY SOURCES / REVISION / ABSOLUTE NUMERIC ANCHORS
All sources below were retrieved 2026-10-20. Source revisions are NOT installed
product versions. All six official main-panel PDFs and Settings/CPC were read.
Rendered https://www.amplesound.net/en/manual.asp exposed the official links
when simplified fetching returned no useful manual links.

- https://www.amplesound.net/en/Main_Panel_Manual-AGLP.pdf
  PDF pp.6-7, sections 2.2.1, 2.2.3 and 2.2.5:
  C0 Sustain, D0 PalmMute, both E1-D5; velocity facts stated above.
  HTTP Last-Modified 2025-09-08 09:00:15 GMT.
  SHA256 7b28b62f3c25ecb774227b15beab06f5e0f0c944f35db9e82121028017f9cedb.
- https://www.amplesound.net/en/Main_Panel_Manual-AME.pdf
  PDF pp.6-7, sections 2.2.1-2.2.4:
  C0 Sustain, D0 PalmMute, both C1-C5; velocity facts stated above.
  HTTP Last-Modified 2025-09-08 09:00:39 GMT.
  SHA256 ab482f08b0546eca0a4233b8be3776c411b77f3dca96979f529debc2dfc0c4ca.
- The rendered https://www.amplesound.net/en/download.asp links vendor-authored:
  https://www.amplesound.net/dl0822/ds/AGLP-Prison_Break.zip
  HTTP Last-Modified 2019-11-24 16:33:18 GMT.
  SHA256 738956bced4e78a00ab755646d34108f9e25c5346ef79b96a5c1664c876f5e5f.
  MIDI entry: AGLP-Prison Break/AGLP-Prison Break-Tempo100.mid, 480 PPQ.
  Zero-based track 1: switch 24, velocity 100, on tick 3837/off 3957.
  Zero-based track 3: switch 26, velocity 100, on 34438/off 34558.
  This is a genuine numeric C0=24/D0=26 anchor; E1-D5 then means 40-86.
- https://www.amplesound.net/dl0822/ds/AME-Eclipse.zip
  HTTP Last-Modified 2019-11-24 17:03:34 GMT.
  SHA256 e448d85f9ff80692f625f23ef6ea4dd0b14367b9f92412adbb76aa6e4a987f66.
  MIDI entry: AME-Eclipse/AME-Eclipse-Tempo130.mid, 480 PPQ.
  Zero-based track 4: switch 24, velocity 100, on 3720/off 3840, musical
  C1 pitch 36 at 3840. The 1 Channel variant also contains switch 24.
  This anchors the manual's C0=24; D0 is two semitones higher (26), C1-C5=36-84.
  Numeric conversions were NOT inferred solely from octave labels.
- Demo streams were read using existing pinned DryWetMIDI 8.0.3, in memory.
  No alternate handwritten MIDI parser, demo MIDI, archive, sample library,
  copied manual or native content was retained or shipped.
- Public third-party numeric corroboration ONLY (no copied implementation):
  https://github.com/zaibuyidao/ReaScripts/blob/98e88777ff4cf2e478d6bc85d35349f62acc7e41/Various/Articulation%20Map/banks/70-96%20Ample%20Metal%20Eclipse%20%28%E9%87%91%E5%B1%9E%E5%90%89%E4%BB%96%29.reabank
  Blob ea878807ac429bd7294b9f8a8612a9261feacb4f corroborates Eclipse 24/26.
  Vendor manual/demo facts remain primary; that map's other interpretations
  were not adopted. Reaticulate's Rickenbacker bank uses 24/26 but is a
  different product, so it was NOT used to fill other targets' numeric gaps:
  https://github.com/jtackaberry/reaticulate/blob/3760589894808c03fac4b07aa0d3a63812484350/userbanks/Ample_Sound/Ample_Sound-Ample_Guitars-Ample_RB_%28Rickenbacker%29.reabank

RESEARCHED BUT UNAVAILABLE / EXACT REMAINING GAPS
- ABJ: https://www.amplesound.net/en/Main_Panel_Manual-ABJ.pdf
  PDF pp.6-7, sections 2.2.1-2.2.4.
  HTTP Last-Modified 2025-04-16 05:04:25 GMT.
  Sustain C0 B0-E4; musical velocities 1-125 Sustain, 126-127 Accent.
  PM D0 E1-D4 distinguishes high-velocity PM and low-velocity Dead Note,
  WITHOUT a numeric dividing threshold. No product-specific absolute numeric
  anchor was established. Missing anchor and dedicated PM threshold prevent
  a complete Sustain/PM profile; no guitar/bass values were substituted.
- AGM: https://www.amplesound.net/en/Main_Panel_Manual-AGM.pdf
  PDF pp.6-7, sections 2.2.1-2.2.4.
  HTTP Last-Modified 2025-09-08 09:00:15 GMT.
  AGT: https://www.amplesound.net/en/Main_Panel_Manual-AGT.pdf
  PDF pp.6-7, sections 2.2.1-2.2.4.
  HTTP Last-Modified 2025-09-08 09:00:02 GMT.
  Both document C0 Sustain/D0 PM, both E1-C5; Sustain 1-126 and Pop at 127;
  PM depth depends on velocity. No product-specific numeric anchor was
  established. Shared labels and another product's demo are not silently
  promoted into exact target evidence. Both remain unavailable.
- AMR: https://www.amplesound.net/en/Main_Panel_Manual-AMR.pdf
  PDF pp.6-7, sections 2.2.1-2.2.4.
  HTTP Last-Modified 2025-04-16 05:04:22 GMT.
  Sustain C0 A0-E4; 64-126 Sustain, 127 Accent, 32-63 PM, 1-31 Dead Note.
  Dedicated PM D0 B0-E4 has an unspecified high/low PM/Dead Note split.
  No product-specific absolute anchor established; unavailable. Even a future
  velocity-only supported subset needs its own absolute numeric anchor.
  The PDF title is Ample Metal R; the catalog retains vendor site's Ray5 name.
- https://www.amplesound.net/en/Settings_and_CPCv2.pdf
  PDF pp.7-9, sections 1.2.2-1.2.9; pp.14-15, section 1.5.
  HTTP Last-Modified 2026-06-16 17:25:14 GMT.
  Documents single/per-string channels, MIDI Guitar mode, editable velocity
  thresholds/accent behavior and user CC assignment. No numeric C0 anchor or
  certified keyswitch advance/pulse minimum was found. Full SHA256 revision
  fingerprints for all seven PDFs are in docs/articulation-mappings.md.
  The legacy https://www.amplesound.net/en/Ample_Guitar_Manual.pdf was also
  checked for a numeric convention; no additional usable anchor was found.
- SD3: https://www.toontrack.com/manual/superior-drummer-3/
  Both simplified fetch and rendered browser require login. Stopped without
  credentials/bypass. The accessible vendor-hosted image-only attachment:
  https://www.toontrack.com/app/uploads/topic/how-can-i-use-midi-or-notaion-created-in-notion-6-to-drive-superior-drummer/pdf/Example-Layout.pdf
  Page 1, HTTP Last-Modified 2026-03-04 08:25:19 GMT, explicitly shows SD3
  Hansa - Marble Room: Kick Open=36, Snare Center=38, Hi-Hat Closed Tip=42.
  It also labels C0=24 within that layout. It is a forum attachment, not
  an established vendor-authored universal/core default mapping; default-state
  authorship, library applicability, velocity and hi-hat/controller assumptions
  are unresolved. Public forum search corroborated the numbers, but body/reply
  access was login-limited, including:
  https://www.toontrack.com/forums/topic/mapping-one-articulation-to-two-midi-notes/
  No SD3 profile is admitted from GM convention or that Hansa-specific example.
  Needed: authorized default layout for the selected SD3 library/map and
  velocity/controller scope; installed-map/custom-override acceptance remains
  a separate application gate.

EXPLICIT COMPATIBILITY POLICIES / LIMITATIONS
- Non-versioned documented default mappings only. 2019 vendor demo files are
  numeric anchors, not claims that a particular release is installed today.
- Default tuning/articulation mappings/velocity thresholds; instrument mode,
  not Strummer; MIDI Guitar mode disabled. Isolated idle receiver with no
  externally held keyswitches or custom remapping. Unknown articulation is
  handled explicitly, but this is not a reset of arbitrary external held notes.
- Writer routing: Lead zero-based channel 0, display channel 1. Host must route
  the isolated role to the exact product accepting that channel. No per-string
  routing, program changes, guessed controller numbers or automatic settings.
- Writer timing at 960 PPQ: velocity-100 latched switch, 120-tick advance,
  30-tick paired pulse released before musical onset. Velocity 100 occurs in
  official examples; timing is deterministic engineering policy, NOT a vendor
  minimum, measured plugin latency or VST-certified behavior. Tempo-relative
  ticks are explicit; 480-PPQ demo timings are not mislabeled as writer limits.
- Shared lead-in preserves all note intervals/durations/dynamics. First requested
  state alone initializes; repeated states suppress duplicate pulses.
  Incompatible overlapping control/music state fails; it is not retimed away.
  No final articulation reset is invented. Switches release; last selection
  remains latched. No claim that the owner's plugin settings match defaults.

TEST COVERAGE AND EXACT FINAL VALIDATION
- Updated historical empty-catalog expectations to two Documented/five unavailable
  with no automatic defaults; preserved strict malformed/binding/failure checks.
  Legacy Verified JSON without notes still loads with unchanged semantics.
  Missing/null/blank/invalid documented notes, missing nested fields, bad public
  source URLs and Synthetic/Unverified status laundering are rejected.
- Both admitted profiles assert exact source/manual/demo revisions, numeric
  switches/ranges/layers, identity/role, honest version scope, explicit policies
  and immutable data. Outside-range notes and unsupported Sustain layers fail.
- Unknown receiver first Sustain and first PM, repeats, transitions, explicit
  known-state compatibility, CC initialization, source preservation and note/
  control pairing are covered. The former null-is-invalid expectation was
  intentionally replaced by positive unknown-state regressions; unsupported
  known initial articulations still have negative coverage.
- 8 new actual file write/read-back cases: each admitted profile with first
  Sustain and PM from CompositionPlanner, plus each profile/first-state boundary
  and transition arrangement. Exact Type 1/960 PPQ, role/channel, pitches,
  velocities, switch/music order, shared lead-in, durations, repeat suppression,
  no overlapping switches, paired releases, EndOfTrack and source immutability
  are checked through MidiFileWriter and DryWetMIDI.Read. 3 further integration
  cases reject invalid Sustain velocity layers before any output exists.
- Final commands, in order (all exit 0):
  1. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --filter "FullyQualifiedName~Articulations|FullyQualifiedName~Instruments|FullyQualifiedName~DocumentedProfileMidiTests" --verbosity minimal
     PASS: 278 unit + 21 integration = 299; 0 failed, 0 skipped.
  2. dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --verbosity minimal
     PASS: all five projects; 0 warnings, 0 errors.
  3. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build --verbosity minimal
     PASS: 658 unit + 56 integration = 714; 0 failed, 0 skipped.
     Baseline 663 -> final 714, net +51, with intentional evidence/initialization
     contract expectation updates and retained generic MIDI/protocol regressions.
  4. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --locked-mode --verbosity minimal
     PASS: all five projects up to date; existing locks/package versions unchanged.
  5. git --no-pager diff --check
     PASS before report; report-only append checked separately.
- Existing SDK 10.0.400 and pinned DryWetMIDI [8.0.3] retained.
  Editor runTests returned "No tests found"; CLI commands above are actual test
  evidence. Editor problems for changed source/new tests reported no errors.
- One initial targeted attempt failed on two xUnit2031 analyzer errors in the
  new integration assertions. Replaced Where+Assert.Single with predicate
  overloads; subsequent targeted/build/full runs all passed. No unresolved
  compiler, analyzer, test or restore failures remain.

FILES / CLEANUP / BOUNDARY
- Modified 18 directly related deliverables including this report:
  README.md; docs/articulation-mappings.md; docs/format-compatibility.md;
  Core Articulations/InstrumentProfile.cs, InstrumentProfileValidator.cs,
  ArticulationPlanner.cs; Generation Profiles/InstrumentProfileCatalog.cs and
  instrument-profiles.json; UnitTests Articulations/SyntheticProfiles.cs,
  InstrumentProfileValidatorTests.cs, InstrumentProfileCatalogTests.cs,
  ArticulationPlannerTests.cs and new DocumentedProfileTests.cs;
  IntegrationTests Articulations/ArticulationPipelineTests.cs,
  Instruments/InstrumentCatalogPipelineTests.cs,
  Midi/MidiGenerationPipelineTests.cs and new DocumentedProfileMidiTests.cs;
  prompts/report_4.md.
- Probed existing PDF helper availability first; pdf-parse was missing.
  Used disposable session-only pdf-parse@2.4.5 for in-memory text extraction
  and the image-only SD3 layout, then removed the entire helper and rendered
  image. No helper manifests/dependencies, manuals, demo MIDI/archives,
  generated MIDI/native fixtures or vendor assets remain in source/test trees.
  Actual file tests clean up only their own checkout-local output directories.
- No personal/vendor directory scan, product installation, credential request,
  account bypass, native format investigation/implementation, new project,
  production dependency, public MCP tool, prompt/plan edit, commit or delegation.
  Owner's pre-existing prompts/plan.md and prompts/step_4_fix.md edits were left
  untouched. Server/public tools and native formats were not changed.

APPLICATION VERIFICATION / STOP
- APPLICATION VERIFICATION PERFORMED: NONE. No VST, SD3, Ample product, Cubase
  import, audible playback, native reopen, publication or runtime-free check.
  Source facts and automated MIDI format read-back are NOT those checks.
- Two documentation-backed default profiles are ready for bounded review and
  in-process source/format use under their explicit assumptions. Five targets
  remain unavailable with exact missing facts above; full requested-product and
  actual installed-plugin readiness remain blocked. Native evidence and
  deployment/public-tool work require their own authorized steps.
- STOP after this report. Do not start another step.

===============================================================================
Correction iteration 4: additional evidenced capabilities
Date: 2026-10-20
Actual entry baseline: 882 tests; Step 8 tools and Step 9 publication already exist.

SUPPORTED CAPABILITY CORRECTION / PUBLICATION REFRESH: PASS.
READY FOR ORCHESTRATOR REVIEW: YES, for this bounded documented-default subset.
CURRENT: seven identities, five Documented profiles, zero application-Verified.
Lead: AGLP/AGM/AGT/AME Sustain and PalmMute. Bass: ABJ Sustain only.
UNAVAILABLE: AMR and SD3. ABJ PalmMute remains explicitly unsupported.
Native writers, installed-plugin/Cubase acceptance and runtime-free host
acceptance remain pending/blocked. This is not full requested-product completion.
Earlier report counts/results are preserved history.

IMPLEMENTED CAPABILITIES / UNCHANGED CONTRACTS
- Added three data-only profiles to the existing embedded catalog:
    ample-agm-documented-defaults-2026-10-20
      Lead channel0; Sustain24/PM26; inclusive range40-84;
      musical Sustain1-126, PM1-127.
    ample-abj-documented-defaults-2026-10-20
      Bass channel1; Sustain24 ONLY; inclusive range35-76;
      musical Sustain1-125. Accents126-127 and PalmMute fail explicitly.
    ample-agt-documented-defaults-2026-10-20
      Lead channel0; Sustain24/PM26; inclusive range40-84;
      musical Sustain1-126, PM1-127.
- AGLP/AME IDs, mapping facts, compatibility/warning semantics and generated
  example content are unchanged. No production planner, generation service,
  grammar, role/articulation enum, DTO/schema or tool implementation changed.
- New evidence remains Documented, never application-Verified. Unknown installed
  version/default scope and independent mapping revision remain explicit.
  Compatibility notes disclose source limitations, default tuning/mapping/
  thresholds, instrument mode, MIDI Guitar mode off and isolated idle receivers.
- Reused unknown-initial-articulation selection, explicit paired switch release
  and repeat suppression. Writer policy remains switch velocity100, advance120/
  pulse30 ticks at960 PPQ. This is engineering policy, NOT a vendor minimum
  or measured/certified plugin timing. ABJ channel1/display2 is our routing policy,
  not a claim that the historical channel0 demo mandates a receiver channel.
- Discovery now exposes five profiles/nine articulation entries: four Lead
  profiles with two articulations each, one Bass profile with Sustain only.
  AMR/SD3 stay visible as mapping_unavailable; no cross-product substitution.
  Missing explicit Bass selection is no_default_profile, not mapping_unavailable.
  Missing Drums mapping, unknown/wrong-role IDs, unselected-role profiles,
  disabled fallback and no-overwrite failures remain explicit.
- Updated affected catalog, discovery, in-process, MIDI, stdio and publication
  tests, README and mapping/format/protocol/text/deployment documentation.
  Explicit ABJ PM requests fail unsupported_articulation with no file, partial
  arrangement, fixed-velocity transformation or implicit Sustain fallback.

EXACT SOURCES / CONFIRMED ABSOLUTE ANCHORS
All new checks performed 2026-10-20. Official rendered download page:
  https://www.amplesound.net/en/download.asp
Publicly linked archives were read unauthenticated and in memory using existing
pinned DryWetMIDI8.0.3. No vendor MIDI/archive/manual/native asset was retained.
Main-panel mapping/velocity facts reuse the already reviewed official manuals;
this was not an open-ended repeat of manual research.

AGM:
  https://www.amplesound.net/en/Main_Panel_Manual-AGM.pdf
  PDF pp.6-7 sections2.2.1-2.2.4: C0 Sustain/D0 PM, E1-C5;
  musical Sustain1-126/127 Pop, PM depth follows velocity.
  HTTP Last-Modified2025-09-08 09:00:15 GMT;
  SHA256449bd7b8bca7771dbf8e08e0029d2bbe999f991efe441d7900ee93da29dd86a4.
  https://www.amplesound.net/dl0822/ds/AGM-Rylynn.zip
  HTTP Last-Modified2019-06-11 17:57:25 GMT;
  SHA256e88c40ce4e67fde7b692b7f1cd5c4d057d7cd2a50e21d71114379b55d1fabd6f.
  Exact entry AGM-Rylynn/AGM3-Rylynn.mid,480PPQ, zero-based track1 "G1":
  channel0 note24/velocity80 on32215/off32335.
  https://www.amplesound.net/dl0822/ds/AGM-Dear_Ben.zip
  HTTP Last-Modified2019-11-24 16:38:43 GMT;
  SHA256bb6dd773b5f998a1d0efa80ebc77d6661922e49f137f74a685000792ed618fe5.
  Exact entry AGM-Dear Ben/AGM-Dear Ben Tempo 74.mid,480PPQ,
  track1 "AGM ARP", channel0:
  note26/velocity80 on28798/off28858; note24/velocity80 on30238/off30298.
  These directly anchor C0=24/D0=26, hence E1-C5=40-84.

ABJ:
  https://www.amplesound.net/en/Main_Panel_Manual-ABJ.pdf
  PDF pp.6-7 sections2.2.1-2.2.4: C0 Sustain, B0-E4, velocities1-125;
  126-127 Accent. Dedicated D0 PM/Dead Note threshold is unspecified.
  HTTP Last-Modified2025-04-16 05:04:25 GMT;
  SHA2569291c4e3027ac1469bd845bb04614f5a2754bd35a4f017bcfd7cdb75db335e7e.
  Official download row "Project - Ample Bass Articulations" explicitly lists
  products ABJ ABP, linking:
  https://www.amplesound.net/dl0822/ds/AB-Articulations.zip
  HTTP Last-Modified2019-06-11 17:32:45 GMT;
  SHA256c3efc1dc787c59a00be7405687488317efaf952822aededf54b9e19f4e145cb7.
  Exact entry AB-Articulations/4.2 Articulations & Poly Legato.mid,480PPQ,
  track1 "ABP", channel0: note24/velocity90 on3720/off4080;
  musical note40/velocity90 on3840. Shared applicability is explicitly vendor-
  listed, NOT an independently ABJ-named performance.
  This anchors C0=24/B0-E4=35-76 for Sustain. The missing D0 threshold blocks
  PM, NOT an otherwise supported Sustain-only profile. AMR does not inherit it.

AGT CONCLUSION: GENUINE NAMED-NOTE ANCHOR CONFIRMED; PROFILE ADMITTED.
  The concrete official Tab Player lead was confirmed in rendered:
  https://www.amplesound.net/en/tutorial-b.asp
  Section6.3 "Tab Play Toggle" explicitly names MIDI note A6 for tab playback,
  high velocity on/low velocity off. This is actual vendor text, not a MIDI-
  library-supplied label. Historical applicable Tab Player documentation;
  no HTTP Last-Modified header. HTML source SHA256:
  542ae25caec1dfea772fbe9f5cc80be0c12ad3104f057e654410226aa1e69e92.
  Official download row "Tab Project - Wish You Were Here" lists AGT AGM:
  https://www.amplesound.net/dl0822/ds/AGT-Wish_You_Were_Here.zip
  HTTP Last-Modified2019-06-11 18:04:59 GMT;
  SHA25682a9b42109519d20d9340c6c6cdb972a66663482df483fd0bf5034b84b5d9262.
  Exact entry AGT-Wish_You_Were_Here/AGT3-Wish You Were Here Tempo 62.mid:
  the directory uses underscores, correcting the prose entry spelling.
  480PPQ; tracks1 "Solo"/2 "Strum" each contain only note105/velocity80,
  channel0 on3840/off4320.
  Matching the named A6 tab control to numeric105 establishes:
    C0 = 105 - (6*12 + 9) = 24; D0=26; E1-C5=40-84.
  This is NOT a direct Sustain/PM performance or an octave label inferred from
  an assumed convention. The profile emits no Tab Player/note105 control.
  Main-panel source:
  https://www.amplesound.net/en/Main_Panel_Manual-AGT.pdf
  PDF pp.6-7 sections2.2.1-2.2.4; HTTP Last-Modified2025-09-08 09:00:02 GMT;
  SHA2562e5696d750841a47061d37737ec7d8435cb4e30756cda15596d1f89ff87810dd.
  Its documented C0/D0, E1-C5 and Sustain1-126/PM1-127 facts are anchored
  under explicit historical/default scope, not an installed-release claim.

LIMITS
- AMR has no public demo archive among the nine inspected official rows.
  No invented URL, another bass substitute or open-ended search was attempted.
- SD3 remains unavailable; no GM guess, login bypass or new mapping claim.
- Existing AGP/SDP codecs remain unavailable. No native research/implementation,
  package/project, new feature/tool, user/global settings edit or delegation.
- No licensed application, VST hosting, audible articulation, native reopen,
  exact installed-setting acceptance or runtime-free Windows host was tested.

ACTUAL MIDI / RPC / PUBLICATION EVIDENCE
- All five admitted profiles pass real in-process composition->profile->plan->
  MIDI write/read-back. New cases cover AGM/AGT first Sustain/PM, boundaries
  and transitions; ABJ first Sustain, pitch35/76 and velocity1/125 boundaries,
  separate Bass channel1, PM rejection and accents126/127 rejection.
- Actual built-server RPC and refreshed published-server RPC each exercise all
  four Lead profiles with explicit ABJ, both MIDI-only and AGP+MIDI fallback.
  Exactly one artifact retains both roles; native fallback has two native
  target reasons, two written MIDI target outcomes and source-only warnings.
- Eight detailed refreshed-publication Lead+Bass cases each wrote/read435 bytes:
  SHA256 F31C7C2236637AF9412738418AF61E7D613D51C89A8FFB43B379012C7798384A.
  Type1/960PPQ, Conductor/Lead/Bass; tick-zero120BPM/4-4;
  Lead channel0:32 pitch64/velocity96 notes, start120+480*i/duration480;
  Bass channel1:4 pitch40/velocity96 notes, start120+3840*i/duration3840;
  PM26/100 and Sustain24/100 on0/off30; shared lead-in120;
  76 channel events, exact paired note-offs and three EOTs at15480.
  No stuck switches/notes or silently omitted role. Test-owned files removed.
- Refreshed existing executable:
  artifacts/publish/win-x64/GAJ3T.MusicGen.RiffGrooveBuilder.Server.exe
  74,734,064 bytes; SHA256
  921AADE7FB75222E8A7E5E81151F3DC73747CD8036EE751555A613A5DBDD308E.
  Its isolated process advertises the five-profile subset, not stale metadata.
- Preserved existing artifacts/examples/ame-lead-example.mid,371 bytes:
  SHA256 6F5791FB5C3A7A17E54AAF6436963E4D5723FB948057585060C09BF9B2AFCA3E.
  Before/after hash and explicit read-back test pass; no replacement/new retained
  example was made. Full payload inventory/refresh evidence is appended to report9.

FINAL COMMANDS / RESULTS
All exit0; SDK10.0.400, existing pinned DryWetMIDI[8.0.3].
1. dotnet build .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-restore --verbosity quiet
   PASS,0 warnings/errors; repeated after ordinary restore.
2. dotnet restore .\src\GAJ3T.MusicGen.RiffGrooveBuilder.Server\GAJ3T.MusicGen.RiffGrooveBuilder.Server.csproj -p:PublishProfile=win-x64 --locked-mode --verbosity minimal
   PASS, dedicated existing publication lock.
3. dotnet publish .\src\GAJ3T.MusicGen.RiffGrooveBuilder.Server\GAJ3T.MusicGen.RiffGrooveBuilder.Server.csproj -p:PublishProfile=win-x64 --no-restore -o .\artifacts\publish\win-x64 --verbosity minimal
   PASS, accepted self-contained/single-file profile retained unchanged.
4. dotnet restore .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx --locked-mode --verbosity minimal
   PASS, ordinary solution locks; build then focused/full validation.
5. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build --filter "FullyQualifiedName~Articulations|FullyQualifiedName~Instruments|FullyQualifiedName~GenerationServiceTests|FullyQualifiedName~MusicGenToolsTests|FullyQualifiedName~DocumentedProfileMidiTests|FullyQualifiedName~McpGenerationTests|FullyQualifiedName~PublishedServerTests" --verbosity quiet
   PASS:414 unit+107 integration=521;0 failed/skipped.
6. dotnet test .\GAJ3T.MusicGen.RiffGrooveBuilder.slnx -c Release --no-build --verbosity quiet
   PASS:794 unit+142 integration=936;0 failed/skipped.
   Baseline882 retained with intentional availability/default expectation updates;
   net+54 tests (14 unit,40 integration).
7. dotnet test .\tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests.csproj -c Release --no-build --filter FullyQualifiedName~PublishedLeadBassUsesRefreshedProfilesAndOneReadableArtifact --logger 'console;verbosity=detailed'
   PASS:8; actual435-byte paths/hashes/read-back reported above.
8. dotnet test .\tests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests\GAJ3T.MusicGen.RiffGrooveBuilder.IntegrationTests.csproj -c Release --no-build --filter FullyQualifiedName~PublishedServerTests --verbosity quiet
   PASS:28;0 failed/skipped, refreshed payload and retained-example check.
9. Both restore commands repeated with --verbosity quiet after full validation:
   PASS, unchanged ordinary/dedicated lock graphs.
10. git --no-pager diff --check: PASS before report; both appends checked afterward.

DEVELOPMENT ISSUE / PRESERVATION
- Initial focused run had two discovery assertions fail because new AGM scope
  disclosed "No exact ... verification is claimed" but lacked the existing
  explicit "not" wording assertion. Strengthened the AGM compatibility note:
  "installed configuration is not verified". No assertion was weakened.
  All final focused/full/publication runs pass.
- Editor runTests reported "No tests found"; CLI runs are actual test evidence.
  Editor problems on changed tests reported no errors.
- No new package/helper or project was needed. All vendor data was streamed;
  no copied assets remain. No generated MIDI/native/stage/PDF files remain
  under src/tests, no owned published-check directories/processes remain.
- Existing publish profile, ordinary/dedicated locks and all production engine/
  MCP code were preserved. Prompt/plan files were not edited; their pre-report
  scope hashes remain unchanged. No commit, delegation or settings edit.
- Direct deliverables: profile JSON; affected catalog/articulation/MIDI/service/
  protocol/RPC/publication tests; README and five existing docs; these two report
  appends; refreshed ignored publication. No unrelated work/later step started.
- STOP for report review. Supported capabilities/publication pass; runtime-free,
  licensed-application, remaining mapping/articulation and native gates stay open.