/**
 * Extract project-specific support guidance from a repo's SETUP.md (or similar
 * setup file). Two things feed the templates:
 *
 *   - projectContext  — WHY a correct environment matters for this project, woven
 *     into the "Why this matters" section of an external ticket.
 *   - corporateGuidance — an instruction telling the author/agent to rewrite the
 *     message in the organisation's standard support language, surfaced as an
 *     "adapt before sending" footer.
 *
 * Both are opt-in via explicit HTML-comment markers (precise, unambiguous); for
 * projectContext we also fall back to the first paragraph under a `## Why` /
 * `## Background` / `## Overview` / `## Purpose` / `## About` heading so existing
 * setup files contribute something without edits.
 *
 * Pure string parsing — the caller does the file read (integration). Marker names
 * are intentionally generic (`support:*`), carrying no tool branding into the
 * project's own setup file.
 */
export interface SupportGuidance {
    /** Why correct environment config matters here (markers win over the heading fallback). */
    projectContext?: string;
    /** How to adapt the outgoing message to corporate language. */
    corporateGuidance?: string;
    /**
     * Real routing metadata (assignment group, ticket prefix, …) the project chose
     * to publish. Rendered verbatim in the ticket's Environment block. Only ever
     * present when the setup file provides it — never inferred or invented.
     */
    routing?: string;
}
/** Parse SETUP.md text into the guidance the support templates consume. */
export declare function parseSupportGuidance(text: string): SupportGuidance;