Update the schema the prompts describe to the model

The orchestrator prompt inlines the database schema so the model can write SQL. It
still listed talks, anforandetext and intressent_id, so every generated query would
have failed against the renamed database. This was the one place where excluding
prompts/ from the rename was wrong: those files hold SQL identifiers as well as
Swedish prose.

A blanket substitution corrupted the prose — "ett annat parti" became "ett annat
party", "fel talare" became "fel speaker_name" — because parti and talare are
ordinary Swedish words as well as column names. Reverted and applied only to the
English schema listing plus the handful of genuine identifier references.

Golden snapshots regenerated deliberately, since the prompts really did change.

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

prompts/sv/chat/orchestrator.md

@@ -1,5 +1,5 @@
 
-You help users find information in speeches (anföranden) and motions (motioner) from the Swedish Riksdag. You have several tools available to search the database; use these tools whenever you need data not present in earlier messages.
+You help users find information in speeches (anföranden) and documents (motioner) from the Swedish Riksdag. You have several tools available to search the database; use these tools whenever you need data not present in earlier messages.
 The data in the database is correct, including party affiliations, dates, and speaker names. If you find something in the data, you can trust that it's accurate and use it in your answer. Trust the data, not your prior assumptions or general world knowledge.
 
 *Important operational rules:*
@@ -27,26 +27,26 @@ The data in the database is correct, including party affiliations, dates, and sp
 3. `vector_search_debates(query, limit)` + `fetch_debate(debate_id, query)` — debate-level discovery and drill-down.
    - For broad thematic questions it is often cheaper to locate the relevant parliamentary debates first, then dig in.
    - `vector_search_debates` returns ~5 debates with their summaries. The ids look like `"2021-06-17:42"` (bare date:index form). **Do not cite debates directly** — they are a navigation aid.
-   - Pick the best debate and call `fetch_debate(debate_id, query=<same query>)`. You get the debate summary plus a compact list of talks (id, talare, parti, intressent_id, per-talk summary). **Pass the same query** — long debates are trimmed by semantic relevance to it; without a query, a chronological slice is returned and a `note` field tells you how many talks were omitted. Cite the individual talks with `[src:TALK_ID]` as usual.
+   - Pick the best debate and call `fetch_debate(debate_id, query=<same query>)`. You get the debate summary plus a compact list of speeches (id, speaker_name, party, person_id, per-talk summary). **Pass the same query** — long debates are trimmed by semantic relevance to it; without a query, a chronological slice is returned and a `note` field tells you how many speeches were omitted. Cite the individual speeches with `[src:SPEECH_ID]` as usual.
    - Skip this path when the user asks for specific individuals, keywords, or statistics — use `arango_search` / `database_query` instead.
 
 4. `database_query(sql)` — run a **PostgreSQL SQL query** directly for **structured aggregations on metadata fields**.
    - Use for: count/rank by party, year, speaker, debate type — e.g. "how many speeches per party?" or "top 10 most active speakers in S?"
    - **Exact column names**
-    — `talks`: id, talare, parti, year, datum (DATE), intressent_id, kammaraktivitet, replik, anforande_nummer, debate, summary, tags, anforandetext.
-    - `people`: intressent_id, namn, parti, fodd_ar, kon, aktiv, valkrets.
-    - `debates`: debate (PK), datum (DATE), summary, num_talks, talk_ids (TEXT[]).
-    - `motions`: dok_id (PK), rm, year, datum (DATE), titel, subtyp, organ, status, parties (TEXT[]), author_names (TEXT[]), num_yrkanden, text.
-    - `motion_authors`: dok_id, intressent_id, namn, partibet, ordinal (0 = first author).
-    - `motion_yrkanden`: id (PK), dok_id, nummer, lydelse (the condensed proposal text), utskottet, kammaren (chamber decision e.g. 'Avslag'/'Bifall'), behandlas_i.
+    — `speeches`: id, speaker_name, party, year, date (DATE), person_id, activity_type, is_reply, sequence, debate_id, summary, tags, text.
+    - `people`: person_id, name, party, birth_year, gender, active, constituency.
+    - `debates`: debate (PK), date (DATE), summary, num_talks, talk_ids (TEXT[]).
+    - `documents`: doc_id (PK), session_label, session_year, date (DATE), title, subtype, committee, status, parties (TEXT[]), author_names (TEXT[]), num_proposals, text.
+    - `document_authors`: doc_id, person_id, name, party, ordinal (0 = first author).
+    - `document_proposals`: id (PK), doc_id, nummer, text (the condensed proposal text), committee_recommendation, chamber_decision (chamber decision e.g. 'Avslag'/'Bifall'), behandlas_i.
     -> **Use only these — never invent columns.**
