chore: ignore the local live-provider probes (#1007)

Seven probe scripts sat untracked in `tool/` through the whole 2.2.0
release: `live_model_compare`, `live_openai`, `live_openai_client_check`,
`live_openrouter`, `live_own_server`, `live_routing_policy` and
`verify_openai_key`. They take a key as a file-path argument rather than
embedding one, so the exposure was never the key. The risk is a `git add
-A` sweeping an ad-hoc script into a release branch, and `git status`
listing seven files that are neither wanted nor ignored makes that
easier, not harder.

`tool/policy_snapshot.dart` is a committed tool and stays tracked; the
pattern is scoped to the probes.

`docs/ai-model-candidates.md` listed `tool/live_routing_policy.dart`
under "In-repo files cited" as a link, which resolved to a 404 on
github.com and now would not even be a file the repo could contain. It
is named there instead, with a line saying why it is not committed. The
two other references to these scripts are code spans in command
examples, which were never links.

Author: simonoppowa

.gitignore

@@ -66,5 +66,14 @@ result
 # Exception for Gemfile.lock, which is needed for Fastlane / Bundler
 !**/Gemfile.lock
 
+# Live provider probes — scripts that talk to a real AI provider with a real
+# key, kept locally and never committed. They take the key as a *file path*
+# argument rather than embedding one, so the risk is not the key leaking; it
+# is a `git add -A` sweeping an ad-hoc script into a release branch, which is
+# exactly what nearly happened during 2.2.0. `tool/policy_snapshot.dart` is a
+# committed tool and stays tracked — this ignores only the probes.
+tool/live_*.dart
+tool/verify_openai_key.dart
+
 # Fastlane / Bundler — local gem install path (bundle config set path vendor/bundle)
 ios/vendor/

docs/ai-model-candidates.md

@@ -568,5 +568,8 @@ Related notes in this repo:
 
 In-repo files cited:
 [`lib/core/utils/ai_model_catalogue.dart`](../lib/core/utils/ai_model_catalogue.dart) ·
-[`lib/features/add_meal/data/openrouter_meal_items_api.dart`](../lib/features/add_meal/data/openrouter_meal_items_api.dart) ·
-[`tool/live_routing_policy.dart`](../tool/live_routing_policy.dart)
+[`lib/features/add_meal/data/openrouter_meal_items_api.dart`](../lib/features/add_meal/data/openrouter_meal_items_api.dart)
+
+The routing-policy check behind the table above was run with a local probe,
+`tool/live_routing_policy.dart`. It talks to a real provider with a real key and
+is deliberately not committed, so it is named here rather than linked.