chore(changelog): clean up empty code change sections in the changelog

[orangekame3]

Ticket

• N/A

Summary

• Cleaned up the changelog by removing empty code change sections to enhance clarity and maintainability.

Changes

• Removed empty sections from the changelog.
• Updated subproject commit reference.
• Refactored imports for consistency across measurement defaults.
• Adjusted parameter names in various functions for clarity.

[claude]

Claude finished @orangekame3's task —— View job

---

PR Review Complete ✅

Reviewing PR #768: "chore(changelog): clean up empty code change sections in the changelog"

Todo List:

• Analyze the scope and nature of changes across 40 files
• Review dependency updates in requirements.txt files
• Review Python code changes in calibration tasks
• Check parameter name consistency and potential breaking changes
• Assess security implications of dependency changes
• Evaluate impact on test coverage
• Provide comprehensive review feedback

---

Code Review Feedback

✅ Overall Assessment: LGTM with Minor Observations

This is a well-structured maintenance PR that successfully updates the qubex dependency and adapts the codebase to API changes. The changes are systematic and follow consistent patterns.

📋 Summary of Changes

• Dependency Update: qubex updated from develop branch to stable v1.5.0b4 tag
• Import Refactoring: Moved from qubex.measurement.measurement to qubex.measurement.measurement_defaults
• Parameter Standardization: Renamed function parameters across 35+ calibration tasks:
  • shots → n_shots
  • interval → shot_interval
• Dependency Cleanup: Significant reduction in dependency tree (1720 deletions vs 997 additions)

🔍 Detailed Analysis

Code Quality: ✅ Good

• Consistent pattern applied across all calibration tasks
• No breaking changes to public interfaces
• Proper error handling preserved (see check_qubit.py:63-64)
• Import standardization improves maintainability

Security: ✅ Safe

• Moving to tagged release (v1.5.0b4) instead of develop branch improves security posture
• No new security vulnerabilities introduced
• Dependency reduction decreases attack surface

Performance: ✅ Neutral/Positive

• Large reduction in dependency tree should improve build times
• No performance regressions in core functionality
• Consistent parameter naming may improve readability

Breaking Changes: ✅ None

• All changes are internal to calibration task implementations
• Public API interfaces remain unchanged
• Parameter names in task definitions unchanged (run_parameters)

🎯 Specific Observations

Well Done:

1. Systematic Approach: All 35+ calibration tasks updated consistently
2. Stable Release: Moving from develop to v1.5.0b4 tag is good practice
3. Import Organization: One import moved to local scope in check_skew.py:50 to avoid circular dependencies
4. Dependency Cleanup: 723 fewer lines in lock files indicates cleaner dependency tree

Minor Notes:

1. Import Relocation (check_skew.py:47-50): The import of Skew moved inside the method. While this avoids import issues, consider if this pattern should be documented for future maintainers.

2. SciPy Dependency (pyproject.toml:169,215): Version constraint removed (scipy>=1.15.3 → scipy). Verify this doesn't cause version conflicts in production environments.

3. Large Lock File Changes: The uv.lock file shows significant churn. While this is expected with dependency updates, ensure the updated lock file is tested in CI/CD.

🧪 Test Coverage Impact

• Risk Level: Low
• Parameter renames are internal API changes that should be covered by existing integration tests
• Recommend running full test suite to validate qubex v1.5.0b4 compatibility
• No new test coverage appears needed

📝 Recommendations

1. CI Validation: Ensure CI passes with new qubex version
2. Integration Testing: Run end-to-end calibration workflows to validate parameter changes
3. Documentation: Consider updating developer docs if qubex API patterns have changed significantly

🎯 Verdict

Approved - This is a well-executed dependency update that follows best practices for API evolution. The systematic approach to parameter renaming and import updates demonstrates careful attention to consistency.

---

[claude]

Claude finished @orangekame3's task —— View job

---

PR Review Complete ✅

Reviewing PR #768: "chore(changelog): clean up empty code change sections in the changelog"

Todo List:

• Analyze the scope and nature of changes across 41 files
• Review dependency updates in requirements.txt files
• Review Python code changes in calibration tasks
• Check parameter name consistency and potential breaking changes
• Assess security implications of dependency changes
• Evaluate impact on test coverage
• Provide comprehensive review feedback

---

Code Review Feedback

✅ Overall Assessment: LGTM with Minor Observations

This is a well-structured maintenance PR that successfully updates the qubex dependency and adapts the codebase to API changes. The changes are systematic and follow consistent patterns.

📋 Summary of Changes

