Add Convex backend tests for listLinkedSignalsForProject covering: - Per-issue grouping with correct source counts - Project membership/authz (denies non-member access) - Cross-project signal suppression (project1 cannot see project2 signals) - Multi-source signal source-count accuracy - Empty project returns empty record - Issues without linked signals are omitted from result Make linked signals deterministically ordered newest-first within each issue group via toSorted(createdAt descending).
Convex Backend
This directory contains the Convex control plane for the app and daemon runtime. Generated files under _generated/ are maintained by Convex and should not be edited by hand.
Daemon Control Plane
schema.tsdefines daemon definitions, high-churn daemon presence, leased daemon commands, append-only command events, and the sampletodostable.daemons.tsmanages stable daemon definitions withupsert,get, andlist.daemonRuntime.tsrecords daemon session lifecycle:connect,heartbeat,disconnect,recordEvent, and bounded event listing.daemonCommands.tsowns the command queue:enqueue,available,claim,start,succeed,fail,cancel, and bounded command listing.
Commands are claimed by daemon session. Preserve the claimedBySessionId ownership checks, leaseExpiresAt expiry semantics, terminal statuses, and bounded query results when changing this flow.
Usage
Convex functions are exposed by file path through the generated api object, for example api.daemonCommands.enqueue or api.daemonRuntime.connect. Run bun run dev:server from the repository root to start the development deployment, and bun run dev:setup when configuring Convex for the first time.