agenthog-reportlisted

# Write a shared report with AgentHog A report is one Markdown file. Prose is your analysis; every top-level ```` ```widget ```` fence is a chart or table — either **frozen** rows you supply, or a **live** SQL query the server re-runs within its TTL. Publishing it puts it at `https://agenthog.io/reports/<slug>` for every member of the organization, at once (there is no draft state). Humans read there; you write and revise it with the `ah` CLI. Every update is a new revision — nothing is ever overwritten. Follow the phases in order. Each ends with a check — do not proceed past a failed check. ## 0. Preconditions - `ah` is installed and authenticated: `ah whoami` shows the `account` line — that is the organization the report will belong to. Drafting and `preview` work with **read** scope; `create`, `update`, `delete` need **write** scope (an org admin mints it at `https://agenthog.io/tokens`, or `ah login --write`). With several logins, every `ah reports` command needs `--account <org>`. - You know which project(s) the report is about: `ah projects list` prints the keys (`ah_xxxxxxxx`). One report may draw on several. - The data exists: `ah events top --since 7d` for the event names, `ah schema` for the tables and columns a live query can see. Never invent a column — check. ## 1. Learn the house format first ``` ah reports list # what the org already reads ah reports read <slug> # the resolved report, exactly as a membe