@ttsc/unplugin 0.28.3 → 0.28.5

package/src/core/transform.ts

@@ -17,8 +17,12 @@ import type { TransformResult } from "unplugin";
 
 import type { ResolvedTtscUnpluginOptions } from "./options";
 import {
+  type ITtscProjectMembershipPolicy,
+  PERMISSIVE_PROJECT_MEMBERSHIP_POLICY,
   absolutizePathsTarget,
+  mergeMembershipPolicyOverlay,
   readEffectiveTsconfigPaths,
+  readProjectMembershipPolicy,
 } from "./tsconfigPaths";
 
 /**
@@ -34,22 +38,51 @@ export type TtscTransformResult = Exclude<
 >;
 
 /**
- * Normalised alias entry used when building the `paths` overlay for the
- * generated tsconfig. Derived from either a Vite array alias or a webpack/
- * Rspack object alias.
+ * One alias entry as the host declared it, before anything decides whether a
+ * tsconfig `paths` map can express it.
+ *
+ * Both of Vite's spellings reach here, the `{ "@": "/src" }` object and the `{
+ * find, replacement }` array, and only Vite's: `aliases` is populated in
+ * `vite.configResolved` alone, and every other adapter passes `undefined`. (The
+ * previous wording credited the object form to webpack and Rspack, which never
+ * supply one.)
+ *
+ * `find` is `unknown` rather than `string` because Vite's array form accepts a
+ * `RegExp`, and narrowing it here is what used to drop that form before the one
+ * place that could report the drop ever saw it (samchon/ttsc#1315).
  */
