ci: teach every rank table to READ the agent column (backend#1577)

[LukasWodka]

Summary

Hop 1 of RFC-BACKEND-1552 D5 — reads before writes, in separate hops, because org-github's callers are pinned @main and both old and new callee code are live during a promotion of the reusables.

This was already a live landmine

Staging (agent review)exists on project 2 today (added by the #1592 rename) and no rank table knew it.rank() returned "", the [ -n "$SR" ] guard failed, evaluation fell through to strict equality, and the card would have blocked every prod promotion carrying it — the backend#1411 shape.

Measured: 633 board items scanned, zero currently in that column. Armed and waiting, not yet firing.

Changes

file
fr-gate.yml	rank 7; FR on staging→8, Ready for prod→9, Prod→10, terminals→11
advance-deploy-env.yml	same table, plus the agent column maps to the staging deploy environment if a card is dragged there by hand
kanban-reconcile.yml	the agent column joins its sibling post-merge columns, so an open issue drifting there returns to Backlog as it would from On dev

Why renumbering is safe

Every comparison is relative — rank(a) >= rank(b), and TARGET_RANK is itself $(rank …). No hardcoded rank literals anywhere. I checked that before touching the numbers.

Caught while renumbering:Prod moved to 10 and collided with the terminals, also 10. Terminals must rank strictly aboveProd or the no-demotion guard weakens. Bumped to 11.

Read-only, deliberately

Nothing writes this Status yet. That is #1578, and it must not land before the agent can produce a verdict — otherwise cards park in a column nothing advances.

Test plan

agent column vs required "On dev" -> PASS
agent column vs required "Ready for prod" -> BLOCKED
an unknown column -> BLOCKED (still fails closed)

actionlint clean on all three; standards selftest 20/20.

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes shared promotion-gate and monotonic deploy-advancement ordering used on every staging/main promotion; mistakes could block or mis-rank cards, though comparisons are relative-only and the change is intentionally read-only.

Overview
Hop 1 (read-only) for RFC-BACKEND-1552 D5: the board already has Staging (agent review), but workflows treated it as unknown—rank() returned empty and cards there would fail closed on prod promotions. This PR fixes that before anything writes that Status (#1578).

fr-gate.yml and advance-deploy-env.yml add the agent column at rank 7 (between On dev and human FR) and renumber later stages (Staging (human review)/FR on staging → 8, Ready for prod → 9, Prod → 10, Done/Cancelled → 11 so terminals stay strictly above Prod). advance-deploy-env.yml also maps a .kanban.yml override of that Status to the staging deploy environment.

kanban-reconcile.yml includes the agent column in the reconcile sweep and treats it like other post-merge deploy columns: closed-completed issues there are not forced to Done, and open issues drifted there move back to Backlog.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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