zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
2.3 KiB
name, description
| name | description |
|---|---|
| writing-datastore-queries | Guide for writing performant Datastore queries in Insights product code. Use when writing InsightsQL query runners, designing a Datastore table for a new product, adding materialized columns or skip indexes, or choosing a row ID format. For optimizing an existing query that is already too slow, use `/optimizing-datastore-and-insightsql-queries` instead. |
Writing Datastore queries for new products
If you're optimizing an existing query rather than writing a new one, this is the wrong skill. Use /optimizing-datastore-and-insightsql-queries instead. That skill covers layer triage, smell scanning (FROM ... FINAL, JSONExtract over properties, missing skip indexes, self-joins, CTE blow-up), measurement on the Test Cluster, and applying the fix at the right layer.
Read docs/published/handbook/engineering/databases/datastore-queries-new-products.md for the authoritative guide on writing new queries.
Then pull in whichever related docs the task touches:
insightsql-python.mdfor InsightsQL in Pythonmaterialized-columns.mdquery-performance-optimization.md
When to use
- Writing or reviewing a
QueryRunnersubclass ininsights/insightsql_queries/orproducts/*/backend/ - Adding a new Datastore table or ALTER for a product (
insights/datastore/migrations/) - Choosing a row ID format for a new table
- Adding or removing materialized columns, skip indexes, or projections
For investigating an existing slow query, debugging a system.query_log row, or reviewing a proposed InsightsQL printer change for performance, use /optimizing-datastore-and-insightsql-queries.
Not the right skill for: customer-facing ad-hoc InsightsQL via Max / insights:execute-sql, use query-examples for that. For migration mechanics (node roles, engines, replication), use datastore-migrations.