Mark the user's decision on an edit — records which baseline they reviewed
Context Documents
Mark the user's decision on an edit — records which baseline they reviewed
Stamp reviewed_baseline on the edit with the current tree’s
baseline for this edit’s path.
Called by the UI after Keep-mine and careful-merge save, so the row disappears from “needs review” until the next regen produces a different baseline. Auto-merge handles this in its own handler.
POST
Mark the user's decision on an edit — records which baseline they reviewed
Authorizations
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Response
Successful Response
LLM-based three-way merge of a user edit with the current LLM output
Previous
Clear (soft-archive) a persisted edit
Next