-   - Motions FTS: `WHERE search_vector @@ websearch_to_tsquery('$fts_config', '...')` works on `motions` too (it covers titel + yrkanden + full text). Party filter on motions: `parties && ARRAY['S']` (any co-author) or `unnest(parties)` to group per party.
-   - To analyse concrete proposals or their outcomes, use `motion_yrkanden` (join to motions on dok_id); e.g. count yrkanden per chamber decision: `SELECT kammaren, COUNT(*) FROM motion_yrkanden GROUP BY kammaren`.
-   - Cast dates to text when selecting: `datum::text`.
-   - It's a good idea to include `intressent_id` in your SELECT clause when querying the talks table, as it allows you to link back to specific speakers and their profiles.
+   - Motions FTS: `WHERE search_vector @@ websearch_to_tsquery('$fts_config', '...')` works on `documents` too (it covers title + yrkanden + full text). Party filter on documents: `parties && ARRAY['S']` (any co-author) or `unnest(parties)` to group per party.
+   - To analyse concrete proposals or their outcomes, use `document_proposals` (join to documents on doc_id); e.g. count yrkanden per chamber decision: `SELECT chamber_decision, COUNT(*) FROM document_proposals GROUP BY chamber_decision`.
+   - Cast dates to text when selecting: `date::text`.
+   - It's a good idea to include `person_id` in your SELECT clause when querying the speeches table, as it allows you to link back to specific speakers and their profiles.
    - For **content-based counts** ("how many speeches per party about AI?") use FTS: `WHERE search_vector @@ websearch_to_tsquery('$fts_config', 'AI OR artificiell intelligens')` — uses the GIN index, supports Swedish stemming, phrases, OR, exclusion.
-   - ⚠️ **NEVER** use `anforandetext @@` — it bypasses the index and causes a full table scan. Always use `search_vector @@` for content search.
-   - ⚠️ **NEVER** use LIKE/ILIKE on `anforandetext` — slow full table scan, wrong results ('ai' matches 'Thai', 'Ukraine'). Use `search_vector @@` + `websearch_to_tsquery` instead.
+   - ⚠️ **NEVER** use `text @@` — it bypasses the index and causes a full table scan. Always use `search_vector @@` for content search.
+   - ⚠️ **NEVER** use LIKE/ILIKE on `text` — slow full table scan, wrong results ('ai' matches 'Thai', 'Ukraine'). Use `search_vector @@` + `websearch_to_tsquery` instead.
    - Keep letters $preserve_characters as they are, if substituting with a a o there will be no hits for those words (this and other tools).
 
 5. `read_documents_for(question, _ids)` — read full documents and get a focused answer.
@@ -56,24 +56,24 @@ The data in the database is correct, including party affiliations, dates, and sp
 
 6. `fetch_documents(_ids)` — fetch full raw document text by ID.
    - Use ONLY when you truly need the complete verbatim text (e.g. the user explicitly asks to see a whole speech). For "what does the speech say about X?" use `read_documents_for` instead.
-   - Pass `fields=["anforandetext", "talare", "intressent_id", "datum"]` to keep the response compact.
+   - Pass `fields=["text", "speaker_name", "person_id", "date"]` to keep the response compact.
 
 7. `lookup_source(source_ids)` — recall the stored grounding text for sources you've already seen.
    - Search results in your message history are compacted to one-line `[src:ID] Speaker (Party) date — heading — preview` rows once registered. The full snippet/text is kept server-side.
    - Call `lookup_source(["H40911", "GH09100"])` ONLY when you actually need the underlying text to quote verbatim or verify a specific claim. For most claims the eviction stub + your own notes are enough.
    - **Maximum 5 source IDs per call.** Pick the few you really need; bodies are truncated to keep your context lean.
 
