The CREATE_TRACKING_ISSUE and CREATE_ANNOUNCEMENT_ISSUE scenarios in
features/automation_tracking_mandatory_labels.feature used Behave tables
without explicit column headers, but the step implementations index rows
by row["name"] / row["value"]. Behave was treating the first data row as
the heading row, raising KeyError('"value" is not a row heading') and
erroring both scenarios.
Add the missing `| name | value |` header row to both tables so the
indexed access works as written. Also apply `ruff format` to the steps
module to satisfy the lint/format gate (trailing commas in dict literals
and parenthesised long assert messages).
ISSUES CLOSED: #3105
Updated automation-tracking-manager.md to enforce mandatory labels on all tracking issues:
- Status tracking issues now require both 'Automation Tracking' and 'Priority/Medium' labels
- Announcement issues require both 'Automation Tracking' and a priority label
- Added critical rule #4 to enforce label application with failure handling
- Added comprehensive BDD tests to verify mandatory label application
ISSUES CLOSED: #3105
HAL9000
controller-ci-rerun
HAL9000