Allow editing prompt revision metadata after commit

[mmabrouk]

Currently, it's only possible to add meta-information about a prompt revision when committing the change. After that, you cannot:

1. Add comments
2. Edit the revision name (fixed to v{i})
3. Edit the commit message

However, users often want to add information after committing a prompt (e.g., "we should deploy this one", "best accuracy").

Potential solutions:

1) Add comments to prompt revisions

• Pros: Enables team discussions on revisions; can be reused for other entities (e.g., evaluation comments)
• Cons: Hard to display cleanly in the registry; significant implementation effort

2) Allow editing commit messages

• Pros: Directly solves the problem
• Cons: Commit messages are typically immutable (like in Git); editing them changes history

3) Allow editing version names

• Pros: Solves the problem simply
• Cons: Could make organization chaotic; inconsistent with how variants are named

4) Add tags to revisions

• Pros: Lightweight solution
• Cons: Less descriptive than full comments or messages

Original user request:

Hey, is it possible to rename the version of the prompt, for example next to V2 add deploy?
Also would it be possible to edit notes after committing the prompt? Sometimes we want to add some comments after Commit but it seems not possible

[jp-agenta]

Thanks @mmabrouk,

Some comments to add color to the discussion,

On revisions:

Reference (not editable)

• revision id (unrelated, here)
• revision slug matches name in our current apps, but is a separate field in new workflows.
• revision version is the auto-increasing number that is used in v{i} in the webUI.

Header (editable)

• revision name is a string, editable at and after commit, except... in current apps where it matches the slug. 😕
• revision description is a string, editable at and after commit, except... that it doesn't exist yet in current apps. 😕

Commit (not editable)

• revision author (unrelated, here)
• revision date (unrelated, here)
• revision message could be made editable, at the expense of immutable commit ; I wouldn't do it but I could be convinced.

On metadata:

• tags would be key-only or key-value attributes that will allow operations like search, filter, suggestions, auto-complete and so on.
• meta would be a user-defined blob (json object) that is opaque to Agenta that will allow operations like set and get.
• comments would be a thread-like discussion with mentions to resources like team members, and entities in Agenta.

[jp-agenta]

TL;DR

name and description seem like appropriate solutions here, but our current revisions don't have description and their name is used as a slug. 😄

[mmabrouk]

I guess this means we'll have to wait for the migrations of apps to workflows to be able to achieve this through:

• revision name
• revision description
• tags