'use client';

import { SQLCommenterTag } from "./analyzer.mjs";

//#region src/sql/test-origin.d.ts
/**
 * Whether a query originated from a test file, decided from its SQLCommenter
 * `file` tag.
 *
 * The CI gate should never flag a query that no production route runs — e.g. a
 * read-back assertion in `tests/pg/postgres.test.ts` — yet before this such
 * queries had to be ignored one hash at a time (#3199). SQLCommenter already
 * carries the caller's file (surfaced in query detail per #2585); this reads it
 * so both the analyzer's gate and the server's alert engine can bucket
 * test-origin queries out with a single shared rule instead of drifting apart.
 *
 * Conservative by construction: the decision keys only off the `file` tag's
 * origin path. A query with no `file` tag is never test-origin, so untagged
 * codebases behave exactly as before.
 */
declare function isTestOriginQuery(tags: readonly SQLCommenterTag[] | undefined | null): boolean;
/**
 * Whether a source path looks like a test file. Query Doctor analyzes clients in
 * any language, so this spans the common cross-language conventions rather than
 * assuming JS/TS — directory-scoped (`tests/`, `__tests__/`, `spec/`, `e2e/`,
 * Maven's `src/test/`) and filename-scoped (`*.test.*` / `*.spec.*`, Python
 * `test_*.py` / `*_test.py`, Go `*_test.go`, Ruby `*_test.rb` / `*_spec.rb`,
 * Java `*Test.java`). Anchored on path separators so `testimonials/user.ts` or
 * `latest/report.py` don't get mistaken for tests.
 */
declare function isTestFilePath(path: string): boolean;
//#endregion
export { isTestFilePath, isTestOriginQuery };
//# sourceMappingURL=test-origin.d.mts.map