-export interface TtscTransformAlias {
-  /** The alias key (module specifier prefix). */
-  find: string;
+interface TtscDeclaredAlias {
+  /** The alias key, as declared: a module specifier prefix, or a `RegExp`. */
+  find: unknown;
   /** Absolute or cwd-relative path that the alias points to. */
   replacement: string;
 }
 
-/** One directory's cheap project-membership identity at generation time. */
+/** One directory's project-membership identity at generation time. */
 interface TtscProjectDirectorySnapshot {
   /** Absolute directory spelling used by the project walk. */
   path: string;
-  /** Metadata signature that changes when its immediate membership changes. */
+  /**
+   * Whether this directory's subtree can hold a program input.
+   *
+   * A directory that cannot is still walked and still watched, so a source
+   * appearing in it later is noticed, but it takes no part in the membership
+   * comparison. That is what lets a bundler create its output directory and
+   * fill it without voiding a generation no compiler input touched, for any
+   * output directory rather than for fifteen names (samchon/ttsc#1307).
+   */
+  relevant: boolean;
+  /**
+   * Digest of the entries the walk itself considers: every immediate child the
+   * ignore list does not drop, with its kind.
+   *
+   * Deliberately not the directory's own metadata. A directory's stamp moves
+   * whenever _any_ entry is added or removed, including the ones the walk
+   * exists to ignore, so a bundler emitting into `dist/` — or merely creating
+   * that directory for the first time — moved the project root's stamp and
+   * voided a generation that no compiler input had touched. The ignore list
+   * only protects the generation if the membership proof honours it too.
+   */
   signature: string;
 }
 
@@ -131,8 +164,52 @@ interface TtscFailedGenerationValidation {
   projectWalkFailures: string;
 }
 
-/** A bounded proof failure that stays authoritative until its inputs change. */
-class TtscUnstableGenerationError extends Error {
+/**
+ * A verdict about one generation that later deliveries replay instead of
+ * repeating the whole compile behind it.
+ *
+ * The two kinds are replayed on different evidence, and each carries its own: a
+ * pass verdict knows the pass it belongs to, and an unstable generation knows
+ * the recorded environment it was proven against.
+ */
+abstract class TtscTerminalGenerationError extends Error {}
+
+/**
+ * The compile succeeded and produced no output for one requested module,
+ * because the program does not contain it.
+ *
+ * Not a terminal generation error, and deliberately not a build failure. It is
+ * a fact about one file, and the answer to it is to leave that file to the host
+ * (samchon/ttsc#1308). It is a distinct type rather than a message match so the
+ * decision travels as a type: `@ttsc/metro` used to recognise this case by
+ * searching the message text for "did not return output", which is how one
+ * product came to hold two different answers to one condition.
+ */
+class TtscMissingProgramOutputError extends Error {
+  /** The module the bundler asked for. */
+  public readonly file: string;
+  /** The project config whose program does not contain it. */
+  public readonly tsconfig: string;
+  public constructor(file: string, tsconfig: string) {
+    super(
+      `ttsc: ${file} is not part of the program described by ${tsconfig}, so it was left untransformed. Add it to that project's "include" if ttsc plugins should apply to it.`,
+    );
+    this.name = "TtscMissingProgramOutputError";
+    this.file = file;
+    this.tsconfig = tsconfig;
+  }
+}
+
+/**
+ * A bounded proof failure that stays authoritative until its inputs change.
+ *
+ * This is the adapter failing to _obtain_ a coherent snapshot — a race it lost
+ * — so a later attempt may well succeed with the same inputs. It is retried
+ * when its recorded environment moves, and a new delivery epoch grants it the
+ * one fresh attempt the per-pass cache clear used to give it
+ * (samchon/ttsc#1300).
+ */
+class TtscUnstableGenerationError extends TtscTerminalGenerationError {
   public readonly validation: TtscFailedGenerationValidation;
 
   public constructor(
@@ -145,6 +222,56 @@ class TtscUnstableGenerationError extends Error {
   }
 }
 
+/**
+ * A compile this pass already attempted, whose envelope failed outright.
+ *
+ * The envelope cannot say whether the host reported diagnostics about the
+ * project or failed to run at all: an ordinary type error arrives as an
+ * `"exception"` carrying the compiler's own diagnostic text, exactly as a
+ * crashed host would. Sniffing that message to tell the two apart would be a
+ * guess, so the adapter uses the one boundary it genuinely owns. Inside a pass
+ * the answer is already settled, so every later module replays it instead of
+ * repeating a whole-project transform to reach the same verdict, which is what
+ * made a single broken save cost one compile per delivered module
+ * (samchon/ttsc#1303).
+ *
+ * The scope is exactly the pass. A host whose `buildStart` repeats drops the
+ * verdict at its next rebuild, so a transient host failure costs that one
+ * rebuild. A host with no pass boundary never retains one at all and keeps
+ * retrying on its very next delivery. Between them sits a host that opens
+ * exactly one pass for its whole process — Bun's runtime plugin, and a Vite dev
+ * server configured with `server.watch: null` — where the verdict lasts the
+ * session. That follows from what those hosts already publish about themselves,
+ * that their session is one immutable load session and the remedy for changed
+ * inputs is to restart, and it is the deliberate trade: without it, one type
+ * error costs such a session a whole-project compile per delivered module,
+ * which is the workload samchon/ttsc#970 is about.
+ *
+ * It carries the original error's message, stack and `cause` rather than
+ * replacing them, so what a bundler reports is what it reported before the
+ * verdict existed.
+ */
+class TtscPassVerdictError extends TtscTerminalGenerationError {
+  /** The delivery pass this verdict belongs to, and its whole scope. */
+  public readonly epoch: number;
+
+  public constructor(original: unknown, epoch: number) {
+    super(
+      original instanceof Error
+        ? original.message
+        : formatUnknownError(original),
+      { cause: original },
+    );
+    if (original instanceof Error) {
+      this.name = original.name;
+      if (original.stack !== undefined) this.stack = original.stack;
+    } else {
+      this.name = "TtscPassVerdictError";
+    }
+    this.epoch = epoch;
+  }
+}
+
 /** Proof witnesses retained beside a compiler result without extending its API. */
 const TRANSFORM_GENERATION_FAILURES = new WeakMap<
   ITtscCompilerTransformation,
@@ -157,10 +284,10 @@ const TRANSFORM_FAILED_GENERATION_VALIDATIONS = new WeakMap<
   TtscFailedGenerationValidation
 >();
 
-/** Rejected cache promises whose unchanged terminal verdict may be replayed. */
+/** Cache promises whose unchanged terminal verdict may be replayed. */
 const TERMINAL_TRANSFORM_GENERATIONS = new WeakMap<
   Promise<TtscCachedProjectTransform>,
-  TtscUnstableGenerationError
+  TtscTerminalGenerationError
 >();
 
 /** Maximum witnesses printed and retained for each failed transform attempt. */
@@ -228,6 +355,28 @@ export interface TtscCachedProjectTransform {
    * transform.
    */
   inputHashes: Record<string, string>;
+  /**
+   * What the resolved configuration admitted into this generation's program.
+   *
+   * Recorded per generation rather than read per validation because it is a
+   * property of the configuration the compile ran under, so a later delivery
+   * must judge membership by the same rule the compile did. A tsconfig edit
+   * that changes the rule also changes a declared input, which replaces the
+   * generation and its policy together.
+   */
+  membershipPolicy: ITtscProjectMembershipPolicy;
+  /**
+   * Files already reported as absent from the program, and the pass that
+   * reporting belongs to, so the notice is one per file per pass rather than
+   * one per delivery.
+   */
+  missingOutputReported?: Set<string>;
+  missingOutputEpoch?: number;
+  /**
+   * The project config this generation compiled, so a module the program does
+   * not contain can be told which program that was.
+   */
+  tsconfig: string;
   /**
    * Metadata signature of each {@link inputHashes} entry whose hash was proven
    * against an unracing read of the file on disk, in a tick the observed
@@ -290,10 +439,35 @@ export interface TtscCachedProjectTransform {
   projectRoot: string;
   /** Raw compiler output returned by {@link TtscCompiler.transform}. */
   result: ITtscCompilerTransformation;
+  /**
+   * The delivery epoch this generation is currently settled against, or
+   * `undefined` for a generation no epoch has proven.
+   *
+   * Set when the generation is compiled, and again whenever a later epoch's
+   * first delivery proves the whole generation still matches the filesystem.
+   * While it equals the cache's current epoch, each module's first delivery is
+   * settled by the supplied source alone, exactly as it was when every pass
+   * compiled its own generation (samchon/ttsc#1300).
+   */
+  deliveryEpoch?: number;
+  /**
+   * Whether this generation's non-error diagnostics have been surfaced at all,
+   * and the epoch they were last surfaced in.
+   *
+   * The diagnostics describe one compile of one program, so they belong to the
+   * generation rather than to a delivery; a pass that reuses a retained
+   * generation still surfaces them once, because a build's warnings are part of
+   * what that build reports (samchon/ttsc#1304). The two fields are separate so
+   * a persistent host, whose epoch is `undefined`, still reports the first
+   * time.
+   */
+  diagnosticsReported?: boolean;
+  diagnosticsEpoch?: number;
   /**
    * Files already delivered from this generation, keyed by filesystem identity.
-   * Build-scoped caches use this to skip persistent validation only for a
-   * module's first delivery inside the current build.
+   * A cache with a delivery epoch uses this to skip persistent validation only
+   * for a module's first delivery inside the current pass; the set is cleared
+   * whenever a new epoch's gate re-proves the generation.
    */
   servedFiles?: Set<string>;
   /**
@@ -387,10 +561,30 @@ const TRANSFORM_RESULT_FILESYSTEM = new WeakMap<
 >();
 
 /**
- * Caches whose owner has declared a real per-build lifecycle by calling
- * {@link beginTtscTransformBuild} before transforms begin.
+ * The current delivery epoch of each cache whose owner has declared a real
+ * per-pass lifecycle by calling {@link beginTtscTransformBuild}.
+ *
+ * A _delivery epoch_ is one bundler pass: the window inside which each module
+ * is requested at most once, so its first delivery may be settled against the
+ * state the pass started from. It is deliberately not the same fact as whether
+ * the generation is still valid, which the recorded snapshot answers.
+ * Conflating the two is what made every host with a repeating `buildStart` —
+ * webpack and Rspack watch, Rollup and Rolldown watch, `vite build --watch`,
+ * esbuild rebuild — discard a perfectly good whole-project compile on every
+ * edit (samchon/ttsc#1300).
+ *
+ * Absent from the map means persistent validation: a host with no pass boundary
+ * at all (a watching Vite dev server, Metro, the Turbopack loader), where every
+ * delivery proves the generation for itself.
  */
-const BUILD_SCOPED_TRANSFORM_CACHES = new WeakSet<TtscTransformCache>();
+const TRANSFORM_CACHE_EPOCHS = new WeakMap<TtscTransformCache, number>();
+
+/** The pass a delivery belongs to, or `undefined` under persistent validation. */
+function transformCacheEpoch(
+  cache: TtscTransformCache | undefined,
+): number | undefined {
+  return cache === undefined ? undefined : TRANSFORM_CACHE_EPOCHS.get(cache);
+}
 
 function createHostPathIdentityContext(
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
@@ -453,28 +647,41 @@ function resultFilesystem(
 }
 
 /**
- * Start a host build, clearing its prior generation and enabling constant-time
- * first delivery for modules compiled during this build.
+ * Open a new delivery pass, enabling constant-time first delivery for every
+ * module this pass asks for.
+ *
+ * This deliberately retains the cached generation. The pass boundary is a
+ * statement about _deliveries_ — each module is requested at most once inside
+ * it — not about whether the compiled program is still correct, which the
+ * generation's own recorded snapshot answers and which
+ * {@link matchesCachedSource} proves once at the pass's first delivery. Clearing
+ * here instead made a host whose `buildStart` repeats recompile the whole
+ * project on every rebuild even when no compiler input had changed
+ * (samchon/ttsc#1300). Use {@link resetTtscTransformCache} to actually discard a
+ * generation and its watchers.
  *
- * Hosts without a guaranteed build-start callback use persistent validation
- * unless they have another immutable lifecycle. Bun runtime setup, for example,
+ * Hosts without a guaranteed pass boundary use persistent validation unless
+ * they have another immutable lifecycle. Bun runtime setup, for example,
  * defines one process-scoped module-loading session.
  */
 export function beginTtscTransformBuild(cache: TtscTransformCache): void {
-  clearTtscTransformCache(cache);
-  BUILD_SCOPED_TRANSFORM_CACHES.add(cache);
+  TRANSFORM_CACHE_EPOCHS.set(
+    cache,
+    (TRANSFORM_CACHE_EPOCHS.get(cache) ?? 0) + 1,
+  );
 }
 
 /**
- * Clear a cache and return it to persistent validation mode.
+ * Discard every generation, dispose its watchers, and return the cache to
+ * persistent validation mode.
  *
- * This is distinct from {@link beginTtscTransformBuild}: hosts such as Vite's
- * development server may invoke `buildStart` only once for a process that spans
- * many edits, so that callback cannot authorize build-scoped shortcuts.
+ * This is the unconditional lifecycle boundary, and it is distinct from
+ * {@link beginTtscTransformBuild}: a pass ending is not a reason to throw a
+ * proven compile away, while a session ending is.
  */
 export function resetTtscTransformCache(cache: TtscTransformCache): void {
   clearTtscTransformCache(cache);
-  BUILD_SCOPED_TRANSFORM_CACHES.delete(cache);
+  TRANSFORM_CACHE_EPOCHS.delete(cache);
 }
 
 /** Dispose generation-owned filesystem resources before clearing a cache. */
@@ -589,16 +796,20 @@ export async function transformTtsc(
   });
 
   for (;;) {
+    // Read once per iteration, before the cache is consulted, so a delivery
+    // belongs to the pass that was current when it started examining the
+    // generation. A pass opened while this one awaits an in-flight compile is
+    // picked up by the next iteration, which is the one that runs when the
+    // entry it awaited turns out to have been superseded.
+    const epoch = transformCacheEpoch(cache);
     let transformed = cache?.get(key);
     if (transformed !== undefined) {
       const terminal = TERMINAL_TRANSFORM_GENERATIONS.get(transformed);
       if (terminal !== undefined) {
-        // A proof failure is a verdict about one observed environment, not an
-        // invitation for every later module to repeat the whole compile. Keep
-        // replaying it until a source/input probe or an explicit cache reset
-        // establishes that a new generation could differ.
+        // A terminal verdict is an answer about one observed environment, not an
+        // invitation for every later module to repeat the whole compile.
         if (
-          !failedGenerationEnvironmentChanged(terminal.validation, {
+          replaysTerminalGeneration(terminal, epoch, {
             currentFile: file,
             currentSource: source,
             filesystem,
@@ -621,9 +832,7 @@ export async function transformTtsc(
       if (cache?.get(key) !== transformed) {
         continue;
       }
-      const buildScoped =
-        cache !== undefined && BUILD_SCOPED_TRANSFORM_CACHES.has(cache);
-      if (!buildScoped) {
+      if (epoch === undefined) {
         await settleProjectMutationEvents(cached);
         if (cache?.get(key) !== transformed) {
           continue;
@@ -638,16 +847,33 @@ export async function transformTtsc(
           projectRoot: cached.projectRoot,
           result: cached.result,
         }) &&
-        matchesCachedSource(cached, file, source, buildScoped)
+        matchesCachedSource(cached, file, source, epoch)
       ) {
-        reportSuccessDiagnostics(cached.result);
+        reportSuccessDiagnostics(cached, epoch);
         // A resolved `"exception"` / `"failure"` envelope makes this throw;
-        // that is a failed generation too, so evict before surfacing it.
-        const code = selectOrEvict(cache, key, transformed, {
-          file,
-          projectRoot: cached.projectRoot,
-          result: cached.result,
-        });
+        // that is a failed generation too, so it is retained for this pass or
+        // evicted outside one before being surfaced.
+        let code: string;
+        try {
+          code = selectOrEvict(cache, key, transformed, epoch, {
+            file,
+            projectRoot: cached.projectRoot,
+            result: cached.result,
+            tsconfig: cached.tsconfig,
+          });
+        } catch (error) {
+          if (!(error instanceof TtscMissingProgramOutputError)) {
+            notifyFailedGenerationInputs(hooks, cached);
+            throw error;
+          }
+          // The compile is fine and simply has nothing for this module, so the
+          // module goes back to the host untransformed rather than failing the
+          // build (samchon/ttsc#1308). It still counts as delivered in this
+          // pass, and there is nothing to watch for a file with no output.
+          reportMissingProgramOutput(cached, error, epoch);
+          markCachedSourceServed(cached, file);
+          return undefined;
+        }
         notifyWatchInputs(hooks, cached, file);
         markCachedSourceServed(cached, file);
         return createTransformResult(source, code);
@@ -668,6 +894,10 @@ export async function transformTtsc(
         compilerOptions: options.compilerOptions,
         currentFile: file,
         currentSource: source,
+        // Stamp the pass this compile was started for, not the one it happens
+        // to finish in: a boundary crossed mid-compile leaves the generation
+        // belonging to the earlier pass, so the next pass re-proves it.
+        deliveryEpoch: epoch,
         filesystem,
         plugins: options.plugins,
         trackProjectMembership: cache !== undefined,
@@ -681,12 +911,24 @@ export async function transformTtsc(
       continue;
     }
     const { projectRoot, result } = cached;
-    reportSuccessDiagnostics(result);
-    const code = selectOrEvict(cache, key, generation, {
-      file,
-      projectRoot,
-      result,
-    });
+    reportSuccessDiagnostics(cached, epoch);
+    let code: string;
+    try {
+      code = selectOrEvict(cache, key, generation, epoch, {
+        file,
+        projectRoot,
+        result,
+        tsconfig: cached.tsconfig,
+      });
+    } catch (error) {
+      if (!(error instanceof TtscMissingProgramOutputError)) {
+        notifyFailedGenerationInputs(hooks, cached);
+        throw error;
+      }
+      reportMissingProgramOutput(cached, error, epoch);
+      markCachedSourceServed(cached, file);
+      return undefined;
+    }
     notifyWatchInputs(hooks, cached, file);
     markCachedSourceServed(cached, file);
     if (
@@ -730,29 +972,146 @@ async function awaitOrEvict(
 }
 
 /**
- * Extract the transformed source, evicting the generation when the result is a
- * host `"exception"` or compiler `"failure"` (which makes
- * {@link selectTransformedSource} throw). Such a failed generation must not be
- * replayed to later callers of an unchanged module.
+ * Extract the transformed source, and decide what a throwing generation is.
+ *
+ * {@link selectTransformedSource} throws for two different reasons, and only one
+ * of them is about the generation. A host `"exception"` or a compiler
+ * `"failure"` means the compile produced nothing for anyone: inside a pass that
+ * verdict is retained and replayed, because evicting it made every remaining
+ * module repeat the whole-project transform only to reach the identical answer
+ * (samchon/ttsc#1303), and outside a pass it keeps being evicted so a
+ * long-lived worker retries on its very next delivery exactly as before.
+ *
+ * A `"success"` envelope that has no output for the module asking is the other
+ * reason, and it is a fact about that one file: an ordinary condition for a
+ * module the bundle reaches and the tsconfig program does not contain. It is
+ * neither retained nor evicted. The error reaches the caller, and the
+ * generation, which compiled perfectly well for every other module, stays.
  */
 function selectOrEvict(
   cache: TtscTransformCache | undefined,
   key: string,
   generation: Promise<TtscCachedProjectTransform>,
+  epoch: number | undefined,
   props: {
     file: string;
     projectRoot: string;
     result: ITtscCompilerTransformation;
+    tsconfig: string;
   },
 ): string {
   try {
     return selectTransformedSource(props);
   } catch (error) {
-    evictGeneration(cache, key, generation);
+    const verdict = retainPassVerdict(
+      cache,
+      key,
+      generation,
+      epoch,
+      props.result,
+      error,
+    );
+    if (verdict !== undefined) {
+      throw verdict;
+    }
+    // A generation that compiled fine and simply has no output for the module
+    // asking is not a failed generation. Discarding it made every later module
+    // recompile the whole project to reach the same answer, which is the cost
+    // samchon/ttsc#1303 is about, for a bundle that merely reaches a file the
+    // tsconfig program does not contain.
+    if (props.result.type !== "success") {
+      evictGeneration(cache, key, generation);
+    }
     throw error;
   }
 }
 
+/**
+ * Retain the verdict of a compile this pass already attempted, or return
+ * `undefined` when nothing may be retained.
+ *
+ * Only inside a delivery pass. A pass is the window in which every delivery is
+ * settled against the state the pass started from, so an attempt it already
+ * made is part of that state and the remaining modules replay it rather than
+ * each repeating a whole-project transform to reach the same answer. Outside a
+ * pass there is no such window, and a long-lived worker must keep retrying on
+ * its very next delivery so a transient host failure never becomes permanent.
+ */
+function retainPassVerdict(
+  cache: TtscTransformCache | undefined,
+  key: string,
+  generation: Promise<TtscCachedProjectTransform>,
+  epoch: number | undefined,
+  result: ITtscCompilerTransformation,
+  error: unknown,
+): TtscTerminalGenerationError | undefined {
+  // Only an envelope that failed outright is a statement about the generation.
+  // `selectTransformedSource` also throws for a file the compile simply has no
+  // output for, which is an ordinary condition for a module the bundle reaches
+  // but the tsconfig program does not contain, and which says nothing about the
+  // other modules. Retaining that would fail the whole pass, naming a file none
+  // of them asked about.
+  if (
+    result.type === "success" ||
+    epoch === undefined ||
+    cache?.get(key) !== generation
+  ) {
+    return undefined;
+  }
+  const existing = TERMINAL_TRANSFORM_GENERATIONS.get(generation);
+  if (existing !== undefined) {
+    return existing;
+  }
+  const verdict = new TtscPassVerdictError(error, epoch);
+  TERMINAL_TRANSFORM_GENERATIONS.set(generation, verdict);
+  return verdict;
+}
+
+/**
+ * Whether a terminal verdict still answers for this delivery.
+ *
+ * Inside the pass that produced or confirmed it, it is replayed without
+ * re-probing anything: the pass settles every delivery against the state it
+ * started from, so re-walking the project once per module would spend exactly
+ * the cost this gate exists to remove.
+ *
+ * Across passes the two kinds part company. A pass verdict is dropped, because
+ * a new pass is the first boundary at which the host itself claims something
+ * may have changed, and the compile it stood for was never proven against a
+ * recorded environment. An unstable generation was, so it keeps its own rule:
+ * one fresh attempt per pass, and otherwise replayed until that recorded
+ * environment provably moves.
+ */
+function replaysTerminalGeneration(
+  terminal: TtscTerminalGenerationError,
+  epoch: number | undefined,
+  props: {
+    currentFile: string;
+    currentSource: string;
+    filesystem: TtscTransformFilesystemOperations;
+  },
+): boolean {
+  if (terminal instanceof TtscPassVerdictError) {
+    // A pass verdict has no recorded environment to re-confirm against, so the
+    // pass that produced it is its whole scope.
+    return epoch !== undefined && terminal.epoch === epoch;
+  }
+  if (!(terminal instanceof TtscUnstableGenerationError)) {
+    return false;
+  }
+  // An unstable generation does have one, and confirming it per delivery is the
+  // behaviour its own contract describes, so the pass does not cache that
+  // answer. A new pass still grants the fresh attempt the per-pass cache clear
+  // used to give it.
+  if (
+    epoch !== undefined &&
+    terminal.validation.cached.deliveryEpoch !== epoch
+  ) {
+    return false;
+  }
+  return !failedGenerationEnvironmentChanged(terminal.validation, props);
+}
+
 /**
  * Delete a failed generation from the cache only when it is still the entry
  * stored under `key`. The identity check prevents an older failed generation's
@@ -1204,6 +1563,51 @@ function collectDeclaredIdentities(
  * transform scratch tree (see
  * {@link TtscCachedProjectTransform.scratchDirectory}).
  */
+/**
+ * Register the failed generation's own project inputs so the host can observe
+ * the fix.
+ *
+ * A successful delivery registers the derived watch inputs, which is how a
+ * type-only file that no bundler graph contains still invalidates the modules
+ * depending on it. A failed one used to register nothing: `selectWatchInputs`
+ * returns an empty list for an `"exception"` envelope, and the throw happens
+ * before `notifyWatchInputs` is reached at all. When the failing compile is the
+ * first of a watching session, that leaves no channel through which the fix can
+ * arrive: the user repairs a file the bundler does not track, nothing is
+ * invalidated, and the error stays on screen (samchon/ttsc#1312).
+ *
+ * The generation records the project walk even when the compile failed, so the
+ * files a fix would touch are exactly what it already holds. The cost is paid
+ * only on a failure, and only until the next compile succeeds and narrows the
+ * set back to the derived inputs.
+ */
+function notifyFailedGenerationInputs(
+  hooks: TtscTransformHooks | undefined,
+  cached: TtscCachedProjectTransform,
+): void {
+  const addWatchFile = hooks?.addWatchFile;
+  if (addWatchFile === undefined) {
+    return;
+  }
+  for (const key of Object.keys(cached.inputHashes)) {
+    const input = path.resolve(cached.projectRoot, key);
+    if (isTransformScratchInput(input, cached.scratchDirectory)) {
+      continue;
+    }
+    // No evidence argument, deliberately. `missing: false` would be a claim
+    // this path cannot back: a failed generation is replayed for the rest of
+    // its pass without re-proving its inputs, so the walk that recorded them
+    // may be older than the delivery, and one of them having been deleted is a
+    // live reason for that compile to have failed. Letting the adapter probe
+    // also routes an absent input to the missing-input poll, which is the only
+    // channel through which restoring it can invalidate anything: a bundler
+    // watch on a path that does not exist registers nothing, and no module
+    // graph carries a type-only input. It costs one `existsSync` per input,
+    // and only where the adapter reads evidence at all, which is Vite serve.
+    addWatchFile(input);
+  }
+}
+
 function notifyWatchInputs(
   hooks: TtscTransformHooks | undefined,
   cached: TtscCachedProjectTransform,
@@ -1703,20 +2107,21 @@ export function createTransformResult(
  * state.
  *
  * Always compares the current module's in-memory source with the generation
- * snapshot. A cache whose owner called {@link beginTtscTransformBuild} can use
- * that comparison alone for a stable generation's first module delivery in the
- * current build. An incomplete generation may not take this shortcut: otherwise
- * a sibling output captured during a filesystem race could still be served
- * once. Later graph-bearing requests validate the file's derived input set and
- * project membership; graph-free envelopes conservatively re-hash the complete
- * project and out-of-walk snapshots. Any mismatch forces a complete
+ * snapshot. A cache with a delivery epoch can use that comparison alone for a
+ * stable generation's first delivery of each module in the current pass, once
+ * the pass's own first delivery has proven the whole generation still matches
+ * the filesystem. An incomplete generation may not take this shortcut:
+ * otherwise a sibling output captured during a filesystem race could still be
+ * served once. Later graph-bearing requests validate the file's derived input
+ * set and project membership; graph-free envelopes conservatively re-hash the
+ * complete project and out-of-walk snapshots. Any mismatch forces a complete
  * re-transform.
  */
 function matchesCachedSource(
   cached: TtscCachedProjectTransform,
   file: string,
   source: string,
-  buildScoped: boolean,
+  epoch: number | undefined,
 ): boolean {
   const identities = envelopeDerivation(cached).identityContext;
   const currentKey = toProjectKey(cached.projectRoot, file, identities);
@@ -1728,12 +2133,24 @@ function matchesCachedSource(
   if (expected !== hashText(source)) {
     return false;
   }
-  if (
-    buildScoped &&
-    cached.projectSnapshotComplete === true &&
-    !cached.servedFiles?.has(pathIdentityKey(file, identities))
-  ) {
-    return true;
+  if (epoch !== undefined && cached.projectSnapshotComplete === true) {
+    if (cached.deliveryEpoch !== epoch) {
+      // The pass's first delivery. The generation was settled against an
+      // earlier pass, so prove the whole of it once — every input the envelope
+      // declares, the directory membership, the universal host inputs, and the
+      // out-of-walk snapshot — before any of this pass's deliveries may be
+      // settled against it. That proof is what a per-pass recompile used to buy
+      // (samchon/ttsc#1300), at a walk instead of a compile.
+      if (!matchesCompleteInputSnapshot(cached, currentKey, source)) {
+        return false;
+      }
+      cached.deliveryEpoch = epoch;
+      cached.servedFiles?.clear();
+      return true;
+    }
+    if (!cached.servedFiles?.has(identity)) {
+      return true;
+    }
   }
   if (
     cached.result.type !== "exception" &&
@@ -2590,6 +3007,12 @@ function matchesCompleteInputSnapshot(
     cached.inputSignatures === undefined
       ? undefined
       : { hashes: cached.inputHashes, signatures: cached.inputSignatures },
+    {
+      // Judge membership by the rule the compile ran under, and read only the
+      // inputs this comparison actually consults.
+      declaredKeys: declaredInputs,
+      policy: cached.membershipPolicy,
+    },
   );
   if (!walkSnapshotComplete(current, declaredInputs)) {
     return false;
@@ -2961,9 +3384,17 @@ export function collectProjectInputHashes(
   projectRoot: string,
   identities: FilesystemPathIdentityContext = createHostPathIdentityContext(),
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
+  policy?: ITtscProjectMembershipPolicy,
 ): Record<string, string> {
-  return collectProjectInputSnapshot(projectRoot, identities, filesystem)
-    .hashes;
+  return collectProjectInputSnapshot(
+    projectRoot,
+    identities,
+    filesystem,
+    undefined,
+    {
+      policy,
+    },
+  ).hashes;
 }
 
 /** Hash project files and snapshot the directory topology in one walk. */
@@ -2975,6 +3406,16 @@ function collectProjectInputSnapshot(
     hashes: Record<string, string>;
     signatures: Record<string, string>;
   },
+  options?: {
+    /**
+     * Restrict hashing to these project keys. Supplied by a validating caller,
+     * which compares over exactly this set, and omitted by a capturing one,
+     * which has no generation to compare against yet.
+     */
+    declaredKeys?: ReadonlySet<string>;
+    /** What the resolved configuration admits into the program. */
+    policy?: ITtscProjectMembershipPolicy;
+  },
 ): {
   complete: boolean;
   directoryComplete: boolean;
@@ -2990,13 +3431,26 @@ function collectProjectInputSnapshot(
   const provenSignatures: Record<string, string> = {};
   const unstableFiles = new Set<string>();
   let attributed = true;
-  const walked = walkProjectInputs(projectRoot, filesystem);
+  const walked = walkProjectInputs(projectRoot, filesystem, options?.policy);
   const walkFailures = [...walked.failures];
   let complete = walked.complete;
   for (const file of walked.files) {
     try {
-      const before = inputMetadataEvidence(file, filesystem);
       const key = toProjectKey(projectRoot, file, identities);
+      // A caller validating a generation compares hashes over that
+      // generation's declared inputs alone (`sameHashes` takes the declared key
+      // set), so reading anything else is work whose result is never consulted.
+      // Skipping it is what keeps a directory full of emitted files from
+      // costing a read per file on the pass that first sees them
+      // (samchon/ttsc#1307). Capture passes supply no restriction and still
+      // record the whole walk.
+      if (
+        options?.declaredKeys !== undefined &&
+        !options.declaredKeys.has(key)
+      ) {
+        continue;
+      }
+      const before = inputMetadataEvidence(file, filesystem);
       // A file whose signature still equals the one captured around the read
       // that produced the recorded hash carries that content, so the whole
       // project does not have to be re-read to prove one delivery. A signature
@@ -3061,8 +3515,9 @@ function collectProjectInputSnapshot(
 }
 
 /**
- * Enumerate every regular file under `root`, skipping well-known output and
- * tooling directories (see {@link isIgnoredProjectDirectory}).
+ * Enumerate every regular file under `root`, skipping the directories no
+ * configuration can name ({@link isIgnoredProjectDirectory}) and the ones the
+ * resolved configuration excludes ({@link isExcludedProjectDirectory}).
  *
  * Uses an iterative DFS instead of `fs.readdirSync` recursion to avoid
  * unbounded call-stack depth on deep project trees. The result is sorted so
@@ -3071,6 +3526,7 @@ function collectProjectInputSnapshot(
 function walkProjectInputs(
   root: string,
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
+  policy: ITtscProjectMembershipPolicy = PERMISSIVE_PROJECT_MEMBERSHIP_POLICY,
 ): {
   complete: boolean;
   directories: TtscProjectDirectorySnapshot[];
@@ -3078,9 +3534,18 @@ function walkProjectInputs(
   files: string[];
 } {
   let complete = true;
-  const directories: TtscProjectDirectorySnapshot[] = [];
   const failures: TtscProjectWalkFailure[] = [];
   const files: string[] = [];
+  // Collected in one pass, then digested in a second. A directory's digest has
+  // to know whether each child directory can hold program inputs, and the walk
+  // learns that only after descending, so the two cannot be one pass.
+  const visited: {
+    childDirectories: string[];
+    entries: { name: string; kind: string; possible: boolean }[];
+    ownInput: boolean;
+    path: string;
+    stable: string | undefined;
+  }[] = [];
   const stack = [root];
   while (stack.length !== 0) {
     const current = stack.pop()!;
@@ -3112,34 +3577,108 @@ function walkProjectInputs(
         path: current,
       });
     }
-    directories.push({
+    const visit = {
+      childDirectories: [] as string[],
+      entries: [] as { name: string; kind: string; possible: boolean }[],
+      ownInput: false,
       path: current,
       // If membership moved during enumeration, force the next delivery to
       // replace this generation instead of blessing a torn directory/file
       // snapshot as stable.
-      signature:
+      stable:
         after !== undefined && before === after
-          ? after
+          ? undefined
           : `unstable:${before}:${after ?? "missing"}`,
-    });
+    };
     for (const entry of entries) {
       if (isIgnoredProjectDirectory(entry.name)) {
         continue;
       }
       const file = path.join(current, entry.name);
+      if (entry.isDirectory() && isExcludedProjectDirectory(file, policy)) {
+        continue;
+      }
+      const possible = isPossibleProgramEntry(entry, policy);
+      visit.entries.push({
+        kind: [
+          entry.isDirectory(),
+          entry.isFile(),
+          entry.isSymbolicLink(),
+        ].join(":"),
+        name: entry.name,
+        possible,
+      });
       if (entry.isDirectory()) {
+        visit.childDirectories.push(file);
         stack.push(file);
-      } else if (entry.isFile()) {
+      } else if (entry.isFile() && possible) {
+        // Only a file that could enter the program is hashed. A file that
+        // could not is either irrelevant to every generation, or it is one the
+        // compiler actually read, in which case the graph reports it and
+        // `isProjectWalkPath` now agrees it is out of the walk, so it is
+        // recorded and proven by the out-of-walk snapshot instead. Hashing an
+        // emitted tree here bought nothing and cost a read per file, including
+        // in `@ttsc/metro`, whose fingerprint re-keys every transformed file
+        // (samchon/ttsc#1307).
         files.push(file);
+        visit.ownInput = true;
       }
     }
+    visited.push(visit);
   }
+
+  // A directory matters to program membership only if its subtree can hold a
+  // program input. Propagate that up from the directories that hold one, so a
+  // bundler creating `out/` and filling it with JavaScript a project admitting
+  // none can never compile is not a membership change at any level: not in the
+  // directory itself, and not in the parent that now lists it
+  // (samchon/ttsc#1307).
+  const byPath = new Map(visited.map((visit) => [visit.path, visit]));
+  const relevant = new Set<string>();
+  for (const visit of visited) {
+    if (!visit.ownInput) {
+      continue;
+    }
+    let current: string | undefined = visit.path;
+    while (current !== undefined && !relevant.has(current)) {
+      relevant.add(current);
+      const parent = path.dirname(current);
+      current = parent === current || !byPath.has(parent) ? undefined : parent;
+    }
+  }
+
+  const directories: TtscProjectDirectorySnapshot[] = visited.map((visit) => {
+    const membership = visit.entries
+      .filter(
+        (entry) =>
+          entry.possible &&
+          (!visit.childDirectories.includes(
+            path.join(visit.path, entry.name),
+          ) ||
+            relevant.has(path.join(visit.path, entry.name))),
+      )
+      .map((entry) => `${entry.name}:${entry.kind}`);
+    return {
+      path: visit.path,
+      relevant: relevant.has(visit.path),
+      signature:
+        visit.stable ??
+        hashText(membership.sort().join(String.fromCharCode(0))),
+    };
+  });
   directories.sort((left, right) => left.path.localeCompare(right.path));
   files.sort();
   return { complete, directories, failures, files };
 }
 
-/** Return a cheap identity for one directory's immediate membership. */
+/**
+ * Return a directory's metadata stamp, used to detect that its membership moved
+ * _while_ the walk was enumerating it, and to feed the observed-clock floor.
+ *
+ * This is the right instrument for that job and the wrong one for comparing two
+ * generations: it moves for ignored entries too. {@link walkProjectInputs}
+ * records the filtered membership digest for the comparison instead.
+ */
 function projectDirectorySignature(
   directory: string,
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
@@ -3170,14 +3709,31 @@ function sameProjectDirectories(
   left: readonly TtscProjectDirectorySnapshot[],
   right: readonly TtscProjectDirectorySnapshot[],
 ): boolean {
-  return (
-    left.length === right.length &&
-    left.every(
-      (directory, index) =>
-        directory.path === right[index]?.path &&
-        directory.signature === right[index]?.signature,
-    )
-  );
+  // Compare only the directories that can hold program inputs, on either side.
+  // A directory irrelevant on both is not part of the program's membership at
+  // all, so its appearance, disappearance or churn says nothing: that is a
+  // bundler's output tree. One that gained or lost relevance is present in the
+  // comparison from the side where it counts, and so is caught.
+  const select = (
+    snapshots: readonly TtscProjectDirectorySnapshot[],
+  ): Map<string, TtscProjectDirectorySnapshot> =>
+    new Map(
+      snapshots
+        .filter((directory) => directory.relevant)
+        .map((directory) => [directory.path, directory]),
+    );
+  const leftRelevant = select(left);
+  const rightRelevant = select(right);
+  const paths = new Set([...leftRelevant.keys(), ...rightRelevant.keys()]);
+  for (const location of paths) {
+    if (
+      leftRelevant.get(location)?.signature !==
+      rightRelevant.get(location)?.signature
+    ) {
+      return false;
+    }
+  }
+  return true;
 }
 
 /**
@@ -3209,6 +3765,7 @@ function openDirectoryWatch(
 async function createProjectMutationTracker(
   directories: readonly TtscProjectDirectorySnapshot[],
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
+  policy: ITtscProjectMembershipPolicy = PERMISSIVE_PROJECT_MEMBERSHIP_POLICY,
 ): Promise<TtscProjectMutationTracker> {
   const tracker: TtscProjectMutationTracker = {
     changes: new Set(),
@@ -3223,6 +3780,13 @@ async function createProjectMutationTracker(
       directories.map((directory) => ({ directory: directory.path })),
       false,
       filesystem,
+      (location, filename) =>
+        reportsProgramMembership(
+          path.join(location, filename),
+          filename,
+          policy,
+          filesystem,
+        ),
     );
     return tracker;
   }
@@ -3238,14 +3802,26 @@ async function createProjectMutationTracker(
           filesystem,
           directory.path,
           (eventType, filename) => {
-            if (eventType === "rename") {
-              recordProjectMutation(
-                tracker,
-                filename === null
-                  ? directory.path
-                  : path.join(directory.path, filename),
-              );
+            if (eventType !== "rename") {
+              return;
+            }
+            if (
+              filename !== null &&
+              !reportsProgramMembership(
+                path.join(directory.path, filename),
+                filename,
+                policy,
+                filesystem,
+              )
+            ) {
+              return;
             }
+            recordProjectMutation(
+              tracker,
+              filename === null
+                ? directory.path
+                : path.join(directory.path, filename),
+            );
           },
           () => {
             tracker.failed = true;
@@ -3361,6 +3937,90 @@ async function createHostInputMutationTracker(
   return tracker;
 }
 
+/**
+ * Whether a path lies inside a directory the configuration excludes.
+ *
+ * Lexical, exactly like the walk and like {@link isProjectWalkPath}, and for the
+ * reason that predicate states: walk membership is lexical, so resolving a path
+ * to physical identity first would collapse two spellings the walk keeps apart
+ * and claim it covered a subtree it never followed. A junction whose target the
+ * walk hashes under its own name is exactly that, and canonicalizing here would
+ * suppress every event in it.
+ *
+ * `strictly` excludes an exact match, for the case where the excluded entry
+ * names a file rather than a directory: `exclude` accepts one, the walk applies
+ * exclusion to directories alone, so that file is still hashed and its events
+ * must keep counting.
+ */
+function insideExcludedProjectDirectory(
+  location: string,
+  policy: ITtscProjectMembershipPolicy,
+  strictly: boolean,
+): boolean {
+  if (policy.excludedDirectories.length === 0) {
+    return false;
+  }
+  const resolved = path.resolve(location);
+  return policy.excludedDirectories.some((excluded) => {
+    const target = path.resolve(excluded);
+    if (strictly && target === resolved) {
+      return false;
+    }
+    return pathIsWithin(resolved, target);
+  });
+}
+
+/**
+ * Whether one directory event can be a change to the program's membership.
+ *
+ * The live tracker has to answer the same question the membership digest does,
+ * or the two disagree about the same project: a bundler writing content-hashed
+ * output fires a rename per rebuild, and treating that as membership kept the
+ * cost samchon/ttsc#1307 removes on every host that has no build boundary,
+ * which is every host the narrow path exists for.
+ *
+ * A name that could be a program input counts, unless it sits under a directory
+ * the walk never descends into. A name that could not still counts when the
+ * path is now a directory, because the walk's watches were opened for the
+ * directories that existed when the generation was captured, so a directory
+ * created since is not watched and the sources that may appear in it would
+ * otherwise be invisible. A directory the configuration excludes is the
+ * exception: the walk cannot see inside it, so the tracker must not either, or
+ * emptying and recreating an `outDir` costs a compile per build. An event whose
+ * name the host did not report is unattributable and always counts.
+ */
+function reportsProgramMembership(
+  location: string,
+  filename: string,
+  policy: ITtscProjectMembershipPolicy,
+  filesystem: TtscTransformFilesystemOperations,
+): boolean {
+  if (isPossibleProgramFileName(filename, policy)) {
+    // A name the program could admit. It still says nothing if it lies inside a
+    // directory the walk never descends into, because the digest cannot see
+    // there either and the tracker must not be the one side that reacts.
+    return !insideExcludedProjectDirectory(location, policy, true);
+  }
+  let directory: boolean;
+  try {
+    directory = filesystem.lstat(location).isDirectory();
+  } catch {
+    // Gone again, or unreadable. Its name could not have been a program input,
+    // and a directory removed under this one reports its own contents leaving
+    // through the watch that was opened on it.
+    return false;
+  }
+  if (!directory) {
+    return false;
+  }
+  // A directory counts, because it can hold sources and the tracker is not
+  // watching it yet, unless the configuration says the program does not contain
+  // it. Emptying and recreating an `outDir`, which is what `emptyOutDir` and
+  // `output.clean` do on every build, would otherwise void the generation once
+  // per build on every host that has no build boundary.
+  return !insideExcludedProjectDirectory(location, policy, false);
+}
+
 /** Record enough exact mutation evidence without retaining an event stream. */
 function recordProjectMutation(
   tracker: TtscProjectMutationTracker,
@@ -3387,7 +4047,24 @@ interface WindowsProjectMutationBroker {
   trackers: Map<
     number,
     {
+      /**
+       * Whether one named event can be a program membership change. Present
+       * only for the project-directory tracker, which watches whole directories
+       * and so has to narrow what it hears; the trackers that watch exact names
+       * have already narrowed theirs by construction.
+       */
+      membership?: (location: string, filename: string) => boolean;
       ready: () => void;
+      /**
+       * The walk's own spelling for each canonical directory the child watches,
+       * so a reported event can be translated back before anything compares it
+       * with a path the walk or the configuration produced.
+       *
+       * Required, not optional. A registration that forgot it would fall back
+       * to the child's canonical spelling and silently reintroduce the mismatch
+       * this map exists to remove, with no type error and no failing test.
+       */
+      spellings: ReadonlyMap<string, string>;
       tracker: TtscProjectMutationTracker;
     }
   >;
@@ -3412,8 +4089,21 @@ async function registerWindowsProjectMutationTracker(
   locations: readonly WindowsMutationLocation[],
   allEvents: boolean,
   filesystem: TtscTransformFilesystemOperations,
+  /**
+   * Optional filter for the project-directory tracker, whose events have to be
+   * narrowed to program membership exactly as the in-process watcher's are. The
+   * name-watching trackers pass none, since they already watch exact names.
+   */
+  membership?: (location: string, filename: string) => boolean,
 ): Promise<void> {
   const broker = getWindowsProjectMutationBroker();
+  // The child watches canonical directories, and reports its events under that
+  // spelling. Everything else in the adapter speaks the walk's own spelling,
+  // which on Windows can be an 8.3 short form of the same directory, so keep
+  // the way back: a filter that compared the child's spelling against the
+  // configuration's would be comparing two names for one directory that share
+  // no common prefix (samchon/ttsc#1307).
+  const spellings = new Map<string, string>();
   const normalized = locations.map((location) => {
     let directory: string;
     try {
@@ -3421,6 +4111,7 @@ async function registerWindowsProjectMutationTracker(
     } catch {
       directory = path.resolve(location.directory);
     }
+    spellings.set(directory, location.directory);
     return {
       directory,
       ...(location.names === undefined ? {} : { names: location.names }),
@@ -3434,7 +4125,12 @@ async function registerWindowsProjectMutationTracker(
   const ready = new Promise<void>((resolve) => {
     resolveReady = resolve;
   });
-  broker.trackers.set(id, { ready: resolveReady, tracker });
+  broker.trackers.set(id, {
+    membership,
+    ready: resolveReady,
+    spellings,
+    tracker,
+  });
   tracker.drain = () => drainWindowsProjectMutationBroker(broker);
   tracker.close = () => {
     const active = broker.trackers.get(id);
@@ -3529,11 +4225,22 @@ function getWindowsProjectMutationBroker(): WindowsProjectMutationBroker {
     if (record.ready === true) registration.ready();
     if (record.ready !== true && record.failed !== true) {
       if (typeof record.directory === "string") {
+        // The walk's spelling for this directory, which is what every
+        // comparison and every recorded witness downstream expects.
+        const reported =
+          registration.spellings.get(record.directory) ?? record.directory;
+        if (
+          typeof record.filename === "string" &&
+          registration.membership !== undefined &&
+          !registration.membership(reported, record.filename)
+        ) {
+          return;
+        }
         recordProjectMutation(
           registration.tracker,
           typeof record.filename === "string"
-            ? path.join(record.directory, record.filename)
-            : record.directory,
+            ? path.join(reported, record.filename)
+            : reported,
         );
       } else {
         registration.tracker.membershipChanged = true;
@@ -3741,6 +4448,7 @@ export function isProjectWalkPath(
   file: string,
   _identities: FilesystemPathIdentityContext = createHostPathIdentityContext(),
   filesystem: TtscTransformFilesystemOperations = DEFAULT_FILESYSTEM_OPERATIONS,
+  policy: ITtscProjectMembershipPolicy = PERMISSIVE_PROJECT_MEMBERSHIP_POLICY,
 ): boolean {
   // Walk membership is lexical. Resolving `file` to physical identity first
   // would turn `root/alias/value.ts` into `root/target/value.ts`, hide the
@@ -3757,7 +4465,20 @@ export function isProjectWalkPath(
     return false;
   }
   const segments = relative.split(path.sep);
-  if (segments.some(isIgnoredProjectDirectory)) {
+  // The last segment is the file itself, which the walk names rather than
+  // descends into, so only the directory components decide walk membership.
+  if (segments.slice(0, -1).some(isIgnoredProjectDirectory)) {
+    return false;
+  }
+  if (isExcludedProjectDirectory(path.dirname(path.resolve(file)), policy)) {
+    return false;
+  }
+  // The walk hashes only files that could enter the program, so a path it does
+  // not hash is out of the walk by definition. Answering otherwise would leave
+  // a graph input the compiler really read in neither snapshot: absent from
+  // `inputHashes` because the walk skipped it, and absent from the out-of-walk
+  // snapshot because this predicate claimed the walk covered it.
+  if (!isPossibleProgramFileName(path.basename(file), policy)) {
     return false;
   }
   let current = resolvedRoot;
@@ -3889,6 +4610,7 @@ function matchesCachedExternalInputs(cached: TtscCachedProjectTransform): {
  */
 function selectExternalInputPaths(props: {
   filesystem?: TtscTransformFilesystemOperations;
+  membershipPolicy: ITtscProjectMembershipPolicy;
   projectRoot: string;
   result: ITtscCompilerTransformation;
   scratchDirectory?: string;
@@ -3970,7 +4692,13 @@ function selectExternalInputPaths(props: {
       isTransformScratchInput(absolute, props.scratchDirectory) ||
       seen.has(spelling) ||
       (!missingCandidate &&
-        isProjectWalkPath(props.projectRoot, absolute, identities, filesystem))
+        isProjectWalkPath(
+          props.projectRoot,
+          absolute,
+          identities,
+          filesystem,
+          props.membershipPolicy,
+        ))
     ) {
       continue;
     }
@@ -4155,22 +4883,57 @@ function insideProject(directory: string, projectRoot: string): boolean {
 const NOTIFIABLE_ABSENCE_DIRECTORY_LIMIT = 512;
 
 function isIgnoredProjectDirectory(name: string): boolean {
-  return (
-    name === ".git" ||
-    name === ".ttsc" ||
-    name === ".cache" ||
-    name === ".next" ||
-    name === ".nuxt" ||
-    name === ".svelte-kit" ||
-    name === ".turbo" ||
-    name === ".vite" ||
-    name === "build" ||
-    name === "coverage" ||
-    name === "dist" ||
-    name === "node_modules" ||
-    name === "out" ||
-    name === "temp" ||
-    name === "tmp"
+  // The residue of what used to be a fifteen-name list, kept to the three
+  // directories no tsconfig can name and no program can contain: the VCS
+  // store, the package manager's tree (TypeScript's own default `exclude`
+  // carries it too), and ttsc's own plugin cache. Everything else the old list
+  // guessed at, and guessing was wrong in both directions: a bundler writing
+  // to an unnamed directory changed project membership with its own output,
+  // while a real source directory named `build` or `temp` was dropped from the
+  // walk and its new files were never seen (samchon/ttsc#1307). Those are now
+  // decided by `ITtscProjectMembershipPolicy`, which reads the configuration
+  // that actually knows.
+  return name === ".git" || name === ".ttsc" || name === "node_modules";
+}
+
+/**
+ * Whether the resolved configuration keeps this directory out of the program.
+ *
+ * Compared by physical containment rather than by name, so `outDir: "./dist"`
+ * excludes that one directory instead of every directory called `dist` at every
+ * depth, which is the distinction the name list could not draw.
+ */
+function isExcludedProjectDirectory(
+  directory: string,
+  policy: ITtscProjectMembershipPolicy,
+): boolean {
+  return insideExcludedProjectDirectory(directory, policy, false);
+}
+
+/**
+ * Whether this entry could enter the program, and so whether its appearance or
+ * removal is a membership change.
+ *
+ * A directory always could, since it can hold sources. A file could only if it
+ * carries an extension the resolved configuration admits, which is what makes a
+ * bundle emitted beside the sources invisible to a project that compiles no
+ * JavaScript.
+ */
+function isPossibleProgramEntry(
+  entry: fs.Dirent,
+  policy: ITtscProjectMembershipPolicy,
+): boolean {
+  return entry.isFile() ? isPossibleProgramFileName(entry.name, policy) : true;
+}
+
+/** The same question for a bare file name, for callers holding no `Dirent`. */
+function isPossibleProgramFileName(
+  name: string,
+  policy: ITtscProjectMembershipPolicy,
+): boolean {
+  const lowered = name.toLowerCase();
+  return policy.inputExtensions.some((extension) =>
+    lowered.endsWith(extension),
   );
 }
 
@@ -4626,6 +5389,8 @@ function failedGenerationEnvironmentChanged(
       validation.cached.projectRoot,
       identities,
       props.filesystem,
+      undefined,
+      { policy: validation.cached.membershipPolicy },
     );
     if (
       validation.projectWalkComplete !==
@@ -4725,6 +5490,11 @@ async function transformProject(props: {
   compilerOptions: Record<string, unknown>;
   currentFile: string;
   currentSource: string;
+  /**
+   * Delivery pass this compile was started for; see
+   * {@link TtscCachedProjectTransform.deliveryEpoch}.
+   */
+  deliveryEpoch?: number;
   filesystem: TtscTransformFilesystemOperations;
   plugins?: ResolvedTtscUnpluginOptions["plugins"];
   trackProjectMembership: boolean;
@@ -4771,6 +5541,7 @@ async function captureTransformGeneration(props: {
   compilerOptions: Record<string, unknown>;
   currentFile: string;
   currentSource: string;
+  deliveryEpoch?: number;
   filesystem: TtscTransformFilesystemOperations;
   plugins?: ResolvedTtscUnpluginOptions["plugins"];
   trackProjectMembership: boolean;
@@ -4792,15 +5563,27 @@ async function captureTransformGeneration(props: {
     const temporaryTsconfig =
       configured.path === props.tsconfig ? undefined : configured.path;
     const identities = createHostPathIdentityContext(props.filesystem);
+    // Read from the project's own tsconfig rather than the generated one: a
+    // relative `outDir` is anchored at the config that declares it, and the
+    // generated config lives in a system temp directory. The caller's
+    // compiler-options overlay still wins, since it wins for the compile too.
+    const membershipPolicy = mergeMembershipPolicyOverlay(
+      readProjectMembershipPolicy(props.tsconfig),
+      props.compilerOptions,
+      projectRoot,
+    );
     const before = collectProjectInputSnapshot(
       projectRoot,
       identities,
       props.filesystem,
+      undefined,
+      { policy: membershipPolicy },
     );
     tracker = props.trackProjectMembership
       ? await createProjectMutationTracker(
           before.projectDirectories,
           props.filesystem,
+          membershipPolicy,
         )
       : undefined;
     const result = withTransformScratchEnvironment(scratchDirectory, () =>
@@ -4876,6 +5659,7 @@ async function captureTransformGeneration(props: {
         : undefined;
     const externalInputPaths = selectExternalInputPaths({
       filesystem: props.filesystem,
+      membershipPolicy,
       projectRoot,
       result,
       scratchDirectory,
@@ -4885,6 +5669,8 @@ async function captureTransformGeneration(props: {
       projectRoot,
       identities,
       props.filesystem,
+      undefined,
+      { policy: membershipPolicy },
     );
     // Whether the recorded snapshot describes one coherent state of the
     // project. A membership event during the compile taints it exactly like an
@@ -4935,6 +5721,12 @@ async function captureTransformGeneration(props: {
       delete inputSnapshot.provenSignatures[currentFileKey];
     }
     const cached: TtscCachedProjectTransform = {
+      // The pass this compile was started for. Its snapshot describes the
+      // project as of this compile, so it is settled for this pass and any
+      // later pass must re-prove it.
+      ...(props.deliveryEpoch === undefined
+        ? {}
+        : { deliveryEpoch: props.deliveryEpoch }),
       // Capture the out-of-walk input hashes while the generation is fresh so
       // cache validation can re-check them; computed before dispose so the
       // scratch-tree exclusion is the only reason its disposed artifacts never
@@ -4944,7 +5736,9 @@ async function captureTransformGeneration(props: {
       externalInputPaths,
       inputHashes: inputSnapshot.hashes,
       inputSignatures: inputSnapshot.provenSignatures,
+      membershipPolicy,
       projectDirectories: inputSnapshot.projectDirectories,
+      tsconfig: props.tsconfig,
       projectSnapshotComplete: false,
       projectRoot,
       result,
@@ -5388,10 +6182,40 @@ function readPaths(value: unknown): Record<string, string[]> {
 function createAliasPaths(aliases: unknown): Record<string, string[]> {
   const paths: Record<string, string[]> = {};
   for (const alias of normalizeAliases(aliases)) {
-    if (typeof alias.find !== "string" || alias.find.length === 0) {
+    if (typeof alias.find !== "string") {
+      // Vite's array form accepts a `RegExp` find, and `{ find: /^~/ }` is a
+      // common way to spell a prefix alias. A tsconfig `paths` map has no
+      // regular-expression form, so there is nothing to translate it into
+      // (samchon/ttsc#1315). Reducing the simple prefix cases to a string is
+      // possible in principle and deliberately not done: telling `/^~/` from
+      // `/^~(?=\/)/` or `/^@app/` — which matches `@apple` too — means
+      // implementing enough of a regular-expression engine that a wrong
+      // reduction becomes likely, and a mistranslated alias resolves imports to
+      // the wrong file silently, which is worse than not forwarding it.
+      //
+      // Not reported, unlike the wildcard below, and that asymmetry is the
+      // whole point: Vite merges two `RegExp` aliases of its own into every
+      // resolved config, `/^\/?@vite\/env/` and `/^\/?@vite\/client/`. Measured
+      // on a bare project with no user aliases at all, `resolve.alias` has
+      // exactly those two entries under both `serve` and `build`, so a report
+      // on this form would fire twice for every Vite user in every build, name
+      // aliases they never wrote, and say nothing about their configuration.
+      // A diagnostic that cannot distinguish the user's input from the host's
+      // is noise, and noise is what teaches people to stop reading the channel
+      // the out-of-program report depends on. The documentation carries this
+      // form instead, in both README and guide.
+      continue;
+    }
+    if (alias.find.length === 0) {
       continue;
     }
     if (alias.find.includes("*")) {
+      // A `paths` key reads `*` as its own wildcard, so forwarding a `find`
+      // that already contains one cannot preserve the caller's meaning.
+      reportUntranslatableAlias(
+        JSON.stringify(alias.find),
+        'a "paths" key already reads "*" as its own wildcard',
+      );
       continue;
     }
     const key = alias.find.replace(/\/+$/, "");
@@ -5409,9 +6233,54 @@ function createAliasPaths(aliases: unknown): Record<string, string[]> {
   return paths;
 }
 
-function normalizeAliases(aliases: unknown): TtscTransformAlias[] {
+/**
+ * Alias descriptions already reported in this process.
+ *
+ * The message is about configuration rather than about a module:
+ * `resolve.alias` is resolved once and then consulted on every delivery, so
+ * reporting per delivery would repeat one statement about the config for every
+ * file in the bundle. Keyed by the description, so a Vite dev server that
+ * reloads its config reports again only when the alias itself changed.
+ */
+const REPORTED_UNTRANSLATABLE_ALIASES = new Set<string>();
+
+/**
+ * Tell the user once that an alias they declared is not reaching the compile.
+ *
+ * A dropped alias is not silent in its consequence — the compile resolves
+ * through the tsconfig's own `paths`, and a module that resolves for the
+ * bundler but not for the compiler surfaces as the out-of-program report
+ * (samchon/ttsc#1308) — but that report names the module, not the alias, so the
+ * user cannot learn from it that a configuration they wrote was ignored.
+ *
+ * Only the wildcard form reaches here. Every entry it names was written by the
+ * user, because nothing injects one; the `RegExp` form is left to the
+ * documentation precisely because Vite does inject those, and
+ * {@link createAliasPaths} carries that measurement.
+ */
+function reportUntranslatableAlias(description: string, reason: string): void {
+  if (REPORTED_UNTRANSLATABLE_ALIASES.has(description)) {
+    return;
+  }
+  REPORTED_UNTRANSLATABLE_ALIASES.add(description);
+  process.stderr.write(
+    `ttsc: the Vite alias ${description} was not forwarded to the compile, because ${reason}. Declare it in your tsconfig's "paths" if ttsc must resolve through it.\n`,
+  );
+}
+
+/**
+ * Collect the host's declared aliases without deciding which of them can be
+ * expressed as `paths`.
+ *
+ * That decision belongs to {@link createAliasPaths} alone. It used to be split:
+ * this function's type guard required a string `find` and dropped Vite's
+ * `RegExp` form before `createAliasPaths` ever saw it, which left
+ * `createAliasPaths`'s own non-string branch unreachable and put the drop
+ * somewhere nothing could report it (samchon/ttsc#1315).
+ */
+function normalizeAliases(aliases: unknown): TtscDeclaredAlias[] {
   if (Array.isArray(aliases)) {
-    return aliases.filter(isAlias);
+    return aliases.filter(isDeclaredAlias);
   }
   if (typeof aliases === "object" && aliases !== null) {
     return Object.entries(aliases)
@@ -5469,13 +6338,12 @@ function isRelativeSpecifier(value: string): boolean {
   );
 }
 
-function isAlias(value: unknown): value is TtscTransformAlias {
+function isDeclaredAlias(value: unknown): value is TtscDeclaredAlias {
   return (
     typeof value === "object" &&
     value !== null &&
     "find" in value &&
     "replacement" in value &&
-    typeof value.find === "string" &&
     typeof value.replacement === "string"
   );
 }
@@ -5493,6 +6361,7 @@ function selectTransformedSource(props: {
   file: string;
   projectRoot: string;
   result: ITtscCompilerTransformation;
+  tsconfig: string;
 }): string {
   if (props.result.type === "exception") {
     throw new Error(formatUnknownError(props.result.error));
@@ -5523,20 +6392,68 @@ function selectTransformedSource(props: {
   if (source !== undefined) {
     return source;
   }
-  throw new Error(`ttsc transform did not return output for ${props.file}`);
+  throw new TtscMissingProgramOutputError(props.file, props.tsconfig);
 }
 
 /**
- * Forward non-fatal plugin diagnostics to stderr.
+ * Tell the user once that a module was left untransformed, and why.
+ *
+ * The condition is ordinary and the build continues, but it must never be
+ * silent: a file the program does not contain keeps whatever plugin syntax it
+ * carries, so a typia `assert<T>()` in it becomes a runtime failure rather than
+ * a build failure. One line per file per generation per pass, on the channel
+ * the generation's other non-fatal diagnostics already use, so a bundle that
+ * reaches many such files does not repeat itself per delivery.
+ */
+function reportMissingProgramOutput(
+  cached: TtscCachedProjectTransform,
+  error: TtscMissingProgramOutputError,
+  epoch: number | undefined,
+): void {
+  const reported = (cached.missingOutputReported ??= new Set<string>());
+  if (cached.missingOutputEpoch !== epoch) {
+    cached.missingOutputEpoch = epoch;
+    reported.clear();
+  }
+  if (reported.has(error.file)) {
+    return;
+  }
+  reported.add(error.file);
+  process.stderr.write(`${error.message}
+`);
+}
+
+/**
+ * Forward non-fatal plugin diagnostics to stderr, once per generation per pass.
  *
  * A `success` result may still carry warnings or informational messages from
- * plugins. These are surfaced via stderr rather than throwing so the build
- * continues. Failures and exceptions are handled by the caller.
+ * plugins — `@ttsc/lint` reports every rule below error severity this way.
+ * These are surfaced via stderr rather than throwing so the build continues.
+ * Failures and exceptions are handled by the caller.
+ *
+ * They describe one compile of one program, so writing them per delivery
+ * printed the same warning once per module and scaled the noise with exactly
+ * the reuse the cache exists to provide (samchon/ttsc#1304). A pass that reuses
+ * a retained generation still surfaces them once, because a build's warnings
+ * are part of what that build reports; a host with no pass boundary surfaces
+ * them once per generation, which is the same rule with one pass.
  */
-function reportSuccessDiagnostics(result: ITtscCompilerTransformation): void {
+function reportSuccessDiagnostics(
+  cached: TtscCachedProjectTransform,
+  epoch: number | undefined,
+): void {
+  const result = cached.result;
   if (result.type !== "success" || result.diagnostics === undefined) {
     return;
   }
+  if (
+    cached.diagnosticsReported === true &&
+    cached.diagnosticsEpoch === epoch
+  ) {
+    return;
+  }
+  cached.diagnosticsReported = true;
+  cached.diagnosticsEpoch = epoch;
   const text = formatDiagnostics(result.diagnostics);
   if (text.length !== 0) {
     process.stderr.write(`${text}\n`);
@@ -5562,7 +6479,7 @@ function formatDiagnostics(diagnostics: ITtscCompilerDiagnostic[]): string {
         diag.line === undefined
           ? undefined
           : `${diag.line}:${diag.character ?? 1}`,
-        diag.messageText,
+        stripTerminalEscapes(diag.messageText),
       ]
         .filter((part) => part !== undefined && part !== "")
         .join(": "),
@@ -5572,7 +6489,7 @@ function formatDiagnostics(diagnostics: ITtscCompilerDiagnostic[]): string {
 
 function formatUnknownError(error: unknown): string {
   if (error instanceof Error) {
-    return error.message;
+    return stripTerminalEscapes(error.message);
   }
   if (
     typeof error === "object" &&
@@ -5580,9 +6497,33 @@ function formatUnknownError(error: unknown): string {
     "message" in error &&
     typeof error.message === "string"
   ) {
-    return error.message;
+    return stripTerminalEscapes(error.message);
   }
-  return String(error);
+  return stripTerminalEscapes(String(error));
+}
+
+/**
+ * Remove terminal colour and cursor sequences from text the adapter surfaces.
+ *
+ * An ordinary type error reaches the adapter as an `"exception"` envelope whose
+ * `error` is the host's own rendered output, colour and all, and the envelope
+ * carries no structured diagnostics to format instead. What the adapter hands
+ * back is not going to a terminal: it becomes the `Error` a bundler reports, so
+ * it lands in a Vite overlay, a webpack error report or a CI annotation, where
+ * the escapes render as literal noise around the file and line the reader needs
+ * (samchon/ttsc#1312).
+ *
+ * The colour originates in the host's rendering rather than in anything this
+ * adapter configures, so this is the adapter-side repair, applied to every
+ * message it surfaces rather than to one call site.
+ */
+function stripTerminalEscapes(text: string): string {
+  // Built from a char code so no control byte lives in this source file, and
+  // written with `[[]` (a class holding one literal bracket) so the pattern
+  // needs no backslash escapes to survive the string it is assembled from.
+  const escape = String.fromCharCode(27);
+  const controlSequence = new RegExp(escape + "[[][0-9;?]*[ -/]*[@-~]", "g");
+  return text.replace(controlSequence, "");
 }
 
 /**