feat/discovery

clicked_at set without guaranteed updated_at advancement

packages/database/drizzle/0065_discovery_state.sql:12

When clicked_at is first written, updated_at must be advanced by the shell. If a shell issues a click-only update without setting updated_at/version, the timestamp will silently go stale. Not detectable from the migration alone — verify the click shell path sets both fields.

updated_at has no ON UPDATE trigger — relies on application layer

packages/database/drizzle/0065_discovery_state.sql:5

Consistent with the rest of the schema (shell sets updated_at). Raw SQL UPDATE would silently leave it stale, but that's a known constraint across all tables.

Journal ordering correct after renumber

packages/database/drizzle/meta/_journal.json

idx 63→64→65 is strictly monotonic. idx:64 = 0064_strong_echo (main), idx:65 = 0065_discovery_state (this branch). No collision, no gap.

schema/index.ts merge-in (utilityContractOverviewReconcileRuns) is unrelated to discovery

packages/database/src/schema/index.ts

Export came from main's 2deee0e8 merge commit. Correct placement in the barrel; no interaction with discovery_state.

public_id uniqueness via unique index rather than UNIQUE constraint

packages/database/drizzle/0065_discovery_state.sql:16

public_id is text NOT NULL + a unique index. Functionally equivalent for enforcement but a unique index can be dropped without a table migration while a UNIQUE constraint cannot. Low risk in a migration-controlled schema; consistent with other tables in the repo.

RLS policies follow established profiles-subquery pattern

packages/database/drizzle/0065_discovery_state.sql

SELECT/INSERT/UPDATE gate on profile_id IN (SELECT id FROM profiles WHERE auth_id = auth.uid()). Identical to user-preferences pattern. profiles.auth_id is indexed — subquery is efficient.

No DELETE policy for authenticated role — intentional

packages/database/drizzle/0065_discovery_state.sql

Authenticated users cannot delete their own rows; deletion happens only via CASCADE from profiles. Correct posture for exposure-tracking state.

service_role ALL policy is standard and acceptable

packages/database/drizzle/0065_discovery_state.sql

Standard Supabase pattern used across the schema. No concern.

Journal ordering and file naming correct

packages/database/drizzle/meta/_journal.json

idx values strictly monotonic 0→65, no gaps. File names match journal tags exactly.

schema/index.ts barrel export placement follows established pattern

packages/database/src/schema/index.ts

Merged export placed correctly after the UCO export, before billing schemas. Style consistent with surrounding exports.

Migration files require no tests — Drizzle convention

Generated migration SQL has no test requirement. Discovery feature itself has unit, integration, and E2E coverage already in the branch.