05 — Host / FS / KB Blind Spot (v_rp_host_fs_kb_blind_spot_status)

For each non-DB source: count_known, count_partial_basis, adapter_coverage, source_freshness_at, freshness_age_hours, ui_safe_as_count, blind_spot_label.

source	layer	known	freshness	ui_safe_as_count	label
host_crontab	HOST	54	02:10 UTC	true	COVERED_FRESH
systemd_timers	HOST	22	02:10 UTC	true	COVERED_FRESH
docker_containers	HOST	11	02:10 UTC	true	COVERED_FRESH
fs_dot_bin	FS	287	02:10 UTC	true	COVERED_FRESH
fs_scripts	FS	42	02:10 UTC	true	COVERED_FRESH
kb_sop_docs	KB	2	06-04 10:15	false	PARTIAL_DECLARED_BLIND_SPOT
host_trigger_classes	HOST	77	02:10 UTC	false	HOST_ONLY_NOT_IN_DB_UNIVERSE_SHOW_AS_HOST_PARTIAL

Findings

• 5 host/FS sources are fresh (≤26h) and safe to render as exact counts.
• kb_sop_docs enumerates only a 2-doc subset of KB SOP prose (vector store is not exhaustively crawlable) → declared PARTIAL; UI must show a "subset only" badge, never a definitive count.
• host_trigger_classes (77) exist on the host (crontab/cron.d/systemd) but are not enumerable in the DB universe — they must appear as HOST_PARTIAL, never silently dropped because the DB-only view doesn't contain them. This is the single most important "host-only must not disappear" guarantee.