cclaw-cli 7.7.1 → 8.1.1

package/dist/artifact-linter/shared.d.ts

@@ -1,637 +0,0 @@
-import { type DiscoveryMode, type FlowStage, type FlowTrack } from "../types.js";
-/**
- * Stages that run adaptive elicitation. The `qa_log_unconverged` rule
- * only fires for these. Other stages may still record a Q&A Log but no
- * convergence floor is enforced.
- */
-export declare const ELICITATION_STAGES: ReadonlySet<FlowStage>;
-/**
- * Language-neutral forcing-question topic descriptor.
- *
- * Each forcing-question row in a stage's checklist declares topics as
- * `id: human-readable label` pairs (e.g. `pain: what pain are we solving`).
- * The `id` (kebab-case ASCII) is the machine-key authors stamp on Q&A Log
- * rows via `[topic:<id>]` so the linter can verify coverage in ANY natural
- * language (RU/EN/UA/etc.). English keyword detection is intentionally
- * absent because it silently mis-reports convergence on RU/UA Q&A.
- */
-export interface ForcingQuestionTopic {
-    id: string;
-    topic: string;
-}
-export interface QaLogFloorOptions {
-    discoveryMode?: DiscoveryMode;
-    /**
-     * When true, downgrades the finding to advisory (`required: false`).
-     * Set when `--skip-questions` was persisted to the active stage flags.
-     */
-    skipQuestions?: boolean;
-    /**
-     * Optional pre-extracted forcing-question topic descriptors. When
-     * omitted, the evaluator calls `extractForcingQuestions(stage)` which
-     * scans the stage's checklist row. Strings are accepted as topic IDs
-     * (label = id) for callers that build their own list.
-     */
-    forcingQuestions?: ReadonlyArray<ForcingQuestionTopic | string>;
-}
-export interface QaLogFloorResult {
-    /** Whether convergence is satisfied (passes the gate). */
-    ok: boolean;
-    /** Substantive Q&A Log row count (excludes `skipped`/`waived` only rows). */
-    count: number;
-    /**
-     * Legacy field, retained for harness UI compatibility. Always 0 in
-     * the convergence floor no longer enforces a fixed count.
-     * Harness can still surface `questionBudgetHint(track, stage).recommended`
-     * as a soft hint, but it is NOT tied to gate blocking.
-     */
-    min: number;
-    /** Whether a stop-signal row was detected. */
-    hasStopSignal: boolean;
-    /**
-     * Legacy field, retained for harness UI compatibility. Always false in
-     * convergence semantics replaced the lite-tier short-circuit.
-     */
-    liteShortCircuit: boolean;
-    /** Whether `--skip-questions` flag downgraded the finding to advisory. */
-    skipQuestionsAdvisory: boolean;
-    /** Forcing-question topics deemed addressed (substring match in Q&A). */
-    forcingCovered: string[];
-    /** Forcing-question topics still pending (no matching Q&A row). */
-    forcingPending: string[];
-    /**
-     * True when the last 2 substantive rows have decision_impact marking
-     * `skip`/`continue`/`no-change`/`done`/etc. — i.e. Q&A is no longer
-     * surfacing decision-changing answers (Ralph-Loop convergence detector).
-     */
-    noNewDecisions: boolean;
-    /** Human-readable details for the linter finding. */
-    details: string;
-}
-/**
- * Parse a single checklist row into the list of forcing-question topic
- * descriptors it declares. Returns `null` when the row is not a
- * forcing-questions header. Throws when the header is found but its
- * body does not match the `id: topic; id: topic; ...` syntax — authors
- * fix the stage definition rather than silently ship un-coverable
- * topics.
- *
- * Exposed for unit tests that exercise the parser without depending on
- * the live stage schema.
- */
-export declare function parseForcingQuestionsRow(row: string, context?: string): ForcingQuestionTopic[] | null;
-/**
- * Extract forcing-question topics from a stage's checklist.
- *
- * Only the `id: topic; id: topic; ...` syntax is accepted. Throws when
- * the syntax is malformed so authors fix the stage definition rather
- * than silently shipping un-coverable topics.
- *
- * Returns empty array when no forcing-questions row is present (caller
- * treats absence as "no forcing requirement" — convergence falls back
- * to the no-new-decisions / stop-signal detectors). Returning [] when
- * the row exists but lists no segments is also legal.
- */
-export declare function extractForcingQuestions(stage: FlowStage): ForcingQuestionTopic[];
-/**
- * Evaluate the Q&A Log convergence floor for a brainstorm / scope /
- * design artifact. Returns ok=true when convergence is reached or any
- * escape hatch fires.
- *
- * Convergence sources (any one can set ok=true — see also
- * `adaptiveElicitationSkillMarkdown`):
- * - Every forcing-question topic id from the stage checklist is tagged
- *   `[topic:<id>]` on at least one `## Q&A Log` row.
- * - Ralph-Loop path: last 2 substantive rows read as no-new-decisions,
- *   substantive count ≥ max(2, questionBudgetHint(discoveryMode, stage).min),
- *   and not (guided/deep discovery with pending forcing-topic ids).
- * - Stop-signal row (`QA_LOG_STOP_SIGNAL_PATTERNS`).
- * - `--skip-questions` (`options.skipQuestions`): ok remains false but
- *   `skipQuestionsAdvisory` is true (linter treats as non-blocking).
- * - No forcing-questions row in the checklist and ≥1 substantive row.
- *
- * `[topic:<id>]` is the sole topic-coverage signal. The `min` and
- * `liteShortCircuit` fields stay for harness compatibility (min is
- * always 0; liteShortCircuit false).
- */
-export declare function evaluateQaLogFloor(qaLogBody: string | null, track: FlowTrack, stage: FlowStage, options?: QaLogFloorOptions): QaLogFloorResult;
-export interface LintFinding {
-    section: string;
-    required: boolean;
-    rule: string;
-    found: boolean;
-    details: string;
-}
-export interface LintFindingDedupSummary {
-    newCount: number;
-    repeatCount: number;
-    resolvedCount: number;
-    /**
-     * Short single-line human-facing summary of the dedup outcome. Empty
-     * string when there is nothing to report.
-     */
-    header: string;
-    /**
-     * Parallel to the `findings` array on `LintResult`; each status tags
-     * the finding at the same index as `new`, `repeat`, or `resolved`.
-     * `null` slots correspond to findings that weren't classified (for
-     * example, when the dedup cache is unreadable).
-     */
-    statuses: Array<{
-        kind: "new";
-    } | {
-        kind: "repeat";
-        count: number;
-    } | {
-        kind: "resolved";
-    } | null>;
-}
-export interface LintResult {
-    stage: string;
-    file: string;
-    passed: boolean;
-    findings: LintFinding[];
-    dedup?: LintFindingDedupSummary;
-}
-export declare function normalizeHeadingTitle(title: string): string;
-export type H2SectionMap = Map<string, string>;
-/**
- * Collect H2 sections and body content (`## Section Name`).
- *
- * - Ignores lines that live inside fenced code blocks (``` / ~~~) so a
- *   commented `## Approaches` inside an example doesn't open a phantom
- *   section and swallow real content.
- * - When the same heading appears more than once at the top level we
- *   concatenate the bodies rather than silently overwriting the earlier
- *   occurrence. This keeps lint rules honest when authors split a section
- *   into multiple passes.
- */
-export declare function extractH2Sections(markdown: string): H2SectionMap;
-export declare function duplicateH2Headings(markdown: string): string[];
-/**
- * Return the author-authored prose of an artifact, stripping linter meta
- * regions so free-text scans (placeholder tokens, scope-reduction phrases,
- * investigation trigger words) don't self-cannibalize by matching the
- * linter's own templated meta-phrases.
- *
- * Stripping rules (in order):
- *   1. `<!-- linter-meta --> ... <!-- /linter-meta -->` paired blocks.
- *      Both markers must appear on their own line; unterminated openings
- *      are left as-is so a malformed artifact cannot hide arbitrary
- *      content by omitting the closing marker.
- *   2. Every other HTML comment (`<!-- ... -->`, possibly multi-line).
- *   3. Fenced code blocks that are tagged `linter-rule` (e.g.
- *      ```` ```linter-rule ````). Plain fenced code blocks are preserved
- *      because many stages quote code samples that the linter should
- *      still see.
- *
- * The function guarantees the returned string is a strict subset of the
- * original: no characters are synthesized, and line offsets are
- * preserved for any surviving line (blank lines stand in for stripped
- * regions). This keeps regex-based linter checks stable when authors
- * add or remove linter-meta blocks between runs.
- */
-export declare function extractAuthoredBody(rawArtifact: string): string;
-export declare function headingPresent(sections: H2SectionMap, section: string): boolean;
-export declare function sectionBodyByName(sections: H2SectionMap, section: string): string | null;
-export declare function sectionBodyByAnyName(sections: H2SectionMap, sectionNames: string[]): string | null;
-export declare function sectionBodyByHeadingPrefix(sections: H2SectionMap, prefix: string): string | null;
-export interface CriticPredictionsContractCheck {
-    found: boolean;
-    details: string;
-}
-export declare function checkCriticPredictionsContract(sections: H2SectionMap): CriticPredictionsContractCheck | null;
-export interface LayeredDocumentReviewStatus {
-    triggeredReviewers: string[];
-    missingStructured: string[];
-    failOrPartialWithoutWaiver: string[];
-}
-export declare function evaluateLayeredDocumentReviewStatus(sections: H2SectionMap, confidenceFindingRegexSource: string): LayeredDocumentReviewStatus | null;
-/**
- * Build a regex that matches `<field>: <value>` even when the field name
- * and/or value are wrapped in markdown emphasis (`*`, `**`, `_`, `__`).
- *
- * The shipped templates render fields as `- **Field name:** value`, so any
- * structural check that searches for `Field:\s*token` against the rendered
- * artifact must tolerate the closing `**` between the colon and the value.
- *
- * `field` is treated as literal text (regex meta-characters are escaped).
- * `value` is inserted verbatim so callers can pass alternation
- * (`STARTUP|BUILDER|...`). `flags` defaults to case-insensitive Unicode.
- */
-export declare function markdownFieldRegex(field: string, value: string, flags?: string): RegExp;
-export declare function extractMarkdownSectionBody(markdown: string, section: string): string | null;
-export declare function headingLineIndex(markdown: string, section: string): number;
-export declare function parseShortCircuitStatus(sectionBody: string | null): string;
-export declare function isShortCircuitActivated(sectionBody: string | null): boolean;
-export declare function meaningfulLineCount(sectionBody: string): number;
-export declare function lineHasToken(line: string, token: string): boolean;
-export declare function countListItems(sectionBody: string): number;
-export declare function parseMarkdownTableRow(line: string): string[];
-export declare function tableHeaderCells(sectionBody: string): string[] | null;
-export declare function extractMinItemsFromRule(rule: string): number | null;
-export declare function tokensFromRule(rule: string): string[];
-export declare const VAGUE_AC_ADJECTIVES: string[];
-export declare function isSeparatorRow(line: string): boolean;
-export declare function getMarkdownTableRows(sectionBody: string): string[][];
-export type BinaryFlag = "yes" | "no" | "unknown";
-export declare function parseBinaryFlag(value: string): BinaryFlag;
-export declare function parseKeyedBinaryFlag(value: string, key: string): BinaryFlag;
-export declare function parseFailureModeRescueFlag(rescueCell: string): BinaryFlag;
-export declare function parseFailureModeTestFlag(rowText: string): BinaryFlag;
-export declare function validateFailureModeTable(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export declare const SCOPE_MODE_FULL_TOKENS: readonly string[];
-export type CanonicalScopeMode = (typeof SCOPE_MODE_FULL_TOKENS)[number];
-export declare const SCOPE_MODE_LINE_REGEX: RegExp;
-export declare const SCOPE_MODE_SHORT_TOKEN_REGEX: RegExp;
-export declare const SPEC_MAX_MODULES = 5;
-export declare const NEXT_STAGE_HANDOFF_REGEX: RegExp;
-export declare function hasCanonicalScopeMode(body: string): boolean;
-export declare function canonicalModesInText(text: string): CanonicalScopeMode[];
-export declare function shortModeToCanonical(text: string): CanonicalScopeMode | null;
-export declare function canonicalModeFromCandidate(candidate: string): CanonicalScopeMode | null;
-export declare function extractCanonicalScopeMode(body: string): CanonicalScopeMode | null;
-export declare function validateScopeSummary(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export declare const APPROACH_ROLE_VALUES: readonly ["baseline", "challenger", "wild-card"];
-export declare const APPROACH_UPSIDE_VALUES: readonly ["low", "modest", "high", "higher"];
-export declare const REQUIREMENT_PRIORITY_VALUES: readonly ["P0", "P1", "P2", "P3", "DROPPED"];
-export declare function normalizeTableToken(value: string): string;
-export declare function columnIndex(header: string[], expected: string): number;
-export declare function validateApproachesTaxonomy(sectionBody: string): {
-    rowCount: number;
-    roleUpsideOk: boolean;
-    challengerOk: boolean;
-    details: string;
-};
-export declare function validateCalibratedSelfReview(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export declare function validateRequirementsTaxonomy(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export interface InteractionEdgeCaseRequirement {
-    label: string;
-    pattern: RegExp;
-}
-export declare const INTERACTION_EDGE_CASE_REQUIREMENTS: readonly InteractionEdgeCaseRequirement[];
-/**
- * context for `validateInteractionEdgeCaseMatrix`.
- *
- * Background: a quick-tier test of a 3-file static landing page used
- * to trip "Interaction Edge Case row \"nav-away-mid-request\" must mark
- * Handled? as yes/no" because the author wrote `N/A` (no network at
- * all), then `unhandled must reference a deferred item id (for example
- * D-12)`. Two relaxations apply:
- *
- *   1. `N/A — <reason>` (em-dash + free-text reason) is now an
- *      accepted Handled? value. The reason replaces the D-XX
- *      requirement.
- *   2. When the caller signals lite-tier and the design has no
- *      network/external dependencies (detected via the Architecture
- *      Diagram body or a missing Failure Mode Table), the standard
- *      mandatory rows (`nav-away-mid-request`, `10K-result dataset`,
- *      `background-job abandonment`, `zombie connection`) are
- *      treated as advisory rather than required. The `double-click`
- *      row stays mandatory because UI duplicate-action handling is
- *      relevant even for static pages.
- */
-export interface InteractionEdgeCaseValidationContext {
-    /** Optional H2 sections map for cross-section "no network" detection. */
-    sections?: H2SectionMap | null;
-    /** When true, network-dependent mandatory rows become advisory. */
-    liteTier?: boolean;
-}
-export declare function validateInteractionEdgeCaseMatrix(sectionBody: string, context?: InteractionEdgeCaseValidationContext): {
-    ok: boolean;
-    details: string;
-};
-export declare const PRE_SCOPE_AUDIT_SIGNALS: ReadonlyArray<{
-    label: string;
-    pattern: RegExp;
-}>;
-export declare function validatePreScopeSystemAudit(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export declare const DIAGRAM_ARROW_PATTERN: RegExp;
-export declare const DIAGRAM_FAILURE_EDGE_PATTERN: RegExp;
-export declare const DIAGRAM_GENERIC_NODE_PATTERN: RegExp;
-/**
- * external-dependency keywords that trigger the
- * failure-edge requirement. The architecture diagram is allowed to
- * omit failure edges only when ALL of:
- *   - Failure Mode Table has zero rows.
- *   - The diagram body mentions no external-dependency keyword.
- *
- * Static landing pages (3 HTML/CSS/JS files, no network) match this:
- * no failure modes to map, no external systems to fail. The previous
- * blanket "must include at least one failure-edge" rule produced
- * ceremony-only failures that the agent worked around with fake
- * `(timeout)` annotations, defeating the spirit of the rule.
- */
-export declare const DIAGRAM_EXTERNAL_DEPENDENCY_PATTERN: RegExp;
-export declare const TEST_COMMAND_MARKER_PATTERN: RegExp;
-export declare const RED_FAILURE_MARKER_PATTERN: RegExp;
-export declare const GREEN_SUCCESS_MARKER_PATTERN: RegExp;
-export declare function diagramEdgeLines(sectionBody: string): string[];
-export declare function hasFailureEdgeInDiagram(sectionBody: string): boolean;
-export declare function hasLabeledDiagramArrow(lines: string[]): boolean;
-/**
- * accepted async edge patterns. Returns true when
- * a line carries any of:
- *
- *   - `-.->`, `-->>`, `~~>` (mermaid dotted/messaging arrows)
- *   - `- - ->` (loose dotted ASCII arrow with optional spaces)
- *   - `.....>` (3-or-more dots followed by `>`)
- *   - `\basync\b` text token (label-based)
- *   - `[async]` bracketed label, `async:` prefix, `async:` cell content
- *
- * The error message printed when this fails (see
- * `validateArchitectureDiagram`) lists every accepted pattern
- * verbatim so the agent does not have to guess.
- */
-export declare function hasAsyncDiagramEdge(lines: string[]): boolean;
-/**
- * accepted sync edge patterns. Returns true when a
- * line carries any of:
- *
- *   - `\bsync\b` text token (label-based)
- *   - `[sync]` bracketed label, `sync:` prefix, `sync:` cell content
- *   - Solid `-->`, `->`, `=>`, `→`, `⟶`, `↦` arrow that is NOT a known
- *     dotted/async variant (`-.->`, `-->>`, `~~>`)
- *   - `===>` (3+ `=` then `>`) and `--->` (3+ `-` then `>`) heavy solid
- *     arrows
- */
-export declare function hasSyncDiagramEdge(lines: string[]): boolean;
-/**
- * exact accepted-pattern list shown in the error
- * message when sync/async distinction fails. Keep in sync with
- * `hasAsyncDiagramEdge` / `hasSyncDiagramEdge` above.
- */
-export declare const DIAGRAM_SYNC_ASYNC_ACCEPTED_PATTERNS: readonly ["Solid arrows: `-->`, `->`, `===>`, `--->`, `=>`, `→`, `⟶`, `↦`", "Dotted/async arrows: `-.->`, `-->>`, `~~>`, `- - ->`, `.....>`", "Text labels on the same line: `sync` / `async`", "Bracket labels: `[sync]` / `[async]`", "Cell-prefix labels: `sync:` / `async:` (e.g. `A -->|sync: persist| B`)"];
-export interface ArchitectureDiagramValidationContext {
-    /** Optional H2 sections map for cross-section checks (e.g. Failure Mode Table presence). */
-    sections?: H2SectionMap | null;
-}
-export interface ArchitectureDiagramValidationResult {
-    ok: boolean;
-    details: string;
-}
-/**
- * Architecture Diagram structural check.
- *
- * Promoted out of `validateSectionBody` so it can take a `sections`
- * map and conditionally enforce the failure-edge rule based on
- * cross-section context (Failure Mode Table presence + diagram body
- * mentioning external-dependency keywords).
- */
-export declare function validateArchitectureDiagram(sectionBody: string, context?: ArchitectureDiagramValidationContext): ArchitectureDiagramValidationResult;
-/**
- * pointer-mode evidence acceptance. RED/GREEN sections may
- * substitute pasted stdout with a single line of the form
- * `Evidence: <relative-or-abs-path>` or `Evidence: spanId:<id>`. The
- * validator alone cannot reach the filesystem or delegation ledger
- * synchronously, so the lint pipeline pre-resolves pointers and then
- * passes booleans through these option flags.
- */
-export interface TddEvidencePointerOptions {
-    /**
-     * True when the section body has at least one `Evidence:` pointer line
-     * AND the pointer resolved to either an existing file or a known
-     * delegation spanId. The validator then short-circuits without
-     * requiring pasted stdout markers.
-     */
-    pointerSatisfied?: boolean;
-    /**
-     * true when `delegation-events.jsonl` carries at least
-     * one slice-tagged event for the current run with the matching phase
-     * (`phase=red` for RED, `phase=green` for GREEN) and a non-empty
-     * `evidenceRefs` array. Phase events are the new source of truth in
-     * the markdown evidence block is auto-satisfied without
-     * requiring hand-pasted stdout content.
-     */
-    phaseEventsSatisfied?: boolean;
-}
-/**
- * Sync helper that scans for `Evidence:` lines in a section body and
- * returns the trimmed value of each. Used by the lint pipeline to
- * pre-resolve pointers (filesystem path-existence or delegation ledger
- * spanId match) before invoking the validators.
- *
- * Recognised forms:
- *   Evidence: <path>
- *   Evidence: spanId:<id>
- *   - Evidence: <path>
- */
-export declare function extractEvidencePointers(sectionBody: string): string[];
-export declare function validateTddRedEvidence(sectionBody: string, opts?: TddEvidencePointerOptions): {
-    ok: boolean;
-    details: string;
-};
-export declare function validateTddGreenEvidence(sectionBody: string, opts?: TddEvidencePointerOptions): {
-    ok: boolean;
-    details: string;
-};
-export declare function validateVerificationLadder(sectionBody: string): {
-    ok: boolean;
-    details: string;
-};
-export declare function hasVerificationLadderTableRow(sectionBody: string): boolean;
-export type LearningEntryType = "rule" | "pattern" | "lesson" | "compound";
-export type LearningConfidence = "high" | "medium" | "low";
-export type LearningSeverity = "critical" | "important" | "suggestion";
-export type LearningSource = "stage" | "retro" | "compound" | "idea" | "manual";
-export interface LearningSeedEntry {
-    type: LearningEntryType;
-    trigger: string;
-    action: string;
-    confidence: LearningConfidence;
-    severity?: LearningSeverity;
-    stage?: FlowStage | null;
-    origin_stage?: FlowStage | null;
-    frequency?: number;
-    created?: string;
-    first_seen_ts?: string;
-    last_seen_ts?: string;
-    project?: string | null;
-    source?: LearningSource | null;
-}
-export interface LearningsParseResult {
-    ok: boolean;
-    none: boolean;
-    entries: LearningSeedEntry[];
-    errors: string[];
-    details: string;
-}
-/** Multiline block used by linter + learnings harvest stderr (identical text). */
-export declare function formatLearningsErrorsBullets(errors: string[]): string;
-export declare function learningsParseFailureHumanSummary(artifactRelPath: string, errors: string[]): string;
-export declare const LEARNING_TYPE_SET: Set<LearningEntryType>;
-export declare const LEARNING_CONFIDENCE_SET: Set<LearningConfidence>;
-export declare const LEARNING_SEVERITY_SET: Set<LearningSeverity>;
-export declare const LEARNING_SOURCE_SET: Set<LearningSource>;
-export declare const FLOW_STAGE_SET: Set<"brainstorm" | "scope" | "design" | "spec" | "plan" | "tdd" | "review" | "ship">;
-export declare const LEARNING_ALLOWED_KEYS: Set<string>;
-export declare function isIsoUtcTimestamp(value: string): boolean;
-export declare function isNullableString(value: unknown): value is string | null;
-export declare function isNullableStage(value: unknown): value is FlowStage | null;
-export declare function parseLearningSeedEntry(raw: unknown, index: number): {
-    ok: boolean;
-    entry?: LearningSeedEntry;
-    error?: string;
-};
-export declare function parseLearningsSection(sectionBody: string): LearningsParseResult;
-/**
- * file-path / reference detector for the
- * `investigation_path_first_missing` advisory rule.
- *
- * The detector is intentionally permissive: it only needs to recognize
- * "the author wrote down a path or ref" — the linter does NOT validate
- * the path resolves on disk. Patterns matched (any one is enough):
- *   - TS/JS/MD/JSON/YAML path with extension
- *     (`src/foo/bar.ts`, `tests/spec.test.ts`, `docs/quality-gates.md`).
- *   - Slash-bearing path under a known repo root prefix
- *     (`src/...`, `tests/...`, `docs/...`, `scripts/...`,
- *     `.cclaw/...`, `.cursor/...`, `node_modules/...`,
- *     `examples/...`, `e2e/...`).
- *   - GitHub-style ref (`owner/repo#123`, `org/repo@sha`,
- *     `path:line`, `path:line-line`).
- *   - Explicit `path:` / `paths:` / `ref:` / `refs:` marker.
- *   - Stable cclaw IDs (`R1`, `D-12`, `AC-3`, `T-4`, `S-2`, `DD-5`,
- *     `ADR-1`, `R-1`, `F-1`, `CR-1`, `I-1`, `QS-1`).
- *   - Backticked path-like token containing a slash.
- *
- * Exposed for unit tests (`tests/unit/investigation-trace-evaluator.test.ts`).
- */
-export declare const INVESTIGATION_TRACE_PATH_PATTERNS: readonly RegExp[];
-export interface InvestigationTraceFinding {
-    ok: boolean;
-    details: string;
-}
-/**
- * Internal core that does NOT depend on `StageLintContext`. Returned
- * shape is consumed by `evaluateInvestigationTrace` (which pushes a
- * finding into the context) and by unit tests that exercise the
- * detector directly.
- *
- * Returns `null` for sections that are missing, empty, or contain only
- * template scaffolding (table headers, separators, placeholder rows
- * with empty cells, lone `- None.` lines). Callers treat `null` as
- * silent — no finding is emitted.
- */
-export declare function checkInvestigationTrace(sectionBody: string | null): InvestigationTraceFinding | null;
-/**
- * advisory rule wired into the brainstorm / scope /
- * design / tdd / plan / review linters.
- *
- * Behavior contract:
- * - Section missing or empty / placeholder-only: silent (no finding).
- * - Section has substantive content with a recognizable file path /
- *   ref / explicit `path:`-style marker in the first non-empty rows:
- *   advisory pass (no finding).
- * - Section has substantive content but no path/ref signal: advisory
- *   FAIL finding with ruleId `investigation_path_first_missing`.
- *
- * The rule is `required: false` so it never blocks `stage-complete`.
- */
-export declare function evaluateInvestigationTrace(ctx: StageLintContext, sectionName: string): void;
-export declare function lineContainsVagueAdjective(text: string): string | null;
-export interface ParsedFrontmatter {
-    hasFrontmatter: boolean;
-    values: Record<string, string>;
-}
-export declare const FRONTMATTER_REQUIRED_KEYS: readonly ["stage", "schema_version", "version", "locked_decisions", "inputs_hash"];
-export declare const PLACEHOLDER_PATTERNS: Array<{
-    label: string;
-    regex: RegExp;
-}>;
-export declare const SCOPE_REDUCTION_PATTERNS: Array<{
-    label: string;
-    regex: RegExp;
-}>;
-export declare function parseFrontmatter(markdown: string): ParsedFrontmatter;
-export declare function extractDecisionIds(text: string): string[];
-export declare function extractRequirementIdsFromMarkdown(text: string): string[];
-export declare function extractAcceptanceCriterionIdsFromMarkdown(text: string): string[];
-export declare function collectPatternHits(text: string, patterns: Array<{
-    label: string;
-    regex: RegExp;
-}>): string[];
-export interface ValidateSectionBodyContext {
-    /**
-     * optional H2 sections map for cross-section
-     * checks (e.g. Architecture Diagram failure-edge enforcement gates
-     * on Failure Mode Table presence). When omitted, cross-section
-     * checks fall back to legacy blanket enforcement.
-     */
-    sections?: H2SectionMap | null;
-    /**
-     * when true, lite-tier-only relaxations apply.
-     * Currently used by the Interaction Edge Case matrix to demote
-     * network-dependent mandatory rows to advisory when the design has
-     * no Failure Mode Table rows and no external-dependency keywords
-     * in the Architecture Diagram body.
-     */
-    liteTier?: boolean;
-    /**
-     * pre-resolved RED/GREEN Evidence pointer state. The
-     * artifact linter resolves `Evidence: <path|spanId:...>` lines and
-     * inspects the TDD slice sidecar before invoking
-     * `validateSectionBody`; the resulting booleans here let the
-     * validator short-circuit without re-doing async work.
-     */
-    tddEvidence?: {
-        red?: TddEvidencePointerOptions;
-        green?: TddEvidencePointerOptions;
-    };
-}
-export declare function validateSectionBody(sectionBody: string, rule: string, sectionName: string, context?: ValidateSectionBodyContext): {
-    ok: boolean;
-    details: string;
-};
-export interface StageLintContext {
-    projectRoot: string;
-    stage: FlowStage;
-    track: FlowTrack;
-    discoveryMode: DiscoveryMode;
-    raw: string;
-    absFile: string;
-    sections: H2SectionMap;
-    findings: LintFinding[];
-    parsedFrontmatter: ParsedFrontmatter;
-    brainstormShortCircuitBody: string | null;
-    brainstormShortCircuitActivated: boolean;
-    scopePreAuditEnabled: boolean;
-    staleDiagramAuditEnabled: boolean;
-    isTrivialOverride: boolean;
-    overrideSet: Set<string> | null;
-    /**
-     * Stage-level flags persisted to flow-state.json `activeRun.currentStage.flags`
-     * (or equivalent). Used as escape-hatch signal for the Q&A floor rule
-     * (e.g. `--skip-questions` downgrades `qa_log_unconverged` to advisory).
-     * When orchestrator cannot read flow-state, defaults to an empty array.
-     */
-    activeStageFlags: string[];
-    /**
-     * task class for the active run, mirrored from
-     * `flow-state.json::taskClass`. `null` when not classified. Stage
-     * linters read this together with `track` via
-     * `shouldDemoteArtifactValidationByTrack` to demote advanced
-     * artifact-level checks (architecture diagram async/failure edges,
-     * interaction edge-case mandatory rows, stale-diagram drift,
-     * expansion-strategist delegation) from required → advisory.
-     */
-    taskClass: "software-standard" | "software-trivial" | "software-bugfix" | null;
-    /**
-     * `flow-state.json::packageVersion` when present.
-     */
-    packageVersion?: string | null;
-}