← All frames
Flow 1 · Build entry · Frame (a) · route /applications

“Build your application” card

A second CTA card sits immediately after the existing dashed Add application card at the end of the Applications grid (ApplicationsPage.tsx, today ~L363). Same footprint and keyboard behaviour as its sibling, but solid-bordered with the fuse seam on top: it is the agent-driven path, not the manual one. The card exists only while fuzefront.apps.build-with-agent is ON.

(a1) Flag ON — both CTA cards, Build after Add

Applications

Federated apps registered to your workspace.

(a2) Flag OFF — card not rendered (not disabled, not hidden by CSS)
(a3) Flag still resolving — treat as OFF (no flash-in, no layout jump on Add)
(a4) Flag ON + the caller has an in-flight session — card becomes a resume shortcut

Behaviour. The card is a role="button" with tabIndex=0, activated by click, Enter or Space — identical to the Add card. It routes to /applications/build (frame b). In (a4) the latest non-terminal session from GET /build-sessions?limit=1 turns the card into a resume link to /applications/build/:sessionId; that read only happens when the flag is ON.
Flag. fuzefront.apps.build-with-agent, release, default OFF, builders audience. OFF ⇒ the component returns null. The page change is a single mount of <BuildAppCard /> from @fuzefront/app-builder-ui after the Add card — the card's own markup and logic live in the package.
Test hooks: [data-frame='01-build-entry'] · [data-panel='applications-grid'] · [data-action='add-application'] · [data-card='build-application'] · [data-action='build-application'] · [data-flag-state='off'] · [data-flag-state='loading'] · [data-action='resume-build-session'].

← IndexBuild form →
Review · app-builder approve or reject each flow ↓
build-entrypendingApproveReject
build-sessionpendingApproveReject
creator-ownershippendingApproveReject
marketplace-publishpendingApproveReject