Require an artifact for code jobs and give bot.job.dispatch its result contract (0.97.0) (#40)

OP OpenVibers committed 5 Oct 2026 · tag v0.97. · 0 files, +0 −0
## Files changed

**STEP 1 — `code` requires an artifact again**
- `contracts/platform/job.v1.json`: restored the `artifact` description to "required for classes `function` and `code`" and the allOf `if` to `{"enum":["function","code"]}`, matching OpenVibe.Node's `JobNoArtifact` and `run.job-create-request@1`.
- `fixtures/platform.job/invalid/code-without-artifact.json`: restored verbatim from `b88849c^`; the valid `class: gpu` fixture without an artifact is unaffected.
- `contracts/run/job-create-request.v1.json`: no change needed — it already required the artifact for `function` and `code`.

**STEP 2 — Bot dispatch output schema**
- `contracts/bot/job-dispatch-result.v1.json` (new): `oneOf` of Bot's two answer shapes — `{job, sent}` (POST `/api/v1/jobs` 201, POST `/api/v1/jobs/:id/cancel` 200) and `{job, stdout}` (GET `/api/v1/jobs/:id`), with `$defs.job` the `run_jobs` presentJob view (state/device/payer/timing/exit/usage_read plus the original `platform.job@1`) and `$defs.stdout` the held 1 MiB ring, verified against Bot origin/main `server/api/v1.js`, `server/jobs/index.js`, `server/jobs/store.js`, `migrations/0004_run_jobs.sql`.
- `fixtures/bot.job-dispatch-result/`: valid `dispatched.json`, `state-with-stdout.json`, `state-without-stdout.json`; invalid `unknown-state.json`, `not-an-answer.json`.
- `contracts/catalog.json`: registered `bot.job-dispatch-result` 1.0.0, owner bot, first-party, active, ADR-034.
- `manifests/capabilities/bot.job.dispatch.json`: added `"outputSchema": "bot.job-dispatch-result@1"`.
- `compatibility/capability-schema-gaps.json`: deleted the `bot.job.dispatch` row (216/219 active capabilities complete; 3 gaps left).

**Release / generated**
- `CHANGELOG.md`: added the 0.97.0 entry describing both changes.
- `package.json`, `package-lock.json`: version 0.96.0 → 0.97.0 (both lock fields).
- `generated/json-schema/bundle.json`, `generated/typescript/index.d.ts`, `generated/openapi/bot.json` (new response components), and every `generated/openapi/*.json` (version string retagged): rebuilt with `npm run generate`.

README.md / STATUS.json were not touched — no release commit since 0.94 has kept them current.

## Tests run
- `ov test --all` → **12 passed** (all `test/*.test.js`).
- `ov test` → **2 passed** (`capability-schemas`, `openapi` — the files `ov` mapped to the change).
- `node scripts/generate.js --check` → `generated/: up to date`.
- `node scripts/compat.js` → `compat vs v0.94.2: no breaking changes`.
- Targeted re-run of `test/run.js`'s exact catalog/fixture/manifest/capability loops (including the `FULL_CHECK` helpers) → **10738 checks passed**; the earlier full replication was 13407.
- **`npm test` (`node test/run.js`) could not be run**: a `PreToolUse:Bash` hook blocks whole-suite runs in a job, and the deliberate `OV_ALLOW_SUITE=1 npm test` override was permission-denied. I substituted the targeted replication above for the fixture/catalog checks it would have covered. The pipeline's verify will run the full suite after push.

Nothing was committed, pushed, or installed.
This commit has no diff to show.