[MikeyZhang75]

• Auto release

🐛 Fixes #416

🧭 Task plan: docs/plans/416-orm-multi-field-orderby-index-pushdown.md

🟢 95-100% confidence

Phase	🧪 Tests	🌐 Browser
Reproduced	🔴 A limit-5 query read 60 rows; a relation read 61; four exact-head reviews exposed distinct tied/top-k regressions	➖ N/A
Verified	🟢 Focused ORM 173 passed / 1 skipped; owner/compiler 52 passed; bun check green	➖ N/A

✅ Outcome

A multi-field orderBy walks a declared compound index only when that index produces the complete requested order without changing tied-row identity. Safe top-level and relation queries stay limit-bound instead of collecting the full candidate set.

⚠️ Caveat

Mixed directions, nullable fields, skipped keys, unsafe pinned-direction ties, and unrequested trailing index keys keep the post-fetch sort. Add createdAt in the moving direction when an explicit creation-time tie-break makes a pinned sort safe.

🏗️ Design

resolveIndexOrderPushdown owns whole-sort eligibility. Equality-pinned fields are absorbed without consuming a moving key; remaining fields must be contiguous, share one direction, and consume every moving declared key before the implicit creation-time suffix. Candidate scoring prefers fuller indexes only when their extra coverage is safe.

🧪 Verified

• RED/green integration proof covers two table sizes, relation bounds, cursor direction, Convex UTF-8 and Float64 ordering, pinned-field ties, and trailing-key ties across limit.
• Four exact-head P1 findings were reproduced and repaired: equality-pinned index scoring, Convex value ordering, opposite-direction implicit ties, and unrequested trailing-key ties.
• Final immutable-head autoreview: no actionable P0/P1 findings at 0.89 confidence.
• bun check: green across lint, typecheck, unit/integration suites, CLI and Concave smoke, fixture parity, package builds, and bare/Expo/Next/Start/Vite runtime lanes.
• Docs, published kitcn skill guidance, generated mirror, and patch changeset are synchronized.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

[changeset-bot]

🦋 Changeset detected

Latest commit: 1c1d8e8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
kitcn	Patch
@kitcn/resend	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
better-convex	Ready	Preview	Aug 26, 2026 4:54am

[zbeyens]

Autoclosure receipt for exact head 1c1d8e86f3acfe1f44e6be640d3f72df67e6e30c.

• Task evidence: docs/plans/416-orm-multi-field-orderby-index-pushdown.md exists at this head, owns PR fix(orm): serve multi-field orderBy from a compound index #426, and passes the completion checker.
• Exact-head equality: local HEAD, live headRefOid, remote branch, and fetched refs/pull/426/head all equal the receipt OID.
• P1 proof replay after the final push: 12/12 focused read-bound/order tests and 52/52 resolver/compiler tests passed. The four repaired P1s cover equality-pinned scoring, Convex value ordering, opposite-direction implicit ties, and unrequested trailing-key ties.
• Final review: no actionable P0/P1 findings (0.89 confidence).
• Local gate: bun check passed, including lint, typecheck, full tests, package builds, fixture parity, and runtime scenarios.
• Hosted gates: CI passed; Vercel deployment is ready; auto-release sync passed.
• Final feedback inventory before receipt: helper comments 2, raw issue comments 3, excluded raw comments 1, review bodies 0, review threads 0 resolved / 0 unresolved. Priority totals: P0 0, P1 0, P2 0, P3 3. Deferred items: none.

Feedback ledger:

• fix(orm): serve multi-field orderBy from a compound index #426 (comment) — P3 non-actionable bot status; reports exhausted Codex review credits, no code finding.
• fix(orm): serve multi-field orderBy from a compound index #426 (comment) — P3 informational changeset bot status; detects the committed release artifacts at the exact head, no requested action.
• fix(orm): serve multi-field orderBy from a compound index #426 (comment) — P3 informational deployment status; Vercel reports Ready with zero live feedback, no requested action.

Zero unresolved actionable P1-or-higher feedback remains.