` so the operator can confirm the
* persisted value against the upstream Associates / RMS /
* DG console. The Settings page is `manage_options`-gated
* at the page-callback level (§3), so only admin-tier
* users reach this surface; the operator UX preference
* here is to expose the saved value so it can be audited
* in place. Logs / diagnostics surfaces continue to mask
* via {@see \Affilun\Application\Settings\SettingsCredentialMask}
* so secrets never leak into operational telemetry.
* - The associated `` carries the
* placeholder `(leave blank to keep current)` so the user
* understands the rotating-input contract.
* - Empty submission preserves the current value; a
* non-empty submission rotates. The actual rotation logic
* lives in
* {@see \Affilun\Application\Settings\UseCase\SaveSettingsUseCase}.
*
* Status-flash protocol:
*
* - The optional `$statusFlash` parameter accepts the literal
* `'saved'` / `'error'` / `'forbidden'` / `'invalid_nonce'`
* and renders the corresponding `notice notice-success` or
* `notice notice-error` banner. Other values (and `null`)
* suppress the banner.
*
* Escaping invariants:
*
* - Every visible text emission flows through
* {@see esc_html()}.
* - Every attribute value flows through {@see esc_attr()}.
* - The `