feat(libSceAjm): support ratio ramp in sceAjmBatchJobSetResampleParametersEx

[pushkarreddyy]

What

Supports linear sample-rate ratio ramping across emitted output frames in sceAjmBatchJobSetResampleParametersEx for libSceAjm.native:

• Extends Resampler state to track change (ratio_change_per_sample).
• Updates ResamplerProduce to linearly adjust ratio by change on each emitted output sample frame, clamped at 0.0f.
• Updates JobKind::SetResampleParameters to parse both ratio and change from job.parameters.
• Updates sceAjmBatchJobSetResampleParametersEx to validate ratio_start (isfinite, > 0.0f) and ratio_change_per_sample (isfinite), packing both parameters into the batch header.
• Documents linear ratio ramp behavior and platform assumptions in docs/dev/debt/libSceAjm.native.md.

Tested

• Added unit tests in core/libs/tests/GuestAjm.cpp under TestResampleParametersEx:
  • Validates rejection of non-finite or non-positive ratio_start (0.0f, -1.0f, NaN, INFINITY) with 0x80930005.
  • Validates rejection of non-finite ratio_change_per_sample (NaN, INFINITY, -INFINITY) with 0x80930005.
  • Validates dynamic ratio ramping across decoded MP3 frames (1.0f start, 0.001f change over 512 samples ramping to ~1.512f), confirming output PCM generation and verification via sceAjmBatchJobGetResampleInfo.
• Verified conventions check with 0 findings and 0 errors:
  • python tools/check_conventions.py --base origin/main

Checklist

• Depends on: none
• Unblocks: PPSA01599 sceAjmBatchJobSetResampleParametersEx: RIDE 4 (PPSA01599) passes a non-zero ratio change per sample #3468
• AI-assisted: yes

[github-actions]

Progress report (63fb0cd → 3faeae8)

📉 System libraries: 88.33% (-0.03%, -1 reverted functions)

⚠️ 1 went back to stubs

Library	Name
libSceAjm.native	sceAjmBatchJobSetResampleParametersEx

[adriadam10]

Checked build + ctest (guest_ajm and the Ajm tests pass) and that the new test fails without the change.

Added one commit: the TechnicalDebt line stated the ramp rule as fact, but no source confirms it (KytyPS5 ignores the change, prosper stubs it, and the console does not export the batch builders, per #3468). It now says it is assumed: added after each emitted output frame, clamped at zero, kept across batches. Merging once CI is green.

[pushkarreddyy]

Thanks @adriadam10! All CI checks (conventions, eligibility, report) are green and passing cleanly.

[adriadam10]

Checked build + ctest (guest_ajm and the Ajm tests pass) on the current head; the only change since the last review is the TechnicalDebt wording that marks the ramp rule as assumed. Merging once the full Build is green.

[pushkarreddyy]

Thanks @adriadam10 its passing now ready for merging

[adriadam10]

Checked on the current head merged onto main: build and guest_ajm pass, and the new test fails without the change. The ramp rule (added after each emitted output frame, clamped at zero, kept across batches) is recorded as assumed in the TechnicalDebt entry, since no source confirms it. Merging once the full Build is green.