msd-core/scripts/lint-response-language-coverage.cjs

#!/usr/bin/env node
/**
 * lint-response-language-coverage.cjs
 *
 * Enforces #2529: every workflow must be covered by the response-language
 * contract, so a workflow can never ship English-only when the user has
 * configured `response_language`.
 *
 * A workflow file passes when it contains EITHER:
 *   - a reference to the shared directive
 *     (`references/response-language-directive.md`), OR
 *   - its own inline `response_language` directive (the ~half of the catalog
 *     that already carried one before #2529, plus workflow-specific extracts
 *     like `references/execute-phase-response-language.md`).
 *
 * A bare config-field mention is not coverage: the same line must direct how
 * user-facing output is rendered, or the workflow must load a known directive.
 *
 * Nor is a directive that names only the question/answer surface. #2529's stated
 * defect is that inter-tool NARRATION stays in English while the answers around
 * it are translated, so a line saying "all user-facing questions, prompts, and
 * explanations" describes the gap rather than closing it. Coverage therefore
 * requires a narration-class token as well — see `NARRATION_CLASS_RE`.
 *
 * A workflow FRAGMENT (`<workflow>/<modes|steps|templates|detail>/<name>.md`, the
 * shape the #1671 fragment epic extracts — `detail/` is the fourth such
 * subdirectory kind, added by the #4403/ADR-4139 spine+detail split) additionally
 * passes when its parent workflow
 * names that exact fragment path and is itself covered — see
 * `inheritsParentCoverage`, which proves the inheritance per file instead of
 * granting it to a directory.
 *
 * Exit 0 only when workflows were actually found AND every one of them is
 * covered; exit 1 with a per-file listing if not. "No violations" alone is not
 * a pass: a run that inspected nothing has established nothing.
 */

'use strict';

const fs = require('fs');
const path = require('path');

const ROOT = path.join(__dirname, '..');
const WORKFLOWS_DIR = path.join(ROOT, 'msd-core', 'workflows');
// A reference resolves as a sibling of the workflow catalog, so a fixture tree
// and the real one resolve by one rule.
const REFERENCE_ROOT = path.join(ROOT, 'msd-core');
const DIRECTIVE_REFS = [
  'references/response-language-directive.md',
  'references/execute-phase-response-language.md',
];
// Names the narration class explicitly for the same reason the inline directives
// in the workflow bodies do (see NARRATION_CLASS_RE): "user-facing prose" alone
// reads, in practice, as the question/answer surface, which is the half of the
// output #2529 was never about.
const INLINE_RESPONSE_LANGUAGE_DIRECTIVE =
  'Apply response_language to all user-facing prose — narration between tool calls, status updates, progress notes, and findings included; preserve code, paths, and identifiers.';
