Per-meeting TopicSummary is also context-starved (analyze_topic_summary)

[AndreRobitaille]

Background

While executing #93's fix, a second context-starvation bug surfaced: generate_topic_summaries in SummarizeMeetingJob uses Topics::SummaryContextBuilder to feed analyze_topic_summary, and that builder only passes agenda structure (AgendaItem.title + the usually-empty AgendaItem.summary field + packet attachments) — not the MeetingSummary.generation_data["item_details"] content.

This is the same root cause as #93 RC1, but a different job and different prompt. #93 fixed it for analyze_topic_briefing by adding recent_item_details via Topics::RecentItemDetailsBuilder. That fix does NOT touch analyze_topic_summary.

Observable symptom

On topic 513 after the #93 fix deployed:

• MeetingSummary.generation_data["item_details"] for m94 (2025-08-04 PUC) correctly contains the fake-stickers story: "Staff said fake garbage stickers are still being found, and the hauler is notifying public works and police. They also noted social media chatter about switching away from the sticker system to an automated option…"
• But ts514 (TopicSummary for topic 513 × meeting 94) says only: "A meeting agenda includes an item titled 'SOLID WASTE UTILITY: UPDATES AND ACTION, AS NEEDED.'"
• That stale ts514.generation_data flows into GenerateTopicBriefingJob#build_briefing_context as prior_meeting_analyses, polluting the briefing's factual_record with generic entries even though the underlying meeting has specific content.

Root cause

app/services/topics/summary_context_builder.rb:34-88 — agenda_items_data builds each item as:

{
  id: item.id,
  number: item.number,
  title: item.title,
  summary: item.summary,             # AgendaItem.summary — almost always nil
  recommended_action: item.recommended_action,
  citation: item_citation,
  attachments: doc_attachments       # item-level packet attachments
}

No call to MeetingSummary.generation_data["item_details"]. The per-item minutes content exists but never reaches the per-meeting topic summary prompt.

Proposed fix

Mirror #93's pattern:

1. Add a helper on Topics::SummaryContextBuilder (or a new service) that, for the meeting bound to the builder, fetches the latest MeetingSummary.generation_data["item_details"] and matches entries to the linked agenda items via Topics::TitleNormalizer.normalize.
2. Include the matched entries in agenda_items_data output under a new key (e.g. item_details_summary) alongside summary/recommended_action.
3. Update the analyze_topic_summary prompt template (lib/prompt_template_data.rb) to reference the new field and prefer it over raw packet previews when writing per-meeting factual_record entries.
4. Re-run SummarizeMeetingJob for affected meetings to regenerate TopicSummary rows with fresh content.
5. Re-run GenerateTopicBriefingJob for affected topics so the briefing picks up the cleaner prior_meeting_analyses.

Scope

• Isolated to Topics::SummaryContextBuilder, analyze_topic_summary prompt, and the SummarizeMeetingJob → generate_topic_summaries path.
• Does NOT affect analyze_topic_briefing (already fixed in Topic briefings starve on agenda structure: context starvation + empty KB + orphan TopicSummary rows #93) or any other consumer of SummaryContextBuilder.
• Topics::TitleNormalizer and Topics::RecentItemDetailsBuilder from Topic briefings starve on agenda structure: context starvation + empty KB + orphan TopicSummary rows #93 are reusable — much of the fix is composing existing pieces.

Acceptance

After this fix plus a cascade rerun of SummarizeMeetingJob for topic 513's live meetings (m94, m8, m178):

• ts514 (m94 × topic 513) factual_record names the fake-stickers story, not "agenda includes an item titled…"
• Topic 513's briefing factual_record entry for 2025-08-04 references the fake stickers incident
• Topic 513's briefing factual_record contains no residual "agenda included" boilerplate across meetings where minutes exist

Discovered while working on

Refs #93. Surfaced while diagnosing why topic 513's briefing still had a generic m94 entry after #93 shipped. See the diagnostic output in the #93 PR comments / plan doc for details.

References

• app/jobs/summarize_meeting_job.rb:88-135 (generate_topic_summaries — call site)
• app/services/topics/summary_context_builder.rb:34-88 (agenda_items_data — gap)
• app/services/topics/recent_item_details_builder.rb (reusable pattern from Topic briefings starve on agenda structure: context starvation + empty KB + orphan TopicSummary rows #93)
• lib/prompt_template_data.rb "analyze_topic_summary" entry (prompt to update)

[AndreRobitaille]

Shipped 2026-04-11. Per-meeting TopicSummary context starvation fixed.

Commits

• `15695bc` feat(topics): plumb item_details into SummaryContextBuilder
• `820644f` test(topics): cover unmatched item_details entries in SummaryContextBuilder
• `1657b88` feat(prompts): teach analyze_topic_summary about item_details_* fields

What shipped

`Topics::SummaryContextBuilder#agenda_items_data` now fetches the meeting's latest MeetingSummary and, for each linked agenda item, includes matched `item_details` content (summary, activity_level, vote, decision, public_hearing) via a new private `build_item_details_index` helper. Matching uses `Topics::TitleNormalizer` (extracted in #93) for tolerant title comparison. Prompt updated with a `<data_sources>` block naming `item_details_summary` as the primary source for factual_record entries.

Post-deploy cascade on prod

Re-ran `SummarizeMeetingJob` for topic 513's three live meetings (m94, m8, m178). Result:

• `ts514` (m94) now names fake garbage stickers + Manitowoc Disposal notifying DPW and police, AND the committee's acknowledgment of social-media chatter with staff's 2024-budget-based decision to keep the sticker system
• `ts250` (m8) now names the specific Jan 5 resident complaint about the sticker seller
• `ts674` (m178) appropriately thin (no minutes yet), no stale cross-references to pruned meetings

Bonus find caught during verification

The `analyze_topic_briefing` schema's `factual_record` field description was ambiguous about cardinality ("NEUTRAL. What happened"), which caused the briefing AI to consolidate multiple upstream events into a single entry. Caught by user pushback: "I'm not sure I agree that the other meetings had nothing." Fix in commit `e74af5a` explicitly requires one entry per distinct substantive event and names missing events as a correctness bug. Post-fix regen produced 3 substantive factual_record entries for topic 513 (fake stickers story, social-media-chatter committee decision, Jan 5 resident complaint).

Verification

Live https://tworiversmatters.com/topics/513 shows 3 timeline entries, specific headline, KB-framed story, zero "appeared on the agenda" phrasing. 534 tests green, rubocop clean.

Related

• Topic briefings starve on agenda structure: context starvation + empty KB + orphan TopicSummary rows #93 (shipped, parent fix — briefing-level plumbing)
• Tiered last-activity ranking: weight homepage by evidence quality, not just calendar recency #95 (open, follow-up — tiered last-activity ranking)