Build Dynamic Field Renderer Widget

Implement as a switch/factory pattern: a top-level DynamicFieldRenderer widget switches on FieldConfig.type and returns the appropriate sub-widget. Each sub-widget should be its own class for testability — avoid a monolithic switch inside one build method. Use BlocSelector where FieldRenderData = (currentValue, errorMessage) to make each field subscribe only to its own slice of state. This is critical for performance with large forms.

For the DatePicker, use intl package for locale-aware formatting. For the SpeechToTextFieldOverlay, the trigger icon should be placed inside the InputDecoration suffixIcon of text-based fields — this keeps the touch target within the field boundary and looks native. OrgFieldConfigLoader should be injected via Riverpod provider, not passed as constructor argument, to avoid prop drilling through deep widget trees.

Widget tests for each field type variant using flutter_test. For each type: (1) renders correctly with a null value; (2) renders correctly with a valid value; (3) user interaction dispatches FieldChanged with correct fieldId and new value; (4) validationErrors[field.id] set → error text is visible; (5) validationErrors[field.id] null → error text is absent; (6) field with visible=false is not present in widget tree (use findsNothing). Integration test: render a full schema with all 8 field types and assert no exceptions, no overflow, and all fields present. Golden tests for each field type in error state and normal state.

Verify BlocSelector granularity: changing field A does not rebuild field B's widget (use debugPrintRebuildDirtyWidgets in test).