Missing first-run GUI setup
The GUI warns when config.env is missing, but still allows Run. It should create a config from the example and validate source/archive folders first.
$ cat KNOWN_ISSUES.md
The project is suitable for personal use, but these items should be resolved or clearly documented before broad public release.
The GUI warns when config.env is missing, but still allows Run. It should create a config from the example and validate source/archive folders first.
The shell script currently uses source "$CONFIG_FILE". Users should only load trusted config files until a restricted parser replaces this.
The tool should reject cases where ARCHIVE_ROOT equals or is nested inside SOURCE_PATH.
The current desktop file points at one machine path. Public installs need a generator or installer step.
.env files are not excluded by default. Users should configure additional exclusions before archiving sensitive projects.
Missing Python or Tkinter may fail invisibly from a desktop launcher. Terminal launch remains the clearest diagnostic path.