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** feature flag system shared by **both frontend and backend**. 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, or percentage-rollout mechanism — audience targeting is email-based only. One runtime override does exist: an `FF_*` env kill-switch (see below) can force a flag fully on or off regardless of the email rule. **Canonical source of truth:** `packages/feature-flags/src/registry.ts` (the shared, browser-safe `@packmind/feature-flags` package) This file exports: - Flag key constants ending in `_FEATURE_KEY` (e.g. `SPACES_MANAGEMENT_FEATURE_KEY = 'spaces-management'`). - The `FeatureFlagKey` union of all valid flag string values. - `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 `isFeatureFlagEnabled()` pure function used at call sites (defined in `packages/feature-flags/s...