chore: sweep Kimi mentions from comments and notes

tests/golden-parity-single-source.test.cjs

@@ -81,7 +81,7 @@ test('install-shared.cjs exports the canonical buildParityManifest + exclusion c
 // ALL FIVE identifiers are guarded, not just buildParityManifest + VOLATILE_FILES:
 // the drift that shipped broken fixtures was a MISSING exclusion-constant entry
 // (#2100 = generator's HOOK_CONFIG_FILES copy lacked settings.local.json; #2095 =
-// kimi's HOOK_CONFIG_RELATIVE_PATHS entry), so a re-declared HOOK_CONFIG_FILES /
+// a runtime-specific HOOK_CONFIG_RELATIVE_PATHS entry), so a re-declared HOOK_CONFIG_FILES /
 // HOOK_CONFIG_RELATIVE_PATHS / EXCLUDED_PREFIXES is exactly the failure class this
 // guard exists to prevent — checking only two of four would leave that gap open.
 const FORBIDDEN_INLINE = [
@@ -277,8 +277,8 @@ describe('#1575 — surface path: no prune data-loss over pre-existing legacy ag
 
 test('runMinimalInstall resolves local config dirs from RUNTIME_META alone (#3031)', () => {
   // install-shared.cjs used to carry a SECOND, hand-maintained local-dir map
-  // beside RUNTIME_META. It drifted: four runtimes present in RUNTIME_META
-  // (hermes, kimi, kimi-code, zcode) were missing from it, so `scope: 'local'`
+  // beside RUNTIME_META. It drifted: several runtimes present in RUNTIME_META
+  // (e.g. hermes, zcode) were missing from it, so `scope: 'local'`
   // for any of them resolved `path.join(root, undefined)` and threw a bare
   // TypeError naming neither the runtime nor the map at fault. #3023 had
   // already hit this for `pi` and fixed it by adding one more entry, which