Context
Raised as a side note during review of #205 (request-log gateway consumer).
The request-log ownership model has the gateway as the sole writer of the request log: the orchestrator only publishes log entries to the log topic via `submitqueue/core/request.PublishLog`, and the gateway's consumer persists them.
Task
Update the DLQ orchestrator controllers to publish request-log entries via `PublishLog()` (rather than writing the request log directly), so they conform to the same ownership invariant as the rest of the orchestrator pipeline.
Notes
Follow-up only; not required for #205.
Co-Authored-By: Oz oz-agent@warp.dev
Context
Raised as a side note during review of #205 (request-log gateway consumer).
The request-log ownership model has the gateway as the sole writer of the request log: the orchestrator only publishes log entries to the log topic via `submitqueue/core/request.PublishLog`, and the gateway's consumer persists them.
Task
Update the DLQ orchestrator controllers to publish request-log entries via `PublishLog()` (rather than writing the request log directly), so they conform to the same ownership invariant as the rest of the orchestrator pipeline.
Notes
Follow-up only; not required for #205.
Co-Authored-By: Oz oz-agent@warp.dev