Files
claw-code-parity/worker-protocol/README.md
Wylabb 9e9d440770
Build Claw Telegram / build (push) Successful in 5m39s
Build Claw Telegram / cleanup (push) Successful in 8s
Decouple gateway protocol from Rust runtime types
Move all worker-facing record types (TaskListRecord, RuntimeTaskRecord,
TeamRecord, MailboxSummary, FeedItemRecord, LibraryAppRecord, etc.)
into protocol-owned mirrors in records.rs. The gateway and worker_client
now use these protocol types instead of importing from the runtime crate.

Add worker-protocol/ with OpenAPI spec and JSON schemas as the
language-neutral contract authority for the gateway-worker boundary.
This is the migration surface for the TS worker replacement.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-07 20:12:16 +02:00

1.2 KiB

Worker Protocol

This directory is the contract boundary between the Rust gateway in /Users/makarnovozhilov/clawdcode/claw-code-parity and the future TypeScript worker forked from /Users/makarnovozhilov/clawdcode/claude-code-source.

The migration goal is:

  • keep the current gateway HTTP/SSE client stable
  • move worker ownership out of Rust runtime internals
  • make the worker contract language-neutral

Current state:

  • openapi.yaml is the contract authority for the worker surface the gateway already calls
  • schemas/ contains standalone JSON Schemas for the most important request and event payloads used by the migration slice
  • Rust protocol code is being migrated to use protocol-owned record mirrors instead of importing runtime structs directly

Notes:

  • The contract is intentionally endpoint-compatible with the current gateway.
  • Some domain records are still broad object shapes in the OpenAPI file while the TS worker port is in progress.
  • The next tightening step is to generate TS/Rust bindings from this directory instead of hand-maintaining parallel definitions.