// THE RULE THAT DECIDES THIS SET (#2529, restated in review round 29).
// A lazy-loaded mode/step/template carries its own directive only when it cannot
// PROVE inheritance -- no parent dispatches it from a read/execute context, or the
// parent is itself uncovered. Where inheritance is proven, the parent's directive is
// already in the loaded context by the time the fragment is read, so a second copy
// buys no coverage and adds a sentence that can drift. Pinning the exact wording is
// what makes the first case safe: these files cannot take the eager @-reference (an
// @-line inside a later Read is inert), so the sentence lives inline, and a partial
// typo or rewording would otherwise split the contract silently.
//  enforces the rule in both directions:
// no member of this set may be one that would inherit anyway.
const EXACT_INLINE_DIRECTIVE_WORKFLOWS = new Set([
  'discuss-phase/modes/advisor.md',
  'discuss-phase/modes/all.md',
  'discuss-phase/modes/analyze.md',
  'discuss-phase/modes/auto.md',
  'discuss-phase/modes/batch.md',
  'discuss-phase/modes/chain.md',
  'discuss-phase/modes/default.md',
  'discuss-phase/modes/power.md',
  'discuss-phase/modes/text.md',
  'discuss-phase/templates/context.md',
  'discuss-phase/templates/discussion-log.md',
  'execute-phase/steps/codebase-drift-gate.md',
  'execute-phase/steps/regression-gate-run.md',
  'execute-phase/steps/worktree-recovery-policy.md',
  'help/modes/brief.md',
  'help/modes/default.md',
  'help/modes/full.md',
  'help/modes/topic.md',
  'plan-phase/steps/prd-express-path.md',
  'quick-batch/steps/plan-checker-loop.md',
  'settings-advanced.md',
]);
// This lint once carried a third coverage form, for `verify-phase.md`: a
// workflow file nothing entered directly, covered instead by the directive
// execute-phase.md injects into its `msd-verifier` dispatch prompt. `next`
// deleted that workflow in #3421 (an orphan that shipped ~40 KB to every runtime
// and was never loaded) and migrated its live gates into the verifier, so the
// form has no subject left and is gone with it.
//
// The dispatch contract itself is NOT gone — the verifier subagent still runs and
// still emits user-facing prose, so `references/execute-phase-response-language.md`
// still tells the orchestrator to carry the directive into that prompt. It is
// simply no longer a statement about any file in this catalog, which is all this
// lint reads. `tests/response-language-coverage.test.cjs` pins both ends of it
// (the reference's directive text and the `Create VERIFICATION.md.` anchor it
// positions against in execute-phase.md) directly against the real tree.
// Fragment directories produced by the workflow-fragment epic (#1671). A file
// under one of these is a SECTION of its parent workflow, never an entry point:
// it is reached by a `read and execute msd-core/workflows/<path>` stub, which
// fires with the parent — and therefore the parent's response-language
// directive — already loaded.
//
// The stub is USUALLY in the top-level parent, which is the only case
// `inheritsParentCoverage` can prove, and it deliberately proves no more. Four
// fragments arrive by a different route today, and none of them relies on this
// function: `execute-phase/steps/regression-gate-run.md`,
// `plan-phase/steps/prd-express-path.md` and
// `quick-batch/steps/plan-checker-loop.md` are dispatched by a SIBLING fragment
// (`regression-gate.md`, `prd-express-gate.md`, `planner-wave.md`), and
// `help/modes/topic.md` is routed from a table in `help.md` that names the path
// without a dispatch verb at all. All four carry the pinned inline directive and
// are listed in `EXACT_INLINE_DIRECTIVE_WORKFLOWS`, so `findViolations` settles
// them before inheritance is ever consulted.
//
// Left as one hop on purpose. Walking the sibling chain would let a fragment
// inherit through a file this lint has not proven reachable, trading a loud
// failure for a quiet assumption; as it stands, extracting a fragment-of-a-
// fragment without pinning it turns the lint RED, which is the correct answer
// and names the file to fix.
// `detail` (ADR-4139 §6 Decision 6 / #4403) is the fourth fragment-directory kind,
// alongside modes/steps/templates from #1671: a spine's `detail/<part>.md` is
// reached the same way -- a `read and execute` stub in the top-level parent -- so
// it inherits coverage through the exact same mechanism, not a parallel one.
const FRAGMENT_DIRS = new Set(['modes', 'steps', 'templates', 'detail']);
const DIRECTIVE_ACTION_RE = /\b(?:apply|present|render|respond|translate|use|write|must|should)\b/i;
const USER_OUTPUT_RE = /\b(?:explanations?|language|narration|outputs?|prompts?|prose|questions?|templates?|user-facing)\b/i;
// The defect #2529 reports is NARRATION, not the question/answer surface: a
// directive worded as "all user-facing questions, prompts, and explanations" is
// read as covering what the user is asked and told at a turn boundary, and the
// running commentary the model emits between tool calls stays in English beside
// it. A line that names only that surface therefore certifies the exact gap the
// issue exists to close, so coverage additionally requires a narration-class
// token — narration, status, progress, findings, or output "between tool calls".
// Round 21 tightening: the accepted forms are the two that NAME the class — the
// word "narration", or output described as running "between tool calls". The
// earlier list also accepted a bare "status", "progress" or "findings", which
// are words that merely APPEAR in the canonical phrasing: a line reading "Use
// response_language for all user-facing output; report status." passed while
// naming nothing about inter-tool narration, i.e. weaker than REQ-LANG-04
// requires. Verified before tightening: all 79 catalog files that passed under
// the old list still pass under this one, so no workflow needed rewording — the
// dropped tokens were reachable only by directives nobody ships.
// Still deliberately not a phrase match: pinning one sentence would push authors
// toward copying wording instead of stating the rule (`tests/response-language-coverage.test.cjs`
// pins the old weak wording as a FAILING case so this cannot silently loosen).
const NARRATION_CLASS_RE = /\bnarration\b|\bbetween tool calls\b/i;
// The catalog's extensions, matched case-insensitively and by whole extension.
// `endsWith('.md')` failed in the one direction this lint cannot afford: it is
// silent UNDER-enforcement, the same vacuous pass `main()` refuses when
// discovery returns nothing. `SETTINGS.MD` is the same file to Windows and
// macOS and a different one to Linux, so a case-sensitive test exempts it on
// the only platform whose verdict gates the merge — a workflow certified by
// having gone unseen.
// `.mdx` stays out deliberately. Admitting an extension states what a workflow
// IS, and that claim has a second half: `inheritsParentCoverage` resolves a
// fragment's parent as `<workflow>.md`. If the repo ever emits an `.mdx`
// workflow, the entry belongs here next to the parent resolution it must move
// with, not ahead of it.
const WORKFLOW_EXTENSIONS = new Set(['.md']);

