fix: pass kanban option IDs as raw strings (-f not -F) to survive numeric IDs

[LukasWodka]

Summary

Fixes a real, currently-firing bug in the kanban automation: advance-deploy-env.yml crashes on every push to develop and master/main.

Root cause: the workflows pass single-select option IDs to GraphQL with gh api graphql -F o="$OPT_ID". The -F flag does magic type coercion — an all-digit value becomes an integer — but the mutation variable is $o: String!, which rejects it:

gh: Variable $o of type String! was provided invalid value

ProjectV2 option IDs are 8-char hex and are frequently all-numeric. Some of the status-transition options this automation targets are all-numeric, so the mutation fails. The Deploy-environment update runs first and succeeds (its option IDs contain letters), then the Status update crashes the job — so the run goes red and the Status field doesn't advance. It's been masked because kanban-closure-router.yml (a separate PR-merge-triggered workflow) already uses -f and advances the card correctly. So cards moved, but the advance / advance job has been failing silently.

Fix:-F o= → -f o= (raw string, coercion-proof) in all 5 mutations across 4 workflows. $p/$i/$f stay -F — they're GraphQL ID! (which accepts integer coercion) and are always letter-prefixed anyway.

Workflow	Mutations fixed	Was
advance-deploy-env.yml	2	actively crashing
set-pr-status.yml	1	latent
fr-pass-comment.yml	1	latent
customer-priority-bump.yml	1	latent

No change needed in kanban-closure-router.yml (already -f) or auto-classify.yml (inlines the ID as a quoted string literal). Each fix carries a comment explaining the -f so it isn't reverted later.

⚠️ Activation note

Caller workflows reference these reusables at @main, so this fix only takes effect once it reaches main via the normal develop → staging → main promotion. Targeting develop per branch policy.

Test plan

• YAML parses (all 4 files)
• No -F o= remains; 5× -f o= present; $p/$i/$f unchanged
• After promotion to main: push to develop on any repo → advance / advance job is green and the card advances
• Push to master/main → card advances to the prod state

[LukasWodka]

👋 Heads-up — Code review queue is at 20 / 8

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

Open PRs currently in Code review (oldest first):

• client-runtime#36 — Bump requests from 2.32.3 to 2.33.0 in /Node-deploy · author: @dependabot · no reviewer assigned
• client-runtime#37 — Bump black from 25.1.0 to 26.3.1 in /Node-deploy · author: @dependabot · no reviewer assigned
• client-runtime#38 — Bump requests from 2.32.3 to 2.33.0 · author: @dependabot · no reviewer assigned
• client-runtime#39 — Bump black from 25.1.0 to 26.3.1 · author: @dependabot · no reviewer assigned
• client-runtime#45 — Staging: Enhance jobs-manager with HTTP proxy, ingestion endpoint, and fixes · author: @saadqbal · no reviewer assigned
• data-ingestors#125 — test: add masked_language_modeling equivalence case · author: @LukasWodka · no reviewer assigned
• data-ingestors#126 — test: raise coverage toward 90% (Phase 1 — validators) · author: @divyasinghds · no reviewer assigned
• design-system#19 — fix: un-track coverage/ and node_modules/ from git · author: @LukasWodka · no reviewer assigned
• design-system#22 — ci: add Vitest test workflow · author: @LukasWodka · reviewer: @aptracebloc
• docs#3 — Block bots from crawling Mintlify static assets · author: @LukasWodka · reviewer: @saadqbal

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