Resolve Pipeline Finding
Added 2026-10-01 (docs/01_decisions/DEV_CYCLE_2026_10_01.md): the deployer could OPEN a card through report_pipeline_finding above but had no way to close one, so every watchdog card ("main has been red", "production is behind a promotable sha") stayed open on the desk after the condition had cleared -- the exact "alerted, never confirmed" shape supervision.record_resolution exists to end. Same grant as the report route (system:pipeline_findings:write): clearing a card is the other half of the same conversation, not a second permission.
Returns {"resolved": false} when nothing was open under reference (a healthy tick with nothing outstanding is the common case and must stay silent -- record_resolution returns None and posts nothing).
Request
- Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
- URL: https://api.pigeonly.com/api/system/pipeline-findings/resolve
- Auth: none declared
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.