What each pass admitted, dispatched, finished and spent.

The fire log with the ledger's own accounting joined onto it, newest pass first. The Fires tab already said a pass happened; this says what it did and what it cost, which is the pair that answers "at this rate, what will the rest of this backfill cost" before it is started rather than after. Counts come from the append-only transition log, not from the fire row, and a pass's runs are gathered by the claim that dispatched them rather than by timestamp — a sweep records itself after claiming, and its runs report their spend when they finish, so timestamps alone would credit every pass with the previous one's cost. `cost` therefore rises after `firedAt` as the pass drains, and a pass read moments after firing reports less than it will. `docs/design/item-ledger.md §6.5`.

curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/passes"

{
  "items": [
    {
      "id": "00000000-0000-0000-0000-000000000000",
      "firedAt": 0,
      "source": "SCHEDULE",
      "outcome": "FIRED",
      "detail": "string",
      "admitted": 0,
      "dispatched": 0,
      "completed": 0,
      "runs": 0,
      "cost": 0
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}