Include additional files with releases

[Mirrowel]

Releases are missing vital documentation like .env.example. There could be other relevant files that might warrant being included. This will involve editing the build workflow.

To agent: investigate and propose what files to include, and investigate changing the build workflow to achieve that.

[mirrobot-agent]

@Mirrowel Thank you for submitting this issue. I am now beginning my analysis and will report back shortly.

[mirrobot-agent]

Initial Analysis Report

Summary: The release workflow currently packages only the application executable, omitting essential configuration templates and documentation files required for deployment.
Issue Validation: Confirmed.
Reproducibility Assessment: Reproducible (verified by analyzing .github/workflows/build.yml).
Root Cause Analysis: In .github/workflows/build.yml, the Prepare files for artifact step in the build job explicitly copies only the proxy_app executable to the staging directory. The subsequent release step archives only what is present in that directory.
Suggested Labels: enhancement, documentation.
Proposed Next Steps:

1. Update .github/workflows/build.yml to include additional files in the staging directory:

   cp .env.example README.md LICENSE DOCUMENTATION.md "Deployment guide.md" "$stagingDir/"

2. Update the FILE_TABLE in the Create Release step of the workflow to list these files in the release notes.
3. Consider if other files like requirements.txt or individual license files from src/rotator_library/ should also be included for completeness.
   Missing Information (if any): None.

This analysis was generated by an AI assistant.