Your information: use jurisdiction brand/state and prefill account profile before the page appears

[nonprofittechy]

Partner testing feedback

Vermont LITEFile testing on a laptop in Chrome:

• @VTskier Change Confirm how the court can contact you. We filled in what we could from your eFile account. to refer to LITEFile, or preferably the configured product/brand name for the jurisdiction.
• @VTskier The name and address fields were initially blank and populated a couple of seconds later, long enough for the filer to wonder why the system did not already know their account information.
• @VTskier The default state should be VT in the Vermont experience.

Code check / feasibility

All three reports are directly explained by current code:

• your_information.html hard-codes eFile account in the lede.
• The state field uses {{ filer.state|default:'IL' }}, so the empty-state fallback is Illinois even in Vermont.
• your-information.js fetches /api/auth/profile/ after render and fills only blank inputs, which creates the visible delay.
• states/vermont.yaml already provides jurisdiction.brand_name: "LITEFile" and state.code: "VT", so the correct values are already available in configuration.

Proposed implementation

• Render the configured jurisdiction brand name in the account-copy sentence.
• Use the configured jurisdiction state code as the empty-state default rather than hard-coded IL.
• Prefer loading/merging the account profile in the Django view before rendering the page so known fields are present on first paint.
• If pre-render profile loading is not practical, show a clear loading state and avoid presenting blank account-backed fields as ready before the profile request completes.
• Preserve any draft values/user edits over account defaults.

Acceptance criteria

1. Vermont first paint shows known account name/address values without a later visible population jump.
2. An empty Vermont state field defaults to VT; Illinois still defaults to IL through its own config.
3. The explanatory copy uses LITEFile/the configured brand name, not generic hard-coded eFile.
4. Saved filing-draft values continue to win over account/profile defaults.