Set up automatic update possibility.

Put a twInstallConfig.txt file in /home/<linux username>/maintenance/ that contains the configuration settings of the installation.

Then make a script that scans all the folders/users in /home/ and inspects whether it contains that twInstallConfig.txt file in ../maintenance/. If it is found, read:

the username that contains the taskwarrior installation, and the direct path to the pending.data etc. files.

Preferably build the updates such that they can be added onto, rather than overwritten to, the current tw installation.

However, if need be, and a new installation is required for some reason:

1. Ask permission of the user,


2. Tell the user to make a backup of additional files that were added to the wsl beyond this tw install.


3. Make a backup of the pending.data etc. file


4. lxrun /uninstall /full /y uninstall the wsl.


5. Re-Install the new updated tw setup.

Start by reviewing the existing shell installation flow and how installations under /home//maintenance/ are currently represented. Define how twInstallConfig.txt discovery, pending.data backups, user permission, and the lxrun /uninstall /full /y fallback should fit together; done means existing installations can be identified and updated without losing their data.

Written by the indexing model from the issue text.