@anchrd/intel 0.59.0

package/dist/adapters/db/db-flows.d.ts

@@ -0,0 +1,42 @@
+import type { FlowRepository } from "../../flows/flows.types.js";
+import type { D1Database } from "./db.types.js";
+/**
+ * One page of runs, newest first — and the flow is part of the STATEMENT rather than a bound value
+ * (#774, found in the review of #787).
+ *
+ * ⚠️ **`WHERE (? IS NULL OR run.flow_id = ?)` is the shape that must not be used here**, however
+ * naturally it reads. SQLite picks its plan when the statement is prepared, from the text alone —
+ * it never sees the value — so an `OR` on the leading index column drops that column as an equality
+ * prefix **in both cases**, including the one where a real flow id was passed. Measured on the same
+ * engine and schema, `flow_runs_flow_idx (flow_id, created_at DESC)`:
+ *
+ *     -- WHERE run.flow_id = ?
+ *     SEARCH run USING INDEX flow_runs_flow_idx (flow_id=?)
+ *
+ *     -- WHERE (? IS NULL OR run.flow_id = ?)   — identical for a real id AND for null
+ *     SCAN run | USE TEMP B-TREE FOR ORDER BY
+ *
+ * The damage is not on the new door but on the old one: `GET /flows/:flowId/runs` has existed all
+ * along and is the frequent call, and it would have started scanning every run in the installation
+ * without a single test going red. `db-audit.ts` had the same choice one file over and split its
+ * statements per kind; this is that decision, applied where the review found it missing.
+ *
+ * ⚠️ The two shapes lean on two different indexes, and both are needed. Scoped: `flow_runs_flow_idx`,
+ * whose `flow_id` prefix an equality serves. Unscoped: `flow_runs_time_idx (created_at DESC,
+ * id DESC)` from `0027`, because "every readable flow" has no one `flow_id` to match on and the
+ * ordering has to come from somewhere.
+ *
+ * ⚠️ `failedOnly` and the cursor are shape too, not bindings, and that is not the same decision —
+ * they were already written this way. An absent clause binds nothing, so every caller of this
+ * function has to build its bindings from the SAME three flags, in this order: the CTE's, the flow
+ * id when scoped, `runVisible`'s, the cursor's three when paged, and the limit.
+ */
+export declare function flowRunsPageQuery(shape: {
+    scoped: boolean;
+    failedOnly: boolean;
+    paged: boolean;
+}): string;
+export declare function createFlowRepository(deps: {
+    db: D1Database;
+    now(): Date;
+}): FlowRepository;