/**
 * @fileoverview Dialect for Breeding Management System (BMS) BrAPI servers —
 * the second most-deployed BrAPI stack in the CGIAR / partner crop community
 * (CIMMYT, IRRI, ICRISAT, IITA, CIP all run BMS instances). BMS predates the
 * BrAPI v2.1 plural-filter normalization and honors only the v2.0 singular
 * filter names on GET list endpoints — same translation engine the
 * SGN/Breedbase dialects use.
 *
 * Mappings are marked `verified: false` by default: we don't have a permanent
 * BMS test endpoint pinned, so the table follows the v2.0 naming pattern but
 * hasn't been independently narrowed against a live deployment. Field-test
 * results should flip individual entries to `verified: true` as they're
 * confirmed against IRRI, ICRISAT, IITA, or CIMMYT instances.
 *
 * Known BMS quirks NOT yet wired (deferred until a pinned test endpoint is
 * available):
 *   - 1-indexed pagination on some endpoints (`page=1` for the first page).
 *     Wiring this requires a `pageOffset` mechanism on the dialect interface,
 *     not just filter translation — track separately.
 *   - Inconsistent honoring of `commonCropName` vs `crop` on study queries.
 *   - Some endpoints expose only POST `/search/{noun}` (no GET filtering).
 *     The route resolver already handles this case via capability detection;
 *     the dialect doesn't need to declare anything special.
 *
 * @module services/brapi-dialect/bms-dialect
 */
export declare const bmsDialect: import("./types.js").BrapiDialect;
//# sourceMappingURL=bms-dialect.d.ts.map