/**
 * Deterministic .feature parsing — Gherkin's surface is mechanical, so no
 * model runs here (Orienter.readFeatureFile carries no WorkOrder for the
 * same reason). The parse keeps exactly what the algorithm consumes:
 * feature-level tags, and per scenario its name, tags and step lines.
 *
 * Deliberately tolerant of the constructs it does not model: Background
 * steps are prepended to every scenario (they are preconditions of each),
 * Scenario Outlines keep their Examples rows as step lines (the scenario
 * is still one behavioral contract), and comments/empty lines vanish.
 */
import type { FeatureFile } from "./types.js";
export declare function parseFeatureText(path: string, text: string): FeatureFile;
export declare function readFeatureFileFromDisk(absolutePath: string, reportedPath: string): Promise<FeatureFile>;