From ec24ccf1a76206f9762d0cc9eb95a91a489fab2c Mon Sep 17 00:00:00 2001
From: maebeale <maebeale@users.noreply.github.com>
Date: Thu, 18 Jun 2026 14:53:04 -0400
Subject: [PATCH 1/2] Show primary/additional age groups as chips on recipients
 page

The scholarship recipients page still rendered age ranges as a flat
comma-separated string while sectors already showed the primary/additional
chip treatment. Now that people carry a primary age-group distinction
(categorizable_items.is_primary), render the same starred-chip format so the
"Ages" strip reads in parallel with "Serves", falling back to the form
answer / profile text only when no age groups are tagged. Eager-load
categorizable_items on scholarship_applicants so the chips avoid an N+1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 app/services/event_dashboard.rb      |  4 +++-
 app/views/events/recipients.html.erb | 16 ++++++++++++++--
 spec/requests/events_spec.rb         | 15 +++++++++++++++
 3 files changed, 32 insertions(+), 3 deletions(-)

diff --git a/app/services/event_dashboard.rb b/app/services/event_dashboard.rb
index e3f999e827..6a799e87e2 100644
--- a/app/services/event_dashboard.rb
+++ b/app/services/event_dashboard.rb
@@ -53,7 +53,9 @@ def scholarship_recipient_count
   def scholarship_applicants
     @scholarship_applicants ||= Person
       .where(id: scholarship_applicant_ids)
-      .includes(:sectors, { categories: :category_type }, { affiliations: :organization })
+      .includes(:sectors, { categories: :category_type },
+                { categorizable_items: { category: :category_type } },
+                { affiliations: :organization })
       .sort_by(&:name)
   end
 
diff --git a/app/views/events/recipients.html.erb b/app/views/events/recipients.html.erb
index 886192931e..6d12321d03 100644
--- a/app/views/events/recipients.html.erb
+++ b/app/views/events/recipients.html.erb
@@ -79,6 +79,13 @@
               then the additional sectors alphabetically. %>
           <% sectorable_items = person.sectorable_items_primary_first %>
           <% has_sectors = sectorable_items.any? %>
+          <%# Primary age groups first (starred amber chips), then the additional
+              ones — matching the sector chips above. Falls back to the form
+              answer / profile text only when the person carries no tagged age
+              groups. %>
+          <% primary_age_groups = person.primary_age_groups.to_a %>
+          <% additional_age_groups = person.additional_age_groups.to_a %>
+          <% has_age_groups = primary_age_groups.any? || additional_age_groups.any? %>
           <div class="relative px-5 py-4 pr-12 <%= DomainTheme.bg_class_for(:scholarships, intensity: 100) %> border-b <%= DomainTheme.border_class_for(:scholarships) %>">
             <button type="button" data-action="expandable-card#toggle"
                     aria-label="Toggle <%= person.name %> application"
@@ -117,7 +124,7 @@
                 </div>
 
                 <%# Serves / Ages — parallel with the name %>
-                <% if has_sectors || service_area_text.present? || age_group_text.present? %>
+                <% if has_sectors || service_area_text.present? || has_age_groups || age_group_text.present? %>
                   <div class="flex flex-wrap items-center gap-x-8 gap-y-2">
                     <% if has_sectors %>
                       <div class="flex flex-wrap items-center gap-2">
@@ -132,7 +139,12 @@
                         <%= service_area_text %>
                       </div>
                     <% end %>
-                    <% if age_group_text.present? %>
+                    <% if has_age_groups %>
+                      <div class="flex flex-wrap items-center gap-2">
+                        <span class="text-xs font-semibold uppercase tracking-wide text-gray-400">Ages</span>
+                        <%= render "shared/age_group_tags", primary: primary_age_groups, additional: additional_age_groups %>
+                      </div>
+                    <% elsif age_group_text.present? %>
                       <div class="flex items-center gap-2">
                         <span class="text-xs font-semibold uppercase tracking-wide text-gray-400">Ages</span>
                         <span class="inline-flex items-center rounded-md border border-gray-200 bg-gray-50 px-3 py-1 text-sm font-medium text-gray-600"><%= age_group_text %></span>
diff --git a/spec/requests/events_spec.rb b/spec/requests/events_spec.rb
index 5fa10f5fad..e7647ebc99 100644
--- a/spec/requests/events_spec.rb
+++ b/spec/requests/events_spec.rb
@@ -1255,6 +1255,21 @@ def submit_agency_name(name)
         expect(response.body).not_to include("Pat Plain")
       end
 
+      it "renders each recipient's tagged age groups as chips, primary ones starred" do
+        age_type = create(:category_type, name: "AgeRange", published: true)
+        teens = create(:category, :published, category_type: age_type, name: "13-17")
+        adults = create(:category, :published, category_type: age_type, name: "18+")
+        applicant.tag_age_groups(primary_ids: [ teens.id ], additional_ids: [ adults.id ])
+
+        get recipients_event_path(event)
+
+        page = Capybara.string(response.body)
+        expect(page).to have_content("13-17")
+        expect(page).to have_content("18+")
+        # The primary group leads with the starred amber chip from the shared partial.
+        expect(page).to have_css("span.text-amber-800 i.fa-star")
+      end
+
       it "shows the org linked to its website on the left and the bold recipient name linked to their profile on the right" do
         applicant.update!(shoutout_text: "Grateful to bring art to the survivors we serve.")
         event.event_registrations.find_by(registrant: applicant).update!(shoutout: true)

From 8faada98078b7aaeb903b67534886885df4f1e78 Mon Sep 17 00:00:00 2001
From: maebeale <maebeale@users.noreply.github.com>
Date: Thu, 18 Jun 2026 15:08:07 -0400
Subject: [PATCH 2/2] Seed demo users with a primary age group

The new recipients chips read a person's profile age groups first, but the
three demo accounts (Umberto, Amy, Aisha) carried no age-range taggings, so the
display fell back to plain text for them. Tag each with one primary age group
(plus a few additional) so the starred-chip rendering has real data to show,
modeling the intended shape: one primary, optionally some additional.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 db/seeds/dev/people_profiles.rb | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/db/seeds/dev/people_profiles.rb b/db/seeds/dev/people_profiles.rb
index cec37fd3af..be7fb438f5 100644
--- a/db/seeds/dev/people_profiles.rb
+++ b/db/seeds/dev/people_profiles.rb
@@ -211,3 +211,25 @@
     end
   end
 end
+
+puts "Tagging seed users with primary/additional age groups…"
+# A person serves one core age group and sometimes a few others, so the profile
+# and recipients pages show a single starred primary chip plus any additional
+# ones. Give the three demo accounts that shape so the chip display has real data
+# to render. tag_age_groups marks exactly the named primary and treats the rest
+# as additional, and is idempotent on reseed.
+seed_user_age_groups = {
+  "umberto.user@example.com" => { primary: "13-17", additional: [ "18+" ] },
+  "amy.user@example.com" => { primary: "6-12", additional: [ "3-5", "13-17" ] },
+  "aisha.user@example.com" => { primary: "18+", additional: [] }
+}
+seed_user_age_groups.each do |email, groups|
+  person = User.find_by(email: email)&.person
+  next unless person
+
+  primary = Category.age_ranges.published.find_by(name: groups[:primary])
+  next unless primary
+
+  additional = Category.age_ranges.published.where(name: groups[:additional]).to_a
+  person.tag_age_groups(primary_ids: [ primary.id ], additional_ids: additional.map(&:id))
+end