v1.8.1: Type-conflict findings say which fix they need

SLayer 1.8.1

A small release for applications that act on schema-drift findings.

A type conflict says which fix it needs

When validate_models finds a column whose stored type no longer matches the live database, the finding now carries remedy_kind. It is reingest when re-ingesting the datasource will re-type the column (a live list column on a table-backed model, or an INT column SQLite reports as wider), and set_type when you need to set the column's type yourself, which covers every conflict on an sql-mode model. You can word your own message from this field instead of parsing the remedy text. The remedy and summary texts are unchanged, and the field comes back through REST, MCP and the Python API alike.

Additional technical details

• RetypeFinding.remedy and RetypeFinding.summary are now computed from remedy_kind, so they can never disagree with it.
• RetypeFinding.of(...) takes remedy_kind= in place of reingest: bool.
• A finding serialized by 1.8.0 still loads: its kind is inferred from its remedy text, and a text that matches neither historical form is refused with a validation error.