refactor(boot): narrow legacy-links exports and refresh resolution JSDoc

isPackagedExecutable has one caller in its own module; the installation traversal comment names the runtime resolver instead of the removed fallback directory.

packages/boot/app-boot/src/profile-resolution/legacy-links.ts

@@ -6,7 +6,7 @@ import { realpathSync } from 'node:fs'
  * Return whether the process reads application modules from pkg's virtual filesystem.
  * @returns whether pkg owns the module filesystem.
  */
-export function isPackagedExecutable(): boolean {
+function isPackagedExecutable(): boolean {
   return (process as NodeJS.Process & { pkg?: unknown }).pkg !== undefined
 }
 

packages/boot/app-boot/src/profile.ts

@@ -204,7 +204,7 @@ function profileDependencyNames(manifest: ProfileManifest): string[] {
   return [...Object.keys(manifest.dependencies ?? {}), ...Object.keys(manifest.peerDependencies ?? {})]
 }
 
-/** Resolve the installation generation that every profile must find through the fallback directory. */
+/** Resolve the installation packages that the runtime resolver supplies to every profile. */
 function resolveModuleFallbackEntries(
   installAnchor: string, skippedBundles: ReadonlySet<string>,
 ): {