@nifrajs/cli 2.13.0 → 2.14.1

package/src/check.ts

@@ -29,7 +29,9 @@ import { importProjectTypeScript, type TypeScriptApi } from "./internal/typescri
 // Type-only: `pipeline-report.ts` imports this module's source scanners, so a value import here would
 // close a cycle. Doctor is what actually runs the collector (see the `pipeline` rule below).
 import type { PipelineReport } from "./pipeline-report.ts"
+import { freezeProjectFacts, type ProjectFactsSeed } from "./project-facts.ts"
 import { RULE_CODES } from "./rules/codes.ts"
+import { commentBlockMarkerReason } from "./rules/comment-markers.ts"
 import { parseRulePacks, type RuleContext, runRuleRegistry, sourceIndex } from "./rules/index.ts"
 import { LEGACY_RULE_CODES, legacyRules } from "./rules/legacy.ts"
 import { routeRules } from "./rules/routes.ts"
@@ -902,6 +904,158 @@ function templateShape(
   return { staticText, dynamic }
 }
 
+/** A same-file binding the argument resolver proved holds one expression: a `const`, or a `let` the
+ * whole file never reassigns. `"shadow"` marks a nearer binding of the name we can NOT read through (a
+ * parameter, `var`, destructured, uninitialized, reassigned `let`) - it stops the outward walk so a
+ * farther, resolvable const of the same name is never read in its place. */
+type ResolvableBinding = { readonly initializer: TSApi.Expression } | "shadow"
+
+/** Whether `name` is written to anywhere in the file - a plain, compound, or `++`/`--` assignment to a
+ * bare identifier of that name. A `let` that is is over-cautiously refused (it might be reassigned from
+ * request data); a `const` never needs this. Over-refusal only ever leaves an interpolation flagged as
+ * before, never the reverse. */
+function isReassignedInFile(ts: TypeScriptApi, source: TSApi.SourceFile, name: string): boolean {
+  let found = false
+  const visit = (node: TSApi.Node): void => {
+    if (found) return
+    if (
+      ts.isBinaryExpression(node) &&
+      node.operatorToken.kind >= ts.SyntaxKind.FirstAssignment &&
+      node.operatorToken.kind <= ts.SyntaxKind.LastAssignment &&
+      ts.isIdentifier(node.left) &&
+      node.left.text === name
+    ) {
+      found = true
+      return
+    }
+    if (
+      (ts.isPrefixUnaryExpression(node) || ts.isPostfixUnaryExpression(node)) &&
+      (node.operator === ts.SyntaxKind.PlusPlusToken ||
+        node.operator === ts.SyntaxKind.MinusMinusToken) &&
+      ts.isIdentifier(node.operand) &&
+      node.operand.text === name
+    ) {
+      found = true
+      return
+    }
+    ts.forEachChild(node, visit)
+  }
+  visit(source)
+  return found
+}
+
+/** Does `binding` bind `name` (as a plain identifier or nested inside a destructuring pattern)? Mirrors
+ * the pattern walk in {@link isShadowedAt}. */
+function bindingNameCovers(ts: TypeScriptApi, binding: TSApi.BindingName, name: string): boolean {
+  return ts.isIdentifier(binding)
+    ? binding.text === name
+    : binding.elements.some(
+        (element) =>
+          !ts.isOmittedExpression(element) &&
+          (ts.isIdentifier(element.name)
+            ? element.name.text === name
+            : bindingNameCovers(ts, element.name, name)),
+      )
+}
+
+/** Inspect the bindings a single scope node introduces DIRECTLY (not nested) for `name`: parameters and
+ * catch variables of a function/catch, `var`/`let`/`const` and function/class declarations of a
+ * statement list. Returns the readable initializer, `"shadow"` for a form we cannot read through, or
+ * `undefined` when this scope does not bind the name at all. */
+function directBinding(
+  ts: TypeScriptApi,
+  source: TSApi.SourceFile,
+  scope: TSApi.Node,
+  name: string,
+): ResolvableBinding | undefined {
+  if (ts.isFunctionLike(scope)) {
+    for (const parameter of scope.parameters) {
+      if (bindingNameCovers(ts, parameter.name, name)) return "shadow"
+    }
+  }
+  if (ts.isCatchClause(scope)) {
+    const declared = scope.variableDeclaration
+    if (declared !== undefined && bindingNameCovers(ts, declared.name, name)) return "shadow"
+  }
+  const statements: readonly TSApi.Statement[] | undefined = ts.isSourceFile(scope)
+    ? scope.statements
+    : ts.isBlock(scope) || ts.isModuleBlock(scope)
+      ? scope.statements
+      : ts.isCaseClause(scope) || ts.isDefaultClause(scope)
+        ? scope.statements
+        : undefined
+  const lists: TSApi.VariableDeclarationList[] = []
+  if (statements !== undefined) {
+    for (const statement of statements) {
+      if (ts.isVariableStatement(statement)) lists.push(statement.declarationList)
+      if (
+        (ts.isFunctionDeclaration(statement) || ts.isClassDeclaration(statement)) &&
+        statement.name?.text === name
+      ) {
+        return "shadow"
+      }
+    }
+  }
+  if (
+    (ts.isForStatement(scope) || ts.isForInStatement(scope) || ts.isForOfStatement(scope)) &&
+    scope.initializer !== undefined &&
+    ts.isVariableDeclarationList(scope.initializer)
+  ) {
+    lists.push(scope.initializer)
+  }
+  for (const list of lists) {
+    for (const declaration of list.declarations) {
+      if (!bindingNameCovers(ts, declaration.name, name)) continue
+      // A destructured or uninitialized binding, or a `var` (hoisting + reassignment risk), is not a
+      // value we can read one expression out of.
+      if (!ts.isIdentifier(declaration.name) || declaration.initializer === undefined)
+        return "shadow"
+      const isConst = (list.flags & ts.NodeFlags.Const) !== 0
+      const isLet = (list.flags & ts.NodeFlags.Let) !== 0
+      if (isConst) return { initializer: declaration.initializer }
+      if (isLet && !isReassignedInFile(ts, source, name))
+        return { initializer: declaration.initializer }
+      return "shadow"
+    }
+  }
+  return undefined
+}
+
+/**
+ * Resolve a query-call ARGUMENT identifier to the expression it was initialized from, so a statement
+ * parked in a variable is scanned as if it had been written inline at the call. This is the counterpart
+ * to {@link resolveStaticSqlText}: that folds a const's text INTO a template's shape; this unfolds the
+ * whole statement back out of the variable it was lifted into. Without it, ANY interpolated-SQL finding
+ * could be silenced, invisibly, by hoisting the statement to `const q = …` first.
+ *
+ * Same-file only. Nearest enclosing declaration wins, so a shadowing local is read and never a
+ * same-named module const. Reads through a `const`, or a `let` the file never reassigns, at function or
+ * module scope; transitive through an identifier-valued initializer; depth-capped. A parameter, an
+ * imported or destructured binding, a reassigned `let`, a `var`, or a name with no same-file
+ * declaration returns `undefined` - which leaves the argument scanned as itself (unflagged unless it is
+ * a module const that resolves to static text: exactly the pre-feature behavior).
+ */
+function resolveArgumentInitializer(
+  ts: TypeScriptApi,
+  node: TSApi.Identifier,
+  depth: number,
+): TSApi.Expression | undefined {
+  if (depth > CONST_RESOLUTION_DEPTH) return undefined
+  const source = node.getSourceFile()
+  const name = node.text
+  for (let scope: TSApi.Node | undefined = node.parent; scope !== undefined; scope = scope.parent) {
+    const binding = directBinding(ts, source, scope, name)
+    if (binding === "shadow") return undefined
+    if (binding !== undefined) {
+      let init = binding.initializer
+      while (ts.isParenthesizedExpression(init)) init = init.expression
+      return ts.isIdentifier(init) ? resolveArgumentInitializer(ts, init, depth + 1) : init
+    }
+    if (ts.isSourceFile(scope)) break
+  }
+  return undefined
+}
+
 /** Describe only the first argument's syntax; comments/strings elsewhere cannot influence the result. */
 function sqlExpressionShape(
   ts: TypeScriptApi,
@@ -990,6 +1144,17 @@ function sqlExpressionShape(
       }
     }
   }