• Dependency Update: qubex updated from develop branch to stable v1.5.0b4 tag
• Import Refactoring: Moved from qubex.measurement.measurement to qubex.measurement.measurement_defaults
• Parameter Standardization: Renamed function parameters across 35+ calibration tasks:
  • shots → n_shots
  • interval → shot_interval
• Dependency Cleanup: Significant reduction in dependency tree (1720 deletions vs 997 additions)

🔍 Detailed Analysis

Code Quality: ✅ Good

• Consistent pattern applied across all calibration tasks
• No breaking changes to public interfaces
• Proper error handling preserved (see check_qubit.py:63-64)
• Import standardization improves maintainability

Security: ✅ Safe

• Moving to tagged release (v1.5.0b4) instead of develop branch improves security posture
• No new security vulnerabilities introduced
• Dependency reduction decreases attack surface

Performance: ✅ Neutral/Positive

• Large reduction in dependency tree should improve build times
• No performance regressions in core functionality
• Consistent parameter naming may improve readability

Breaking Changes: ✅ None

• All changes are internal to calibration task implementations
• Public API interfaces remain unchanged
• Parameter names in task definitions unchanged (run_parameters)

🎯 Specific Observations

Well Done:

1. Systematic Approach: All 35+ calibration tasks updated consistently
2. Stable Release: Moving from develop to v1.5.0b4 tag is good practice
3. Import Organization: One import moved to local scope in check_skew.py:52 to avoid circular dependencies
4. Dependency Cleanup: 723 fewer lines in lock files indicates cleaner dependency tree

Minor Notes:

1. Import Relocation (check_skew.py:47-52): The import of Skew moved inside the method. While this avoids import issues, consider if this pattern should be documented for future maintainers.

2. SciPy Dependency (pyproject.toml:169,215): Version constraint removed (scipy>=1.15.3 → scipy). Verify this doesn't cause version conflicts in production environments.

3. Large Lock File Changes: The uv.lock file shows significant churn. While this is expected with dependency updates, ensure the updated lock file is tested in CI/CD.

🧪 Test Coverage Impact

• Risk Level: Low
• Parameter renames are internal API changes that should be covered by existing integration tests
• Recommend running full test suite to validate qubex v1.5.0b4 compatibility
• No new test coverage appears needed

📝 Recommendations

1. CI Validation: Ensure CI passes with new qubex version
2. Integration Testing: Run end-to-end calibration workflows to validate parameter changes
3. Documentation: Consider updating developer docs if qubex API patterns have changed significantly

🎯 Verdict

Approved - This is a well-executed dependency update that follows best practices for API evolution. The systematic approach to parameter renaming and import updates demonstrates careful attention to consistency.

---

[codecov-commenter]

Codecov Report

❌ Patch coverage is 83.78378% with 6 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...alibtasks/qubex/cw/check_resonator_spectroscopy.py	0.00%	2 Missing ⚠️
src/qdash/workflow/engine/backend/qubex.py	0.00%	2 Missing ⚠️
...calibtasks/qubex/cw/check_resonator_frequencies.py	0.00%	1 Missing ⚠️
...ash/workflow/calibtasks/qubex/system/check_skew.py	0.00%	1 Missing ⚠️

@@             Coverage Diff             @@
##           develop     #768      +/-   ##
===========================================
- Coverage    47.67%   47.66%   -0.01%     
===========================================
  Files          245      245              
  Lines        16307    16307              
===========================================
- Hits          7774     7773       -1     
- Misses        8533     8534       +1     

Files with missing lines	Coverage Δ
src/qdash/workflow/calibtasks/fake/fake_rabi.py	39.34% <100.00%> (ø)
...ibtasks/qubex/benchmark/randomized_benchmarking.py	45.45% <100.00%> (ø)
...nchmark/x180_interleaved_randoized_benchmarking.py	51.61% <100.00%> (ø)
...nchmark/x90_interleaved_randomized_benchmarking.py	47.05% <100.00%> (ø)
...nchmark/zx90_interleaved_randoized_benchmarking.py	51.61% <100.00%> (ø)
...btasks/qubex/measurement/readout_classification.py	28.57% <100.00%> (ø)
...s/qubex/one_qubit_coarse/check_dispersive_shift.py	53.57% <100.00%> (ø)
...libtasks/qubex/one_qubit_coarse/check_hpi_pulse.py	50.00% <100.00%> (ø)
...ne_qubit_coarse/check_optimal_readout_amplitude.py	57.69% <100.00%> (ø)
...alibtasks/qubex/one_qubit_coarse/check_pi_pulse.py	50.00% <100.00%> (ø)
... and 25 more

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.