PRDCT-483: Flows section rework — unified method + live-verify

[Iamfle4ka]

Flows section under the unified section-at-a-time method

Reworks the Flows section page-by-page (one section = one PR): structure → form → live-verify against the running platform (project 6015; a temporary flow was created in a dev branch for verification and deleted afterwards).

What changed (per page / commit)

• New page: /flows/variables/ (Flow Variables) — the ~150-line deep-dive (static/dynamic values, JMESPath aggregations, COUNT/DATE functions, variable merging into component jobs) moved out of the hub into its own page; nav entry added, sidebar regenerated. The hub keeps a summary + link. No inbound links pointed at the moved anchors (verified).
• /flows/ (Conditional Flows hub) — live-verified fixes (below), scheduling section rewritten, description frontmatter, 5 TODO(human-review) flags.
• /flows/flows-legacy/, /flows/flow-migration-guide/ — description frontmatter (legacy page intentionally left minimal: deprecated, auto-migration planned).

Live-verified in-product

• ✅ Sidebar section Conditional Flows; conditional listing (/flows-v2) with Create Flow; Legacy Flows listing.
• ✅ Builder tabs: Builder / All Runs / Schedules / Notifications / Versions (now mentioned in Access Flows).
• ❌→fixed: the Add Task menu offers Component / Notification / Variable — docs claimed "+ adds components, conditions, variables, notifications and more" and "choose Set Variable" (actual label: Variable).
• ❌→fixed: scheduling is Schedules tab → Create Schedule, with multiple independent schedules (date/time or table triggers) — docs described a "Set Schedule" button and didn't mention multiple schedules.
• ✅ Set Variable panel: Variable Name; Static Value / Dynamic Value ("Pick from a task, phase, or function").

Flagged for owner review (TODO(human-review))

• Retry defaults (3 attempts / 10 s delay)
• 10-parallel Storage-job guidance/cap
• Trigger cool-down semantics
• "End Flow in the ELSE path" mechanism + exact label
• Condition-type list; how conditions are added in the Builder (not in the Add Task menu)

Verification

• npm run build clean (259 pages).
• node scripts/audit-phase2.mjs: MISSING IMAGES 0; broken internal links = pre-existing only (/404, /workspace/table-export; the /ai/kai-assistant/ one is fixed in PRDCT-482: AI section rework (kai/ai) — unified method + live-verify #1007).
• All inbound /flows/#… anchors (#conditions, #retry, #control-task-execution, #phases-and-tasks, #schedule-and-automate) still resolve after the split.

Draft — do not merge. Owner sign-off needed on the flagged facts.

🤖 Generated with Claude Code

[linear-code]

PRDCT-359

PRDCT-483

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
connection-docs	Ready	Preview	Aug 8, 2026 12:08am

[Iamfle4ka]

Rebased onto main — CONFLICTING → MERGEABLE.

Conflict was flows/index.md, in the Conditions section: this branch had left a TODO(human-review) asking someone to confirm the condition-type list, while main added a sentence about evaluation scope. Kept both — main's sentence as the content, the TODO comment underneath so the verification ask isn't silently dropped.

npm run build clean (307 pages). audit-phase2: 0 missing images, and the only /flows/ findings are the two intentional developers.keboola.com/integrate/jobs/ links (that section isn't migrated yet). The 45 broken internal links the audit reports are all pre-existing in main under /extend/*.

Note: two related edits are sitting uncommitted in my worktree — cross-links to /flows/variables/ from transformations/variables/index.md and the onboarding cheat sheet. They look like they belong to this PR but I did not author them, so I left them out of the rebase rather than ship them unreviewed.