audit-data-contracts

To check data contract consistency, compare declared fields in FacturaRecord with corresponding types and nullability in SelectionVM and MainWindowState. This detects ambiguous fields, inconsistent nullability, and duplicated derived data across layers to prevent silent reporting and export bugs.

Report export nullability mismatches occur when dataframe report column types and conversion logic do not match domain expectations, such as improper handling of None values or string-encoded numeric fields. Auditing the export contract verifies alignment between dataframe logic and domain models.

Verify document state integrity by detecting scattered or inconsistent usage of allowed status values like pendiente and clasificado. This process checks whether status values are centralized across the codebase to ensure consistent invoice classification workflows.

The best way to catch type mismatches is performing field-by-field contract auditing that compares each declared field in FacturaRecord with corresponding types in SelectionVM. This enforces reading implementation files and reporting real findings with clear evidence.

Audit data contracts during invoice classification and report export workflows when code mentions models like FacturaRecord or view models like SelectionVM. This catches potential type issues across layers before they cause silent reporting bugs in production.