function isWorkflowFile(name) {
  return WORKFLOW_EXTENSIONS.has(path.extname(name).toLowerCase());
}

/**
 * Walk the catalog, FOLLOWING symlinked subtrees.
 *
 * `Dirent` uses lstat semantics, so a symlinked directory answers false to both
 * `isDirectory()` and `isFile()`. Branching on those alone skipped a symlinked
 * subtree in silence while `files.length > 0` kept the run green — the exact
 * "reported OK while coverage regressed" outcome `main()` claims to make
 * impossible. Each symlink is resolved with `statSync` and followed.
 *
 * Cycles are bounded by the `seen` set of resolved real paths: a link pointing
 * at an ancestor is entered once and not re-entered. A broken link resolves to
 * nothing and is skipped — it contributes no file to inspect, and no coverage
 * claim rides on it.
 */
function findMarkdownFilesRecursive(dir, seen = new Set()) {
  const files = [];
  let real;
  try { real = fs.realpathSync(dir); } catch { real = dir; }
  if (seen.has(real)) return files;
  seen.add(real);
  for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
    const full = path.join(dir, entry.name);
    let isDirectory = entry.isDirectory();
    let isFile = entry.isFile();
    if (entry.isSymbolicLink()) {
      let stat;
      try { stat = fs.statSync(full); } catch { continue; }
      isDirectory = stat.isDirectory();
      isFile = stat.isFile();
    }
    if (isDirectory) files.push(...findMarkdownFilesRecursive(full, seen));
    else if (isFile && isWorkflowFile(entry.name)) files.push(full);
  }
  return files.sort();
}

