Patch Prediction
I3 / V2 fix (API-IMPLEMENTATION-SPEC.md §8.2): “PATCH shrinks to (you can acknowledge/mute; you cannot edit a probability).” The
dismissed/feedback aliases are gone (REPLACE strategy) — use
status: "dismissed" and POST …/feedback respectively. Also fixes a
latent bug: the previous implementation assumed repo was always a
MemoryRepository and reached into mem._predictions directly, which
AttributeErrors under Postgres — now goes through repo.patch_prediction
(dual-store, per docs/v2/DESIGN.md §0.7).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
I3 / V2 fix (API-IMPLEMENTATION-SPEC.md §8.2): shrinks to {status,
notes} ONLY — "you can acknowledge/mute; you cannot edit a probability."
The dismissed/feedback aliases are REMOVED (REPLACE strategy, no
legacy aliases); POST .../feedback is the real outcome-recording path.
Response
Successful Response
The response is of type Response Patch Prediction V1 Predictions Prediction Id Patch · object.