dsh-plugin-scout

Data and configuration

• Index: ~/.dsh/dsh-plugin-scout/index.json stores facts only (repo metadata, slimmed manifests, npm cache) and is re-judged against the current runtime on every load, so compatibility verdicts follow DSH upgrades automatically.
• Optional config: dataDir, topic, runtimeVersion (overrides runtime detection), autoRefresh (boolean, default true), autoRefreshHours (hours, default 1). Set autoRefresh: false to disable automatic refresh; autoRefreshHours: 0 remains the legacy disable switch.
• Host-only scheduling: after a 45 s startup grace period and index loading, Scout checks whether the persisted succeededAt completion time is older than the configured interval, falling back to the legacy crawledAt crawl-start watermark when no completion clock exists. One in-process timeout checks each interval; missed intervals are not replayed. Scheduling lives only in the DSH Host, not the browser or a daemon; no LaunchAgent or external scheduler is created, and plugin disposal cancels the timeout.
• Shared refresh path: automatic refresh uses the existing default mode: incremental after fullAt exists, otherwise an initial full crawl. Manual and automatic refresh share one single-flight operation and cannot run overlapping crawls. GitHub cooldowns are respected; a long Retry-After defers work rather than being clipped to a shorter wait.
• Durable success clock: succeededAt advances only after successful atomic persistence of a completed refresh. Checkpoints preserve the previous success clock; failures do not mark a refresh as successful or discard old facts.

Automatic refresh has been manually accepted in the live DSH application. UI position preservation is covered by client regression tests.