Backlog

Not ordered. An item here is raised, not sequenced. It leaves by being moved into planning.md with an issue, or by being deleted when it stops being true.

Custom report builder

• What it is: a saved structured query becomes a named, re-runnable report with its own presentation, rather than a query you re-open in a console.
• Where it came from: the operator, 2026-08-24, choosing the structured builder over raw SQL. "This essentially could also become a users custom report builder essentially."
• Why the structured builder makes it possible: a saved SQL string is opaque, so nothing can render a form for it or vary a parameter safely. A saved { collection, filters, orderBy, limit } object can be parameterized, validated, and rendered.
• What would promote it: the Firestore tab shipping and the saved-query store carrying structured payloads. Both are slices 3 and 4 in planning. Until a structured query can be saved at all, there is nothing to build a report on.
• The open question it raises: who the "user" is. An admin building themselves a report is a different product from a merchant building one against their own data, and the second one inherits the whole k-anonymity gate that ad delivery telemetry already carries.

Assistant writes the console query

• What it is: the Assistant answers a data question by handing back a runnable console query, structured or SQL, that opens in the Query Console rather than being pasted by hand.
• Where it came from: the 2026-08-24 failure. The operator's actual workflow was already Assistant to console by copy and paste, and the copy step is where a wrong query survives unchecked.
• What would promote it: the Assistant being grounded first (planning slice 5). An Assistant that still invents tables would just automate pasting a broken query.
• Related: #333: Assistant: BigQuery analytics integration (canned queries), which approaches the same goal from the canned-query side.