ms-markets 2.2.6.dev28__tar.gz → 2.2.6.dev30__tar.gz

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/CHANGELOG.md

@@ -7,32 +7,7 @@ and this project follows versioned releases.
 
 ## [Unreleased]
 
-### Fixed
-
-- Repair the portfolio event ledger's TimescaleDB-incompatible non-time unique
-  constraint through forward migration `0019`, preserving applied `0018`, all
-  existing rows, and full-grain uniqueness. Canonical publication, restart, and
-  projections reject duplicate economic record identities across timestamps
-  and event revisions split across times. Exact retries remain idempotent.
-- Align ADR 0042, accounting and migration documentation, the portfolio tutorial,
-  and the offline dividend/FX example with the storage and validation boundary.
-
-### Changed
-
-- Requires `mainsequence-metatable>=0.1.31,<0.2`; the lock and runtime export
-  select 0.1.31, while Main Sequence remains 9.0.19. The shared migration runner
-  batches table inventories and inspections and waits up to 300 seconds for a
-  waking API, addressing the 30-second discovery timeout in the failed Markets
-  deployment ([MetaTables#55](https://github.com/mainsequence-projects/MetaTables/pull/55)).
-  Server-side batching, unchanged-contract write avoidance, and startup
-  improvements also require deployment of the updated shared MetaTables API.
-- The migration Job exposes the shared runner's INFO phase timings, always
-  reconciles the catalog even at head, and propagates failures to block rollout.
-  Provider identity, version-table binding, and applied revisions are unchanged.
-- Refreshed the MetaTables-owned skills and guide snapshots to 0.1.31; aligned
-  migration documentation, release guidance, tutorial, and print-only example.
-
-## [2.2.6] - 2026-10-09
+## [2.2.6] - 2026-10-10
 
 ### Added
 
@@ -50,6 +25,24 @@ and this project follows versioned releases.
 
 ### Changed
 
+- Requires `mainsequence-metatable>=0.1.33,<0.2`; the lock and runtime export
+  select 0.1.33, while Main Sequence remains 9.0.19. The shared migration runner
+  batches table inventories and inspections and waits up to 300 seconds for a
+  waking API, addressing the 30-second discovery timeout in the failed Markets
+  deployment ([MetaTables#55](https://github.com/mainsequence-projects/MetaTables/pull/55)).
+  Server-side batching, unchanged-contract write avoidance, and startup
+  improvements also require deployment of the updated shared MetaTables API.
+- The upgraded migration runner carries changed, non-empty authored table and
+  column metadata through finalization at an unchanged Alembic revision. Empty
+  values preserve existing catalog metadata and equal-valued reruns avoid
+  catalog writes. The matching API update is required for this payload; it also
+  fixes SQLite schema reflection during multi-batch downgrade finalization
+  ([MetaTables#59](https://github.com/mainsequence-projects/MetaTables/pull/59)).
+- The migration Job exposes the shared runner's INFO phase timings, always
+  reconciles the catalog even at head, and propagates failures to block rollout.
+  Provider identity, version-table binding, and applied revisions are unchanged.
+- Refreshed the MetaTables-owned skills and guide snapshots to 0.1.33; aligned
+  migration documentation, release guidance, tutorial, and print-only example.
 - Requires `mainsequence-metatable>=0.1.29,<0.2`; the lock and exported
   `requirements.txt` select 0.1.29. Changes in MetaTables 0.1.29
   ([MetaTables#52](https://github.com/mainsequence-projects/MetaTables/pull/52)):
@@ -116,6 +109,13 @@ and this project follows versioned releases.
 
 ### Fixed
 
+- Repair the portfolio event ledger's TimescaleDB-incompatible non-time unique
+  constraint through forward migration `0019`, preserving applied `0018`, all
+  existing rows, and full-grain uniqueness. Canonical publication, restart, and
+  projections reject duplicate economic record identities across timestamps
+  and event revisions split across times. Exact retries remain idempotent.
+- Align ADR 0042, accounting and migration documentation, the portfolio tutorial,
+  and the offline dividend/FX example with the storage and validation boundary.
 - The Markets API installs the SDK request identity with
   `install_request_identity(app)` in `create_app()`. The platform launcher
   refuses to serve an application that does not install it, and SDK releases

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-markets
-Version: 2.2.6.dev28
+Version: 2.2.6.dev30
 Summary: Financial markets ORM, engines, and application management extensions for Main Sequence.
 Project-URL: Changelog, https://github.com/mainsequence-projects/MainSequenceMarkets/blob/main/CHANGELOG.md
 Project-URL: Source, https://github.com/mainsequence-projects/MainSequenceMarkets
@@ -227,7 +227,7 @@ Requires-Python: <3.14,>=3.13
 Requires-Dist: alembic>=1.18.4
 Requires-Dist: cachetools
 Requires-Dist: fastapi>=0.136.3
-Requires-Dist: mainsequence-metatable<0.2,>=0.1.31
+Requires-Dist: mainsequence-metatable<0.2,>=0.1.33
 Requires-Dist: mainsequence<10,>=9.0.19
 Requires-Dist: numpy
 Requires-Dist: pandas
@@ -385,7 +385,7 @@ Recommended entry points:
 ## Quick Start
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.31,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.33,<0.2`, which is imported
 as `metatables`. SDK 8 and earlier are not supported; install a 1.x
 `ms-markets` release when maintaining an SDK 8 project. See
 [ADR 0043](https://mainsequence-projects.github.io/MainSequenceMarkets/ADR/0043-sdk-9-metatables-client-hard-cut/)
@@ -503,7 +503,7 @@ The core stack starts with:
 
 - `mainsequence>=9.0.19,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.31,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.33,<0.2` (import `metatables`) for MetaTables,
   time-index table updaters, governed compiled SQL, and application-owned
   Alembic migrations
 - `SQLAlchemy` for market-domain ORM models

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/README.md

@@ -108,7 +108,7 @@ Recommended entry points:
 ## Quick Start
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.31,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.33,<0.2`, which is imported
 as `metatables`. SDK 8 and earlier are not supported; install a 1.x
 `ms-markets` release when maintaining an SDK 8 project. See
 [ADR 0043](https://mainsequence-projects.github.io/MainSequenceMarkets/ADR/0043-sdk-9-metatables-client-hard-cut/)
@@ -226,7 +226,7 @@ The core stack starts with:
 
 - `mainsequence>=9.0.19,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.31,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.33,<0.2` (import `metatables`) for MetaTables,
   time-index table updaters, governed compiled SQL, and application-owned
   Alembic migrations
 - `SQLAlchemy` for market-domain ORM models

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/fast_api/v1/index.md

@@ -173,13 +173,14 @@ push alone as deployment success.
 
 Runtime dependencies must be resolvable from the backend build environment.
 The published `ms-markets` 2.x package therefore declares
-`mainsequence>=9.0.19,<10` and `mainsequence-metatable>=0.1.31,<0.2` without
+`mainsequence>=9.0.19,<10` and `mainsequence-metatable>=0.1.33,<0.2` without
 exact patch pins. The lower bounds enforce the SDK 9 and MetaTables client
 extraction hard cut and the SDK request identity that the platform's current
 caller assertions require (SDK 9.0.18 and later), while the project lock and exported runtime requirements
-select the exact releases validated for this repository. MetaTables 0.1.31 also
-provides batched migration inspections and a five-minute migration API discovery
-budget. Do not replace the
+select the exact releases validated for this repository. MetaTables 0.1.33 retains
+batched migration inspections and a five-minute migration API discovery budget,
+and refreshes changed authored metadata at unchanged revisions. Metadata
+finalization requires the corresponding shared MetaTables API update. Do not replace the
 published dependencies with machine-local `[tool.uv.sources]` path overrides.
 
 `create_app()` installs the SDK request identity with

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/getting-started.md

@@ -1,7 +1,7 @@
 # Getting Started
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.19,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.31,<0.2` (imported as
+the MetaTables client `mainsequence-metatable>=0.1.33,<0.2` (imported as
 `metatables`). It cannot run against an SDK 8 or earlier contract and does not
 provide compatibility aliases or a mixed-version mode. Install a 1.x
 `ms-markets` release when maintaining an SDK 8 project.

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/knowledge/msm/migrations/index.md

@@ -70,7 +70,7 @@ previous release keeps serving.
 
 ### Migration diagnostics and repeated runs
 
-The minimum client is MetaTables 0.1.31. `upgrade_application()` automatically
+The minimum client is MetaTables 0.1.33. `upgrade_application()` automatically
 uses fresh table inventories and batched physical inspections; PostgreSQL
 reflection is batched by schema. Finalization requests remain bounded to ten
 tables each, with the version table first. No batching option or project-specific
@@ -93,6 +93,14 @@ finalization failed, inspect the actual schema and per-table errors, then rerun
 the same migration through a new deployment. Do not stamp, rewrite applied
 revisions, or downgrade to recover catalog state.
 
+The runner carries changed, non-empty authored table descriptions, labels, and
+column descriptions, labels, and logical names in each finalization batch. An
+unchanged revision can therefore refresh catalog metadata without new DDL.
+Empty or absent metadata preserves existing values; fresh physical inspection
+still owns types, keys, indexes, and nullability. Equal-valued reruns avoid
+catalog writes. This payload requires the matching MetaTables API update, which
+also corrects SQLite schema reflection for multi-batch downgrades.
+
 Client improvements require an updated application image. API-side batching,
 unchanged-contract write avoidance, and startup optimizations require the shared
 MetaTables API to be deployed with that release too. Update matching guidance

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/knowledge/msm/platform/metatable_migrations.md

@@ -110,7 +110,7 @@ history is the Alembic revision graph plus the provider's version table.
 
 ## Client Requirement
 
-The implementation requires `mainsequence-metatable>=0.1.31,<0.2` with
+The implementation requires `mainsequence-metatable>=0.1.33,<0.2` with
 `mainsequence>=9.0.19,<10`. The client exposes `AlembicMetaTableMigration`,
 `AlembicVersionMetaTable`, application-owned Alembic execution, and the command
 shape where

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/releasing.md

@@ -131,15 +131,18 @@ stable releases.
 
 ### Upgrading the migration client
 
-The project requires `mainsequence-metatable>=0.1.31,<0.2`; `uv.lock` and
-`requirements.txt` select 0.1.31. After changing the dependency, run
+The project requires `mainsequence-metatable>=0.1.33,<0.2`; `uv.lock` and
+`requirements.txt` select 0.1.33. After changing the dependency, run
 `mainsequence code-repository sync --path .`, refresh the MetaTables-owned
 guidance with `metatables copy-metatables-skills --path .`, and run the checks
 above. Keep the provider identity, version table, and applied revisions unchanged.
 
-The candidate image uses the shared `upgrade_application()` runner. Version
-0.1.31 adds batched inspections and a 300-second discovery budget for a waking
-API. The Job enables its INFO phase timings and must run even when Alembic is
+The candidate image uses the shared `upgrade_application()` runner. It retains
+the batched inspections and 300-second discovery budget introduced in 0.1.31.
+The updated runner also sends changed, non-empty authored table and column
+metadata during finalization, even without a new Alembic revision. That payload
+requires the matching MetaTables API; the updated API also fixes SQLite
+multi-batch downgrade finalization. The Job enables INFO phase timings and must run even when Alembic is
 already at head: catalog reconciliation is not optional. The workflow remains
 image → migration Job → API deployment, all from the same candidate image.
 

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/docs/tutorial/index.md

@@ -17,7 +17,7 @@ helpers for time-indexed facts).
 
 ### Prepare the schema before starting runtime code
 
-1. Install the locked dependencies, including MetaTables 0.1.31 or later.
+1. Install the locked dependencies, including MetaTables 0.1.33 or later.
 2. For local ms-markets schema development, verify the local MetaTables runtime
    and use `metatables --local migrations upgrade --provider msm_migrations:migration head`.
    For a hosted environment, the ms-markets deployment's migration Job applies
@@ -28,7 +28,10 @@ helpers for time-indexed facts).
 
 Run `python examples/msm/platform/metatable_migration_lifecycle.py` for a safe,
 print-only walkthrough. The shared runner batches inspections automatically and
-reconciles the catalog even at the current revision. See
+reconciles the catalog even at the current revision. Changed, non-empty authored
+descriptions, labels, and column metadata refresh during finalization without a
+new revision; empty values preserve existing metadata. The shared MetaTables API
+must support that payload too. See
 [Migrations](../knowledge/msm/migrations/index.md) for the workflow and timing logs.
 
 ## Installing MS Markets Agent Skills

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/examples/msm/platform/metatable_migration_lifecycle.py

@@ -18,8 +18,11 @@ def main() -> None:
 
     print("\nHosted: candidate image -> jobs/migrate_markets.py -> API rollout")
     print(f"The Job calls metatables.upgrade_application({PROVIDER!r}) on every deployment.")
-    print("MetaTables >=0.1.31 batches inspections and waits up to 300s for a waking API.")
+    print("MetaTables >=0.1.33 batches inspections and waits up to 300s for a waking API.")
     print("At head, catalog reconciliation still runs; migrated=False is not a skip signal.")
+    print("Changed non-empty authored metadata refreshes without a new Alembic revision.")
+    print("Empty metadata preserves existing values; equal-valued reruns avoid catalog writes.")
+    print("Metadata finalization also requires the matching shared MetaTables API update.")
     print("INFO logs from metatables.migrations.runner report each phase's elapsed time.")
     print("Consumers migrate only their own providers, not the ms-markets provider.")
 

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-markets"
-version = "2.2.6.dev28"
+version = "2.2.6.dev30"
 description = "Financial markets ORM, engines, and application management extensions for Main Sequence."
 readme = "README.md"
 requires-python = ">=3.13,<3.14"
@@ -37,7 +37,7 @@ dependencies = [
   "cachetools",
   "fastapi>=0.136.3",
   "mainsequence>=9.0.19,<10",
-  "mainsequence-metatable>=0.1.31,<0.2",
+  "mainsequence-metatable>=0.1.33,<0.2",
   "numpy",
   "pandas",
   "pip>=26.1.1",

{ms_markets-2.2.6.dev28 → ms_markets-2.2.6.dev30}/tests/msm/test_package_metadata.py

@@ -40,7 +40,9 @@ def test_package_metadata_requires_extracted_metatables_client() -> None:
     requirement = _requirement("mainsequence-metatable")
 
     assert Version("0.1.30") not in requirement.specifier
-    assert Version("0.1.31") in requirement.specifier
+    assert Version("0.1.31") not in requirement.specifier
+    assert Version("0.1.32") not in requirement.specifier
+    assert Version("0.1.33") in requirement.specifier
     assert Version("0.1.99") in requirement.specifier
     assert Version("0.2.0") not in requirement.specifier
     assert all(specifier.operator != "==" for specifier in requirement.specifier)