[None][chore] Fix guardword

[tongyuantongyu]

Description

Guard word check does not like developer name in the codebase.

Test Coverage

Trivial comment modification.

PR Checklist

Please review the following before submitting your PR:

• PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

• PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

• Test cases are provided for new code paths (see test instructions)

• If PR introduces API changes, an appropriate PR label is added - either api-compatible or api-breaking. For api-breaking, include BREAKING in the PR title.

• Any new dependencies have been scanned for license and vulnerabilities

• CODEOWNERS updated if ownership changes

• Documentation updated as needed

• Update tava architecture diagram if there is a significant design change in PR.

• The reviewers assigned automatically/manually are appropriate for the PR.

• Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

To see a list of available CI bot commands, please comment /bot help.

Dev Engineer Review

• Updated the TODO comment in get_base_page_indices.
• Removed the author attribution that triggered the guard word check.
• Preserved the planned nanobind API migration note.
• No functional code, API, performance, error handling, or configuration changes.
• The comment-only change is consistent with the stated objective.

QA Engineer Review

No test changes.

[coderabbitai]

Walkthrough

The pull request removes author attribution from a TODO comment in get_base_page_indices. The nb::memview migration note remains unchanged.

Changes

Nanobind comment update

Layer / File(s)	Summary
Update migration TODO cpp/tensorrt_llm/nanobind/batch_manager/kvCacheManagerV2.cpp	The TODO comment removes the yaoy attribution and retains the nb::memview migration note.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: lowsfer

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the guardword fix and uses the required ticket and type format.
Description check	✅ Passed	The description explains the issue, identifies the comment-only solution, documents test coverage, and includes the completed checklist.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[tongyuantongyu]

/bot skip --comment "Comment changes only"

[tensorrt-cicd]

PR_Github #63736 [ skip ] triggered by Bot. Commit: 827132b Link to invocation

[tensorrt-cicd]

PR_Github #63736 [ skip ] completed with state SUCCESS. Commit: 827132b
Skipping testing for commit 827132b

Link to invocation