ms-markets 2.2.3.dev12__tar.gz → 2.2.3.dev13__tar.gz

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/CHANGELOG.md

@@ -7,18 +7,31 @@ and this project follows versioned releases.
 
 ## [Unreleased]
 
+## [2.2.3] - 2026-10-03
+
 ### Added
 
 - The portfolio, portfolio-group and asset-category bulk-delete preflights
   report what the delete reaches through foreign keys. They return the
-  MetaTables `delete_rows` impact as `impact`, describe each cascade,
-  `SET NULL` or `SET DEFAULT` action in `warnings`, and add MetaTables'
-  blockers (for example a cascade into a table the caller cannot write), which
-  also stop the bulk delete with `409`. If MetaTables cannot compute the
+  MetaTables `delete_rows` impact as `impact` and describe each cascade,
+  `SET NULL` or `SET DEFAULT` action in `warnings`. MetaTables' blockers (the
+  caller cannot write the table, the table does not accept writes, or its
+  DataSource is read-only) are added to `blockers` and also stop the bulk
+  delete with `409`; cascades never block. If MetaTables cannot compute the
   impact, a warning says so and the delete is not blocked.
   `BulkDeletePreflightResponse` and the `TableImpact` models are exported from
   `msm.api.http`, and `delete_rows_impact` from `msm.services`.
 
+### Changed
+
+- Requires `mainsequence-metatable>=0.1.18,<0.2`; the lock and exported
+  `requirements.txt` select `mainsequence-metatable` 0.1.18. MetaTables 0.1.18
+  removes the cascade write narrowing released in 0.1.17: write on a table
+  depends only on its own grants, so a foreign key on a referencing table no
+  longer locks the referenced table's Writers out. Its impact pre-flight
+  reports cascades as information, never as blockers.
+- Refreshed the MetaTables agent skills to 0.1.18.
+
 ## [2.2.2] - 2026-10-03
 
 ### Changed

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ms-markets
-Version: 2.2.3.dev12
+Version: 2.2.3.dev13
 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.17
+Requires-Dist: mainsequence-metatable<0.2,>=0.1.18
 Requires-Dist: mainsequence<10,>=9.0.5
 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.5,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.17,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.18,<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.5,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.17,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.18,<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.3.dev12 → ms_markets-2.2.3.dev13}/README.md

@@ -108,7 +108,7 @@ Recommended entry points:
 ## Quick Start
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.5,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.17,<0.2`, which is imported
+the MetaTables client `mainsequence-metatable>=0.1.18,<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.5,<10` for identity, login, Git source context,
   CodeRepository, jobs, and agents
-- `mainsequence-metatable>=0.1.17,<0.2` (import `metatables`) for MetaTables,
+- `mainsequence-metatable>=0.1.18,<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.3.dev12 → ms_markets-2.2.3.dev13}/docs/fast_api/v1/command_center_bulk_actions.md

@@ -51,17 +51,19 @@ table reaches through foreign keys. It asks MetaTables
 (`MetaTable.get_impact(action="delete_rows")`) and adds:
 
 - `impact`: the MetaTables impact graph. Nodes are the tables the delete
-  reaches, with their effects and the caller's effective write. Edges are
-  classified as `cascade_delete`, `cascade_update`, `set_null`, `set_default`,
-  `restrict` or `reads`. MetaTables' blockers are included.
+  reaches, with their effects and whether the caller may write each one. Edges
+  are classified as `cascade_delete`, `cascade_update`, `set_null`,
+  `set_default`, `restrict` or `reads`. MetaTables' blockers are included.
 - `warnings`: one sentence for each foreign-key action the delete triggers, for
   example "PortfolioGroupMembership rows that reference deleted PortfolioGroup
   rows are deleted too (ON DELETE CASCADE)." Command Center shows warnings
   without custom rendering.
-- `blockers`: MetaTables' reasons the caller may not run the delete, such as a
-  cascade into a table the caller cannot write, prefixed with that table. The
-  preflight then answers `allowed: false` and execution answers `409` before
-  the database refuses the delete.
+- `blockers`: MetaTables' reasons the caller may not run the delete, prefixed
+  with the table: the caller cannot write the table, the table does not accept
+  writes, or its DataSource is read-only. The preflight then answers
+  `allowed: false` and execution answers `409` before the database refuses the
+  delete. Cascades never block: write on a table depends only on its own grants,
+  because a foreign key's action belongs to the referencing table.
 
 Deleting portfolios or portfolio groups cascades to their
 `PortfolioGroupMembership` rows; deleting asset categories cascades to their
@@ -69,6 +71,12 @@ Deleting portfolios or portfolio groups cascades to their
 `impact` is `null` and a warning says so. The preflight is not blocked, because
 the database still applies and enforces every foreign-key action.
 
+On the local SQLite runtime, MetaTables documents one limitation: its authorizer
+also checks the reads and writes of foreign-key actions, so a delete that
+cascades fails unless the caller can access every referencing table. The
+preflight cannot detect this. PostgreSQL runs these actions as the referencing
+table's owner.
+
 Execution repeats preflight immediately before invoking domain deletion. A
 blocked selection returns HTTP `409` and does not call the delete service. The
 underlying delete operation still performs its own conflict checks, protecting

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/docs/fast_api/v1/index.md

