docs: fix two stale UI labels found by walking the platform (HTTP rows, Kai Agent button)

[Iamfle4ka]

Four places where our docs describe an interface that has moved on. All four were found by actually walking the platform for the Getting Started rework (#1071) and verified live in a project on 2026-08-04 — none is inferred.

Kept out of #1071 deliberately: these belong to their own sections.

flows/

Scheduling is no longer a Set Schedule button. It is the flow's Schedules tab → Create Schedule → Set Up Schedule, with predefined intervals (Every 15 minutes / Every hour / Once a day / Once a week / End of month) or a custom one.

Also documents two things the old text could not: a flow can hold several schedules, they fire independently, and each has a toggle so you can pause one without deleting it.

flows/flows-legacy/ also says "Set Schedule" and is left alone — that is correct for the legacy builder.

management/notifications/

Split by flow type instead of describing only the legacy path.

A Conditional Flow's Notifications tab is edited in place — no "Edit Notifications" button — with three cards: Success, Errors, Processing (longer than usual by a percentage you set). There is no warning notification; Conditional Flows express that through conditions, which is why the old "requires Continue on Error" note doesn't apply there.

The legacy instructions are kept and labelled as legacy.

Also renamed the second of two sections both titled "Flow Notifications" (### 1. and ### 2.).

components/extractors/storage/http/

The page is the reference for the connector the new Getting Started step 2 is built on, so its labels now matter more:

Page said	UI says
"Add Table" button	Add Row, in a Rows section
"Table Name", derived from the configuration table name	Table name, seeded from the row name
"Incremental Load"	Incremental load

Added that Read Header already defaults to Read the header from the file(s) header — the setting most readers want and never need to touch.

kai/

The button reads Kai Agent with a Beta pill, not KAI. Fixed on both kai/index.md and kai/getting-started.md.

Verification

• npm run build clean — 306 pages
• node scripts/audit-phase2.mjs — MISSING IMAGES 0; the 45 broken internal links are pre-existing dev-docs gaps (/overview/encryption/, /overview/api/), none from this change
• no screenshots changed: every fix is a label in prose

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
connection-docs	Ready	Preview	Aug 6, 2026 11:18pm

[Iamfle4ka]

Rebased on main (2026-08-07) — and the scope shrank from four labels to two.

Landed independently, dropped from this PR: flows/ scheduling and management/notifications/ both arrived on main with richer versions than the ones here — screenshots of the Schedules tab and the Create Schedule dialog, the Date & Time vs Triggered split, the Email/Webhook sub-tabs, and the Warnings-card difference between conditional and legacy flows. Main's text is a superset of what this branch proposed, so I took main's side on both conflicts rather than re-landing a thinner version.

Still unlanded, still in this PR:

• components/extractors/storage/http/ — the connector uses configuration rows, not "Add Table": it is Add Row in the Rows section; the base URL lives under Base URL and Connection Options; and Read Header already defaults to reading the file's header, so the step is to leave it alone.
• kai/index.md + kai/getting-started.md — the button is Kai Agent, marked Beta, in the project's top bar, not a KAI button in the navigation bar.

Build clean. The Kai label fix is a prerequisite for the Kai pass going into #1071, which references that button by name.