Intake flow does not map demographic fields or household member data to Person Accounts after intake approval

After a successful intake submission and approval, a record-triggered flow creates Person Accounts for the primary applicant and household members. However, the following data is missing from the created records:

• Primary applicant's Person Account is missing demographic fields: Date of Birth, Gender, Race, Veteran Status, and Disabled Status.
• Household members' Person Accounts are missing the household mailing address and phone number.

This behavior occurs when:

• Demographic data is collected in a Screen Flow's repeater section and stored on Intake Participant records — not on the Intake record itself.
• The record-triggered flow maps demographic fields directly from $Record (the Intake object), which holds null values for the primary applicant's demographics.
• The flow does not include logic to read Intake Participant records or copy household address/phone fields to participant Person Accounts.