import type { PositionDocument, RollupDocument } from '@trazum/core';
import type { CliMessages } from './i18n/index.js';
import type { ProfileMarkdownInput } from './markdown.js';
/**
 * HTML for the person who does not run CLIs.
 *
 * One self-contained file: inline CSS, no scripts, no external assets — a
 * mail client, a wiki upload and a double-click all render it the same. It
 * is a **projection of the document `--json` prints**, taking the exact same
 * input object as the Markdown renderer: no second computation exists to
 * disagree with the first, and the parity guard in the suite walks every
 * figure here back to that document.
 *
 * The design rule this repository applies to its terminal output is applied
 * here where a designer would be tempted to grey it out: **the caveats are
 * furniture, not footnotes.** Unpriced models, skipped lines and the absent
 * fields render inside a bordered block ahead of the detail tables, at the
 * same visual weight as the totals they qualify — a forwarded report whose
 * limits can be cropped out is a lie by omission wearing this tool's name.
 *
 * Escaping is not optional politeness: labels, model ids and file paths come
 * from somebody's log, and a label is exactly where `<script>` would arrive.
 * Everything interpolated goes through `esc()`, tested with hostile labels.
 */
export declare function esc(value: string): string;
/** The profile as one self-contained page. Same input as the Markdown door. */
export declare function renderProfileHtml(input: ProfileMarkdownInput): string;
/**
 * The roll-up as one self-contained page — the team-facing document, for
 * exactly the person who does not run CLIs.
 *
 * The same discipline as the profile door: the input is the roll-up document
 * itself, the one `--json` prints and `conform` checks, so the page cannot
 * disagree with the data. Two things this page refuses to soften, because
 * they are the roll-up's whole honesty: **each contributor's gaps stay under
 * that contributor** — summing them away is the averaging this command
 * exists to refuse — and **the `cannotSay` caveats render in the caveat
 * block**, overlap-invisible included, so the one thing no merge can measure
 * cannot be cropped out of the forwarded copy.
 */
export declare function renderRollupHtml(document: RollupDocument, t: CliMessages): string;
/**
 * The position as one self-contained page — the third door the 1.64 arc's
 * discipline applies to: the input is the position document itself, the one
 * `--json` prints and `conform` checks, so the page cannot disagree with
 * the data. Every sentence is the terminal's own, through the same message
 * catalogue, which is what keeps the two surfaces saying the same thing in
 * the same words. The caveat block — what could not be measured, what is
 * deliberately unanswered, the records nobody can price — renders BEFORE
 * the positions, because a forwarded page gets cropped from the bottom.
 */
export declare function renderPositionHtml(document: PositionDocument, t: CliMessages): string;
//# sourceMappingURL=html.d.ts.map