Duplicate Code: Identical Widget Structure in EmptyCard and InitialCard

*Analysis of commit eaf30eabe62f9b178466629c6d3a4c4390e17311*

## Summary

Two widget files (`EmptyCard` and `InitialCard`) contain nearly identical code with the same structure and implementation, differing only in the class name. Both widgets render an empty centered column with no children.

## Duplication Details

### Pattern: Identical Stateless Widget Boilerplate
- **Severity**: Medium
- **Occurrences**: 2 instances
- **Locations**:
- `lib/ui/widgets/empty_card.dart` (lines 1-17)
- `lib/ui/widgets/initial_card.dart` (lines 1-17)

- **Code Sample**:
``````dart
import 'package:flutter/material.dart';

class EmptyCard extends StatelessWidget {
const EmptyCard({
Key? key,
}) : super(key: key);

`@override`
Widget build(BuildContext context) {
return Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: const [],
),
);
}
}
``````

The `InitialCard` class is identical except for the class name change from `EmptyCard` to `InitialCard`.

## Impact Analysis

- **Maintainability**: Any changes to the widget structure must be duplicated in both files, increasing the risk of inconsistent implementations
- **Bug Risk**: If one widget is updated but not the other, it could lead to unexpected UI inconsistencies
- **Code Bloat**: Two files with 17 lines each containing nearly identical code (34 lines total that could be reduced)
- **Semantic Confusion**: Both widgets appear to serve the same purpose (displaying empty state) but are named differently

## Refactoring Recommendations

1. **Consolidate into Single Widget with State Parameter**
- Create a single `StateCard` widget that accepts a `CardState` enum (empty, initial, loading)
- Estimated effort: 30 minutes
- Benefits: Single source of truth, easier to extend with additional states

2. **Consider Using Builder Pattern**
- If different states need different content in the future, use a builder function parameter
- Benefits: Maintains flexibility while eliminating duplication

3. **Immediate Action (if widgets are truly identical in purpose)**
- Keep only one widget and update all references
- Delete the redundant file
- Benefits: Simplest solution if both widgets serve the same purpose

## Implementation Checklist

- [ ] Review duplication findings with team
- [ ] Clarify whether EmptyCard and InitialCard need different implementations
- [ ] Choose refactoring approach based on future requirements
- [ ] Implement consolidated widget
- [ ] Update all widget references in HomePage and other files
- [ ] Verify UI behavior remains unchanged
- [ ] Remove redundant widget file
- [ ] Update widget exports in `lib/ui/widgets/widgets.dart`

## Analysis Metadata

- **Analyzed Files**: 29 Dart files (excluding tests and generated files)
- **Detection Method**: Manual semantic code analysis
- **Commit**: eaf30eabe62f9b178466629c6d3a4c4390e17311
- **Analysis Date**: 2026-02-22

> AI generated by [Duplicate Code Detector](https://github.com/chimon2000/good_first_issue/actions/runs/22276643303)
>
> To add this workflow in your repository, run `gh aw add github/gh-aw/.github/workflows/duplicate-code-detector.md@94662b1dee8ce96c876ba9f33b3ab8be32de82a4`. See [usage guide](https://github.github.com/gh-aw/guides/packaging-imports/).