Add black/flake8 dev deps and harden Jira Codex workflow

[jirhiker]

Summary

• add and to dev dependencies in
• regenerate to include new dev tools
• harden (safe outputs, curl fail-fast+retry, action SHA pinning, timeout, safer push)

Validation

• updated successfully after dependency changes

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 10e0d55be3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Copilot]

Pull request overview

This PR adds Python formatting/linting tools to the project’s dev dependency set (and regenerates uv.lock accordingly), and updates the Jira Codex GitHub Actions workflow to validate tool availability with the new setup.

Changes:

• Add black and flake8 to the dev dependency group in pyproject.toml.
• Regenerate uv.lock to include black, flake8, and their transitive dependencies.
• Adjust the Jira Codex workflow’s “Verify tooling exists” step to run tool version checks via uv.

Reviewed changes

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

File	Description
uv.lock	Updated lockfile to include black, flake8, and related packages.
pyproject.toml	Adds black/flake8 to [dependency-groups].dev and reorders dev deps.
.github/workflows/jira_codex_pr.yml	Updates tool verification commands to use uv run --with ….

[Copilot]

Pull request overview

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

The dev dependencies are not in alphabetical order. Currently: black, behave, flake8, faker, pyhamcrest, pytest, python-dotenv, requests.

Alphabetically they should be: behave, black, faker, flake8, pyhamcrest, pytest, python-dotenv, requests.

While this doesn't affect functionality, maintaining alphabetical order improves maintainability and reduces merge conflicts when adding new dependencies.