bug(workspace): Add table for workspace folder metadata to manage hashes and conversation history

[dariuszkowalski-com]

Description

Currently in Forge, the workspace_id is a hash derived from the folder name. Since this hash is one-way, it is not possible to recover the folder name from the workspace_id. This leads to a lack of information in the database about which folder/project a conversation originated from. This is problematic especially when working with branches and worktrees. When a branch is closed and the folder is deleted, access to the conversation history is lost, although the data still resides in the database, occupying space and potentially affecting performance.

Current Behavior

workspace_id is a hash of the folder name, making it impossible to trace back the folder/project from the conversation in the database. Lost access to conversation history when branches/folders are deleted while data remains in the database.

Expected Behavior

A new table should be added that stores the folder name from which the workspace_id originated, the workspace_id itself, creation date of the workspace, and the date of last access to the workspace. This will allow future implementation of management and operational mechanisms for workspaces.

Steps to Reproduce

1. Create a workspace from a folder.
2. Use the workspace and generate conversation history.
3. Delete the folder or branch associated.
4. Notice loss of access to conversation history despite data remaining in the database.

Environment

• Forge Version: ALL with conversation based on SQLite

Additional Context

This enhancement is important for workspace management and addressing performance issues caused by orphaned conversation data.

[dariuszkowalski-com]

I am going to repair it