iblai-api-featurelisted

# iblai-api-feature Manage **per-user feature configuration** and **app / onboarding state** from the Data Manager (DM) API: read and write a user's feature config (one feature, or a bulk inline `config` object), bulk-apply a feature's `values` across every user on a platform, list the apps a user has access to, mark onboarding complete, activate an app free trial, and — only when the platform enables it — run an admin **platform-provisioning** config. Use when flipping feature flags/values for a user or an org, inspecting a user's apps, recording onboarding, granting a trial, or provisioning a platform. ## Auth & conventions - **Base URL:** `https://api.iblai.app/dm` — these are Data Manager (DM) endpoints, so the **`/dm` prefix is required**; the `/api/features/...` (and `/api/provision/...`) paths below are appended to it (e.g. `https://api.iblai.app/dm/api/features/config/`). `/dm` is the gateway prefix and does not appear in the app's `urls.py`. - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path / scope vars:** `{org}` = `$IBLAI_ORG` (a.k.a. `platform_key` on the wire). The org/platform is always passed as a **query param or body field** (`platform_key`), never baked into the path. The user is resolved flexibly from **`user_id` _or_ `username` _or_ `email`** (in that precedence) — passed as query params on GET, body fields on POST. - Most feature/app endpoints are open (`AllowAny` — see Notes); the provisioning endpoin