Add architecture info to list command TF request output

[kkaarreell]

Display architecture alongside artifacts URL in 'newa list' output to help users quickly identify which architecture a test request was executed on.

Resolves: #368

🤖 Generated with Claude Code

Summary by Sourcery

New Features:

• Display the architecture of each test request in the newa list command output when available.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds architecture information to the newa list test request output by appending an architecture suffix next to the artifacts URL when available, while preserving existing colored state/result formatting.

Flow diagram for updated newa list architecture output

flowchart TD
    A[Execute newa list] --> B[Iterate execute_job]
    B --> C[Get artifacts_url from execute_job.execution]
    B --> D[Get arch from execute_job.request]
    D --> E{arch is not None?}
    E -- Yes --> F[arch_suffix = ', arch: ' + arch.value]
    E -- No --> G[arch_suffix = empty string]
    C --> H[Format line with colored_state, colored_result, artifacts_url + arch_suffix]
    F --> H
    G --> H
    H --> I[Print formatted line]

Loading

File-Level Changes

Change	Details	Files
Display architecture alongside artifacts URL in list command output when available.	Retrieve architecture from the request object using getattr with a safe default Format architecture as a suffix string only when an architecture value exists Append the architecture suffix to the artifacts URL in the printed output while keeping state and result colorization intact	newa/cli/commands/list_cmd.py

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#368	Modify the newa list command output so that each listed request includes its architecture (when available) alongside state, result, and artifacts URL.	✅

Possibly linked issues

• Add arch info into "newa list" output #368: PR changes list command to append arch info to artifacts line, exactly implementing the requested output enhancement.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• When building arch_suffix, you assume arch has a .value attribute; if arch can be a plain string or another type in some cases, consider using str(arch) (or handling both Enum and non-Enum) to avoid potential attribute errors.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- When building `arch_suffix`, you assume `arch` has a `.value` attribute; if `arch` can be a plain string or another type in some cases, consider using `str(arch)` (or handling both Enum and non-Enum) to avoid potential attribute errors.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[kkaarreell]

Hey - I've left some high level feedback:

* When building `arch_suffix`, you assume `arch` has a `.value` attribute; if `arch` can be a plain string or another type in some cases, consider using `str(arch)` (or handling both Enum and non-Enum) to avoid potential attribute errors.

Prompt for AI Agents

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

The converter=Arch ensures that any value assigned to arch is automatically converted to an Arch enum. This means arch should only ever be:

1. An Arch enum instance, or
2. None