fix(kanban): reconcile derives the missed stage instead of stranding the card (backend#1411)

[LukasWodka]

Bugbot on #127 — and it is the flip side of my own previous fix.

What I got wrong

I stopped reconcile asserting Done for a closed-completed issue that has a PR/Commit closer but sits in a non-deploy column. That removed a false claim and created a worse outcome: the card is closed, in an active column, and archive only takes terminal ones — so it stayed there forever. That is the invariant this job exists to enforce, broken by the job itself.

Skipping was never right, because that case is the router-miss this job backstops.

The fix

Do what the router failed to do — read the closing PR base ref and derive the stage:

closer	base	→
none	–	Done
PullRequest	main/master	Prod
PullRequest	staging	FR on staging
PullRequest	develop	On dev
Commit, or unknown base	–	On dev (the router’s own default)
lookup unreadable	–	skip — unreadable is not evidence
(already in a deploy column)	–	skip — the stage is already recorded

The mapping is character-for-character the router’s, deliberately: when those two disagree the faster one wins and the slower one silently undoes it, which was Bugbot’s third finding on #126 — same two files, same rule, out of step.

Also: ON_DEV_OPT and FR_STAGING_OPT were only resolved in a later step, so the classify step could not have set those columns even if it had tried. Declared there now.

Verified by extracting the decision and running all nine combinations rather than reading the case arms. actionlint clean.

Note

Targets develop; #127 promotes develop → main, so it picks this up automatically.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes automated kanban status moves for closed issues; wrong mapping could mis-route cards, but logic mirrors the existing closure router and still skips on lookup errors.

Overview
Kanban reconcile no longer leaves closed-completed issues stranded in active columns when the closure router missed setting a deploy stage. Instead of skipping PR/Commit closers outside deploy columns, it reads the closing PR’s baseRefName and moves the card to Prod, FR on staging, or On dev using the same base-branch rules as kanban-closure-router.yml (unknown base or Commit → On dev). Failed closer lookups still skip; no-closer still goes to Done.

The classify step now loads On dev and FR on staging status option IDs up front so those moves can be applied.

^{Reviewed by Cursor Bugbot for commit 5f64511. Bugbot is set up for automated code reviews on this repo. Configure here.}