/**
 * Does the file LOAD a shared directive, rather than merely name one?
 *
 * The distinction is the same one `namesFragmentAsEntryPoint` draws a level
 * down, and it matters for the same reason: only a real `@`-import puts the
 * directive in context. A changelog line ("#2529: added the shared
 * response-language-directive.md reference"), a deprecation note, or any prose
 * naming the path proves nothing about what loads — but a bare substring test
 * cannot tell those apart, so such a workflow would be certified covered while
 * shipping the very defect #2529 exists to close.
 *
 * The catalog emits the import exactly one way: an `@`-path occupying the whole
 * line — line 1 for the 43 top-level workflows, line 96 for `execute-phase.md`.
 * Both `@~/` and `@$HOME/` spellings are accepted because the repo writes both
 * (see `scripts/strip-prose-atrefs.cjs`).
 *
 * LIMITATION, stated rather than papered over: like the fragment check, this
 * reads Markdown as text. An import inside a fenced block quoted as an example
 * still counts, and one whose line carries a trailing `<!-- ... -->` no longer
 * does. Neither shape occurs in the catalog today, and both would be visible in
 * review as a quoted or edited import.
 */
const DIRECTIVE_IMPORT_RES = DIRECTIVE_REFS.map(
  (ref) => new RegExp(`^@(?:~|\\$HOME)/\\S*${ref.replaceAll('.', '\\.')}$`),
);

function importsDirectiveReference(content) {
  return importedDirectiveReference(content) !== null;
}

/** Which known reference does this file import, if any? */
function importedDirectiveReference(content) {
  const lines = content.split(/\r?\n/).map((line) => line.trim());
  for (const [index, ref] of DIRECTIVE_REFS.entries()) {
    if (lines.some((line) => DIRECTIVE_IMPORT_RES[index].test(line))) return ref;
  }
  return null;
}

/**
 * The four-predicate test for an actionable directive on a single line.
 *
 * LIMITATION (text, not AST): the four hits are independent, so the predicate
 * reads vocabulary and not polarity. A line that negates the instruction —
 * "Do not translate narration; apply response_language to code only." — satisfies
 * all four and reads as coverage. Contrived rather than plausible: the wording is
 * pinned byte-for-byte in the files that cannot take the reference, and the shared
 * reference is validated against this same predicate, so a negated line would have
 * to be authored deliberately in one of the 44 files that carry their own sentence.
 * Named here because a predicate that cannot see "not" should say so.
 */
function carriesInlineDirective(content) {
  return content.split(/\r?\n/).some((line) =>
    /\bresponse_language\b/i.test(line) &&
    DIRECTIVE_ACTION_RE.test(line) &&
    USER_OUTPUT_RE.test(line) &&
    NARRATION_CLASS_RE.test(line)
  );
}

/**
 * Does the SHARED FILE a workflow imports itself carry an actionable directive?
 *
 * Checking only that the `@`-import LINE exists is a hole the size of the
 * bucket: 43 workflows take their entire coverage from one file, and nothing in
 * the repo pinned that file's text. Rewriting it back to the pre-#2529 wording —
 * the sentence this PR's own round-10 finding calls the DEFECT — left the lint
 * green and every workflow "covered". That is the same "the gate certifies the
 * defect" failure the round-10 fix closed, one level up.
 *
 * So an import is coverage only when the referenced file passes the very
 * predicate an inline directive must pass. A missing, unreadable, or weakened
 * reference covers nobody, and `main()` reports it as one systemic failure
 * rather than as 43 identical per-file violations.
 */
// Keyed by identity AND version, not by path alone. A path-only key is correct
// for a one-shot CLI and for the tests, where every fixture gets a fresh mkdtemp
// root — but it makes the verdict for a path permanent within the process, so a
// caller that rewrites a reference and re-asks gets the stale answer. Stamping
// size and mtime into the key costs one stat and removes the class rather than
// documenting it.
const referenceDirectiveCache = new Map();
function referenceCarriesDirective(ref, refRoot) {
  const file = path.join(refRoot, ref);
  let stamp = 'missing';
  try {
    const stat = fs.statSync(file);
    stamp = `${stat.size}:${stat.mtimeMs}`;
  } catch { /* keep the missing stamp; the read below decides the verdict */ }
  const key = [refRoot, ref, stamp].join('\u0000');
  if (!referenceDirectiveCache.has(key)) {
    let ok = false;
    try { ok = carriesInlineDirective(fs.readFileSync(file, 'utf8')); }
    catch { ok = false; }
    referenceDirectiveCache.set(key, ok);
  }
  return referenceDirectiveCache.get(key);
}

