/**
 * `composePath` — render a display path from a rule context's `displayRoot`
 * and a finding's accessor-relative `location.file`.
 *
 * Rules emit accessor-relative `location.file` values only; messages carry no
 * paths or coordinates. The format-time composition here lets the same rule
 * render different paths for publish (`displayRoot: ""`), registry-installed
 * skills, external skills, and workspace-scope findings.
 *
 * Relative rendered paths are posix and prefixed with `./` so logs are
 * unambiguous about relative-ness. Absolute finding paths are preserved for
 * files outside the workspace root. `location.line` / `location.column`
 * append as `:line:column` when present.
 *
 * @experimental This API is unstable and may change without notice.
 * @packageDocumentation
 */
import type { FindingLocation } from "./rule.js";
/**
 * Compose the rendered path for a finding.
 *
 * @param displayRoot - Context-supplied posix-relative root (or `""`).
 * @param location    - Accessor-relative or absolute file + optional coordinates.
 *
 * @experimental This API is unstable and may change without notice.
 */
export declare const composePath: (displayRoot: string, location: FindingLocation | undefined) => string;
//# sourceMappingURL=compose-path.d.ts.map