The CI gate is a read-only check over published breaking signals visible to the API key’s workspace.

REST check

A passing response has passing: true. A failing response includes stable signal IDs, signal types, severities, and summaries in unacknowledged.

CLI check

Run the repository CLI from the backend environment:
The command exits 0 when the gate passes and 1 when unacknowledged breaking signals remain. Usage and API failures use separate nonzero exit codes.

Acknowledge a handled signal

Acknowledgement requires the write scope. Use a separate read-only key for CI when the workflow should not acknowledge or mutate anything.
Do not acknowledge signals automatically to make a build pass. The acknowledgement is an audit record that the workspace handled or explicitly accepted the change.