/**
 * Of the references these files actually import, which are missing, unreadable,
 * or no longer actionable?
 *
 * Scoped to imported references on purpose: a reference nobody imports cannot
 * uncover anybody, so failing on it would red a run over a file it never
 * consulted. Every reference that IS imported is load-bearing for every workflow
 * that imports it.
 */
function findBrokenDirectiveReferences(files, refRoot = REFERENCE_ROOT) {
  const imported = new Set();
  for (const file of files) {
    let content;
    try { content = fs.readFileSync(file, 'utf8'); } catch { continue; }
    const ref = importedDirectiveReference(content);
    if (ref !== null) imported.add(ref);
  }
  return [...imported].filter((ref) => !referenceCarriesDirective(ref, refRoot)).sort();
}

function hasResponseLanguageCoverage(content, refRoot = REFERENCE_ROOT) {
  const ref = importedDirectiveReference(content);
  if (ref !== null) return referenceCarriesDirective(ref, refRoot);

  return carriesInlineDirective(content);
}

/**
 * How far a read/execute verb may sit from the fragment path it governs on the
 * same line. Sized from the widest shape the catalog actually emits —
 * ``read and execute `msd-core/workflows/...` `` (14 characters between verb and
 * path) — with room for a variant, and deliberately far short of a sentence, so
 * a verb belonging to a different clause cannot reach across and vouch for a
 * path it never dispatches.
 */
const ENTRY_POINT_VERB_WINDOW = 40;
const ENTRY_POINT_VERB_RE = new RegExp(`\\b(?:read|execute|run)\\b.{0,${ENTRY_POINT_VERB_WINDOW}}$`, 'i');

/**
 * Does the parent name this fragment as a live ENTRY POINT, rather than merely
 * mentioning its path?
 *
 * The distinction is the whole basis of inherited coverage: the inheritance is
 * sound only because the fragment cannot be reached except through the parent's
 * dispatch stub, which fires with the parent's directive already loaded. A path
 * that appears in a changelog line, a deprecation note, or a comment proves
 * nothing about how the fragment is reached — but a bare substring test cannot
 * tell those apart, so before this check any mention at all granted coverage.
 *
 * The catalog emits exactly one shape, in five spellings: ``read and execute
 * `<path>` ``, ``Read+execute `<path>` ``, ``Read `<path>` if <condition>``,
 * ``run `<path>` to <effect>`` (the spelling #1689's per-plan executor routing
 * introduced), and the same stub written with the path RELATIVE to the catalog
 * rather than rooted at `msd-core/workflows/` (#3552's `branching_strategy:
 * none` arm). A read/execute/run verb within `ENTRY_POINT_VERB_WINDOW`
 * characters ahead of the path on the SAME LINE covers all five.
 *
 * LIMITATION, stated rather than papered over: this reads Markdown as text, not
 * as a parsed document. A dispatch stub that a future edit comments out with
 * `<!-- ... -->`, or moves inside a fenced block quoted as an example, still
 * matches — the verb and the path are both still there. Distinguishing those
 * needs a Markdown parser, and the cheap approximations (tracking fence state,
 * skipping `<!--` lines) buy little: neither shape occurs in the catalog today,
 * and both would be visible in review as a deleted dispatch. What this DOES
 * close is the common, invisible case — a path mentioned in prose that never
 * dispatches anything. `tests/response-language-coverage.test.cjs` pins both the
 * accepted spellings and the rejected mention forms.
 *
 * SECOND LIMITATION, same class: a dispatch line may sit inside a
 * `<!-- msd:section id="X" when="…" -->` guard, and nothing here checks that the
 * guard is satisfiable or that its `id` still matches the fragment it gates.
 * Every such pairing lines up today. If one drifts, the fragment becomes
 * unreachable while this function still calls it dispatched — an orphan the lint
 * reports as covered. That is not the defect #2529 is about: a dispatch that
 * never fires renders nothing, so no English prose reaches the user through it.
 * The gap is a soundness one, worth naming rather than implying.
 */
