@apifuse/provider-sdk 2.2.0-beta.64 → 2.2.0-beta.65

package/src/runtime-boundary-lint.ts

@@ -3,8 +3,12 @@
  * through the SDK context (`ctx.http`, `ctx.stealth`, `ctx.env`,
  * `ctx.credential`, `ctx.browser`), not through ambient Node/Bun globals.
  *
- * Three rules, all reported at `warn` level in this first release so the
- * fleet can migrate before the level is raised:
+ * Three rules, reported at `error` level: a finding fails `apifuse check` and
+ * `apifuse submit-check` (official and standalone mode alike). The first
+ * release reported them at `warn` as a migration window; the window closed once
+ * the fleet's request-path hits were fixed or acknowledged. A deliberate
+ * exception is acknowledged in code (see below), never through a hidden
+ * allowlist.
  *
  * - `process-env-direct-read`: `process.env.X`, `process.env["X"]`, a bare
  *   `process.env` object use, and the `Bun.env` equivalents. Runtime bootstrap
@@ -82,7 +86,7 @@ export function isBootstrapEnvName(name: string): boolean {
 const BOOTSTRAP_ENTRYPOINT_FILE_PATTERN = /^(?:dev|start|deploy)\.[cm]?[jt]sx?$/;
 /** Operator tooling directories at the provider root (fixture recorders, smoke scripts). */
 const TOOLING_DIRECTORY_PATTERN = /^(?:scripts|tools|bin)\//;
-const TEST_SOURCE_FILE_PATTERN =
+export const TEST_SOURCE_FILE_PATTERN =
 	/(?:^|\/)(?:__tests__|__mocks__|tests)\/|\.(?:test|spec)\.[cm]?[jt]sx?$/;
 const RECORDED_FIXTURE_SOURCE_FILE_PATTERN =
 	/(?:^|\/)__fixtures__(?:\/|$)|(?:^|\/)__tests__\/fixtures(?:\/|$)/;
@@ -595,7 +599,7 @@ export type RuntimeBoundaryLintInput = {
 };
 
 /**
- * Lint the provider runtime boundary. Returns warn-level diagnostics (one per
+ * Lint the provider runtime boundary. Returns error-level diagnostics (one per
  * file and rule, listing every line) and information entries for findings
  * acknowledged with `@apifuse-allow`.
  */
@@ -644,7 +648,7 @@ export function lintRuntimeBoundary(
 			if (findings.length > 0) {
 				diagnostics.push({
 					rule,
-					level: "warn",
+					level: "error",
 					field,
 					message: `${describeSubjects(findings)}: ${remediation(rule)}`,
 				});