@@ -164,7 +164,7 @@ 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.5,<10` and `mainsequence-metatable>=0.1.17,<0.2` without
+`mainsequence>=9.0.5,<10` and `mainsequence-metatable>=0.1.18,<0.2` without
 exact patch pins. The lower bounds enforce the SDK 9 and MetaTables client
 extraction hard cut, while the project lock and exported runtime requirements
 select the exact releases validated for this repository. Do not replace the

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/docs/getting-started.md

@@ -1,7 +1,7 @@
 # Getting Started
 
 `ms-markets` 2.x requires Python 3.13, Main Sequence SDK `>=9.0.5,<10`, and
-the MetaTables client `mainsequence-metatable>=0.1.17,<0.2` (imported as
+the MetaTables client `mainsequence-metatable>=0.1.18,<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.3.dev12 → ms_markets-2.2.3.dev13}/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.17,<0.2` with
+The implementation requires `mainsequence-metatable>=0.1.18,<0.2` with
 `mainsequence>=9.0.5,<10`. The client exposes `AlembicMetaTableMigration`,
 `AlembicVersionMetaTable`, application-owned Alembic execution, and the command
 shape where

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "ms-markets"
-version = "2.2.3.dev12"
+version = "2.2.3.dev13"
 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.5,<10",
-  "mainsequence-metatable>=0.1.17,<0.2",
+  "mainsequence-metatable>=0.1.18,<0.2",
   "numpy",
   "pandas",
   "pip>=26.1.1",

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/src/msm/api/http/bulk_actions.py

@@ -142,9 +142,9 @@ class BulkDeletePreflightResponse(BulkActionPreflightResponse):
         default=None,
         description=(
             "MetaTables delete_rows impact for the table the selected rows are deleted "
-            "from: the tables its foreign-key actions reach, the effect on each and the "
-            "caller's effective write. Each cascade is also summarized in warnings. "
-            "Null when nothing matched or MetaTables could not compute it."
+            "from: the tables its foreign-key actions reach, the effect on each and "
+            "whether the caller may write each table. Each cascade is also summarized "
+            "in warnings. Null when MetaTables could not compute it."
         ),
     )
 

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/src/msm/api/http/table_impact.py

@@ -30,7 +30,7 @@ class TableImpactNode(_TableImpactModel):
     )
     can_write: bool | None = Field(
         default=None,
-        description="The caller's effective write after cascade narrowing; null for updates.",
+        description="Whether the caller may write this table; null for updates.",
     )
 
 

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/tests/msm/fastapi/v1/test_bulk_actions.py

@@ -365,8 +365,8 @@ def test_portfolio_group_preflight_reports_cascades(monkeypatch) -> None:
     }
 
 
-def test_cascade_blockers_stop_bulk_delete(monkeypatch) -> None:
-    blocker = "PortfolioGroupMembership: A cascade reaches a table you cannot write."
+def test_impact_blockers_stop_bulk_delete(monkeypatch) -> None:
+    blocker = "PortfolioGroup: You cannot write this table."
     _stub_portfolio_group_preflight(monkeypatch, DeleteRowsImpact(impact=None, blockers=[blocker]))
 
     def unexpected_delete(*args, **kwargs):

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/tests/msm/services/test_table_impact.py

@@ -143,17 +143,13 @@ def test_set_null_updates_and_hidden_tables_are_described() -> None:
                 "on_update": "no action",
             },
         ],
+        # Cascades never block; only the table itself and its DataSource do.
         "blockers": [
             {"code": "data_source_read_only", "message": "The DataSource does not accept writes."},
             {
-                "code": "cascade_target_unregistered",
-                "message": "A foreign-key action modifies a table MetaTables does not manage.",
-                "node": "relation:public.legacy_notes",
-            },
-            {
-                "code": "cascade_target_not_writable",
-                "message": "A cascade reaches a table you cannot write.",
-                "node": "hidden:1",
+                "code": "table_not_writable",
+                "message": "You cannot write this table.",
+                "node": INDEX,
             },
         ],
     }
@@ -171,8 +167,7 @@ def test_set_null_updates_and_hidden_tables_are_described() -> None:
     ]
     assert result.blockers == [
         "The DataSource does not accept writes.",
-        "public.legacy_notes: A foreign-key action modifies a table MetaTables does not manage.",
-        "A table you cannot view: A cascade reaches a table you cannot write.",
+        "Index: You cannot write this table.",
     ]
 
 

{ms_markets-2.2.3.dev12 → ms_markets-2.2.3.dev13}/tests/msm/test_package_metadata.py

@@ -38,8 +38,8 @@ def test_package_metadata_enforces_sdk_9_floor_without_exact_patch_pin() -> None
 def test_package_metadata_requires_extracted_metatables_client() -> None:
     requirement = _requirement("mainsequence-metatable")
 
-    assert Version("0.1.16") not in requirement.specifier
-    assert Version("0.1.17") in requirement.specifier
+    assert Version("0.1.17") not in requirement.specifier
+    assert Version("0.1.18") 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)