209f2fe983
Review round 4, Major 1: scripts/live-config-guard.cjs is pure test instrumentation and was shipping to every npm install. The repo already carries the exclusion convention (gen-emitted-baseline, qa-smell-ratchet) in the same files[] array. Excluding the guard alone would trip the #2858 shipped-requires-only-shipped gate: run-tests.cjs (shipped) requires it at load time, and affected-tests-lib.cjs / run-affected-tests.cjs sit on the same chain. The four files are one closed require chain of test instrumentation, so the exclusion covers the chain, not one link. The guard's LOCATION header cited affected-tests-lib.cjs as "the precedent for a non-shipped helper", which npm pack disproves — rewritten to the tarball-exclusion fact.
1.0 KiB
type, pr
| type | pr |
|---|---|
| Added | 2677 |
runtime-homes now exports its non-registry config-home descriptors — KIMI_HOOKS_TOML_DESCRIPTOR, NON_REGISTRY_CONFIG_HOME_DESCRIPTORS, GSD_LOCATION_ENV_KEYS, and the ConfigHomeDescriptor type are public, so consumers that need the set of config-location env vars (rather than a single resolved path) can derive it instead of hand-maintaining a copy. resolveKimiHooksTomlDir() behaviour is unchanged; its descriptor is simply named rather than inline (#2665).
The test-instrumentation scripts no longer ship in the npm package — scripts/run-tests.cjs, scripts/live-config-guard.cjs, scripts/affected-tests-lib.cjs, and scripts/run-affected-tests.cjs are now excluded from the tarball (they are one closed require chain of repo-only test tooling). npm test in an installed package was already inoperable (tests/ has never shipped); a deep import of scripts/run-tests.cjs from the published package — an unsupported surface — will now be MODULE_NOT_FOUND (#2665).