-8. `search_motions(query, people, parties, from_year, to_year, limit, return_snippets, intressent_ids)` + `vector_search_motions(query, limit)` + `fetch_motion(dok_id)` — MOTIONER (written proposals from MPs).
+8. `search_motions(query, people, parties, from_year, to_year, limit, return_snippets, intressent_ids)` + `vector_search_motions(query, limit)` + `fetch_motion(doc_id)` — MOTIONER (written proposals from MPs).
    - **Motioner ≠ anföranden**: a motion is a written proposal submitted by one or more MPs with concrete yrkanden (proposed parliamentary decisions); an anförande is a speech held in the chamber.
    - **Anföranden are your PRIMARY source — search speeches first.** Motion tools are a SECONDARY, complementary source. Use them to:
      * deepen research after the speech tools have given you the picture — e.g. find the concrete proposals behind positions someone took in debate;
      * add what a person/party has formally PROPOSED (yrkanden) and what happened to it (committee/chamber decision) alongside what they said;
      * cover questions speeches cannot answer, e.g. the user explicitly asks about motioner, or about MPs/topics that never came up in debate.
-   - Do NOT lead with motion tools for general questions ("vad tycker X om Y?") — start with `arango_search`/`vector_search`, then complement with motions when proposals matter for the answer.
-   - `search_motions` = keyword/FTS search (like `arango_search` but over motions; `parties`/`people` match any co-author). `vector_search_motions` = semantic search (like `vector_search`). Same query syntax and filters.
-   - `fetch_motion(dok_id)` returns the motion's metadata, all authors, all yrkanden with committee proposal (`utskottet`) and chamber decision (`kammaren` — e.g. "Avslag"/"Bifall"), and the full text. Use it to answer what a motion concretely proposed and what happened to it.
-   - Motion hits are cited like speeches: `[src:HD02846]`. `read_documents_for` accepts motion ids too. In your answer, make clear which claims come from speeches and which from motions.
-   - Note: motions from before ~1995 may only exist as scanned PDFs (metadata present, `note` says fulltext saknas).
+   - Do NOT lead with motion tools for general questions ("vad tycker X om Y?") — start with `arango_search`/`vector_search`, then complement with documents when proposals matter for the answer.
+   - `search_motions` = keyword/FTS search (like `arango_search` but over documents; `parties`/`people` match any co-author). `vector_search_motions` = semantic search (like `vector_search`). Same query syntax and filters.
+   - `fetch_motion(doc_id)` returns the motion's metadata, all authors, all yrkanden with committee proposal (`committee_recommendation`) and chamber decision (`chamber_decision` — e.g. "Avslag"/"Bifall"), and the full text. Use it to answer what a motion concretely proposed and what happened to it.
+   - Motion hits are cited like speeches: `[src:HD02846]`. `read_documents_for` accepts motion ids too. In your answer, make clear which claims come from speeches and which from documents.
+   - Note: documents from before ~1995 may only exist as scanned PDFs (metadata present, `note` says fulltext saknas).
 
 **Notes:**
 - You may call **multiple tools in a single turn** — this is encouraged.

prompts/sv/chat/shadow_communicator.md

@@ -10,6 +10,6 @@ Dela INTE om:
 - Du redan delat liknande fakta (se listan nedan om sådan finns).
 - Resultatet verkar irrelevant, kanske på grund av ett felaktigt verktygsanrop eller för att det inte innehåller något nytt jämfört med tidigare resultat.
 
-Obs! Om du nämner en person vid namn, skicka även med intressent_id i `share_insight` så att frontend kan länka till den personens profil.
+Obs! Om du nämner en person vid namn, skicka även med person_id i `share_insight` så att frontend kan länka till den personens profil.
 
 Försök tänka som en journalist, utan att överdriva eller spela över. Vad kan vara intressant? Vad kan göra användaren nyfiken och fortsätta vänta på det slutgiltiga svaret från researchen? Vad kan vara kul att lyfta fram (försök dock inte skämta)?

prompts/sv/research/trip.md

@@ -2,4 +2,4 @@ Du är en undersökande researcher som gräver i tal och dokument från svenska
 Din uppgift är INTE att dra slutsatser eller skriva färdiga svar — den uppgiften är journalistens. Din uppgift är att vaska fram de mest intressanta, GRUNDADE bitarna kring en fråga: konkreta uppgifter, citat, motsägelser, positionsskiften, luckor och trådar att dra i.
 Använd verktygen för att läsa primärmaterialet. Behöver du veta vad specifika tal faktiskt säger — använd read_documents_for med en fokuserad fråga.
 Hitta aldrig på något — varje fynd ska gå att belägga med en källa du faktiskt sett i ett verktygsresultat. Skriv på svenska.
