What problem does it solve? Changing, adding, or retiring remotely controlled feature flags in the Fedi codebase requires coordinated edits across the Rust bridge runtime, the web API endpoint, and generated TypeScript bindings, and mistakes can break older app binaries in the field. ## Core Features & Use Cases - Flag Value Changes: Update existing remote flags in ui/web/src/pages/api/features.ts across production and development maps. - New Flag Addition: Step-by-step workflow for adding fields to RemoteFeatures, FeatureCatalog, apply_remote_layer(), compiled defaults, and regenerating TypeScript bindings. - Safe Flag Retirement: Guidance on graduating a flag in stages so old app binaries still receive the served value while new code removes the gate. - Use Case: When shipping a new wallet feature behind a remote flag, follow the checklist to add the flag in Rust, serve it from the web API, consume it via the selectFeatureFlag Redux selector, and later remove it without breaking released clients. ## Quick Start Ask the assistant to add a new remote feature flag to the Fedi bridge runtime and web API following the feature-flags workflow.