/**
 * Post-emit verification framework — generic interface.
 *
 * SpecVerse realize emits one or more LLM-authored source files per
 * owner (e.g. `backend/src/behaviors/<Owner>.ai.ts` for the TypeScript
 * stack). LLM emissions sometimes carry compile errors / lint issues
 * that don't show up at per-rule validation time (the realize-rules
 * manifest catches forbidden APIs, missing `.js` extensions, etc., but
 * not type mismatches or runtime semantics).
 *
 * A `PostEmitVerifier` runs AFTER all owners have emitted, on the
 * fully-realized output tree. It produces structured errors that the
 * feedback runner uses to drive a per-file re-emit pass.
 *
 * The interface is intentionally language-agnostic. The first
 * implementation is `tsc` for TypeScript stacks; future verifiers can
 * target Python (`mypy`/`ruff`), Go (`go vet`), Java (`mvn compile`),
 * Rust (`cargo check`), etc. Each verifier knows whether it `applies`
 * given the realized target (the manifest's stack tells you).
 *
 * Empirical motivation: 2026-05-13 idle-meta realize at engines 6.50.1
 * produced 48 backend tsc errors. Two hand-crafted feedback prompts
 * (AuthController.ai.ts + FormatNumberService.ai.ts) reduced this to
 * 37 errors with zero regressions. Extrapolation: a full feedback
 * sweep brings idle-meta from ~48 → ~5-10 errors per realize.
 */
export {};
//# sourceMappingURL=types.js.map