feature-flags-audit

# Feature Flags Audit Produce a synthetic inventory of every feature flag declared in the Packmind codebase, with audience targeting, inferred functional descriptions, and orphan detection. The result is a single markdown table the user can scan at a glance. ## Context Packmind uses a **custom, frontend-only** feature flag system. There is no third-party library (LaunchDarkly, GrowthBook, PostHog, etc.). Flags are gated by **email domain** or **exact email** via a single central registry. There is no org-based, plan-based, percentage-rollout, or runtime-override mechanism — what's in the registry file is what's live in production. **Canonical source of truth:** `packages/ui/src/lib/components/content/PMFeatureFlag/PMFeatureFlag.tsx` This file exports: - Flag key constants ending in `_FEATURE_KEY` (e.g. `SPACES_MANAGEMENT_FEATURE_KEY = 'spaces-management'`). - `DEFAULT_FEATURE_DOMAIN_MAP`: a `Record<string, readonly string[]>` mapping each flag's **string value** to a list of allowed entries. Entries starting with `@` are domain rules (e.g. `@packmind.com` matches any user at that domain). Entries containing `@` but not starting with `@` are exact email matches. - The `PMFeatureFlag` React wrapper component and the `isFeatureFlagEnabled()` pure function used at call sites. If a flag is not declared in `DEFAULT_FEATURE_DOMAIN_MAP`, it does not exist. Do not invent flags. ## Workflow ### Step 1 — Parse the canonical registry Read `packages/ui/src/lib/components/content/...