Report real counts from hookdeck_queue_status

[garethx]

Found by actually watching the agent answer with this tool while setting up a demo for the announcement post. Asked what needed attention in a project with four open issues, it said:

⚠️ Attention needed:

• Open issues: 1 page of open issues detected

You have 1 open issue that may need your attention. This could be a connection that's paused, a service experiencing problems, or another configuration issue.

The tool listed events and issues with limit=1 and returned the length of each page:

failed = await api.list_events(status="FAILED", limit=1)
issues  = await api.list_issues(status="OPENED", limit=1)
return json.dumps({
    "failed_events_page_count": len(_models(failed)),   # 0 or 1. Always.
    "open_issues_page_count":   len(_models(issues)),   # 0 or 1. Always.
})

The field names were honest and the numbers were useless. The agent's primary status tool could not report how much of anything there was, so the model filled the gap by speculating — which is the worst failure mode for a tool whose job is telling it what is true.

Issues have a dedicated count endpoint (GET /issues/count), so those are now counted exactly. Events do not — I checked, /events/count 404s — so failures are counted over a page of 100, with failed_events_is_at_least marking a full page. A floor the model can report as a floor beats a ceiling it will report as a total.

Same question now answers "Open issues: 4".

Four tests cover it, including that the old page-count fields are gone rather than renamed alongside.

---

Stacked on #10 (base is fix/dashboard-copy), because the demo that surfaced this needs both in the working tree. If #10 merges first, retarget this to main before merging — last time a stacked PR merged into its base branch instead of main and the work sat stranded until we noticed.

Ships in the wheel, so patch release when convenient.