Recording gaps

Every step below is a genuine UI click-path that no Drive doc or skill covers. Rule 4 in the wiki build brief: "where a UI step is genuinely needed and unknown, write the runbook up to that boundary, mark the gap, and add it here." A short honest list here is the deliverable — a confidently invented click-path in the runbook itself is the failure this file exists to prevent.

Seeded from spec §14 Q4 ("current best guess"), then merged with what WP-1/WP-2 actually hit while authoring. Each row: runbook ID · what's missing · why no other source covers it.

Runbook	Gap	Why
E1	Klaviyo campaign build — full click path	Zero Drive content exists; klaviyo-campaign-builder skill encodes the draft logic, not the UI
E3	Klaviyo segmentation basics — click path	Net new, no source; UI-only task
B3	Kive / Higgsfield generation UI path	~20 hf-* skills are API-level; the operator UI flow (uploads, board management, confirm/generate buttons) was never captured
G3	Tracker dashboard walkthrough	tracker.hewsonbrands.com is CF Access gated; the skill queries data, it doesn't describe the dashboard UI

This table is appended to as each runbook gets authored — see the per-runbook frontmatter for its own sources: citation. A runbook tagged recording-needed in its body links back to a row here.