fix(kanban): finish #1592 step 3 — writers first, then the fallback

[LukasWodka]

Follow-up to #237, found by @shujaatTracebloc's review there. Refs tracebloc/backend#1592.

Step 3, as currently written, is an outage

Three sites still writeStaging (human review) — a column that no longer exists on the board — and two fallbacks quietly translate it to FR on staging. Today's behaviour is correct because of those fallbacks, and both are labelled "removed in step 3 of #1592".

Delete them while the writers remain, and every staging promotion fails its option lookup and exits 1.

site	path
kanban-closure-router.yml:71	pull_request writer
kanban-closure-router.yml:156	issue-closure writer
advance-deploy-env.yml:71	push writer

The order is the fix. Writers emit the live name; only then is the fallback dead code — and it goes in the same change so nothing is left half-done.

What this deliberately does not do

It does not start writing Staging (agent review).

I checked, and nothing writes that column anywhere — by design. fr-gate.yml ranks it 7 and says so: "READ-ONLY for now — nothing writes this value yet (#1578 does that, in a LATER hop)." So a card landing in FR on staging on a staging merge is the documented transition, not a skipped stage.

That's one correction to the review on #237: the mechanism described there is exactly right, but the impact — "every staging promotion appears to bypass agent review" — reads worse than it is. There is nothing to bypass yet. Writing the agent column here would instead move cards into a column nothing advances, which is backend#1846's dead end, created on purpose.

Two sites left alone, on purpose

Readers.case arms accepting both names match values read from the board, which can never return the dead one. That is tolerance, not a dependency, and it costs nothing:

kanban-closure-router.yml:279 advance-deploy-env.yml:88, :209

fr-pass-comment.yml needs no change and is worth pointing at as the shape the other two should have had: it resolves the column by probing the board for whichever name exists, and fails loudly when neither does — so it never depended on a hardcoded name at all.

Evidence

Both files parse as YAML · every embedded run: block parses under bash -n · house-rules clean · no writer of the dead name remains (grep confirms only the three reader arms above).

🤖 Generated with Claude Code

---

Note

Medium Risk
Touches deploy and closure automation that aborts if Status options do not resolve; wrong timing would break staging promotions, but the change matches the documented live column name.

Overview
Completes backend#1592 step 3 by aligning GitHub Actions writers with the live kanban Status column name and removing rename-window fallbacks that are no longer safe once the old option is gone.

advance-deploy-env.yml sets staging push status to FR on staging instead of Staging (human review), and the GraphQL Status lookup no longer falls back to the old name when the new one is missing.

kanban-closure-router.yml uses FR on staging when a PR merges to staging or when a completed issue was closed by such a PR; the same fallback block before Status resolution is removed, so a missing option fails the run instead of silently retargeting.

Read-side tolerance (e.g. rank/override case arms that still accept both names) is unchanged on purpose.

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