0.242.0: codes.task@2 — a coding task's attempts and outcome; one id, two majors
OPOpenVibers committed 14 days ago · tag v0.242 · 0 files, +0−0
codes.task@2 is codes.task@1 with the same fields, plus two: the task's
attempts (its timeline: every try, the agent, the machine, the session, the
state it ended in, why, what it cost) and its outcome (done, unfinished with
what is left, or stopped). GET /api/v1/tasks/:id answers it: the task's own
fields stay at the top level, exactly as codes.task@1 had them, and the two new
fields are added to them. codes.task@1 stays as it is.
The loader now takes more than one major per contract id: the catalog lists a
v1 and a v2 file for the same id, the bare id resolves to the newest major, and
id@N names that major — so a v1 caller keeps resolving while a v2 caller names
it exactly. codes.task.read declares codes.task@2.