version 1

[HANSKMIEL]

Hello Copilot,

Finally, there is a working program that is deployed on the VPS. There are several things that need immediate attention and several things that I would like in the near future. Please analyse the following:

Immediate steps:

1. Protect the functioning deployment from breaking. Analyse all that is needed to do this with regard to isolation from unintentional breaking from further development work, security issues, update issues, pipeline changes.

2. analyse and make a plan on how to do step 1 and then look into all the files in the repo and see how we can clean and restructure the repo. Perhaps all files that are no longer relevant or being used can be catergorized and put into a catergorie folder with one archive folder on the main branch.

3. Look into all op issues and Pr's and close all that are no longer needed for further development.

4. This deployed version is version 1 and will be labelled as V1.00. This version will now be protected and if possible added as a package in the repo. A copy of this version will be used for further development and labelled V.1.00D and added in a development package in the repo.

5. I want to add V1.00 as a pages deploy from the main repo.

6. Dubble check all md files for development steps and bundle into one file. Update the readme file.

7. Update the copilot instructions based on this plan. Make a folder lablled "DEV_OPS_STEPS" and add the extensive new copilot instructions to a sub folder labled "DEV_OPS_COPILOT". The file will be labled COPILOT_INSTRUCTIONS_V1_POSTreporeorganisation.

Adittional steps with lesser priority:

8. Examine all script files for relevance and adjust to work with V1.00D. If script files are needed for V1.00 to run and function than make a copy of that script to run with V1.00D, adjust the copy file where necessary to run with V1.00D.

9. I need a script that I can manually trigger to update working new developments from V1.00D to V1.00. When triggerd the deployed version should be updated after all tests have passed.

10. Update all ci/cd pipeline testing to run on V1.00D.

[github-actions]

The GitHub issue outlines a multi-step plan to stabilize, organize, and improve the development workflow for a newly deployed "Version 1" (V1.00) of a program. Immediate priorities include ensuring the current deployment is safeguarded from unintentional disruptions caused by further development, such as isolating it from security risks, update issues, and pipeline changes. The repository will be cleaned, reorganized, and outdated files archived, while irrelevant issues and pull requests will be closed. Version 1 will be labeled and preserved in the repository, with a development copy (V1.00D) created for ongoing work. V1.00 will also be deployed via GitHub Pages. Documentation will be updated and bundled, including detailed copilot instructions to be placed in a specified folder structure. Additional lower-priority tasks include examining, updating, and duplicating script files needed for compatibility with both V1.00 and V1.00D, creating a manual update script for syncing development changes