clementine-agent 1.1.13 → 1.1.14
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -10,8 +10,17 @@
|
|
|
10
10
|
* data pipeline is identical and any divergence is purely rule-evaluation.
|
|
11
11
|
*/
|
|
12
12
|
import { CronRunLog } from '../../gateway/cron-scheduler.js';
|
|
13
|
-
import {
|
|
14
|
-
|
|
13
|
+
import { DEFAULT_MAX_TURNS_FALLBACK, DEFAULT_TIMEOUT_MS, MAX_TIMEOUT_MS, TIER_MAX_TURNS, getInterventionStats, readReflections, } from '../execution-advisor.js';
|
|
14
|
+
// NOTE: Phase 9c (commit 4451f36) made execution-advisor.ts static-import
|
|
15
|
+
// THIS module, creating a circular dep. The previous module-init line
|
|
16
|
+
// `void CIRCUIT_BREAKER_COOLDOWN_MS as _COOLDOWN_MS` was deferring access
|
|
17
|
+
// in source comment terms but actually FORCED a TDZ access at context.ts
|
|
18
|
+
// module-init — which is BEFORE execution-advisor.ts has reached line 38
|
|
19
|
+
// where the const is declared. That produced "Cannot access '_COOLDOWN_MS'
|
|
20
|
+
// before initialization" errors on every cron run after Phase 9c shipped.
|
|
21
|
+
// Removed the import + the void line. The cooldown duration is encoded as
|
|
22
|
+
// a literal in the builtin YAML rules, so this module never actually
|
|
23
|
+
// needed the constant — the import was documentation noise.
|
|
15
24
|
/**
|
|
16
25
|
* Build a fresh RuleContext for a job. Pass an existing `advice` if you want
|
|
17
26
|
* to mutate it (e.g. shadow mode passes a clone so the TS path's advice is
|