Create activity_types Supabase migration
epic-activity-type-configuration-foundation-task-001 — Write and apply a Supabase database migration that creates the activity_types table with all required columns: id, org_id, name, is_active, metadata (JSONB), created_at, updated_at. Include appropriate indexes on org_id and is_active for query performance.
Acceptance Criteria
Technical Requirements
Implementation Notes
Use gen_random_uuid() for the id default — do not use uuid_generate_v4() as it requires the uuid-ossp extension which may not always be enabled. For the updated_at trigger, create a reusable moddatetime trigger function (CREATE OR REPLACE FUNCTION handle_updated_at()) if one does not already exist in the project's shared migrations, then attach it with CREATE TRIGGER set_updated_at BEFORE UPDATE ON activity_types. Store the metadata JSONB schema definition in a comment block in the migration file to document expected shape (triggersReimbursementWorkflow: bool, isTravelExpenseEligible: bool, labelKey: string). Place the migration in the supabase/migrations/ directory.
Coordinate with the team to ensure the organizations table migration has already been applied, as the foreign key depends on it.
Testing Requirements
Verify migration with supabase db reset followed by supabase db push in a local Supabase environment. Write a SQL test script that: inserts a row with all required columns, queries by org_id and is_active, verifies updated_at changes on UPDATE, and verifies ON DELETE CASCADE removes activity_types when the parent org is deleted. Confirm indexes exist using SELECT * FROM pg_indexes WHERE tablename = 'activity_types'. Verify EXPLAIN ANALYZE uses the composite index for WHERE org_id = $1 AND is_active = true queries.
The JSONB metadata column has no enforced schema at the database level. If the Dart model and the stored JSON diverge (e.g., a field is renamed or a new required flag is added without a migration), the metadata resolver will silently return null or throw at parse time, breaking conditional wizard logic for all organisations.
Mitigation & Contingency
Mitigation: Define a versioned Dart Freezed model for ActivityTypeMetadata and add a Supabase check constraint or trigger that validates the JSONB structure on write. Document the canonical metadata schema in a shared constants file and require schema review for any metadata field additions.
Contingency: Implement a lenient parse path in ActivityTypeMetadataResolver that returns safe defaults for missing fields and logs a structured warning to Supabase edge logs, allowing the app to degrade gracefully rather than crash.
If RLS policies on the activity_types table are misconfigured, a coordinator from one organisation could read or mutate activity types belonging to another organisation, violating data isolation guarantees required by all three client organisations.
Mitigation & Contingency
Mitigation: Write integration tests against the Supabase local emulator that explicitly assert cross-org isolation: a token scoped to org A must receive zero rows when querying org B activity types, and upsert attempts must return permission-denied errors.
Contingency: Apply an emergency RLS policy patch via Supabase dashboard without a code deploy. Audit all activity_type rows for cross-org contamination and restore from backup if any data leakage is confirmed.
If the cache invalidation call in ActivityTypeService is not reliably triggered after an admin creates, edits, or archives an activity type, peer mentors on the same device will see stale data in the registration wizard until the next app restart, leading to confusion and potential misregistrations.
Mitigation & Contingency
Mitigation: Enforce a strict pattern: ActivityTypeService always calls cacheProvider.invalidate() inside the same try block as the successful Supabase mutation, before returning to the caller. Write a widget test that verifies the cache notifier emits an updated list after a service mutation.
Contingency: Add a background Supabase Realtime subscription on the activity_types table that triggers cache invalidation automatically, providing an independent safety net independent of the service call path.