Test Setup

Trace setup.sh execution without running it — dry-run analysis.

If $ARGUMENTS provided (e.g., --terminal, --godot), focus on that component only.

1. Read the scripts:

   • setup.sh (orchestrator)
   • scripts/common.sh (shared utilities)
   • Each component script that would execute

2. Trace execution path: Determine:

   • Which component scripts run, in what order
   • Files copied/created/modified (source -> destination)
   • Packages installed
   • Commands executed

3. Check for issues:

   • Missing source files (every cp/ln target exists in assets/?)
   • Permission needs (sudo operations?)
   • Existing file conflicts (destination already exists?)
   • Package availability (dnf info <pkg> without installing)
   • Idempotency issues (mkdir without -p, ln without )