chore(frontend/types): cleanup vue-tsc errors in Storybook stories cluster (~64 errors, #7227 follow-up) #7273

Cluster cleanup PR for #7227 (vue-tsc baseline). The Storybook *.stories.ts files account for ~64 of the 250 documented errors.

Affected files (top of cluster)

• Icon.stories.ts (14 errors — TS2353 unknown property in literal)
• BaseAlert.stories.ts (7)
• BaseCard.stories.ts (6)
• BaseModal.stories.ts (6)
• BaseTable.stories.ts (5)
• BaseBadge.stories.ts (5)
• ChatHeader.stories.ts (5)
• EmptyState.stories.ts (4)
• ErrorBoundary.stories.ts (3)
• MessageStatus.stories.ts, StableLoadingState.stories.ts, ProgressBar.stories.ts, LoadingSpinner.stories.ts, DataTable.stories.ts, BaseInput.stories.ts (1-2 each)

Error pattern

Most are TS2322/TS2353 — story args don't match component prop types. Examples:

BaseBadge.stories.ts(46,5): error TS2322: Type '"secondary"' is not assignable to type '"success" | "warning" | "error" | "info" | "default" | "primary" | undefined'.

This is mechanical — either fix the story args to match prop unions, or fix the component prop type to include the missing value.

Approach

1. npx vue-tsc --noEmit -p tsconfig.app.json 2>&1 | grep stories.ts to enumerate
2. For each file: align story args with component props (or add the missing variant to props)
3. Re-run vue-tsc; baseline should drop ~64
4. Update .github/workflows/frontend-typecheck-regression.yml BASELINE from 250 to ~186

Why this cluster first

• Lowest risk: stories are isolated dev tooling, not production code
• Largest single category that's mechanical (one fix pattern)
• Each file is independent — can be done in parallel sub-PRs

🤖 Filed during #7227 closure.