Contracts 0.105.0: chat.ticket.write is active (Chat #26); chat.messages.read lists the DM block-state read (Chat #27) (#50)

OP OpenVibers committed 5 Oct 2026 · tag v0.105 · 0 files, +0 −0
**Changes (file:line)**

1. `manifests/capabilities/chat.ticket.write.json:5` — status `planned` → `active`.
2. `manifests/capabilities/chat.ticket.write.json:18-19` — `implementedBy` `[]` → `GET /internal/chat/tickets/:ticket_id`, `POST /internal/chat/tickets/:ticket_id/messages` (exact routes from Chat `server/chat/internal-tickets.js:361-362`).
3. `manifests/capabilities/chat.ticket.write.json:8` — description de-PLANNED (now says it reads the service's own conversation too).
4. `contracts/catalog.json:4819` — `chat.ticket-conversation` catalog status `planned` → `active`.
5. `manifests/capabilities/chat.messages.read.json:18` — added `GET /internal/chat/dm/block-state` to the route list.
6. `contracts/chat/dm-block-state-result.v1.json:1` — new `chat.dm-block-state-result@1` (`{ ok, blocked }`, `anyOf` ok shape + `chat.ingress-ack@1` error), following `first-chat-result`/`sound-result` (route-specific schemas live in the catalog, not in `outputSchema`).
7. `contracts/catalog.json:4750` — new `chat.dm-block-state-result` entry (owner `chat`, first-party, active).
8. `fixtures/chat.dm-block-state-result/valid/blocked.json:1`, `fixtures/chat.dm-block-state-result/invalid/missing-blocked.json:1` — valid + invalid fixtures.
9. `fixtures/chat.ticket-conversation/…` — unchanged (schema unchanged).
10. `CHANGELOG.md:7` — new `## 0.105.0 — 2026-10-05` entry.
11. `STATUS.json:12` version → `v0.105.0`; `:24` ticket feature line planned→active with the two routes; `:25` new `chat.dm-block-state-result@1` line.
12. `package.json:3`, `package-lock.json:3,9` — version → `0.105.0`.
13. `generated/openapi/chat.json` — 3 new operations (`/internal/chat/tickets/{ticket_id}`, `/internal/chat/tickets/{ticket_id}/messages`, `/internal/chat/dm/block-state`); `generated/openapi/index.json` chat operations 19→22, capabilities 11→12; all OpenAPI docs + `json-schema/bundle.json` + `typescript/index.d.ts` regenerated to 0.105.0 via `npm run generate` (kept).

**Verification**
- `node scripts/compat.js v0.104.0` → `no breaking changes`.
- `nice -n 15 ov test --no-cache test/platform-fabric.test.js test/product-catalog.test.js test/capability-schemas.test.js test/openapi.test.js` → `4 passed in 28 s`.
- Direct check of the new fixtures: valid passes, invalid fails; `chat.dm-block-state-result@1` resolves.

One scope note: I did update `chat.ticket.write`'s description (line 8) because it still said "PLANNED … becomes active when OpenVibe.Chat implements the route" — leaving that in an active capability would be contradicted by this release. Everything else is limited to the two capabilities and the release files, exactly as the 0.104.0 commit did.
This commit has no diff to show.