Enqueue Consolidation Run

POST /knowledge-bases/{kb_id}/consolidation/run

“Consolidate now” — the fast lane’s input.

202 rather than 201: the row is queued, the pass has not run, and answering 201 with a finished-looking body is how a caller ends up polling a knowledge base that has not changed yet.

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
kb_id	path	string (uuid)	required	—

Responses

Status	Description	Body
202	Successful Response	ConsolidationQueued
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X POST https://your-deployment.example.com/knowledge-bases/{kb_id}/consolidation/run \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — ConsolidationQueued

Field	Type		Notes
id	string (uuid)	required	—
kb_id	string (uuid)	required	—
status	string	required	—