test(claude_code): rename misleading REPO_ROOT to SUITE_ROOT in test_v0_layout

[mateo-berri]

Relevant issues

Follow-up to a post-merge review of #32548

Linear ticket

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have added meaningful tests (none added; this is a pure variable rename with no behavior change)
• My PR passes all CI/CD checks (e.g., lint, format, unit tests)
• My PR's scope is as isolated as possible; it only solves 1 specific problem
• I have received a Greptile Confidence Score of at least 4/5 before requesting a maintainer review (Greptile reviews automatically once the PR is opened; only comment @greptileai to re-request a review after pushing changes)

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

Screenshots / Proof of Fix

This is a variable rename inside a structural test file with no runtime surface; it never touches the proxy, so there is no proxy behavior to demonstrate. The full _builder_unit_tests suite (203 tests) passes unchanged and make lint-e2e-basedpyright reports 0 errors at ec4639f

Type

🧹 Refactoring
✅ Test

Changes

In tests/e2e/claude_code/_builder_unit_tests/test_v0_layout.py, the module-level constant REPO_ROOT = Path(__file__).resolve().parents[1] actually resolves to tests/e2e/claude_code/ (the suite directory), not the repository root. Every sibling test file that names a variable REPO_ROOT uses parents[4], which is the real repo root, so the name here was misleading even though every usage was functionally correct. This renames it to SUITE_ROOT at all 10 occurrences in that one file (the definition, MANIFEST_PATH, and the path joins inside the layout tests). No paths, assertions, or test behavior change

QA runbook

The only change is a rename of a module-level path constant in _builder_unit_tests/test_v0_layout.py. These builder unit tests are structural (they verify the on-disk layout of the suite) and never drive a proxy, and no assertion changed, so there are no new manual steps to reproduce

Final Attestation

• The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

[greptile-apps]

Greptile Summary

This PR corrects a misleading constant name in one structural test file. REPO_ROOT was computed with parents[1], which resolves to tests/e2e/claude_code/ (the suite directory), not the repository root — but every other file that uses REPO_ROOT in the test tree uses parents[4], the actual repo root. The rename to SUITE_ROOT makes the intent accurate without touching any path values or assertions.

• Renames REPO_ROOT → SUITE_ROOT at all 10 occurrences (definition, MANIFEST_PATH, and 8 path-join sites) in test_v0_layout.py.
• No behavior change: the resolved path, the assertions, and the parametrized test cases are all identical after the rename.

Confidence Score: 5/5

Safe to merge — the change is a mechanical rename with no impact on resolved paths, test assertions, or any runtime surface.

Every change is a textual substitution of one identifier for another; the underlying Path(file).resolve().parents[1] expression and every downstream path join are unchanged. There is no logic to regress.

No files require special attention.

Important Files Changed

Filename	Overview
tests/e2e/claude_code/_builder_unit_tests/test_v0_layout.py	Pure rename of module-level constant REPO_ROOT → SUITE_ROOT at all 10 occurrences; no paths, assertions, or test behavior changed.

_{Reviews (1): Last reviewed commit: "test(claude_code): rename misleading REP..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[codspeed-hq]

Merging this PR will not alter performance

✅ 31 untouched benchmarks

---

_{Comparing litellm_v0_layout_suite_root (ec4639f) with litellm_internal_staging (ff4a40f)}