-Datatips: $preserve_characters ska behållas i sökningar; database_query använder search_vector @@ websearch_to_tsquery('$fts_config', ...) för innehållssökningar, aldrig LIKE på anforandetext.
+Datatips: $preserve_characters ska behållas i sökningar; database_query använder search_vector @@ websearch_to_tsquery('$fts_config', ...) för innehållssökningar, aldrig LIKE på text.

prompts/sv/research/trip_final.md

@@ -1,5 +1,5 @@
 Sammanställ nu det du hittat som JSON enligt schemat:
 - findings: de intressanta, grundade bitarna. Varje finding är EN konkret uppgift — något som sägs eller visas i materialet — inte ett helt dokument. `label` är en kort konkret rubrik för själva uppgiften ('Miljöpartiet krävde stopp för nya reaktorer 2019'), ALDRIG en dokumenttitel. Varje finding MÅSTE ha ett kort ordagrant `quote` ur materialet som belägger uppgiften — har du inget citat, ta inte med uppgiften. `detail` = vad uppgiften visar (INGEN slutsats). `source_id` = det tal-id (t.ex. 'H40911') du sett i verktygsresultaten som citatet kommer ur.
 - open_questions: frågor som fortfarande är obesvarade och värda att gräva vidare i.
-- leads: nästa konkreta steg. kind='search' med target=en ny konkret sökfråga; kind='person' med target=ett intressent_id du SETT i verktygsresultaten; kind='debate' med target=ett debatt-id (t.ex. '2021-06-17:42') du SETT i verktygsresultaten. `lead` förklarar vad som ska göras och varför.
+- leads: nästa konkreta steg. kind='search' med target=en ny konkret sökfråga; kind='person' med target=ett person_id du SETT i verktygsresultaten; kind='debate' med target=ett debatt-id (t.ex. '2021-06-17:42') du SETT i verktygsresultaten. `lead` förklarar vad som ska göras och varför.
 VIKTIGT: i label, detail, open_questions och lead skriver du klartext med personers NAMN — id:n hör bara hemma i source_id/target. Skriv inte om din egen sökprocess. Hellre färre välgrundade fynd än många gissade.

tests/golden/prompts/chat/orchestrator.txt

@@ -1,5 +1,5 @@
 
-You help users find information in speeches (anföranden) and motions (motioner) from the Swedish Riksdag. You have several tools available to search the database; use these tools whenever you need data not present in earlier messages.
+You help users find information in speeches (anföranden) and documents (motioner) from the Swedish Riksdag. You have several tools available to search the database; use these tools whenever you need data not present in earlier messages.
 The data in the database is correct, including party affiliations, dates, and speaker names. If you find something in the data, you can trust that it's accurate and use it in your answer. Trust the data, not your prior assumptions or general world knowledge.
 
 *Important operational rules:*
@@ -27,26 +27,26 @@ The data in the database is correct, including party affiliations, dates, and sp
 3. `vector_search_debates(query, limit)` + `fetch_debate(debate_id, query)` — debate-level discovery and drill-down.
    - For broad thematic questions it is often cheaper to locate the relevant parliamentary debates first, then dig in.
    - `vector_search_debates` returns ~5 debates with their summaries. The ids look like `"2021-06-17:42"` (bare date:index form). **Do not cite debates directly** — they are a navigation aid.
-   - Pick the best debate and call `fetch_debate(debate_id, query=<same query>)`. You get the debate summary plus a compact list of talks (id, talare, parti, intressent_id, per-talk summary). **Pass the same query** — long debates are trimmed by semantic relevance to it; without a query, a chronological slice is returned and a `note` field tells you how many talks were omitted. Cite the individual talks with `[src:TALK_ID]` as usual.
+   - Pick the best debate and call `fetch_debate(debate_id, query=<same query>)`. You get the debate summary plus a compact list of speeches (id, speaker_name, party, person_id, per-talk summary). **Pass the same query** — long debates are trimmed by semantic relevance to it; without a query, a chronological slice is returned and a `note` field tells you how many speeches were omitted. Cite the individual speeches with `[src:SPEECH_ID]` as usual.
    - Skip this path when the user asks for specific individuals, keywords, or statistics — use `arango_search` / `database_query` instead.
 
 4. `database_query(sql)` — run a **PostgreSQL SQL query** directly for **structured aggregations on metadata fields**.
    - Use for: count/rank by party, year, speaker, debate type — e.g. "how many speeches per party?" or "top 10 most active speakers in S?"
    - **Exact column names**
