openvibers/openvibe.contracts Commits

Contracts 0.162.0: codes.task.start/read/cancel (a service starts a coding task for a person on their own machine) (#119)

OP OpenVibers committed 30 days ago · tag v0.162 · 0 files, +0 −0

Plan T16/T17: OpenVibe.Actor routes coding work to OpenVibe.Codes. Today Actor's `codes` agent refuses ("hosted coding runs are not open yet"), but Codes now runs a task on a person's own machine (openvibe.codes/run, live since today).

**Capabilities (codes, first-party)**
- `codes.task.start`: `POST /api/v1/tasks`. A service names the person in `X-OV-Subject`.
  - Codes submits the task to Run as that person, in the project of their latest /run task. Without one: 409 `codes.no_project`.
  - Run places it only on that person's machine.
  - Marked sensitive.
- `codes.task.read`: `GET /api/v1/tasks/:id`.
- `codes.task.cancel`: `POST /api/v1/tasks/:id/cancel`.
- Only the service that started a task, for the same person, sees it.

**Contracts**
- `codes.task-start-request@1`: repo (https, no credentials), ref, prompt, agent, permission edit|full, push, pull_request, idempotency_key.
- `codes.task-start-result@1`.
- `codes.task@1`: state as Run's job, page URL, and once ended: ok, agents, summary, files, patch ≤ 256 KiB, push, cost_usd, duration_ms, error.
- Fixtures: valid and invalid for each.

**Also:** the `codes` service manifest lists the three capabilities. CHANGELOG 0.162.0; `generated/` regenerated.

**Checks**
- `node test/run.js`: 19,653 checks pass.
- `scripts/compat.js v0.161.0`: no breaking changes.