v1.8.0: Ossie export, model filters apply everywhere

SLayer 1.8.0

This release adds Ossie (OSI) export and makes model filters apply wherever a model is read.

Export to Ossie

slayer export-osi --datasource shop --out shop.osi.yaml (or export_osi(...) in Python) writes your models as an Ossie document and reports anything Ossie can't express. Re-importing an unedited export restores your models exactly; --no-extensions writes plain Ossie. See Exporting to OSI.

Model filters apply everywhere

A model's filters used to apply only when a query started from that model, so a query reaching it through a join could return wrong rows. They now apply wherever the model is read. Filters that name a measure or a windowed column, or that form a cycle across models, are refused when you save the model.

Other changes

• MCP tools now report database failures as tool errors (isError: true).
• Usage reports add per-session MCP query counts and your first successful query date, so you'll see the notice once more.
• Cancelling or timing out a SQL call now returns at once (also in 1.6.1).