/** * Human-writing style — the bridge mirror (2026-10). * * THE BRIDGE OWNS NO COPY OF THE CLEANER. The cleanup itself lives in the * backend (`src/common/utils/human-style.ts`) and runs there, on the text as * it is stored, so there is exactly ONE implementation and it cannot drift * from what actually gets saved. * * What the bridge needs is the PROMPT TEXT — the rules an agent is told * before it writes — because the bridge is what composes the brief the agent * reads. This file mirrors the backend's block byte-for-byte, and * `tests/human-style.test.mjs` pins the two copies together: the repos are * separate, so nothing else stops them drifting, and a drift here means the * backend and the bridge tell the agent two different things. */ /** Words an agent should never use in prose. Mirrors the backend list. */ export declare const BANNED_WORDS: string[]; /** Phrases an agent should never use in prose. Mirrors the backend list. */ export declare const BANNED_PHRASES: string[]; /** * The full block, for long-form deliverables (CVs, reports, blog posts, * research briefs). Mirrors the backend's `WRITING_STYLE_BLOCK` exactly. */ export declare const WRITING_STYLE_BLOCK: string; /** * The light block, for agent chatter (task comments, chat replies, closing * summaries). Mirrors the backend's `WRITING_STYLE_BLOCK_LIGHT` exactly. */ export declare const WRITING_STYLE_BLOCK_LIGHT = "## Writing style\n\nDo not use em dashes (\u2014) or en dashes (\u2013) as punctuation. Use a comma, a full stop, a semicolon, a colon, parentheses, or a real conjunction (\"and\", \"but\", \"so\"). Skip the stock phrases: \"it's important to note\", \"it's worth noting\", \"delve into\", \"leverage\", \"unlock\", \"in conclusion\", \"furthermore\". Write plainly, the way a person would.\n\nMarkdown formatting renders inside a note, a document, a blog post, a chat message and a task description. In a task COMMENT it shows the raw characters, so write plain sentences there: no `**bold**`, no `*italic*`, no backticks, no `#` headings. A task description is the place for structure: short sections with `##` headings, `-` lists and code blocks where they help the reader.";