matrx-orm 3.1.185__tar.gz → 3.1.186__tar.gz

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: matrx-orm
-Version: 3.1.185
+Version: 3.1.186
 Summary: Async-first PostgreSQL ORM with bidirectional migrations, schema introspection, many-to-many relationships, and built-in state caching
 Project-URL: Homepage, https://github.com/AI-Matrix-Engine/aidream-current
 Project-URL: Repository, https://github.com/AI-Matrix-Engine/aidream-current

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/matrx_orm/core/types.py

@@ -228,6 +228,15 @@ class UpdateResult:
     rows_affected: int
     updated_rows: list[dict[str, Any]]
 
+    def __bool__(self) -> bool:
+        """True only when the UPDATE changed a row.
+
+        A dataclass without this is ALWAYS truthy, so ``if await q.update(...):``
+        read as "it changed something" even at zero rows — the runtime reaper
+        soft-deleted a stream's frames on that false yes (found 2026-09-26).
+        """
+        return self.rows_affected > 0
+
     def to_dict(self) -> dict[str, Any]:
         """Serialise to the legacy dict shape for JSON / API boundaries."""
         return {

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/matrx_orm/secrets_battery/FEATURE.md

@@ -33,22 +33,20 @@ charset-validated here — `provider_key`, `display_name`, `tags`, `status`,
 alias (nullable). A DB trigger (`trg_user_secrets_owner_match`) rejects any field
 row whose owner columns don't match its item's owner.
 
-**History foundation (capture disabled).** Migration 1034 adds a nonnegative,
-server-managed `history_revision` item counter, but the ORM does not map it until
-the history migrations are installed on every target: mapping it early makes
-ordinary item creation fail with a missing-column error. No battery mutation
-currently writes history. Migrations 1035 and 1036 keep the private
-`vault_history_writer` personal-only and enforce the closed v1 envelope: exact
-keys, typed identifiers and timestamp, locked original ownership, and empty
-component arrays. Organization-owned history refuses until the host supplies the
-grant/offboarding parent-lock contract. Future aggregate capture may use the
-revision-1/revision-2 bootstrap only after its producer, authority, retention,
-rotation, and reader gates are independently accepted. Gate B's source-only
-1047 validator freezes one personal, active ordinary password field shape: its
-first recorded update is an A=A bootstrap followed by A→B, and later records
-are one prior-after-matched delta each. Application capture is explicitly off
-until every producer and reader gate is accepted; 1047 is never applied outside
-the named runner's reviewed rehearsal.
+**Personal-password history.** The installed history counter is mapped and the
+ordinary personal-password capture gate is on. Battery mutations record the
+closed v1 chain under the private writer: revision 1 is an A=A bootstrap and
+later revisions are prior-after-matched deltas. Migrations 1035 and 1036 keep the private
+`vault_history_writer` personal-only and establish the closed v1 envelope.
+Installed migration 1047 requires exact keys, typed identifiers and timestamp,
+locked original ownership, and exactly one manifest and one changed component
+bound to the locked active personal password field. Organization-owned history refuses until the host supplies the
+grant/offboarding parent-lock contract. Capture, list/reveal, and restore are
+backend capabilities for this bounded personal-password chain. Migration 1166
+is reviewed and enabled in source; installed behavior requires the migration
+ledger and exact live validator bodies. The physical history timestamp remains
+the destination audit time, while authenticated backup source dates are retained
+separately when the installed contract supports them.
 
 Items may also own N encrypted **file attachments**
 (`users.credential_attachments`). An attachment has its own stable id,
@@ -391,9 +389,11 @@ delete).
   replacement, matching the host bulk reader's revocation order. A focused
   ordering test fails if deletion moves ahead of the parent lock.
 
-- **2026-09-24** — Migration 1036 closes the personal-only Vault revision envelope and refuses organization history pending the canonical grant/offboarding parent lock; capture remains disabled.
-
-- **2026-09-24** — Kept the history counter out of the ORM until migrations are installed; the branch database lacks the column and a premature model mapping broke ordinary Vault creation. Capture remains disabled.
+- **2026-09-26** — The personal-password capture gate is on. The battery maps
+  the installed history counter and maintains the bounded A=A then A→B chain;
+  organization history remains refused pending the canonical grant/offboarding
+  parent lock. Guarded migration 1166 does not yet provide backup source-date
+  fidelity.
 
 - **2026-09-19** — Restored native lifecycle metadata with the parsed, timezone-aware manifest instant at the typed mutation boundary, preserving the manifest string for aggregate integrity checks.
 

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/matrx_orm/secrets_battery/items.py

@@ -90,9 +90,9 @@ ITEM_SOURCES: tuple[str, ...] = (
     "system_import",
 )
 
-# Gate B is source-complete only.  Turning this on would make history appear
-# complete while sibling producers and readers still omit revisions.
-_PASSWORD_HISTORY_CAPTURE_ENABLED = False
+# Eligible personal password writes capture their prior value and the new
+# value atomically. Organization history remains outside this boundary.
+_PASSWORD_HISTORY_CAPTURE_ENABLED = True
 
 
 class CredentialItemNotFoundError(LookupError):
@@ -1296,9 +1296,8 @@ def _captures_personal_password_history(
 ) -> bool:
     """Return whether this locked row belongs in the private password history.
 
-    The module-local gate remains deliberately false in production. Keeping
-    eligibility here gives every existing-field ciphertext writer the same
-    future activation boundary without adding a caller-controlled switch.
+    The module-local gate keeps every existing-field ciphertext writer behind
+    the same eligibility boundary without adding a caller-controlled switch.
     """
     return (
         _PASSWORD_HISTORY_CAPTURE_ENABLED

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "matrx-orm"
-version = "3.1.185"
+version = "3.1.186"
 description = "Async-first PostgreSQL ORM with bidirectional migrations, schema introspection, many-to-many relationships, and built-in state caching"
 readme = "README.md"
 license = { text = "MIT" }

{matrx_orm-3.1.185 → matrx_orm-3.1.186}/tests/test_secrets_battery.py

@@ -1324,17 +1324,17 @@ async def test_second_history_write_failure_propagates_from_atomic_transaction(m
     assert updates  # The real transaction owns this statement and rolls it back on the propagated failure.
 
 
-def test_password_history_capture_is_off_and_not_a_public_writer_option():
+def test_password_history_capture_is_on_and_not_a_public_writer_option():
     from matrx_orm.secrets_battery import items
 
-    assert items._PASSWORD_HISTORY_CAPTURE_ENABLED is False
+    assert items._PASSWORD_HISTORY_CAPTURE_ENABLED is True
     for writer in (items.update_credential_field_value, items.rotate_credential_fields):
         assert "capture" not in inspect.signature(writer).parameters
 
 
 @pytest.mark.asyncio
 async def test_enabled_history_capture_chains_two_writers_and_rolls_back(monkeypatch):
-    """The private switch is test-only: a failed append restores field and chain."""
+    """An active capture writer propagates append failure so the transaction rolls back."""
     from matrx_orm.secrets_battery import items
 
     monkeypatch.setenv("CREDENTIALS_ENCRYPTION_KEY", _fernet_key())

matrx_orm-3.1.186/tests/test_update_result_truthiness.py

@@ -0,0 +1,6 @@
+from matrx_orm.core.types import UpdateResult
+
+
+def test_an_update_that_changed_nothing_is_falsy() -> None:
+    assert not UpdateResult(rows_affected=0, updated_rows=[])
+    assert UpdateResult(rows_affected=2, updated_rows=[{}, {}])