Approve a proposed prompt
Save the proposal onto the live agent — which bumps its version, so the existing history and revert still apply — then re-run the same training rows for the next cycle. Columns deployed from this agent pick the new prompt up on their next run.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
The proposal the reviewer actually read, echoed back.
The proposed prompt as displayed. A proposal replaced meanwhile is rejected rather than approved unseen.
1 - 20000Response
Successful Response
A whole training session, as the reviewer's page polls it.
Everything the page needs in one payload: the phase (status), the
cycle, the rows with their results and critiques, and the pending proposal
when there is one.
How far the current cycle's run has got.
A pending prompt revision, alongside what it would replace.
Where a session's training inputs came from.
table, manual Where a training session stands — the state the reviewer's screen shows.
One enum rather than a separate lifecycle flag and phase, because the
phase IS the state: a session is either waiting on the machine
(RUNNING), waiting on the reviewer (REVIEWING, PROPOSED), or
finished. Callers never derive the screen from row counts.
running, reviewing, proposed, completed, abandoned