v1.7.2: fix 2 bugs surfaced by v1.7.1 live test

Live testing on @longevityboris's Article (id 2056280764447113305) caught
two real bugs in v1.7.1.

1. **`settings.disable_fxtwitter` opt-out was silently rejected.** The
   config struct had the field but the `config set` allowlist
   (`SETTABLE_KEYS`) and the `config get` matcher both missed it, so
   `xmaster config set settings.disable_fxtwitter true` returned a
   config_error and the flag was never written. Users who wanted strict
   v2-only behavior couldn't opt out. Fixed by adding the key to both
   surfaces.

2. **Bad tweet IDs to `xmaster analyze` silently analyzed the digit
   string as text** instead of erroring. When `parse_tweet_reference`
   matched a 19-digit string but the X API returned 400/404, the fallback
   `Err(_) => text.to_string()` swallowed the error and scored "9999..."
   as 19 chars of text. Now errors are propagated with the upstream API
   error message — users get a clear "tweet not found / bad ID" instead
   of a confusing fake-score.

Verified:
- `config set settings.disable_fxtwitter true` writes successfully; the
  next `xmaster read <article_id>` returns NO `article` field.
- `config set settings.disable_fxtwitter false` re-enables and `article`
  reappears.
- `xmaster analyze 9999999999999999999` errors cleanly with the X API's
  HTTP 400 message; `xmaster analyze 2056280764447113305` still scores
  the full Article body (45 / D, 6387 chars).

99 unit + 29 integration tests pass; clippy clean.

Author: longevityboris

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "xmaster"
-version = "1.7.1"
+version = "1.7.2"
 edition = "2021"
 description = "Enterprise-grade X/Twitter CLI — post, reply, like, retweet, DM, search, and more"
 license = "MIT"

Cargo.toml

@@ -182,11 +182,10 @@ pub async fn execute(
     // content. For Article wrappers (text = single t.co), enrich via
     // FxTwitter and analyze the Article body instead of the t.co link.
     // Friction-free: agents don't need a separate command to score a post.
+    // If the input WAS a tweet reference but the fetch failed, surface the
+    // error — don't silently analyze the ID digits as text.
     let resolved_text = if let Some(id) = parse_tweet_reference(text) {
-        match resolve_post_content(&app, &id).await {
-            Ok(content) => content,
-            Err(_) => text.to_string(), // fall back to raw text on failure
-        }
+        resolve_post_content(&app, &id).await?
     } else {
         text.to_string()
     };

src/commands/analyze.rs

@@ -234,6 +234,7 @@ pub async fn get(format: OutputFormat, key: &str) -> Result<(), XmasterError> {
         "account.premium" => cfg.account.premium.to_string(),
         "account.bio" => cfg.account.bio.clone(),
         "settings.timeout" => cfg.settings.timeout.to_string(),
+        "settings.disable_fxtwitter" => cfg.settings.disable_fxtwitter.to_string(),
         "keys.xai" => mask(&cfg.keys.xai),
         "keys.api_key" => mask(&cfg.keys.api_key),
         "keys.api_secret" => mask(&cfg.keys.api_secret),
@@ -387,6 +388,7 @@ const VALID_CONFIG_KEYS: &[&str] = &[
     "keys.oauth2_access_token", "keys.oauth2_refresh_token",
     "keys.web_ct0", "keys.web_auth_token", "keys.graphql_create_tweet_id",
     "settings.timeout",
+    "settings.disable_fxtwitter",
     "account.premium",
     "account.bio",
     "style.voice",