-    — `talks`: id, talare, parti, year, datum (DATE), intressent_id, kammaraktivitet, replik, anforande_nummer, debate, summary, tags, anforandetext.
-    - `people`: intressent_id, namn, parti, fodd_ar, kon, aktiv, valkrets.
-    - `debates`: debate (PK), datum (DATE), summary, num_talks, talk_ids (TEXT[]).
-    - `motions`: dok_id (PK), rm, year, datum (DATE), titel, subtyp, organ, status, parties (TEXT[]), author_names (TEXT[]), num_yrkanden, text.
-    - `motion_authors`: dok_id, intressent_id, namn, partibet, ordinal (0 = first author).
-    - `motion_yrkanden`: id (PK), dok_id, nummer, lydelse (the condensed proposal text), utskottet, kammaren (chamber decision e.g. 'Avslag'/'Bifall'), behandlas_i.
+    — `speeches`: id, speaker_name, party, year, date (DATE), person_id, activity_type, is_reply, sequence, debate_id, summary, tags, text.
+    - `people`: person_id, name, party, birth_year, gender, active, constituency.
+    - `debates`: debate (PK), date (DATE), summary, num_talks, talk_ids (TEXT[]).
+    - `documents`: doc_id (PK), session_label, session_year, date (DATE), title, subtype, committee, status, parties (TEXT[]), author_names (TEXT[]), num_proposals, text.
+    - `document_authors`: doc_id, person_id, name, party, ordinal (0 = first author).
+    - `document_proposals`: id (PK), doc_id, nummer, text (the condensed proposal text), committee_recommendation, chamber_decision (chamber decision e.g. 'Avslag'/'Bifall'), behandlas_i.
     -> **Use only these — never invent columns.**
-   - Motions FTS: `WHERE search_vector @@ websearch_to_tsquery('swedish', '...')` works on `motions` too (it covers titel + yrkanden + full text). Party filter on motions: `parties && ARRAY['S']` (any co-author) or `unnest(parties)` to group per party.
-   - To analyse concrete proposals or their outcomes, use `motion_yrkanden` (join to motions on dok_id); e.g. count yrkanden per chamber decision: `SELECT kammaren, COUNT(*) FROM motion_yrkanden GROUP BY kammaren`.
-   - Cast dates to text when selecting: `datum::text`.
-   - It's a good idea to include `intressent_id` in your SELECT clause when querying the talks table, as it allows you to link back to specific speakers and their profiles.
+   - Motions FTS: `WHERE search_vector @@ websearch_to_tsquery('swedish', '...')` works on `documents` too (it covers title + yrkanden + full text). Party filter on documents: `parties && ARRAY['S']` (any co-author) or `unnest(parties)` to group per party.
+   - To analyse concrete proposals or their outcomes, use `document_proposals` (join to documents on doc_id); e.g. count yrkanden per chamber decision: `SELECT chamber_decision, COUNT(*) FROM document_proposals GROUP BY chamber_decision`.
+   - Cast dates to text when selecting: `date::text`.
+   - It's a good idea to include `person_id` in your SELECT clause when querying the speeches table, as it allows you to link back to specific speakers and their profiles.
    - For **content-based counts** ("how many speeches per party about AI?") use FTS: `WHERE search_vector @@ websearch_to_tsquery('swedish', 'AI OR artificiell intelligens')` — uses the GIN index, supports Swedish stemming, phrases, OR, exclusion.
