test(regression): promote edit-flow-name.spec.ts to @stable

[daniellicnerski1]

Summary

Promotes `tests/tests-automations/regression/core-functionality/project-management/edit-flow-name.spec.ts` to `@stable`. Trims 4 rename cycles → 2 (loop), fixes the tag list, and adds a QA-CHECKLIST bullet for the unique coverage angle.

Why this spec is non-redundant

`flow-rename-header.spec.ts` (`@stable`) already covers:

• Header rename DOM commit
• API PATCH + GET persistence

`edit-flow-name.spec.ts` uniquely covers:

• Main page listing reflects the rename (and old names disappear)
• Re-opening a flow by clicking its new name
• Idempotence over multiple sequential renames

Changes

Change	Rationale
4 cycles → 2 in a `for` loop	Idempotence is proven at 2 cycles. The 3rd and 4th cycles were copy/paste with no extra signal — they cost ~15-30s in weekly runs
Tags: `["@Release", "@workspace", "@components"]` → `["@stable", "@Release", "@workspace", "@regression"]`	`@components` was incorrect (this is project-management, not component config). Add `@stable` (weekly run) and `@regression` (functional area)
Test title updated	Old title implied a main-page context-menu rename that the test never performs; new title accurately reflects "edit name + see it in listing"
QA-CHECKLIST L566 left as-is	That bullet (`Edit flow name and description`) is about `flowSettings.spec.ts`, which tests description + character limit — out of scope for this round
New QA-CHECKLIST bullet (after L565)	Specific to the listing-verification angle that this spec uniquely tests
ESLint auto-fix	Promoted `expect(await getByText(...).count()).toBe(1)` to the auto-waiting `await expect(...).toHaveCount(1)`

Test plan

• `npm run typecheck` clean
• `npm run lint` filtered on spec: 0 errors (warnings about `waitForSelector` are pre-existing project-wide pattern, present in `flow-rename-header.spec.ts` `@stable` too)
• Static anti-pattern grep — zero `.catch + toBeFalsy` / `waitForTimeout` / `toBeFalsy`
• `npx playwright test --workers=1 --retries=0` — 1 test PASS in 12.2s without retry
• Force-fail confirmed (broke `expect(flowName).toBe(targetName)`, saw failure point to L22 with useful message, reverted, repassed in 13.2s)
• `--trace=on` once — trace shows both cycles coherently
• Zero `🚨 Backend Error` occurrences

[Copilot]

Pull request overview

Promotes edit-flow-name.spec.ts to @stable, consolidates 4 repetitive rename cycles into a 2-iteration loop, corrects the tag list, retitles the test to match its actual behavior, and adds a corresponding QA-CHECKLIST entry.

Changes:

• Refactors test body to a for loop over 2 random names, replacing 4 inlined cycles.
• Updates tags from ["@release", "@workspace", "@components"] to ["@stable", "@release", "@workspace", "@regression"] and refines the test title; promotes expect(...).count() to await expect(...).toHaveCount(1).
• Adds a QA-CHECKLIST bullet under §12.2 mapping the listing-verification angle to this spec.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
tests/tests-automations/regression/core-functionality/project-management/edit-flow-name.spec.ts	Loop-based refactor, tag/title update, auto-waiting assertion
QA-CHECKLIST.md	New [x] bullet linking listing-verification coverage to this spec

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.