chore: update copyright from Red Hat, Inc to Red Hat, LLC

[waynesun09]

Summary

• Update LICENSE copyright holder from "Red Hat, Inc." to "Red Hat, LLC." to reflect the company's legal entity name change

[qodo-code-review]

PR Summary by Qodo

Update LICENSE copyright holder to Red Hat, LLC
📝 Documentation 🕐 Less than 5 minutes

Description

• Update LICENSE copyright holder from "Red Hat, Inc." to "Red Hat, LLC."
• Align legal attribution with Red Hat’s entity name change

High-Level Assessment

The direct edit to the LICENSE file is the simplest and most appropriate approach. Alternatives (e.g., adding a supplemental notice file) would add complexity without benefit for a straightforward legal name correction.

Files changed (1) +1 / -1

Documentation (1) +1 / -1

LICENSERename copyright holder to Red Hat, LLC +1/-1

Rename copyright holder to Red Hat, LLC

• Updates the Apache 2.0 license header attribution to reflect Red Hat’s legal entity name change from Inc. to LLC.

LICENSE

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Previous review results

Review updated until commit 62c40b6

Results up to commit 62c40b6

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[github-actions]

Site preview

Preview: https://5d419ddc-site.fullsend-ai.workers.dev

Commit: c5a34a78c02762ec1d6b075323826b2f0e30d1c5

[fullsend-ai-review]

🤖 Review · ❌ Terminated · Started 8:11 PM UTC · Ended 8:12 PM UTC
Commit: 7f5ce3c · View workflow run →

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

🤖 Finished Review · ❌ Failure · Started 8:11 PM UTC · Completed 8:12 PM UTC
Commit: 62c40b6 · View workflow run →

[qodo-code-review]

Code review by qodo was updated up to the latest commit 62c40b6

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 8:22 PM UTC · Completed 8:36 PM UTC
Commit: 62c40b6 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ❌ Failure · Started 8:24 PM UTC · Completed 8:25 PM UTC
Commit: c5a34a7 · View workflow run →

[fullsend-ai-retro]

Retro: PR #2702 — chore: update copyright from Red Hat, Inc to Red Hat, LLC

What happened

PR #2702 is a trivial 1-line change to the LICENSE file (changing "Red Hat, Inc." to "Red Hat, LLC."). The review agent was dispatched via workflow run 28262503589 and failed after 2 iterations, spending $0.28 and ~4 minutes without producing a review.

Root cause: The sandbox received env_count:0 (zero provider environment variables), and the agent definition (agents/review.md) was not loaded as the active agent persona. The agent received only the generic prompt "Run the agent task" with no PR context. It tried to ask for clarification via AskUserQuestion twice, was denied both times (autonomous mode), and gave up.

The workflow correctly set GITHUB_PR_URL, PR_NUMBER, REPO_FULL_NAME etc. in the step's env: block, and the harness config (harness/review.yaml) correctly references env/review.env with expand: true. The failure occurred somewhere between the workflow step environment and the sandbox bootstrap — the file-based env injection or agent definition upload did not complete successfully.

Existing coverage

Several related issues exist but do not cover the specific failure mode observed here:

• Add fast-path in review orchestrator for trivial bot-authored PRs #2639, Add lightweight review path for trivial bot dependency bumps #1358, Review orchestrator: add fast path for trivial docs/prompt-only changes #1900 — trivial PR fast-path proposals (related but orthogonal)
• fullsend run: add pre-flight Vertex AI authorization check before sandbox creation #1032 — pre-flight Vertex AI auth check (same spirit, different scope)
• Harness should fail fast on authentication errors instead of retrying #2058 — fail fast on auth errors (similar philosophy, narrower)
• Failed review agent runs should update the status comment on the PR #837 — failed review runs should update status comments (downstream of this issue)

Proposals

2 proposals filed below targeting fullsend-ai/fullsend (upstream platform).

Proposals filed

• Harness should validate agent definition and critical env vars before starting LLM conversation (in fullsend-ai/fullsend)
• Include agent name in hardcoded prompt so agent can self-orient on definition load failure (in fullsend-ai/fullsend)

[fullsend-ai-retro]

🤖 Retro · Started 7:08 AM UTC
Commit: c5a34a7 · View workflow run →