Configure Picklist Fields

1. Proposes an implementation plan and waits for the user to approve it before changing anything.
2. Reads the current picklist values, including the standard value set behind a standard field.
3. Checks record types for their own picklist defaults when a field-level default does not show up, and hands back a fix plan with manual Setup steps.
4. Explores the org to see how a picklist is used, counts records with no value and looks at related fields as signals for mapping values.
5. Writes a phased plan covering the metadata deploy, value mapping, bulk update and verification.
6. Deploys through the Metadata API or Tooling API, and falls back to the Setup UI when a deploy is refused.
7. When every route is blocked, records what it found and lays out alternative paths for the admin.

Next capability: Configure Record Types.