chore(smart-composer): default the internal force toggle to ON

So testers and reviewers see the new composer immediately on staging
without flipping the dev toggle. The persistent override is still
respected, so explicit OFF stays OFF.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: tsahimatsliah

packages/shared/src/components/post/SmartComposerDevToggle.tsx

@@ -18,7 +18,7 @@ import { useAuthContext } from '../../contexts/AuthContext';
 export const SmartComposerDevToggle = (): ReactElement | null => {
   const { user } = useAuthContext();
   const [forceEnabled, setForceEnabled, isFetched] =
-    usePersistentContext<boolean>(FORCE_SMART_COMPOSER_KEY, false);
+    usePersistentContext<boolean>(FORCE_SMART_COMPOSER_KEY, true);
 
   if (isProductionAPI || !user || !isFetched) {
     return null;

packages/shared/src/hooks/post/useSmartComposerEnabled.ts

@@ -26,7 +26,7 @@ export const useSmartComposerEnabled = ({
 }: UseSmartComposerEnabledProps): UseSmartComposerEnabled => {
   const [forceOverride] = usePersistentContext<boolean>(
     FORCE_SMART_COMPOSER_KEY,
-    false,
+    true,
   );
   const { value: flagValue } = useConditionalFeature({
     feature: featureSmartComposer,