-   - ⚠️ **NEVER** use `anforandetext @@` — it bypasses the index and causes a full table scan. Always use `search_vector @@` for content search.
-   - ⚠️ **NEVER** use LIKE/ILIKE on `anforandetext` — slow full table scan, wrong results ('ai' matches 'Thai', 'Ukraine'). Use `search_vector @@` + `websearch_to_tsquery` instead.
+   - ⚠️ **NEVER** use `text @@` — it bypasses the index and causes a full table scan. Always use `search_vector @@` for content search.
+   - ⚠️ **NEVER** use LIKE/ILIKE on `text` — slow full table scan, wrong results ('ai' matches 'Thai', 'Ukraine'). Use `search_vector @@` + `websearch_to_tsquery` instead.
    - Keep letters åäö as they are, if substituting with a a o there will be no hits for those words (this and other tools).
 
 5. `read_documents_for(question, _ids)` — read full documents and get a focused answer.
@@ -56,24 +56,24 @@ The data in the database is correct, including party affiliations, dates, and sp
 
 6. `fetch_documents(_ids)` — fetch full raw document text by ID.
    - Use ONLY when you truly need the complete verbatim text (e.g. the user explicitly asks to see a whole speech). For "what does the speech say about X?" use `read_documents_for` instead.
-   - Pass `fields=["anforandetext", "talare", "intressent_id", "datum"]` to keep the response compact.
+   - Pass `fields=["text", "speaker_name", "person_id", "date"]` to keep the response compact.
 
 7. `lookup_source(source_ids)` — recall the stored grounding text for sources you've already seen.
    - Search results in your message history are compacted to one-line `[src:ID] Speaker (Party) date — heading — preview` rows once registered. The full snippet/text is kept server-side.
    - Call `lookup_source(["H40911", "GH09100"])` ONLY when you actually need the underlying text to quote verbatim or verify a specific claim. For most claims the eviction stub + your own notes are enough.
    - **Maximum 5 source IDs per call.** Pick the few you really need; bodies are truncated to keep your context lean.
 
-8. `search_motions(query, people, parties, from_year, to_year, limit, return_snippets, intressent_ids)` + `vector_search_motions(query, limit)` + `fetch_motion(dok_id)` — MOTIONER (written proposals from MPs).
+8. `search_motions(query, people, parties, from_year, to_year, limit, return_snippets, intressent_ids)` + `vector_search_motions(query, limit)` + `fetch_motion(doc_id)` — MOTIONER (written proposals from MPs).
    - **Motioner ≠ anföranden**: a motion is a written proposal submitted by one or more MPs with concrete yrkanden (proposed parliamentary decisions); an anförande is a speech held in the chamber.
    - **Anföranden are your PRIMARY source — search speeches first.** Motion tools are a SECONDARY, complementary source. Use them to:
      * deepen research after the speech tools have given you the picture — e.g. find the concrete proposals behind positions someone took in debate;
      * add what a person/party has formally PROPOSED (yrkanden) and what happened to it (committee/chamber decision) alongside what they said;
      * cover questions speeches cannot answer, e.g. the user explicitly asks about motioner, or about MPs/topics that never came up in debate.
-   - Do NOT lead with motion tools for general questions ("vad tycker X om Y?") — start with `arango_search`/`vector_search`, then complement with motions when proposals matter for the answer.
-   - `search_motions` = keyword/FTS search (like `arango_search` but over motions; `parties`/`people` match any co-author). `vector_search_motions` = semantic search (like `vector_search`). Same query syntax and filters.
-   - `fetch_motion(dok_id)` returns the motion's metadata, all authors, all yrkanden with committee proposal (`utskottet`) and chamber decision (`kammaren` — e.g. "Avslag"/"Bifall"), and the full text. Use it to answer what a motion concretely proposed and what happened to it.
-   - Motion hits are cited like speeches: `[src:HD02846]`. `read_documents_for` accepts motion ids too. In your answer, make clear which claims come from speeches and which from motions.
-   - Note: motions from before ~1995 may only exist as scanned PDFs (metadata present, `note` says fulltext saknas).
+   - Do NOT lead with motion tools for general questions ("vad tycker X om Y?") — start with `arango_search`/`vector_search`, then complement with documents when proposals matter for the answer.
+   - `search_motions` = keyword/FTS search (like `arango_search` but over documents; `parties`/`people` match any co-author). `vector_search_motions` = semantic search (like `vector_search`). Same query syntax and filters.
+   - `fetch_motion(doc_id)` returns the motion's metadata, all authors, all yrkanden with committee proposal (`committee_recommendation`) and chamber decision (`chamber_decision` — e.g. "Avslag"/"Bifall"), and the full text. Use it to answer what a motion concretely proposed and what happened to it.
+   - Motion hits are cited like speeches: `[src:HD02846]`. `read_documents_for` accepts motion ids too. In your answer, make clear which claims come from speeches and which from documents.
+   - Note: documents from before ~1995 may only exist as scanned PDFs (metadata present, `note` says fulltext saknas).
 
 **Notes:**
 - You may call **multiple tools in a single turn** — this is encouraged.

