Reconcile main release/UI line into default develop and close warning output debt

[seonghobae]

Current role

Canonical 업무 / O1 issue for keeping the default branch aligned with the current release/UI line and for closing warning/deprecation debt without hiding warnings.

Current state

• Repository default branch is develop.
• origin/develop and origin/main diverged after release/UI work landed on main.
• Fresh evidence from stepwise/default-reconcile: git rev-list --left-right --count origin/develop...origin/main returned 28 25.
• PR feat(ui): finalize rehearsal console redesign #177 is merged on main and contains the rehearsal console redesign.
• Warning issues Resolve Librosa and Audioread Warnings/Deprecations during Analysis #153 and Fix warnings and deprecation messages in test suite #154 remain open, and PR fix: resolve python pytest warnings and deprecations #155 is currently dirty/conflicting.

Current-code evidence

• Baseline worktree: /Users/seonghobae/opencode_tasks/bandscope/.worktrees/stepwise-default-reconcile
• Baseline quickcheck on origin/develop passed but emitted 11 Python warnings:
  • librosa FFT-size warnings from short chord-recognizer test audio.
  • PySoundFile/audioread fallback and FutureWarning from missing-file temporal analyzer test.

Relationships

• Milestone / 직무: v0.1.4 Default-branch Reconciliation & Zero-warning Stabilization
• Parent / 업무: this issue
• Children / 과업:
  • Sync origin/main release/UI commits back to default develop.
  • Refresh warning/deprecation cleanup on reconciled develop.
  • Verify rehearsal console UI after PR feat(ui): finalize rehearsal console redesign #177 lands on default develop.
  • Revalidate open develop PR queue after default branch reconciliation.
• Predecessors: v0.1.1 feat: implement rehearsal workspace design #159, feat(ui): redesign workspace with shadcn and tailwind v4 #164, fix(release): publish immutable release assets before publication #175, feat(ui): finalize rehearsal console redesign #177
• Related warning issues: Resolve Librosa and Audioread Warnings/Deprecations during Analysis #153, Fix warnings and deprecation messages in test suite #154
• Related PRs: fix: resolve python pytest warnings and deprecations #155, feat: implement V1.1 metadata-only local handoff #156, feat: implement V2 Advanced Rehearsal Collaboration Features #158, feat: implement local ML stem separation with chunking #111
• Historical/stale reference: Orchestrate PR #159 Rollout: Diagnostics, Fixes, and AKS Production Deployment #160

Next actions

1. Land a reconciliation PR to develop from a default-branch worktree.
2. Apply warning root-cause fixes on top of the reconciled branch.
3. Keep PR fix: resolve python pytest warnings and deprecations #155 as evidence or supersede it explicitly if the new branch replaces it.
4. Re-check PR feat: implement V1.1 metadata-only local handoff #156, feat: implement V2 Advanced Rehearsal Collaboration Features #158, feat: implement local ML stem separation with chunking #111, and relevant dependency PRs after develop moves.
5. Use robot-reviewer evidence and required checks for merge readiness. Do not wait for human review unless explicitly requested.

Acceptance criteria

• origin/develop contains intended release/UI commits from origin/main, including PR feat(ui): finalize rehearsal console redesign #177, without dropping existing develop-only work.
• Reconciliation PR to develop passes required checks: CI, CodeQL, dependency review, secret scan, security audit, SBOM, Trivy, Windows build gate, and macOS build gate.
• Warning/deprecation fixes are applied on current develop, not on stale/conflicting PR fix: resolve python pytest warnings and deprecations #155 state.
• Python analysis tests run warning-free, with root causes fixed rather than broad-suppressed.
• Resolve Librosa and Audioread Warnings/Deprecations during Analysis #153 and Fix warnings and deprecation messages in test suite #154 are closed only after current-code verification proves zero warning/deprecation output for the targeted path.
• fix: resolve python pytest warnings and deprecations #155 is updated, clean, and review-ready, or explicitly superseded by a linked replacement PR.
• feat: implement V1.1 metadata-only local handoff #156, feat: implement V2 Advanced Rehearsal Collaboration Features #158, and feat: implement local ML stem separation with chunking #111 are refreshed, superseded, or deferred with evidence after default-branch reconciliation.
• UX/UI verification covers PR feat(ui): finalize rehearsal console redesign #177 rehearsal console on desktop/tablet/phone breakpoints and stores evidence in PR comments/check logs.

Security Notes

• Trust boundaries touched: project files, local audio decode paths, test fixtures, GitHub workflow/release state, and WebView-rendered UI.
• Mitigation: reconcile through PR, keep CI/security gates intact, fail missing files before decoder fallback, and do not broaden URL/file/subprocess capability.
• Test points: warning-free Python tests, full harness quickcheck, local UI smoke where UI is touched, and required GitHub checks on the PR head.

[coderabbitai]

🔗 Related PRs

#81 - chore: patch npm audit vulnerabilities and restore canonical docs [merged]
#88 - feat: implement practical rehearsal workspace UI [merged]
#91 - feat: implement rehearsal priority calculation and cue-sheet export (#36) [merged]
#92 - docs: finalize roadmap completion (#26) [merged]
#95 - Sync main to develop after v0.1.0 release [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]

Linked #186 as the current-head CodeRabbit remediation work item for PR #185. It is a child execution issue under the v0.1.4 reconciliation meta flow and tracks the remaining robot-review blockers before merge.