async fn operator_records(
__arg0: State<AppState>,
headers: HeaderMap,
) -> ResponseExpand description
GET /dashboard/api/operator-records
Every bot.did.operator record the poll’s last listing of the
operator’s repository read, so the operator can find one they did not
write. An app holding their session writes as them, and their PDS cannot
tell the two apart, so seeing the records is the whole of the defence.
Read-only, and nothing here marks a record: what a record says is the operator’s repository’s business, and this deployment reading it does not make it this deployment’s.
Unreachable rather than an empty list when no listing has landed yet —
a repository holding no records and a poll that has not read one are
different facts, and a zero standing in for the second is the lie this
module is built not to tell.