@unotest/web 0.42.0 → 0.43.0

package/dist/{linter-Yf4gPe5J.d.ts → linter-BWSAYBQy.d.ts}

@@ -7,6 +7,14 @@ interface LintDiagnostic {
     message: string;
     line: number;
     col: number;
+    /** This diagnostic must stop a run before anything is driven, not just
+     *  print. A rule sets it when proceeding would act on the WRONG target
+     *  — the steps before the offending one would run against the wrong
+     *  host and leave their side effects there. The CLI (whose pre-run lint
+     *  is otherwise advisory) refuses on it; run_test already gates on
+     *  errors and is unaffected. Rules opt in themselves, so no frontend
+     *  keeps a list of rule ids. */
+    blocksRun?: true;
 }
 /** What the linter may ask about external variables (bare UPPER_SNAKE
  *  identifiers). A predicate, not a list, because the two callers hold
@@ -17,6 +25,22 @@ interface ExternalVariableLookup {
     has(name: string): boolean;
     /** Where `has` looked, for the diagnostic (`unotest/.env, unotest/.env.dev (no such file)`). */
     describeSources?(): string;
+    /** Host policy of the environment this lookup describes (#199) — it
+     *  answers why NAME must not be used as a HOST in `usage`, or undefined
+     *  when the use is fine. Absent on a lookup with no project behind it,
+     *  which leaves the rule off. Structural on purpose: the policy hands
+     *  back a typed error and the linter needs only what it says, never the
+     *  config layer it came from. */
+    hostPolicy?: {
+        rejectAsHost(name: string, usage: string): {
+            message: string;
+        } | undefined;
+        /** The base-URL variable, which the policy names itself — every
+         *  relative `goto` in the file resolves against it. */
+        rejectBaseUrl(usage: string): {
+            message: string;
+        } | undefined;
+    };
 }
 interface LintOptions {
     /** Per-rule severity override. Default severities live with each rule. */