test: fix local-midnight logger flake and stale kimi k3 thinking format pin

- logger-multiprocess asserted the UTC day (toISOString) while DailyRotateFile names files with the LOCAL date, failing nightly between 00:00 and 02:00 local (UTC+2); the per-pid rotation-file invariant now matches any dated name. - kimi-code k3 bundled compat moved to thinkingFormat 'kimi' with the catalog regen; the K3 named-tool-choice downgrade gate keys on provider/id/baseUrl, so only the stale precondition needed updating.
2026-07-23 00:13:14 +02:00
parent b6e68fd243
commit fc6256372d
4 changed files with 12 additions and 9 deletions
@@ -50,9 +50,12 @@ describe("multiprocess file logging", () => {

 		expect(await Promise.all(processes.map(proc => proc.exited))).toEqual([0, 0]);
 		const entries = await fs.readdir(logsDir);
-		const datedPrefix = `omp.${new Date().toISOString().slice(0, 10)}`;
+		// DailyRotateFile's %DATE% uses the LOCAL date; don't pin an exact day
+		// (toISOString is UTC and diverges around local midnight) — the invariant
+		// is one dated rotation file per pid.
 		for (const proc of processes) {
-			expect(entries).toContain(`${datedPrefix}.${proc.pid}.log`);
+			const perPid = new RegExp(`^omp\\.\\d{4}-\\d{2}-\\d{2}\\.${proc.pid}\\.log$`);
+			expect(entries.some(name => perPid.test(name))).toBe(true);
 		}
 		expect(entries.filter(name => name.endsWith("-audit.json"))).toHaveLength(2);
 	});