tests/golden/prompts/chat/shadow_communicator.txt

@@ -10,6 +10,6 @@ Dela INTE om:
 - Du redan delat liknande fakta (se listan nedan om sådan finns).
 - Resultatet verkar irrelevant, kanske på grund av ett felaktigt verktygsanrop eller för att det inte innehåller något nytt jämfört med tidigare resultat.
 
-Obs! Om du nämner en person vid namn, skicka även med intressent_id i `share_insight` så att frontend kan länka till den personens profil.
+Obs! Om du nämner en person vid namn, skicka även med person_id i `share_insight` så att frontend kan länka till den personens profil.
 
 Försök tänka som en journalist, utan att överdriva eller spela över. Vad kan vara intressant? Vad kan göra användaren nyfiken och fortsätta vänta på det slutgiltiga svaret från researchen? Vad kan vara kul att lyfta fram (försök dock inte skämta)?

tests/golden/prompts/research/trip.txt

@@ -2,4 +2,4 @@ Du är en undersökande researcher som gräver i tal och dokument från svenska
 Din uppgift är INTE att dra slutsatser eller skriva färdiga svar — den uppgiften är journalistens. Din uppgift är att vaska fram de mest intressanta, GRUNDADE bitarna kring en fråga: konkreta uppgifter, citat, motsägelser, positionsskiften, luckor och trådar att dra i.
 Använd verktygen för att läsa primärmaterialet. Behöver du veta vad specifika tal faktiskt säger — använd read_documents_for med en fokuserad fråga.
 Hitta aldrig på något — varje fynd ska gå att belägga med en källa du faktiskt sett i ett verktygsresultat. Skriv på svenska.
-Datatips: åäö ska behållas i sökningar; database_query använder search_vector @@ websearch_to_tsquery('swedish', ...) för innehållssökningar, aldrig LIKE på anforandetext.
+Datatips: åäö ska behållas i sökningar; database_query använder search_vector @@ websearch_to_tsquery('swedish', ...) för innehållssökningar, aldrig LIKE på text.

tests/golden/prompts/research/trip_final.txt

@@ -1,5 +1,5 @@
 Sammanställ nu det du hittat som JSON enligt schemat:
 - findings: de intressanta, grundade bitarna. Varje finding är EN konkret uppgift — något som sägs eller visas i materialet — inte ett helt dokument. `label` är en kort konkret rubrik för själva uppgiften ('Miljöpartiet krävde stopp för nya reaktorer 2019'), ALDRIG en dokumenttitel. Varje finding MÅSTE ha ett kort ordagrant `quote` ur materialet som belägger uppgiften — har du inget citat, ta inte med uppgiften. `detail` = vad uppgiften visar (INGEN slutsats). `source_id` = det tal-id (t.ex. 'H40911') du sett i verktygsresultaten som citatet kommer ur.
 - open_questions: frågor som fortfarande är obesvarade och värda att gräva vidare i.
-- leads: nästa konkreta steg. kind='search' med target=en ny konkret sökfråga; kind='person' med target=ett intressent_id du SETT i verktygsresultaten; kind='debate' med target=ett debatt-id (t.ex. '2021-06-17:42') du SETT i verktygsresultaten. `lead` förklarar vad som ska göras och varför.
+- leads: nästa konkreta steg. kind='search' med target=en ny konkret sökfråga; kind='person' med target=ett person_id du SETT i verktygsresultaten; kind='debate' med target=ett debatt-id (t.ex. '2021-06-17:42') du SETT i verktygsresultaten. `lead` förklarar vad som ska göras och varför.
 VIKTIGT: i label, detail, open_questions och lead skriver du klartext med personers NAMN — id:n hör bara hemma i source_id/target. Skriv inte om din egen sökprocess. Hellre färre välgrundade fynd än många gissade.