fix(weekly-flow): distinguish queued upgrades and Lidarr tracks

[lklynet]

Summary

Distinguish queued quality upgrades from ineligible tracks and label files reused from Lidarr. Add regression coverage for both behaviors.

Linked issues

None

Validation

• CI passes
• Tested using the ghcr.io/lklynet/aurral:pr-<number> preview image, or not required
• Upgrade, migration, and rollback notes are updated where applicable

Test plan

• Affected area(s): weekly flow, quality upgrades, playlists, UI, documentation
• Automated coverage: Added tests for duplicate queued upgrades and reused Lidarr files.
• Manual steps and expected result: Start an upgrade search twice and confirm the second attempt reports that it is already queued. Verify Lidarr-reused tracks display the Lidarr label and are not eligible for upgrades.

Release impact

• Major: incompatible change
• Minor: backward-compatible feature
• Patch: backward-compatible fix
• None: documentation, CI, tests, or internal-only change

Summary by CodeRabbit

• New Features
  • Re-search requests now clearly indicate whether an upgrade was newly queued or already in progress.
  • Tracks reused from Lidarr are labeled “Lidarr” in playlist quality information.
• Bug Fixes
  • Duplicate upgrade requests no longer return an error when an upgrade is already queued.
  • External Lidarr files are correctly classified and excluded from upgrade eligibility checks.
• Documentation
  • Updated playlist guidance to explain Lidarr labels and queued upgrade behavior.

[github-actions]

Aurral preview image ready

This image was rebuilt from the latest push to this pull request. It will be replaced when you push another change.

docker pull ghcr.io/lklynet/aurral:pr-577

To test it with your existing Docker Compose setup:

1. Back up your Aurral config.
2. Temporarily change the Aurral service image to ghcr.io/lklynet/aurral:pr-577.
3. Run docker compose pull aurral && docker compose up -d aurral.
4. Exercise the behavior changed by this pull request.
5. Restore the image reference that was configured before testing.

View the preview workflow run · Report a problem

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1f64e7a3-d89f-4ff4-9417-768b5addd00c

📥 Commits

Reviewing files that changed from the base of the PR and between 1f6cec7 and 713106e.

📒 Files selected for processing (8)

• .tests/weekly-flow/approved-import-path.test.js
• .tests/weekly-flow/download-tracker.test.js
• backend/routes/weeklyFlow/handlers/jobs.js
• backend/services/qualityProfileService.js
• backend/services/weeklyFlow/weeklyFlowDownloadTracker.js
• docs/src/content/docs/using/playlists.mdx
• frontend/src/pages/FlowPage.jsx
• frontend/src/pages/flows/flowComponents/flowTrackComponents.jsx

---

📝 Walkthrough

Walkthrough

The change updates quality classification for completed files stored outside the library, including reused Lidarr files. Upgrade queueing now returns distinct statuses and detects active duplicate jobs. The route returns a successful response for already-queued requests. The frontend displays separate messages for new and duplicate searches. Tests cover repeated requests and external-file classification. Documentation describes the Lidarr label and duplicate-search behavior.

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Included in stable release 2.3.0

This change is included in the Aurral 2.3.0 release.

docker pull ghcr.io/lklynet/aurral:2.3.0

View the release