ci(owned-pool rescue): list backend.yml, whose push guard reads the Linux pool
tests/test_ci_owned_pool_sources.py fails on feat-cmux-next with .github/workflows/backend.yml: job migrations-push-guard reads vars.RUNNER_POOLS. cmux#30685 introduced that read (my lane) and cmux#30761 kept it deliberately as the job's secretless fleet route. The test wants main's scripts/ci/owned_pool_rescue.py to either watch the workflow or list it as unrescued.
Change: backend.yml goes into UNRESCUED_WORKFLOW_PATHS, with the reason. The job holds no secret, runner_pools.py keeps the pool on a live member, and the next backend push supersedes a stuck run. The deploy jobs take bounded Blacksmith routes that the rescue doesn't act on. The rescue's behaviour does not change: an unrescued entry makes it do nothing.
Tests: on this tree, test_ci_owned_pool_sources and test_ci_owned_pool_rescue pass. Against the feat-cmux-next tree (87b4c905), owned_pool_sources.owned_workflows() minus this file's watched and unrescued paths is now empty.
Agent session: agent session
🤖 Generated with Claude Code
Summary by CodeRabbit
- Chores
- Updated internal workflow tracking to include the backend CI workflow and its associated checks.
- No changes to end-user features or application behavior.