Release v15.33.7
Fixed
- SQL read model instances query failing with `42703: column does not exist` when two read models share the same container name across namespaces and the existing table was created by a different read model with a different column set.
Summary
`ReadModelMigrator.EnsureTableMigrated` previously only created the table when it did not exist; it never verified that existing table columns matched the expected schema. After the fix, every `EnsureTableMigrated` call also runs `EnsureMissingColumnsAdded`, which queries the real column names from the database and issues `ALTER TABLE ADD COLUMN` for any columns present in the schema but absent in the table. Results are cached by connection-string + table + column-set so the extra DB roundtrip is paid at most once per unique schema per process.