chore: rename app from Solitaire Quest to Ferrous Solitaire

Updates all in-tree references:
- Android package: com.solitairequest.app → com.ferrousapp.solitaire
- APK name: solitaire-quest → ferrous-solitaire
- Data dir: solitaire_quest → ferrous_solitaire (across all 6 data modules + engine)
- Keyring service: solitaire_quest_server → ferrous_solitaire_server
- Android Keystore key: solitaire_quest_token_key → ferrous_solitaire_token_key
- Gitea repo: Rusty_Solitare → Ferrous-Solitaire (also fixes "Solitare" typo)
- Renamed pkg/solitaire-quest* → pkg/ferrous-solitaire*
- Updated ArgoCD, docker-compose, CI workflow, build script, all docs

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

docs/ANDROID.md

@@ -6,7 +6,7 @@ later sections document what's known to compile, what's stubbed, and
 the next milestones.
 
 > **Status (2026-05-07):** First working APK at `fb8b2ac`. 54 MB
-> debug-signed `solitaire-quest.apk` for `x86_64-linux-android`. Has
+> debug-signed `ferrous-solitaire.apk` for `x86_64-linux-android`. Has
 > NOT yet been verified to launch on a device or emulator — that's
 > the next milestone.
 
@@ -121,7 +121,7 @@ cargo apk build -p solitaire_app --target x86_64-linux-android
 Output:
 
 ```
-target/debug/apk/solitaire-quest.apk
+target/debug/apk/ferrous-solitaire.apk
 ```
 
 Targets shipped via `[package.metadata.android].build_targets` in
@@ -164,8 +164,8 @@ Physical device:
 
 ```bash
 adb devices                                    # confirm connection
-adb install target/debug/apk/solitaire-quest.apk
-adb shell am start -n com.solitairequest.app/android.app.NativeActivity
+adb install target/debug/apk/ferrous-solitaire.apk
+adb shell am start -n com.ferrousapp.solitaire/android.app.NativeActivity
 adb logcat | grep -iE "RustStdoutStderr|solitaire|panic"
 ```
 
@@ -174,7 +174,7 @@ Emulator:
 ```bash
 emulator -avd bevy_test -no-window -gpu swiftshader_indirect &
 adb wait-for-device
-adb install target/debug/apk/solitaire-quest.apk
+adb install target/debug/apk/ferrous-solitaire.apk
 # ... same start + logcat steps as above.
 ```
 
@@ -203,7 +203,7 @@ What's NOT yet ported / not yet measured:
 - `dirs::data_dir()` returns `None` on Android. Callers in
   `solitaire_data/src/storage.rs`, `progress.rs`, `replay.rs`,
   `achievements.rs`, `settings.rs` all need an Android-aware
-  helper (likely `/data/data/com.solitairequest.app/files`).
+  helper (likely `/data/data/com.ferrousapp.solitaire/files`).
 - Touch UX pass — hit-target sizes, modal scaling on small screens,
   app lifecycle (suspend / resume), font scaling.
 - Android Keystore via JNI for `auth_tokens`.
@@ -221,8 +221,8 @@ cargo build -p solitaire_app                           # desktop sanity
 cargo clippy --workspace --all-targets -- -D warnings  # gate
 cargo test --workspace                                 # gate
 cargo apk build -p solitaire_app --target x86_64-linux-android --lib
-adb install -r target/debug/apk/solitaire-quest.apk    # `-r` reinstalls
-adb logcat -c && adb shell am start -n com.solitairequest.app/android.app.NativeActivity
+adb install -r target/debug/apk/ferrous-solitaire.apk    # `-r` reinstalls
+adb logcat -c && adb shell am start -n com.ferrousapp.solitaire/android.app.NativeActivity
 adb logcat | grep -iE "RustStdoutStderr|solitaire"
 ```
 

docs/sync_test_runbook.md

@@ -39,13 +39,13 @@ Before starting, delete any existing local save files to ensure a clean state:
 
 ```
 # Linux
-rm -rf ~/.local/share/solitaire_quest/
+rm -rf ~/.local/share/ferrous_solitaire/
 
 # macOS
-rm -rf ~/Library/Application\ Support/solitaire_quest/
+rm -rf ~/Library/Application\ Support/ferrous_solitaire/
 
 # Windows
-rmdir /s %APPDATA%\solitaire_quest\
+rmdir /s %APPDATA%\ferrous_solitaire\
 ```
 
 ---
@@ -130,10 +130,10 @@ On the machine where you want to test (Linux example):
 
 ```bash
 # List keychain entries (uses secret-tool on GNOME)
-secret-tool search service solitaire_quest_server
+secret-tool search service ferrous_solitaire_server
 
 # Overwrite alice's access token with a deliberately invalid value
-secret-tool store --label="alice_access" service solitaire_quest_server account alice_access <<< "invalid.token.value"
+secret-tool store --label="alice_access" service ferrous_solitaire_server account alice_access <<< "invalid.token.value"
 ```
 
 ### Step 2 — Trigger a sync with the expired/invalid token
@@ -148,7 +148,7 @@ secret-tool store --label="alice_access" service solitaire_quest_server account
 
 ```bash
 # Extract the new token from the keychain
-secret-tool lookup service solitaire_quest_server account alice_access | head -c 50
+secret-tool lookup service ferrous_solitaire_server account alice_access | head -c 50
 # Should look like a valid JWT (three base64 segments separated by dots)
 ```
 
@@ -157,8 +157,8 @@ secret-tool lookup service solitaire_quest_server account alice_access | head -c
 1. Corrupt both the access token and the refresh token in the keychain:
 
    ```bash
-   secret-tool store --label="alice_access" service solitaire_quest_server account alice_access <<< "bad"
-   secret-tool store --label="alice_refresh" service solitaire_quest_server account alice_refresh <<< "bad"
+   secret-tool store --label="alice_access" service ferrous_solitaire_server account alice_access <<< "bad"
+   secret-tool store --label="alice_refresh" service ferrous_solitaire_server account alice_refresh <<< "bad"
    ```
 
 2. Launch the game and trigger a sync.