function namesFragmentAsEntryPoint(parent, relative) {
  // Two spellings of the same dispatch: catalog-rooted and catalog-RELATIVE.
  // #3552's `"none"` arm introduced the second one — `Read and execute
  // `execute-phase/steps/protected-branch.md`` — and a rooted-only needle read
  // that live dispatch as no dispatch at all.
  const needles = [`msd-core/workflows/${relative}`, relative];
  return parent.split(/\r?\n/).some((line) => needles.some((needle) => {
    const at = line.indexOf(needle);
    // A path character immediately before the match means this is the TAIL of
    // some longer path, not the fragment itself: `vendor/<relative>` must not
    // grant `<relative>` coverage. The rooted needle carries its own prefix and
    // is matched on its own, so nothing legitimate is lost here.
    if (at === -1 || (at > 0 && /[\w/.-]/.test(line.charAt(at - 1)))) return false;
    return ENTRY_POINT_VERB_RE.test(line.slice(0, at));
  }));
}

/**
 * A fragment inherits its parent workflow's coverage, but only when the
 * inheritance is PROVEN per file rather than assumed from the directory:
 *   1. the path is `<workflow>/<fragment-dir>/<name>.md`,
 *   2. `<workflow>.md` exists and dispatches this exact fragment path from a
 *      read/execute context — i.e. the parent really is the way in, not just a
 *      file that happens to spell the name (see `namesFragmentAsEntryPoint`), and
 *   3. the parent is itself covered.
 * A fragment nobody dispatches, or one hanging off an uncovered parent, stays a
 * violation. Without this the lint reds on every new fragment the #1671 epic
 * extracts, even though the extraction moved prose that was already covered.
 */
function inheritsParentCoverage(workflowsDir, relative, refRoot = REFERENCE_ROOT) {
  const segments = relative.split('/');
  if (segments.length !== 3 || !FRAGMENT_DIRS.has(segments[1])) return false;
  const parentPath = path.join(workflowsDir, `${segments[0]}.md`);
  if (!fs.existsSync(parentPath)) return false;
  const parent = fs.readFileSync(parentPath, 'utf8');
  if (!namesFragmentAsEntryPoint(parent, relative)) return false;
  return hasResponseLanguageCoverage(parent, refRoot);
}

function findViolations(workflowsDir, refRoot = REFERENCE_ROOT) {
  return findMarkdownFilesRecursive(workflowsDir).filter((file) => {
    const relative = path.relative(workflowsDir, file).replaceAll(path.sep, '/');
    const content = fs.readFileSync(file, 'utf8');
    if (EXACT_INLINE_DIRECTIVE_WORKFLOWS.has(relative)) {
      if (content.split(/\r?\n/).includes(INLINE_RESPONSE_LANGUAGE_DIRECTIVE)) return false;
      // The pin exists because these files cannot take the eager @-reference, not
      // because the reference is worse. If one ever CAN take it -- a fragment that
      // becomes eagerly loaded -- that conversion is strictly better than the pin and
      // must not read as a violation. Only the reference form is admitted here: its
      // wording is validated in turn by findBrokenDirectiveReferences, so the contract
      // survives the swap. An arbitrary reworded inline line stays a violation, which
      // is the whole point of pinning.
      return !importsDirectiveReference(content) || !hasResponseLanguageCoverage(content, refRoot);
    }
    if (hasResponseLanguageCoverage(content, refRoot)) return false;
    return !inheritsParentCoverage(workflowsDir, relative, refRoot);
  });
}

