Project Agent Guidance

License Headers

Add the repository's standard OceanBase copyright and Apache 2.0 license header to every new database source file, including C/C++ headers and Rust sources.
Scripts and build files, including Bazel files, do not require license headers.

Do not add project-name prefixes (Seekdb, SeekDB, or seekdb_) to new type or function names. Use namespaces or modules to distinguish names.
New C++ classes, including interface classes, do not need the legacy Ob prefix.
Keep the I prefix for interface classes. For example, use ICacheMemoryGetter instead of ObICacheMemoryGetter.
Do not rename existing types only to remove the Ob prefix unless the task explicitly requires it.

Use #pragma once in new C++ header files instead of macro-based #ifndef/#define include guards.

Before designing, implementing, or reviewing a Rust migration or refactor, read and follow Rust refactoring guidelines. This includes changes to C++ callers, CXX bridges, and build integration within that task.
Use CXX (#[cxx::bridge]) for Rust–C++ interoperability in both directions.
Extend the repository's existing CXX bridges and build integration; do not add handwritten C ABI bridges or another FFI framework for Rust–C++ calls.

For pull request or diff review tasks, read and follow .agents/skills/code-review/SKILL.md.

Prefer adding regression and correctness coverage to the repository's established test suites and test directories.
Keep test-only and benchmark-only files out of tools/.
Do not add tests for developer tools or scripts, including build, code-generation, packaging, and dependency-preparation tools, regardless of where the tests would live.
Validate tool and script changes by running the relevant commands and inspecting their outputs or generated artifacts.