feat(sds): render F0HILActionConfirmation with F0CardRow

[warcos-fact]

What

Updates F0HILActionConfirmation to render with F0CardRow instead of its bespoke div + buttons layout: the confirm action becomes the primary, cancel becomes a secondary.

Sequencing

Third step of the ship sequence:

1. ButtonGroup (feat(ui): add ButtonGroup — a data-driven action bar #4339)
2. F0CardRow (feat(ui): add F0CardRow component #4340)
3. F0HIL → F0CardRow (this PR)

Stacked on feat/f0-card-row so it compiles against F0CardRow. Retarget to main once #4340 merges. The dead oneLiner variant has been removed from the cocreation branch, so nothing competes with this.

🤖 Generated with Claude Code

[github-actions]

📦 Alpha Package Version Published

Use pnpm i github:factorialco/f0#npm/alpha-pr-4341 to install the package

Use pnpm i github:factorialco/f0#6cc0b5777f99148cccdb7811fbf99d7d0e19b8e5 to install this specific commit

[github-actions]

🔍 Visual review for your branch is published 🔍

Here are the links to:

• the Visual Review Page

• the latest build on chromatic

• the full storybook

[github-actions]

Coverage Report for packages/react

Status	Category	Percentage	Covered / Total
🔵	Lines	53.05%	15409 / 29041
🔵	Statements	52.18%	15989 / 30638
🔵	Functions	45.23%	3468 / 7667
🔵	Branches	46.05%	10945 / 23767

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
packages/react/src/sds/ai/F0HILActionConfirmation/F0HILActionConfirmation.tsx	0%	0%	0%	0%	5-29
packages/react/src/sds/ai/F0HILActionConfirmation/types.ts	100%	100%	100%	100%

Generated in workflow #14376 for commit 043da63 by the Vitest Coverage Report Action

[rubenmoya]

title is mandatory in F0CardRow, that's why we're using ?? "", but if that happens we will show a card without any title... do we want that? Sounds like a broken UI to me

[warcos-fact]

Good catch. We had the same issue in the previous PR that builds the CardRow. I'll review and fix.

[warcos-fact]

Reviewed — this is not addressed yet. text is still optional (text?: string in types.ts) and we still coerce with title={text ?? ""}.

F0CardRow guards the title with {title && …}, so an empty text won't crash, but it renders a confirmation row with no prompt — just the description + ✓/✗ buttons — which is the broken UI you flagged.

Fix I'm going with: make text required (text: string) and drop the ?? "". A HIL confirmation without a prompt has no meaning, and there are no external consumers yet (only the stories, which all pass text), so tightening the type is safe and removes the coercion entirely. Pushing that now.

[github-actions]

✅ No New Circular Dependencies

No new circular dependencies detected. Current count: 0

[github-actions]

⚠️ Breaking public API changes (4)

These public exports were renamed/removed, or had a property/parameter removed, retyped, or newly required compared to main — that breaks consumers. Adding new exports or new optional props is always safe and is not flagged. If a breaking change is intentional, note it in the PR description and use a feat!:/BREAKING CHANGE commit so the release is a major bump.

Comparing f0, experimental and ai against main. Adding components, types, or optional props is safe. This check is non-blocking.

f0

• ✏️ F0HILActionConfirmation — breaking change

  • __0.text became required
  before → after

  // before
  ({ text, confirmationText, onConfirm, cancelText, onCancel, }: F0HILActionConfirmationProps) => JSX_2.Element
  // after
  ({ text, description, avatar, confirmationText, onConfirm, cancelText, onCancel, stackAt, }: F0HILActionConfirmationProps) => JSX_2.Element

• ✏️ F0HILActionConfirmationProps — breaking change

  • text became required
  before → after

  // before
  F0HILActionConfirmationProps
  // after
  F0HILActionConfirmationProps

ai

• ✏️ F0HILActionConfirmation — breaking change

  • __0.text became required
  before → after

  // before
  ({ text, confirmationText, onConfirm, cancelText, onCancel, }: F0HILActionConfirmationProps) => JSX_2.Element
  // after
  ({ text, description, avatar, confirmationText, onConfirm, cancelText, onCancel, stackAt, }: F0HILActionConfirmationProps) => JSX_2.Element

• ✏️ F0HILActionConfirmationProps — breaking change

  • text became required
  before → after

  // before
  F0HILActionConfirmationProps
  // after
  F0HILActionConfirmationProps