This PR addresses code quality issues found in the feature-utilize-dvd-label-batch-processing changes to ensure compliance with the repository's contribution guidelines and coding standards.

Changes Made

Test Files

Fixed linting violations in the new unit test files:

test/unittest/test_disc_label_tv.py:

• Removed trailing whitespace from 34 blank lines (W293)

test/unittest/test_group_tv_discs.py:

• Removed trailing whitespace from 30 blank lines (W293)
• Removed unused MagicMock import (F401)
• Fixed import statement order to match project conventions (E402)
• Updated to use consistent sys.path.insert(0, '/opt/arm') pattern like other test files

Migration Files

Verified that both migration files follow proper alembic conventions:

• a1b2c3d4e5f6_config_add_use_disc_label_for_tv.py ✅
• b2c3d4e5f6g7_config_add_group_tv_discs_under_series.py ✅

Validation

All files now pass:

• ✅ flake8 linting with --max-line-length=120 and --max-complexity=15
• ✅ Python syntax validation
• ✅ PEP8 compliance
• ✅ Project-specific code style requirements

Testing

The changes are purely cosmetic (whitespace and import cleanup) and do not modify any test logic or functionality. All test methods, assertions, and test coverage remain identical.

Contribution Guidelines Compliance

This PR ensures the feature code adheres to:

• Repository's .pylintrc configuration
• Project's flake8 standards (as defined in .github/workflows/main.yml)
• Existing code patterns and conventions used throughout the test suite
• Proper migration file structure per alembic standards

No functional changes were made - this is strictly a code quality improvement to prepare the feature for merge.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.