The steering route kept the identity lifecycle, the row locks, the
acknowledgement replay checks, the provider steering call, the queue
removal, the wake cancellation, and the run acknowledgement write inline.
Move that logic into createQueuedCommentQueue as steerQueuedWakeComment,
the fourth mutation on the same queue adapter. The route now keeps only
authorization, validation, issue access, error mapping, the activity log,
and the response shape.
The three identity calls that must run before or after the module's own
transaction (reserveSteeredIdentity, reconcileSteeredIdentity,
rejectSteeredIdentity) stay on the root database handle, so a lost
response after the final queued message still resolves to a durable
idempotency record instead of a second steer. The module reserves the
identity itself; no caller-supplied pending identity id crosses the port.
Delete lockQueuedCommentState and assertQueueMutationTarget from the route
now that steering is their only caller. buildQueuedCommentQueue stays,
since the read-only queued-comments route still needs it.
Co-authored-by: Paperclip <noreply@paperclip.ing>
c66868abb9