Dirty-main narrow fix promotion with stash recovery Use when: - a single verified fix commit must be promoted to - is dirty - you also need to create GitHub issues from generated scripts without trusting assumed labels Core lessons 1. Do not cherry-pick onto dirty . 2. Before , verify exact repo labels; do not assume generic labels like , , or exist. 3. may be the right move for a quick narrow promotion, but can fail after the cherry-pick/push if the restored work overlaps files changed by ongoing local work. 4. If restore fails, keep the stash; do not drop it. Prefer recovery in isolation ra…