refactor(process-table): read the staleness bound from its own module, not the Node-only reader

#18814 moved PROCESS_TABLE_SNAPSHOT_MAX_STALENESS_MS into process-table-snapshot.ts and left
a re-export on the reader, so these two callers still resolve it through
`node:child_process`. Both run in Node, so neither is broken — but the renderer file beside
this test was the one that blanked the app by importing that exact path, and the boundary
ratchet only walks shipped code, so nothing would flag a copy-paste back out of the test.
Point both at the defining module.
This commit is contained in:
Neil
2026-09-05 02:35:30 -07:00
parent 0bbf86bb7a
commit ae9fce9b4d
2 changed files with 2 additions and 2 deletions
@@ -57,7 +57,7 @@ const { POLL_TIER_INTERVAL_MS } = await import(
path.join(ROOT, 'src/renderer/src/components/terminal-pane/agent-completion-poll-cadence.ts')
)
const { PROCESS_TABLE_SNAPSHOT_MAX_STALENESS_MS } = await import(
path.join(ROOT, 'src/shared/process-table-snapshot-reader.ts')
path.join(ROOT, 'src/shared/process-table-snapshot.ts')
)
// Pre-change: independent ±10% jitter per pane, re-rolled on every reschedule.
@@ -1,5 +1,5 @@
import { describe, expect, it } from 'vitest'
import { PROCESS_TABLE_SNAPSHOT_MAX_STALENESS_MS } from '../../../../shared/process-table-snapshot-reader'
import { PROCESS_TABLE_SNAPSHOT_MAX_STALENESS_MS } from '../../../../shared/process-table-snapshot'
import { POLL_TIER_INTERVAL_MS } from './agent-completion-poll-cadence'
import { nextCadenceInspectionDelayMs } from './agent-completion-poll-interval'