Refresh warning/deprecation cleanup on reconciled develop

[seonghobae]

Parent: #178

Current role

Child 과업 / O2 for fixing current warning/deprecation output after the default branch is reconciled.

Current-code evidence

• Baseline quickcheck on origin/develop passed but emitted 11 Python warnings.
• Warning families:
  • librosa n_fft=1024 is too large on short chord-recognizer fixtures.
  • PySoundFile failed. Trying audioread instead and FutureWarning: librosa.core.audio.__audioread_load on temporal missing-file test.

Relationships

• Parent: Reconcile main release/UI line into default develop and close warning output debt #178
• Related issues: Resolve Librosa and Audioread Warnings/Deprecations during Analysis #153, Fix warnings and deprecation messages in test suite #154
• Related PR: fix: resolve python pytest warnings and deprecations #155
• Blocked by: Sync origin/main release/UI commits back to default develop #179 until branch reconciliation is available or the warning fix branch itself carries the reconciliation.

Acceptance criteria

• Root cause is fixed, not hidden by broad warning suppression.
• Tests prove short chord-recognizer clips do not emit librosa FFT warnings.
• Tests prove missing temporal input paths fail before decoder fallback.
• Targeted Python tests run with -W always and no warning summary.
• Full ./scripts/harness/quickcheck.sh runs without warning/deprecated output.
• Resolve Librosa and Audioread Warnings/Deprecations during Analysis #153/Fix warnings and deprecation messages in test suite #154 are closed only after PR-head evidence proves the warnings are gone.

[coderabbitai]

🔗 Related PRs

#99 - chore: fix cargo audit warnings and python test coverage warnings [merged]
#157 - feat: implement V2 Transcription Groove Map [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[seonghobae]

Related follow-through: #186 now tracks the current PR #185 warning/review remediation slice. It covers the live CodeRabbit findings that must be fixed or proven obsolete before default-branch reconciliation can land.