Rebrand entire project from Feels to Reflect

Complete rename across all bundle IDs, App Groups, CloudKit containers,
StoreKit product IDs, data store filenames, URL schemes, logger subsystems,
Swift identifiers, user-facing strings (7 languages), file names, directory
names, Xcode project, schemes, assets, and documentation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

uiTestPrompt.md

@@ -8,7 +8,7 @@ Create 3 solid iOS UI tests from the QA plan that compile and run reliably using
 
 Project:
 - Root: /Users/treyt/Desktop/code/Feels
-- QA source: /Users/treyt/Desktop/code/Feels/docs/Feels_QA_Test_Plan.xlsx
+- QA source: /Users/treyt/Desktop/code/Feels/docs/Reflect_QA_Test_Plan.xlsx
 
 Optional explicit test IDs/names from me (if provided, prioritize these):
 <PASTE_TEST_IDS_AND_NAMES_HERE_OR_LEAVE_EMPTY>
@@ -56,7 +56,7 @@ Deliverable shape:
 
 Validation gates (required before done):
 1. Run only the 3 new tests (not full suite), e.g.:
-   - `xcodebuild -project Feels.xcodeproj -scheme "Feels (iOS)" -destination 'platform=iOS Simulator,name=iPhone 16 Pro' -only-testing:"Tests iOS/<SuiteName>/testA" -only-testing:"Tests iOS/<SuiteName>/testB" -only-testing:"Tests iOS/<SuiteName>/testC" test`
+   - `xcodebuild -project Reflect.xcodeproj -scheme "Reflect (iOS)" -destination 'platform=iOS Simulator,name=iPhone 16 Pro' -only-testing:"Tests iOS/<SuiteName>/testA" -only-testing:"Tests iOS/<SuiteName>/testB" -only-testing:"Tests iOS/<SuiteName>/testC" test`
 2. If failures occur, fix and rerun until green.
 3. Run the same targeted command a second time to check flakiness.
 4. Only mark complete if both runs pass.