Update tracker agents prompts

Signed-off-by: Émile Ré <emile@probo.com>

pkg/cookiebanner/prompts/tracker_enrichment.txt.tmpl

@@ -18,7 +18,7 @@ Return a structured JSON response with:
    - With a recognizable prefix or name: "[prefix] cookie purpose" (e.g. "_ga cookie purpose").
    - For localStorage keys: "[prefix] localStorage purpose tracking".
    - Broaden if needed: "[prefix] cookie what is it used for".
-   - Stop once you have a confident, well-sourced answer; do not exhaust all queries if the first succeeds.
+   - Stop once you have a confident, well-sourced answer; do not exhaust all queries if the first succeeds. You have a limited number of turns: always keep at least one turn in reserve to return the final JSON, and never keep calling tools until you run out — if you are running low on turns, stop searching and return your best answer (an empty description is valid).
    - Verify that any result discusses a tracker whose name shares a meaningful prefix with the pattern being described. Discard results about a differently-named tracker. A generic token shared with a vendor's terminology (e.g. distinct_id, session, uid) is NOT a match when it sits behind a different, meaningful prefix — the leading prefix attributes the vendor, not a common word elsewhere in the name.
 
 4. Be factual and conservative. Describe only what the evidence supports. Do not speculate about data flows or purposes you cannot substantiate. The supplied third party is corroborated when the tracker's meaningful prefix belongs to that vendor, when the vendor's name is embedded in the key (e.g. "posthog" in "ph_phc_*_posthog"), or by a perfect pattern match; in those cases name the vendor and describe its purpose. Only when none of those hold — the vendor rests on a shared generic word alone — withhold the vendor name and describe just what you can substantiate, or return an empty description.

pkg/cookiebanner/prompts/tracker_identification.txt.tmpl

@@ -21,7 +21,7 @@ Return a structured JSON response with:
    - If observed domains are available and the name is opaque, search by domain instead: "[domain] cookies tracking privacy" (e.g. "clarity.ms cookies tracking privacy").
    - For localStorage keys, include the type: "[name] localStorage tracking script".
    - If the first query returns nothing useful, broaden: "[name] web tracker" or "site:[domain] cookie documentation".
-   - Stop searching once you get a confident match; do not exhaust all query slots if the first one succeeds.
+   - Stop searching once you get a confident match; do not exhaust all query slots if the first one succeeds. You have a limited number of turns: always keep at least one turn in reserve to return the final JSON, and never keep calling tools until you run out — if you are running low on turns, stop searching and return your best answer (an empty third_party_name with confidence below 0.3 is valid).
    - When evaluating web search results, verify that the tracker name discussed in the result shares a meaningful prefix with the pattern you are identifying. Trackers with different prefixes are distinct — for example, _hjCookieTest (Hotjar's _hj prefix) must not be confused with a pattern named cookietest (no _hj prefix). If the search result discusses a tracker whose prefix does not match, discard it and continue searching or lower your confidence.
    - A generic token shared with a vendor's terminology is NOT a match when it appears as a suffix or substring behind a different, meaningful prefix. The leading prefix is what attributes a vendor, not a common word elsewhere in the name. For example, probo_distinct_id carries the custom prefix probo_, so it must NOT be attributed to Mixpanel merely because Mixpanel uses a distinct_id key — the prefix probo_ does not belong to Mixpanel. Likewise, a key ending in _session or _uid is not attributable to a vendor just because that vendor also uses such a word.