correctness-and-error-handling

Correctness & Error Handling Fix

Find and fix correctness issues and missing error handling in $ARGUMENTS (or the whole app if no argument is given). Work through every step below. Each step searches for problems and then fixes them in place. Only report issues that cannot be auto-fixed.

Step 1 — Map data flows and fix known defects

Read these files before checking anything:

• src/main.tsx / src/App.tsx — top-level error boundaries and auth flow
• All files matching **/hooks/*.ts, **/contexts/*.tsx — shared async state
• All files matching **/api/*.ts, **/services/*.ts — CDF SDK call sites

For each async data source, note:

• What happens when the request fails (network error, CDF 403, timeout)?
• What does the UI show while loading?
• What does the UI show if the result is empty?

Find and fix known defects in critical paths

# Find TODO/FIXME/HACK in critical code paths (not test files)
grep -rn --include="*.ts" --include="*.tsx" -E "(TODO|FIXME|HACK|XXX):" src/ | grep -v ".test." | grep -v ".spec."

# Find "fix" or "broken" or "workaround" markers
grep -rn --include="*.ts" --include="*.tsx" -i -E "(TODO.*fix|workaround|broken|known.?bug|temporary.?hack)" src/

For each match in a critical path (data fetching, rendering, auth, navigation):

1. Read the surrounding code to understand the incomplete/broken behavior.
2. Fix the underlying issue — implement the missing logic, correct the broken behavior, or add proper error handling.
3. If the fix requires significant architectural changes beyond this skill's scope, replace the TODO with a safe failure mode: graceful error handling, a sensible fallback value, or an explicit user-facing message explaining degraded functionality.
4. Remove the TODO/FIXME/HACK comment after fixing. The code should speak for itself.

Do not leave TODOs in critical paths. Every one must be resolved or converted to a safe fallback.

Step 2 — Add top-level error boundary