Copy/paste prompt — extend Community Registry for government employers & servants
===================================================================================

Use this with your AI or issue tracker if you want first-class fields instead of stuffing
data into notes / employer_notes.

Context: WordPress plugin “Community Registry” already supports person CSV import with
employer_name, employer_position, employer_address, employer_notes, and a separate employer
directory table (name, address, phone_primary, phone_secondary, notes). There is no dedicated
column for government-specific metadata today.

Goal: Add optional fields for government use cases and surface them on employer directory,
profile edit screens, public profile (if applicable), and CSV import/export.

Requested additions (adjust to your privacy policy):
- Employer directory: agency_type (city | county | state | federal | school | library |
  transit | other), website_url, parent_agency_name, jurisdiction (e.g. “Mansfield, OH”).
- Person / employment: job_title_official (separate from free-text employer_position if you
  keep both), department, elected_or_appointed (enum), term_start, term_end, public_bio_url.
- CSV: extend allowed headers in CR_Import::expected_columns() and export in CR_DB::export_csv()
  to round-trip the new person + employment fields; add matching columns to employer directory
  CSV import if implemented.

Implementation constraints: follow existing CR_Sanitize / CR_DB patterns, migrations via
dbDelta or incremental CR_DB::upgrade, capability cr_edit_records for admin, and document
new headers in admin Import CSV / employer directory help text.
