Update OWNERS file

[xueli181114]

Summary

• Update OWNERS file to match the latest configuration from hyperfleet-adapter

Test plan

• Verify OWNERS file format is correct
• Confirm appropriate maintainers and approvers are listed

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated configuration file formatting for consistency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The OWNERS file has been reformatted to use quoted string literals for the approvers and reviewers lists instead of unquoted scalars. The actual set of users and their roles remain unchanged, with no impact on functionality or validation logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Quick visual verification that all users are preserved in the conversion from unquoted to quoted format
• Minimal risk of introducing errors in a configuration file with no executable logic

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update OWNERS file' is concise and clearly identifies the main change: reformatting the OWNERS file with quoted string literals for approvers and reviewers.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7272d13 and 2e83114.

📒 Files selected for processing (1)

• OWNERS (1 hunks)

🔇 Additional comments (1)

OWNERS (1)

1-33: OWNERS file format looks good.

The YAML structure is valid, with properly quoted string literals for all approvers and reviewers entries. Both lists are correctly formatted and identical, which is appropriate for this use case.

One minor note: Line 2 and Line 19 contain "86254860", which appears to be a numeric GitHub user ID. Ensure this ID corresponds to an active/valid user account; if it represents an archived or removed user, consider replacing it with a current username.

If you haven't already, please verify that the numeric ID "86254860" and all listed usernames are valid, active GitHub users and appropriate maintainers for the project.

---

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

[yasun1]

/lgtm