chore: remove redundant runtime update comments

Author: carderne

apps/webapp/app/services/projectRuntimeUpdates.server.ts

@@ -85,13 +85,6 @@ export async function listCurrentProductionProjectRuntimes(scope: Scope) {
   );
 }
 
-/**
- * Whether any project in the organization needs a Node.js runtime update in Production.
- *
- * The SQL filter mirrors `needsNodeRuntimeUpdate(runtime, runtimeVersion)`, including legacy
- * deployments with missing runtime metadata. Keep the two in step. Scoped to the caller's
- * membership so the side menu cannot report on an organization the user does not belong to.
- */
 export async function organizationHasProjectRuntimeUpdate({
   organizationSlug,
   userId,

packages/core/src/v3/schemas/api.ts

@@ -79,13 +79,6 @@ export function nodeMajor(
   return match ? Number(match[1]) : undefined;
 }
 
-/**
- * Whether a deployment should move off the Node.js major targeted by the runtime update report.
- *
- * Older deployments can be missing either runtime field. A missing runtime historically meant
- * Node.js, while a missing version means we cannot prove that the deployment is on a supported
- * major, so both are treated as needing an update. An explicit non-Node runtime is never included.
- */
 export function needsNodeRuntimeUpdate(
   runtime: string | null | undefined,
   runtimeVersion: string | null | undefined