kimi-code/scripts/check-service-naming.mjs
Haozhe bb16383aa1
refactor: remove the legacy agent-core v1 package (#3542)
* refactor: remove the legacy agent-core v1 package

Delete packages/agent-core (v1 engine) and migrate node-sdk fully onto
agent-core-v2:

- node-sdk owns its public contract (error protocol, KimiConfig schema
  and file IO, process-global logging facade, telemetry client
  interface); event and interaction types re-export from
  @moonshot-ai/protocol or agent-core-v2
- createKimiHarness is now the single harness factory, backed by the
  v2 client; the v1 SDKRpcClient is deleted
- CLI and vscode run agent-core-v2 unconditionally;
  KIMI_CODE_LEGACY_FLAG and useAgentCoreV1 are removed
- the wire.jsonl replay fold moves into agent-core-v2's replayBuilder
  (foldWireRecords), and the v2 journal now persists tool-call display
  so replay restores diff/todo displays
- TUI engineV2 branches collapse to the v2 path

* test(vscode): retry temp-dir teardown in replay-resume integration test
2026-09-07 11:17:51 +08:00

70 lines
2.2 KiB
JavaScript

#!/usr/bin/env node
/**
* Enforce the VS Code-style service naming convention finalized in
* Phase 5 of the 2026.06.07 services-alignment plan:
*
* - packages/services/src/<domain>/<domain>.ts (+ <domain>Service.ts)
* - packages/kap-server/src/services/<domain>/<domain>.ts (+ <domain>Service.ts)
*
* Domain dirs and service-related .ts files must be camelCase — never
* kebab-case (no `-` in the name). Anything outside these two roots is
* ignored (test fixtures, etc.).
*
* Exit code 0 if clean, 1 with an actionable report otherwise.
*/
import { readdirSync, statSync, existsSync } from "node:fs";
import { resolve, join, relative } from "node:path";
const ROOT = resolve(import.meta.dirname, "..");
const SERVICES_SRC = join(ROOT, "packages/services/src");
const SERVER_SERVICES_SRC = join(ROOT, "packages/kap-server/src/services");
/** @type {Array<{ kind: string, path: string }>} */
const violations = [];
function isKebab(name) {
return name.includes("-");
}
function report(kind, absPath) {
violations.push({ kind, path: relative(ROOT, absPath) });
}
/**
* Both roots are organised as <domain>/<files>.ts plus a few top-level files
* (index.ts, module.ts, pinoLoggerService.ts). Flag kebab in dir names and in
* any .ts file directly under a domain dir.
*/
function scanServicesSrc(srcRoot = SERVICES_SRC) {
if (!existsSync(srcRoot)) return;
for (const entry of readdirSync(srcRoot)) {
const abs = join(srcRoot, entry);
const st = statSync(abs);
if (st.isDirectory()) {
if (isKebab(entry)) report("kebab-dir", abs);
for (const f of readdirSync(abs)) {
if (!f.endsWith(".ts")) continue;
if (isKebab(f)) report("kebab-file", join(abs, f));
}
} else if (entry.endsWith(".ts") && isKebab(entry)) {
report("kebab-file", abs);
}
}
}
scanServicesSrc();
scanServicesSrc(SERVER_SERVICES_SRC);
if (violations.length > 0) {
console.error(
"Service naming violations (no kebab-case allowed for service files/dirs):"
);
for (const v of violations) console.error(` [${v.kind}] ${v.path}`);
console.error(
"\nRename to camelCase per VS Code convention: <domain>.ts + <domain>Service.ts."
);
process.exit(1);
}
console.log("Service naming check passed.");