/**
 * `context-doc-stale` (report tier): a machine-generated context doc is older than
 * the code it claims to describe.
 *
 * These docs are inlined verbatim into every compiled phase skill, so they are
 * resident context on every turn of every phase. A stale one does not sit quietly
 * being out of date — it actively tells an agent something false at the moment the
 * agent is deciding what to build. One downstream repo's regenerated doc asserted
 * the project "contains no product runtime or cloud resources" four commits after a
 * verified AWS deployment (update-overwrites-authored-context/AC-18).
 *
 * **Only generated docs are reported.** A doc whose frontmatter lacks
 * `generated_by: aidlc-discover` is hand-owned, and `discover` already preserves it
 * (`discover/scanner.ts`'s `isMachineOwned`). Nagging about a hand-written doc would
 * punish exactly the behaviour that protection exists to encourage, and its author
 * maintains it on their own schedule. So the report has a permanent exit: write the
 * doc by hand, drop the marker, and it never fires again.
 *
 * **Why `report`.** The remedy is a person writing prose. `aidlc discover
 * --rediscover` would regenerate from a directory scan, which is what produced the
 * wrong text in the first place — a scanner cannot describe a seam. Doctor states
 * the condition and applies nothing, under any tier or flag, and never gates the
 * exit code (NFR-4).
 *
 * Requirements: update-overwrites-authored-context/AC-18, AC-19
 */
import type { CheckResult, DoctorContext, Migration } from '../types.js';
/**
 * The single source of pending-ness (`../types.ts`). Exported for the tests, which
 * drive it against fixture repositories.
 */
export declare function contextDocStaleCheck(ctx: DoctorContext): CheckResult;
export declare const contextDocStale: Migration;
//# sourceMappingURL=context-doc-stale.d.ts.map