hexis

kami/hexis

T

kami ed593efb71 Propagate correlation_id/causation_id through execution events, add API version header

Execution events (started/failed/succeeded) never carried the
correlation/causation IDs from the ExecuteRequest, even though the
fields existed on Execution. Added CausationID to ExecuteRequest and
Execution, and split emitEvent into a correlated variant used
throughout the execution lifecycle. handleExecute falls back to
X-Correlation-ID/X-Causation-ID headers when the body omits them.
Also add X-Hexis-Version negotiation on /api/v1/*, matching Nexus.

Part of Vikunja #273.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ghELqYhZNLub2TXGMazqA

2026-07-20 11:11:49 +04:00

cmd

Initial commit: Hexis capability registry + execution service baseline

2026-07-20 00:50:37 +04:00

etc

Initial commit: Hexis capability registry + execution service baseline

2026-07-20 00:50:37 +04:00

internal

Propagate correlation_id/causation_id through execution events, add API version header

2026-07-20 11:11:49 +04:00

pkg/client

Propagate correlation_id/causation_id through execution events, add API version header