/**
 * The one place lint turns a document filename into the human label that opens
 * a finding message ("Skill manifest has unrecognized top-level field ...").
 *
 * Three copies of this switch used to exist — one in `issues-to-findings.ts`,
 * one in `catalog/shared/schema-rule.ts`, one in
 * `catalog/shared/manifest-json.ts` — and they had drifted: only one knew
 * `hook.json`, none knew `rule.json` or `knowledge.json`, and the parse-failure
 * copy defaulted to "Manifest" where the others defaulted to "Document".
 *
 * The manifest labels are derived from `MANIFEST_FILENAME_BY_TYPE` and
 * `extensionTypeSentenceLabels`, both of which are total over `ExtensionType`,
 * so a new extension type gets a label the moment its row lands in
 * `EXTENSION_TYPE_TABLE`.
 *
 * @experimental This API is unstable and may change without notice.
 * @packageDocumentation
 */
/** Label used when a filename matches no known document. */
export declare const UNKNOWN_DOCUMENT_LABEL = "Document";
/**
 * Describe the document at `file` for use as the subject of a finding message.
 *
 * Keyed by basename, so both bare accessor-relative filenames (`hook.json`,
 * as the per-extension rules pass) and workspace-relative paths
 * (`axm.json`, as `issues-to-findings` passes) resolve.
 *
 * @experimental This API is unstable and may change without notice.
 */
export declare const describeSchemaDocument: (file: string) => string;
//# sourceMappingURL=describe-document.d.ts.map