potiuk opened a new pull request, #383: URL: https://github.com/apache/airflow-steward/pull/383
## Summary Supersedes [PR #374](https://github.com/apache/airflow-steward/pull/374)'s "walk CVE-affecting trackers individually" contract with a merged-proposal shape, scoped to the CVE-affecting bucket only. The bucketing introduced in #374 stays — only the UX changes from per-tracker walk → single merged bulk proposal. ### Why Per-tracker walk through N CVE-affecting trackers serialises confirmation into N round-trips. The operator can't: - Compare proposed summaries across trackers - Notice that two trackers should converge on the same CWE long-form - See at a glance that three are blocked on the same missing field A single merged proposal puts everything on one page. The hygiene gates in Step 5b 1b still catch *mechanical* drift on every regen; the bulk-review surface is for *judgment* calls (threat-model framing, credit-line shape, CWE choice) before the push fires. ### Confirmation syntax - \`all\` — apply every proposed change across all trackers - \`<N>:all\` — apply every change on tracker \`<N>\`; skip the others - \`<N>:1,3,5\` — apply only the listed items on tracker \`<N>\` - \`<N>:skip\` — skip tracker \`<N>\` entirely - \`<N>:edit <item-number>: <new value>\` — replace before applying - \`cancel\` / \`none\` — apply nothing ## Test plan - [x] Bulk-mode section in SKILL.md rewritten with the merged-proposal shape + confirmation syntax - [ ] Next bulk sync run on \`airflow-s/airflow-s\` confirms operator can review N CVE-affecting trackers in one pass ## Notes for reviewers - Bucket-and-walk eval case from #374 (\`step-bulk-orchestration\`) still applies — the bucketing decision is unchanged. The eval doesn't test the CVE-affecting bucket's *internal walk pattern*, so no eval change needed for this PR. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
