report_list
report_list is implemented by handleReportList in src/api/handlers/report/report_list.osl.
Handles the report list protocol operation through the resource-specific helper and storage layers.
Access
Section titled “Access”| Gate | Requirement |
|---|---|
| Authentication | Required by the central API gate. |
| Central permission | review_reports |
| Broadcast | Not marked global directly by this adapter. A helper may emit focused or server-wide updates. |
Request
Section titled “Request”Every request includes cmd: "report_list" and may include an opaque listener correlation value.
| Field | Validation / meaning |
|---|---|
status |
schema.enum(["open", "resolved", "dismissed"]).optional() |
Validator source
Section titled “Validator source”The handler and shared validation path use these OSL schema definitions before normalization:
*schema.Schema schemaReportList = schema.object({ status: schema.enum(["open", "resolved", "dismissed"]).optional()})Processing path
Section titled “Processing path”handleCmdenforces authentication and thereview_reportspermission.dispatchCmdroutesreport_listtohandleReportList.- The adapter validates and normalizes input, then calls its domain collaborators.
- Durable mutations complete before the response or event is returned.
onMessageadds the request listener to direct responses and performs any marked broadcast.
Direct collaborators visible in the handler: reportList
Responses and events
Section titled “Responses and events”Response/event command names visible in this adapter: report_list.
Validation and domain failures use:
{ "cmd": "error", "val": "<message>", "src": "report_list", "listener": "<copied from request>"}