+  // A bare name that did not resolve to compile-time text. If it is a same-file binding we can prove
+  // holds one expression, scan THAT expression's shape - so a statement hoisted into `const q = …` is
+  // read exactly as if it were written inline at the call, closing the "extract a variable to launder
+  // the finding" hole. `literal` is forced false: the value arrived through a variable, which is the
+  // property the `unsafe`/`$queryRawUnsafe` hatch rule keys on.
+  if (ts.isIdentifier(node)) {
+    const initializer = resolveArgumentInitializer(ts, node, 0)
+    if (initializer !== undefined) {
+      return { ...sqlExpressionShape(ts, initializer, scope), literal: false }
+    }
+  }
   return {
     staticText: "",
     dynamic: true,
@@ -1024,6 +1189,11 @@ function sqlMethod(
 
 const SQL_RECEIVER = /(?:^|\.)(?:db|sql|prisma|drizzle|database|conn|connection|client|tx)$/i
 
+/** The opt-out pragma that silences one interpolated-SQL finding. Written `// nifra-expect sql-dynamic:
+ * <reason>` on the flagged line or in the comment block directly above it; the reason after the colon
+ * is mandatory (see {@link commentBlockMarkerReason}). Scoped to the single statement it sits on. */
+const SQL_DYNAMIC_PRAGMA = "nifra-expect sql-dynamic"
+
 /**
  * Scan one file's text for SQL assembled by interpolation. Pure + line-accurate.
  *
@@ -1062,7 +1232,12 @@ export function scanInterpolatedSql(
         if (unsafeEscape || assembledSql) {
           const index = node.getStart(source)
           const line = source.getLineAndCharacterOfPosition(index).line + 1
-          out.push({ file, line, snippet: (lines[line - 1] ?? "").trim() })
+          // Sanctioned escape hatch for genuinely-dynamic-but-bound SQL (batch VALUES placeholder
+          // generation, an allowlisted identifier). The reason is mandatory: a bare `// nifra-expect
+          // sql-dynamic` with no reason after the colon does NOT silence, so the hatch always leaves a
+          // greppable audit trail instead of becoming a second laundering trick.
+          const silenced = commentBlockMarkerReason(lines, line, SQL_DYNAMIC_PRAGMA) !== undefined
+          if (!silenced) out.push({ file, line, snippet: (lines[line - 1] ?? "").trim() })
         }
       }
     }
@@ -1846,7 +2021,7 @@ export interface CheckAssuranceContext {
 
 /** Optional per-project `nifra.check.json` - pure data (no code execution), so it's safe to read before
  * the app is built or even importable, preserving check's pre-`loadApp` invariant. */
-interface CheckConfig {
+export interface CheckConfig {
   readonly externalMounts: readonly string[]
   readonly rules: Readonly<Record<string, RuleOverride>>
 }
@@ -2095,25 +2270,27 @@ function responseRouteSuggestion(): CheckSuggestion {
   }
 }
 
-/** Run the three checks and assemble a structured, machine-readable result. The single source the CLI
- * report, `--json`, and the MCP tool all render from. */
-export async function collectCheckResult(
+interface CheckCollectionOptions {
+  readonly lintsOnly?: boolean
+  readonly signal?: AbortSignal
+  readonly maxDiagnostics?: number
+  readonly loadTypeScript?: () => Promise<TypeScriptApi | undefined>
+  readonly assurance?: CheckAssuranceContext
+}
+
+interface ProjectScan {
+  readonly facts: ProjectFactsSeed
+  readonly typecheck: TypecheckResult
+  readonly sqlCompiler: TypeScriptApi | undefined
+  readonly checkConfigError?: string
+  readonly checkConfigWarnings: readonly string[]
+}
+
+/** Build the rule input from one source walk and the other check-wide scans. */
+async function buildProjectScan(
   cwd: string,
-  opts: {
-    readonly lintsOnly?: boolean
-    readonly signal?: AbortSignal
-    /** Cap the returned `diagnostics` to this many (adds {@link CheckResult.truncated}). The MCP tool sets
-     * it so a huge project can't produce a transport-breaking result; the CLI leaves it unset (all shown). */
-    readonly maxDiagnostics?: number
-    /** How the interpolated-SQL rule gets its compiler. Injectable so the "not installed" path - the
-     * one where a security rule reports that it did not run - is testable on a machine that has it. */
-    readonly loadTypeScript?: () => Promise<TypeScriptApi | undefined>
-    /** Route-assurance inputs already computed by {@link collectProjectVerification}. When present,
-     * the capability + trust-manifest diagnostics reuse them instead of loading/reflecting a second
-     * time; when absent, they are computed here (unchanged standalone behavior). */
-    readonly assurance?: CheckAssuranceContext
-  } = {},
-): Promise<CheckResult> {
+  opts: Pick<CheckCollectionOptions, "lintsOnly" | "signal" | "loadTypeScript">,
+): Promise<ProjectScan> {
   const fetches: SourceFinding[] = []
   const staticRoutes: StaticRouteFinding[] = []
   const untypedClients: SourceFinding[] = []
@@ -2121,31 +2298,18 @@ export async function collectCheckResult(
   const serverImports: TransitiveServerImportFinding[] = []
   const responseRoutes: SourceFinding[] = []
   const interpolatedSql: SourceFinding[] = []
-  // Route modules (rel + content) collected during the walk, so the TRANSITIVE server-only resolution
-  // (#4.4) - which needs fs-backed import resolution, not just per-file text - runs after the walk.
   const routeModules: Array<{ rel: string; content: string }> = []
   const sourceFiles: Array<{ file: string; content: string }> = []
-  // Load the optional check config first - the typed-client scan needs the external-mount allowlist as it
-  // walks. It's a tiny pure-JSON read; a malformed file surfaces as a warning below, never blocking.
   const {
     config: checkConfig,
     error: checkConfigError,
     warnings: checkConfigWarnings,
   } = await loadCheckConfig(cwd)
-  // The interpolated-SQL rule parses with the TypeScript compiler, which is an optional peer. Resolved
-  // once, before the walk, so a project without it is told the rule did not run rather than being
-  // handed a clean report the rule never produced.
   const sqlCompiler = await (opts.loadTypeScript ?? (() => importProjectTypeScript(cwd)))()
-  // AST facts are a lazy refinement of lexical candidates. The parser is not invoked for a file until
-  // one of the route/import/response scanners finds something worth disambiguating, and the cache is
-  // shared across those rules for this check run.
   const sourceFacts = sqlCompiler === undefined ? undefined : createSourceFacts(sqlCompiler)
-  // One loader + parse cache for the whole walk, so a shared `sql-fragments.ts` is read once no matter
-  // how many route modules import a fragment out of it.
   const sqlImports = sqlCompiler === undefined ? undefined : createProjectSqlImports(cwd)
-  // lintsOnly: skip the tsc pass (seconds on a big project) and run just the near-instant source
-  // lints - the agent inner-loop mode; the full gate stays the definition of done.
-  const [tc, _, dr, manifestDrift] = await Promise.all([
+
+  const [typecheckResult, _, doctor, manifestDrift] = await Promise.all([
     opts.lintsOnly
       ? Promise.resolve<TypecheckResult>({ ran: false, ok: true, note: "lints-only mode" })
       : typecheck(cwd, opts.signal),
@@ -2164,19 +2328,12 @@ export async function collectCheckResult(
     scanServerManifestDrift(cwd),
   ])
 
-  // #4.4: resolve the FULL transitive server-only chain per route. The resolver/reader are fs-backed
-  // (`Bun.resolveSync` from the importing file's dir + a sync read), so the walk follows the real local
-  // module graph (`route → ../data → ../db → node:crypto`). Both are best-effort + total: a resolve/read
-  // miss returns `undefined`, and the walk falls back to the direct edge. The whole walk is bounded
-  // (depth + visited caps), so a deep/cyclic graph can't blow up the check.
   const resolveModule: ModuleResolver = (fromFile, specifier) => {
     try {
-      // `fromFile` is a cwd-RELATIVE route path on the first hop (`routes/x.tsx`) but ABSOLUTE on the
-      // deeper hops the walk takes (it carries resolved absolute paths) - resolve the dir for each.
       const fromAbs = isAbsolute(fromFile) ? fromFile : join(cwd, fromFile)
       return Bun.resolveSync(specifier, dirname(fromAbs))
     } catch {
-      return undefined // unresolvable (bare pkg without install, tsconfig path alias, missing file)
+      return undefined
     }
   }
   const readModule: ModuleReader = (absPath) => {
@@ -2192,6 +2349,43 @@ export async function collectCheckResult(
     )
   }
 
+  const source = sourceIndex(sourceFiles)
+  const facts: ProjectFactsSeed = {
+    source,
+    routes: staticRoutes,
+    importGraph: serverImports,
+    packages: { doctor, manifestDrift },
+    ...(doctor.pipeline === undefined ? {} : { pipeline: doctor.pipeline }),
+    policies: { checkConfig, rulePacks: [] },
+    sourceFindings: { fetches, untypedClients, removedImports, responseRoutes, interpolatedSql },
+  }
+  return {
+    facts,
+    typecheck: typecheckResult,
+    sqlCompiler,
+    ...(checkConfigError === undefined ? {} : { checkConfigError }),
+    checkConfigWarnings,
+  }
+}
+
+/** Run the three checks and assemble a structured, machine-readable result. The single source the CLI
+ * report, `--json`, and the MCP tool all render from. */
+export async function collectCheckResult(
+  cwd: string,
+  opts: CheckCollectionOptions = {},
+): Promise<CheckResult> {
+  const scan = await buildProjectScan(cwd, opts)
+  const factsSeed = scan.facts
+  const { fetches, untypedClients, removedImports, responseRoutes, interpolatedSql } =
+    factsSeed.sourceFindings
+  const staticRoutes = factsSeed.routes
+  const serverImports = factsSeed.importGraph
+  const { doctor: dr, manifestDrift } = factsSeed.packages
+  const { checkConfig } = factsSeed.policies
+  const tc = scan.typecheck
+  const sqlCompiler = scan.sqlCompiler
+  const checkConfigError = scan.checkConfigError
+  const checkConfigWarnings = scan.checkConfigWarnings
   const diagnostics: CheckDiagnostic[] = []
   const structuredExtras: Diagnostic[] = []
   if (checkConfigError !== undefined) {
@@ -2267,7 +2461,7 @@ export async function collectCheckResult(
       })
   }
   const routes = staticRouteMap(staticRoutes)
-  for (const f of fetches.sort(bySite)) {
+  for (const f of [...fetches].sort(bySite)) {
     diagnostics.push({
       rule: "typed-client",
       severity: "error",
@@ -2278,7 +2472,7 @@ export async function collectCheckResult(
       suggestion: ownFetchSuggestion(f, routes),
     })
   }
-  for (const f of removedImports.sort(bySite)) {
+  for (const f of [...removedImports].sort(bySite)) {
     const entry = REMOVED_IMPORTS.find(
       (candidate) =>
         f.snippet.includes(`"${candidate.specifier}`) ||
@@ -2293,7 +2487,7 @@ export async function collectCheckResult(
       fix: entry?.replacement ?? "see the changelog",
     })
   }
-  for (const f of untypedClients.sort(bySite)) {
+  for (const f of [...untypedClients].sort(bySite)) {
     diagnostics.push({
       rule: "untyped-client",
       severity: "error",
@@ -2304,7 +2498,7 @@ export async function collectCheckResult(
       suggestion: untypedClientSuggestion(f),
     })
   }
-  for (const f of serverImports.sort(bySite)) {
+  for (const f of [...serverImports].sort(bySite)) {
     // #4.4: the FULL transitive chain the import-resolution walk found - `route → ../data → ../db →
     // node:crypto`, matching the build leak-guard's depth - instead of just the direct edge. The chain's
     // tail is the actual server-only sink; the head is the route. When a precise resolve wasn't possible
@@ -2337,7 +2531,7 @@ export async function collectCheckResult(
       },
     })
   }
-  for (const f of interpolatedSql.sort(bySite)) {
+  for (const f of [...interpolatedSql].sort(bySite)) {
     diagnostics.push({
       rule: "interpolated-sql",
       severity: "error",
@@ -2353,12 +2547,13 @@ export async function collectCheckResult(
           "Pass the value as an argument alongside the statement, so the driver binds it.",
           `Or switch to the driver's tagged template (sql\`… ${SQL_INTERPOLATION_EXAMPLE} …\`): the tag receives substitutions separately and binds them.`,
           "An identifier that genuinely cannot be bound (a table or column name) must be checked against an allowlist you control, never taken from the request.",
+          "If the statement is dynamic but every value is already bound (generating `($1),($2),…` for a batch insert), mark it with a `// nifra-expect sql-dynamic: <reason>` comment on the line above - the reason is required.",
         ],
       },
     })
   }
   // Advisory - surfaced but NOT folded into `ok`, so it never fails the gate (a raw Response is valid).
-  for (const f of responseRoutes.sort(bySite)) {
+  for (const f of [...responseRoutes].sort(bySite)) {
     diagnostics.push({
       rule: "response-route",
       severity: "warning",
@@ -2390,7 +2585,7 @@ export async function collectCheckResult(
       diagnostics.push({
         rule: "duplicate-install",
         severity: "error",
-        message: `${finding.package} resolves to multiple physical copies (${copies}) - ${finding.explanation}`,
+        message: `${finding.package} identity preflight found ${finding.cause} (${copies}) - ${finding.explanation}`,
         fix: finding.remediation,
         suggestion: {
           kind: "manual",
@@ -2470,6 +2665,8 @@ export async function collectCheckResult(
   // without nifra.assurance.ts retain the historical scan and hot path unchanged.
   const provided = opts.assurance
   let applicationRulePacks: readonly import("./rules/index.ts").RulePack[] = []
+  let loadedPolicy = provided
+  let loadedCapability: CapabilityProjectReport | undefined = provided?.capability
   const assuranceConfigPath = join(cwd, "nifra.assurance.ts")
   if (provided !== undefined ? provided.present : existsSync(assuranceConfigPath)) {
     try {
@@ -2494,6 +2691,14 @@ export async function collectCheckResult(
           const { collectCapabilityProjectReport } = await import("./capabilities-tool.ts")
           project = await collectCapabilityProjectReport(cwd, config.source, config.capabilities)
         }
+        loadedPolicy = {
+          present: true,
+          config,
+          ...(routeAssurance === undefined ? {} : { routeAssurance }),
+          ...(project === undefined ? {} : { capability: project }),
+          ...(evidence === undefined ? {} : { evidence }),
+        }
+        loadedCapability = project
       }
       applicationRulePacks = parseRulePacks(config.rulePacks)
       const capabilityReport = project?.report
@@ -2616,6 +2821,7 @@ export async function collectCheckResult(
         }
       }
     } catch (err) {
+      loadedPolicy = { present: true, error: err }
       diagnostics.push({
         rule: "capability-config",
         severity: "error",
@@ -2649,6 +2855,20 @@ export async function collectCheckResult(
         }),
       )
     } else {
+      if (contract.vacuous) {
+        // Every route hashes to the empty-schema digest, so the lock exists but the drift rule guards
+        // nothing: it can only ever compare "no schema" to "no schema". Say so, or a green contract check
+        // reads as proof of a stable contract when there is no contract to be stable.
+        structuredExtras.push(
+          diagnostic({
+            code: "NF-K001",
+            severity: "info",
+            message:
+              "no route schemas declared - the trust manifest is vacuous: every contract hash is the empty-schema digest, so drift detection guards nothing. Declare route schemas (body/query/params/response) so the lock has a contract to protect.",
+            verify: "nifra check --lints-only",
+          }),
+        )
+      }
       for (const finding of contract.diagnostics) {
         diagnostics.push({
           rule: "contract-drift",
@@ -2675,16 +2895,22 @@ export async function collectCheckResult(
     }
   }
 
+  const projectFacts = freezeProjectFacts(
+    {
+      ...factsSeed,
+      policies: {
+        ...factsSeed.policies,
+        ...(loadedPolicy === undefined ? {} : { assurance: loadedPolicy }),
+        ...(loadedCapability === undefined ? {} : { capability: loadedCapability }),
+        rulePacks: applicationRulePacks,
+      },
+    },
+    diagnostics,
+  )
   const ruleContext: RuleContext = {
     root: cwd,
-    sources: sourceIndex(sourceFiles),
-    project: {
-      legacyDiagnostics: diagnostics,
-      assurance: opts.assurance,
-      // Route registrations collected during the source walk, so the route-table rules
-      // (rules/routes.ts) lint them without a second scan.
-      staticRoutes,
-    },
+    sources: projectFacts.source,
+    project: projectFacts,
   }
   const structuredDiagnostics = [...structuredExtras]
   let registryDiagnostics: Diagnostic[] = []
@@ -2692,7 +2918,7 @@ export async function collectCheckResult(
     registryDiagnostics = await runRuleRegistry(
       ruleContext,
       [...legacyRules, ...securityRules, ...routeRules],
-      applicationRulePacks,
+      projectFacts.policies.rulePacks,
     )
     structuredDiagnostics.push(...registryDiagnostics)
   } catch (error) {