Define provider scheduling and coherent model revision baseline for #66

[Joncallim]

Problem

Current refresh publication combines Docker inventory with every optional runtime provider in one bounded blocking pass; the browser refetches snapshot/runtime on every SSE heartbeat. #66 needs an evidence-backed contract before changing scheduling.

Scope

• Add an ADR defining fixed provider slots/policies, provider-state vocabulary, opaque model revision semantics, and source/redaction constraints.
• Add deterministic baseline instrumentation/tests for current static collection cadence and SSE/browser refetch behavior.
• Generate/validate only the minimal core contract additions required for the baseline.

Non-goals

• Do not introduce the scheduler, new provider commands, generic job framework, user-configurable policy DSL, conditional fetching, or telemetry persistence in this slice.
• Do not change existing refresh cadence/public behavior except adding correctly source-stamped metadata.

[Joncallim]

Resolution Evidence

• What changed: PR Define #66 provider scheduling and model revision baseline #180 adds the Epic: Build a provider scheduler, freshness model and revision-based refresh path #66 scheduling/model-revision ADR and debug-only deterministic instrumentation for the current static refresh pass.
• Why this resolves the issue: It records the true baseline—fixed sequential provider stages and a non-unique snapshot-observation token—without falsely claiming that a scheduler or coherent model revision already exists.
• How I checked it: Independent review corrected the initial overstatement of snapshotVersion; the amended PR had a clean review and full green CI. Focused checks included contracts, rustfmt, Clippy, and 129 daemon tests. Merged main: 69cb972.
• Remaining risk or follow-up: Epic: Build a provider scheduler, freshness model and revision-based refresh path #66 scheduler, independent provider freshness, coherent model revision, revision-driven SSE and conditional browser fetching remain future implementation slices.

Recommendation: This issue appears resolved and can be closed by a maintainer.