#### What this PR does / why we need it?

#### Summary of your change

#### Please indicate you've done the following:

- [ ] For API changes, defined/updated the contract first: error codes, pagination, sorting/filtering, versioning, and field names.
- [ ] For API changes, confirmed the contract with frontend consumers before implementation.
- [ ] Kept changes inside the frozen module boundary or documented the cross-domain dependency.
- [ ] Made sure tests are passing and test coverage is added if needed.
- [ ] Ran the required release gates when touching high-risk areas: smoke, API regression, auth/token, permission, and rollback review.
- [ ] Confirmed the login -> knowledge base -> upload -> retrieval -> application -> permission -> API Key path is covered or documented why it is not affected.
- [ ] Confirmed coverage does not drop below the current ratchet target for touched core modules.
- [ ] Made sure commit message follow the rule of [Conventional Commits specification](https://www.conventionalcommits.org/).
- [ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.