function main(workflowsDir = WORKFLOWS_DIR, io = console, refRoot = REFERENCE_ROOT) {
  // The catalog is discovered, not declared, so an unreadable or empty
  // directory yields an empty violation list — indistinguishable from full
  // coverage if the only success condition is `violations.length === 0`. Both
  // discovery failures below are therefore lint failures in their own right:
  // a stripped install tree, a `__dirname`-relative path typo, or an
  // unfollowed symlink must not be able to report OK while coverage silently
  // regresses to the pre-#2529 state.
  let files;
  try {
    files = findMarkdownFilesRecursive(workflowsDir);
  } catch (error) {
    if (error.code !== 'ENOENT' && error.code !== 'ENOTDIR') throw error;
    io.error(
      `lint-response-language-coverage: cannot read the workflow directory ${workflowsDir} (${error.code}).\n` +
      `Coverage cannot be established, so this is a failure and not a pass (#2529).`,
    );
    return 1;
  }

  if (files.length === 0) {
    io.error(
      `lint-response-language-coverage: no workflow files found under ${workflowsDir}.\n` +
      `A run that inspected zero workflows cannot establish coverage (#2529).`,
    );
    return 1;
  }

  // The shared references are checked ONCE, before the per-file pass. 43
  // workflows hold no directive of their own, so a reference that has gone
  // missing or been reworded back to the pre-#2529 sentence is a single
  // systemic failure, not 43 identical ones — and reporting it as 43 would bury
  // the cause under its symptoms.
  const brokenReferences = findBrokenDirectiveReferences(files, refRoot);
  if (brokenReferences.length > 0) {
    io.error(
      'lint-response-language-coverage: ' + brokenReferences.length +
      ' shared directive reference(s) no longer carry an actionable directive (#2529, REQ-LANG-04).\n' +
      'Workflows that @-import a reference take ALL of their coverage from it, so a missing,\n' +
      'unreadable, or reworded reference silently uncovers every one of them:\n\n' +
      brokenReferences.map((ref) => '  - ' + ref).join('\n') + '\n\n' +
      'The file must itself name the narration class on the same line as response_language\n' +
      '— the same rule an inline directive must satisfy.',
    );
    return 1;
  }

  const violations = findViolations(workflowsDir, refRoot);

  if (violations.length > 0) {
    io.error(
      `lint-response-language-coverage: ${violations.length} workflow(s) have no response-language coverage (#2529).\n` +
      `Each workflow must either @-reference a recognized response-language directive\n` +
      `or carry its own inline \`response_language\` directive (unless its parent dispatches it).\n` +
      `An inline directive names the narration class with the word "narration" or the phrase\n` +
      `"between tool calls" (REQ-LANG-04); enumerating status updates, progress notes or\n` +
      `findings without naming the class does not satisfy it:\n\n` +
      violations.map((file) => `  - ${path.relative(workflowsDir, file).replaceAll(path.sep, '/')}`).join('\n'),
    );
    return 1;
  }

  io.log(`lint-response-language-coverage: OK (${files.length} workflows covered)`);
  return 0;
}

if (require.main === module) process.exitCode = main();

module.exports = {
  EXACT_INLINE_DIRECTIVE_WORKFLOWS,
  INLINE_RESPONSE_LANGUAGE_DIRECTIVE,
  NARRATION_CLASS_RE,
  WORKFLOW_EXTENSIONS,
  WORKFLOWS_DIR,
  REFERENCE_ROOT,
  carriesInlineDirective,
  findBrokenDirectiveReferences,
  findMarkdownFilesRecursive,
  findViolations,
  hasResponseLanguageCoverage,
  importedDirectiveReference,
  importsDirectiveReference,
  inheritsParentCoverage,
  namesFragmentAsEntryPoint,
  main,
};