Prioritize recent flaky tests in the automated testing task

[gonzaloriestra]

WHY are these changes introduced?

The automated testing task starts with coverage gaps, leaving recurring CI failures competing with new test coverage for attention.

WHAT is this pull request doing?

Prioritize flaky-test fixes by reviewing every Main tests workflow run from the last seven days, including failed attempts and matrix jobs. Require evidence, check for existing fixes, investigate the cause, and repeat focused tests. Fall back to coverage improvements only when no actionable, non-duplicate flake remains.

Keep fixes focused and preserve useful assertions instead of hiding failures with retries or larger timeouts. Include representative failed-job links and validation limits in the PR description.

Label maintenance PR notifications as "CLI maintenance PR" so their repository context is clear.

Validated the instruction flow, workflow reference, notification text, and diff formatting. Instruction and message-only changes; no test execution needed.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

[Suleimanlatrsh]

Nice, this makes the task way more useful. Did you get a chance to try it with a workflow_dispatch run? The permissions block doesn't list actions, so I wasn't sure the bot can read run logs.

[gonzaloriestra]

@Suleimanlatrsh We can't try it until it gets merged. The repo is public, so I think you don't need permission to read the action logs. But let's merge and adjust if needed!

[gonzaloriestra]

@Suleimanlatrsh it worked, this PR mentions the flaky tests found.