[Refactor] Feature flag store uses in-memory Map — resets to seed data on every server restart

[RUKAYAT-CODER]

Overview

src/lib/feature-flags/store.ts stores all feature flags in a module-level Map and seeds it with hard-coded values on startup. Any flags created or modified via the admin UI are lost when the server restarts, making the feature flag system unreliable for production use.

Specifications

Features:

• Feature flags are stored in the database and loaded on startup
• Flag mutations are immediately persisted
• The admin UI reflects the true persisted state after a restart

Tasks:

• Create a feature_flags table with columns for id, name, description, enabled, strategy, percentage, rules (JSONB), tags, created_at, updated_at, created_by
• Implement getFlagById(), getAllFlags(), createFlag(), updateFlag(), deleteFlag() as SQL-backed functions
• Seed the table via a database migration instead of runtime code
• Update the route handlers to use the database functions

Impacted Files:

• src/lib/feature-flags/store.ts
• src/app/api/admin/feature-flags/route.ts
• src/lib/db/ (new migration)

Acceptance Criteria

• Feature flags survive server restarts
• Creating a flag via the API persists it to the database
• Seed flags are applied via migration, not runtime code

[Olasunkanmi975]

@Olasunkanmi975 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I want to work on this issue because it sits at the intersection of logic and reliability

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Olasunkanmi975 to this issue.

[fredericklamar342-prog]

@fredericklamar342-prog has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Kindly assign to me I can implement this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @fredericklamar342-prog to this issue.