Add archiving UI with configurable version retention

[Copilot]

Implements UI for archiving older project versions to a destination folder, keeping only N most recent versions active.

Changes

New module: archiving.lua

• Scans parent directory for versioned folders
• Determines archivable versions: version < (current_version - versions_to_keep)
• Copies old versions to archive destination (preserves originals)

UI section in gui.lua

• Integer input for versions to keep (default: 3, validates ≥1)
• Archive destination display with path truncation
• Browse button (uses JS extension if available, validates text input fallback)
• Archive Now button (enabled when project loaded + destination set)

Event handlers in RASP.lua

• Browse: folder selection with validation
• Archive: executes archiving, displays status

Configuration in config.lua

• Added archive_destination and versions_to_keep settings (persist via ExtState)
• Increased default window height to 400px

Example

With current version v10 and keep=3:

• Cutoff: v10 - 3 = v7
• Archives: v1-v6 (all versions < v7)
• Keeps: v7-v10 active

Original prompt

---

This section details on the original issue you should resolve

<issue_title>UI for archiving</issue_title>
<issue_description>Create user interface for the archiving.
This should be there below save button.

It should state "archive now".
As well there is integer field where can me added number of versions what should be kept active and not archived. All other versions (older ones) what version number is less than current version minus that set value should be arviced.

Ui should as well have destination selection. It should be file folder destination browser.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes UI for archiving #5

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Zesseth]

This should be merged to V0.2_features branch, not to master.

[Zesseth]

@copilot please change branch to V0.2_features

[Copilot]

@copilot please change branch to V0.2_features

I can see that the V0.2_features branch already contains all my commits (7923418, 9714c54, 2465b56). The PR base branch needs to be changed on GitHub - I cannot change it directly via git commands.

If you'd like me to create a new branch based on a different starting point for V0.2_features, please let me know what the base should be. Otherwise, you can change the PR target branch in the GitHub UI by editing the PR and selecting V0.2_features as the base branch.