feat(kanban): collapse FR on dev + Ready for staging → On dev (D6, code only)

[LukasWodka]

RFC-BACKEND-0008 D6 — collapse FR on dev + Ready for staging into On dev

Drops the dev-side functional review. Merge to dev → automatic On dev (no manual gate). The one human review stays at staging: FR on staging → /fr-pass → Ready for prod. 11 columns → 10.

Code changes (this PR — safe, no live-board impact)

Workflow	Change
advance-deploy-env	develop push → On dev (was FR on dev)
kanban-closure-router	merged-to-develop → On dev
fr-pass-comment	drop the FR on dev → Ready for staging transition; /fr-pass now only at FR on staging
fr-gate	staging hop requires On dev (automatic — no dev-side human gate); rank table collapses FR on dev(6)+Ready for staging(7) → On dev(6)
kanban-reconcile	column arrays updated

actionlint clean on all five.

⚠️ The live cutover is a SEPARATE, coordinated step — do not merge+promote alone

These workflows reference the On dev option, which doesn't exist yet. If they reach main before the option is renamed, every develop-merge fails (On dev not found). Conversely, renaming first breaks the old workflows still on main. So the cutover must be near-simultaneous, done in a quiet window:

1. Merge this PR to develop and promote to main (callers read @main).
2. Immediately rename the Status option FR on dev → On dev via the API (preserves the option ID and every item's assignment — this is a rename, not a new option).
3. Move any items sitting in Ready for staging → On dev.
4. Delete the Ready for staging option.

Steps 1–2 must not be separated by a working day. I'll drive this with you watching, when you're ready — it's the one board-wide change that can strand promotions if mis-sequenced.

Depends on

#1274 (staging in every repo) should land first — a repo with no staging branch still can't complete the ladder. This PR is the column model; #1274 is the branches it flows through.

---

Note

High Risk
Changes org-wide promotion gates and status resolution for every repo using these workflows; deploying before the board option is renamed to On dev will break develop deploy automation and can block staging merges.

Overview
Implements RFC D6 by replacing FR on dev and Ready for staging with a single automatic On dev column across the reusable kanban workflows (11 → 10 stages in code).

Develop path: advance-deploy-env and kanban-closure-router set On dev on develop merges (and matching issue mirrors) instead of FR on dev. .kanban.yml overrides recognize On dev rather than the old dev FR column.

Human FR only on staging: fr-pass-comment no longer advances from FR on dev; /fr-pass only moves FR on staging → Ready for prod.

Promotion gates: fr-gate requires On dev (not Ready for staging) for PRs targeting staging, and the rank() ordering collapses the two removed columns so On dev is stage 6 and downstream ranks shift up by one.

Reconcile: kanban-reconcile scans and treats On dev in place of the old dev/ready-for-staging columns for drift and misplaced open issues.

Cutover note: workflows assume a live Project Status option named On dev; board rename/migration must happen in the same window as promoting these workflows to main, or status updates will fail to resolve options.

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

[LukasWodka]

bugbot run

[LukasWodka]

👋 Heads-up — Code review queue is at 39 / 30

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• averaging-service#207 — Promote develop → staging · author: @shujaatTracebloc · no reviewer assigned
• backend#1201 — docs(rfc): Data spaces & federated dataset composition (draft) · author: @LukasWodka · no reviewer assigned
• backend#1217 — docs(rfc): Dataset integrity & score reproducibility (draft) · author: @LukasWodka · no reviewer assigned
• backend#1228 — Promote develop → staging · author: @shujaatTracebloc · reviewer: @saadqbal
• backend#1244 — fix(experiments): surface save-time failures as 5xx + guard new NOT NULL columns · author: @LukasWodka · reviewer: @saqlainsyed007
• backend#1251 — docs(bugbot): add .cursor/BUGBOT.md project context (#930) · author: @LukasWodka · no reviewer assigned
• backend#1254 — docs(pr-template): owner-qualify cross-repo closing keywords · author: @LukasWodka · no reviewer assigned
• backend#1259 — docs(rfc): qualified RFC identifiers + org-wide index · author: @LukasWodka · no reviewer assigned
• backend#1261 — RFC-BACKEND-0008: board & process reset (decision RFC — for markup) · author: @LukasWodka · no reviewer assigned
• cli#397 — Release develop → main · author: @shujaatTracebloc · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 0029c27. Configure here.}