CI Optimizer: it would really be nice if "Always run CI on topmost PR of a stack" could actually mean "Always run CI on topmost non-draft PR of a stack". We frequently have stacks with continuing work in drafts, and: • running CI on the draft isn't necessarily that useful; it's not complete and may not be expected to pass • we don't get validation on the published upstack prs, which we may want to merge while keeping the draft open It would also be nice if PRs had a "always run CI on this PR" toggle or something

Appreciate the flag! Makes sense that running CI on a draft isn’t super helpful when the real validation should happen on the first non-draft PR. I’ve captured this in our feedback tracker for the team to consider.