import type { RecheckConfig } from '../../types/index.js';
/**
 * Builds preset rule entries for a set of already-ported rule names: one
 * `recheck/<name>` entry each, `severity: 'error'`, and empty assertion
 * options (`{}`, i.e. upstream/rule defaults) — per spec §4.
 *
 * Message resolution (single source of truth, no hand-maintained message
 * strings duplicated here): for a **token** rule (every markdownlint-ported
 * rule from Task 5 onward), the message comes straight from that rule's own
 * `defaults.message` via `resolveAssertion` — the same default a user's
 * config falls back to when it omits `message` (see
 * rules/token/messages.ts formatTokenMessage). For a **scope** rule (the
 * pre-existing native rules, which have no `defaults` object at all — see
 * rules/types.ts ScopeRule), there's nothing to derive a message from, so
 * an explicit override in `messages` is required; passing one for a token
 * rule is also allowed and wins, in case a preset ever needs to override a
 * rule's wording. The current config schema still requires a non-empty
 * `message` on every rule (see schema.ts `required: [...]`) — that hasn't
 * changed, only where the string comes from at preset-build time.
 */
export declare function registerPresetRules(names: string[], messages?: Record<string, string>): RecheckConfig;
/**
 * Rule (short) names ported into the `recheck/markdown` preset so far. Each
 * batch task (5-10) appends the rule names it lands. Token-rule messages
 * are derived automatically from the rule's own `defaults.message` (see
 * defaultMessageFor above) — only list a name in MARKDOWN_PRESET_MESSAGES
 * if it's a scope rule (no `defaults`) or the preset wants to override the
 * rule's own wording.
 */
export declare const MARKDOWN_PRESET_RULES: string[];
/**
 * Explicit message overrides for markdown preset rules, keyed by (short)
 * rule name. Only needed for scope rules (which have no `defaults.message`
 * to derive from) or to override a token rule's own default wording — see
 * registerPresetRules/defaultMessageFor above. Empty today: every rule in
 * MARKDOWN_PRESET_RULES is a token rule and derives its message from its own
 * `defaults.message`. (`no-trailing-spaces` and `no-hard-tabs` needed
 * entries here before Task 11 removed the legacy scope rules that used to
 * shadow them via `resolveAssertion`'s scope-first resolution.)
 */
export declare const MARKDOWN_PRESET_MESSAGES: Record<string, string>;
export declare function buildMarkdownPreset(): RecheckConfig;
//# sourceMappingURL=markdown.d.ts.map