memorytalk 0.9.0__tar.gz → 0.9.2__tar.gz

{memorytalk-0.9.0 → memorytalk-0.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memorytalk
-Version: 0.9.0
+Version: 0.9.2
 Summary: Persistent cross-session memory for AI agents — Talk-Card architecture with forum-dynamics sinking/floating (v3)
 License-Expression: Apache-2.0
 Requires-Python: >=3.10

{memorytalk-0.9.0 → memorytalk-0.9.2}/memorytalk/cli/setup.py

@@ -447,6 +447,25 @@ def _apply_install(r: HookRow, cfg: Config) -> dict:
     else:
         err_console.print(f"  [dim]·[/dim] assets up to date")
 
+    # Force re-install when our marketplace content changed AND the
+    # plugin is already in the host's cache. Host CLIs(Codex / Claude
+    # Code)copy plugin files into their own cache at ``plugin add``
+    # time and never re-read our marketplace directory afterwards.
+    # ``marketplace upgrade`` only re-pulls if the plugin manifest's
+    # ``version`` field bumped, which we don't reliably do — so to
+    # guarantee the new ``hooks.json`` reaches the host, we
+    # uninstall + reinstall. The cost (re-trust step on Codex) is
+    # unavoidable anyway since the trust hash is tied to hook content.
+    if changed and r.state != HostState.ABSENT:
+        err_console.print(
+            "  [dim]· content changed — forcing reinstall to refresh "
+            "host plugin cache[/dim]"
+        )
+        try:
+            adapter.uninstall()
+        except RuntimeError as e:
+            err_console.print(f"  [yellow]⚠ uninstall before reinstall: {e}[/yellow]")
+
     try:
         adapter.install(r.materialized)
     except RuntimeError as e:

{memorytalk-0.9.0 → memorytalk-0.9.2}/memorytalk/repository/schema.py

@@ -250,20 +250,10 @@ async def _additive_migrations(conn: aiosqlite.Connection) -> None:
     #    separate ``sync.db`` (see ``repository/sync_checkpoint.py``).
     await conn.execute("DROP TABLE IF EXISTS ingest_log")
 
-    # 4. 0.9.0: drop ``recall_log`` (replaced by ``recall_event`` +
-    #    ``recall.jsonl`` file). History is intentionally not migrated
-    #    — the old table never stored prompts, so a faithful
-    #    ``RecallEvent`` row can't be reconstructed. The old table's
-    #    own DDL comment was "in-memory-ish — cleared on rebuild", so
-    #    losing it is the documented contract.
-    await conn.execute("DROP INDEX IF EXISTS idx_recall_log_session")
-    await conn.execute("DROP TABLE IF EXISTS recall_log")
-
-    # 5. 0.9.0: drop ``card_stats.recall_count`` column — popularity is
-    #    now derived from ``recall_event`` on read. SQLite ALTER TABLE
-    #    DROP COLUMN requires 3.35+ (Mar 2021); Python 3.10+ ships well
-    #    above that.
-    async with conn.execute("PRAGMA table_info(card_stats)") as cursor:
-        stats_cols = {row[1] for row in await cursor.fetchall()}
-    if "recall_count" in stats_cols:
-        await conn.execute("ALTER TABLE card_stats DROP COLUMN recall_count")
+    # 0.9.x: NO in-place migration from 0.8.x ``recall_log`` /
+    # ``card_stats.recall_count`` — upgrades require deleting
+    # ``~/.memory.talk`` and starting fresh. The recall subsystem
+    # changed shape too deeply (file canonical, session_id namespace
+    # correction) to make a partial in-place migration meaningful.
+    # New installs hit the fresh DDL above and have no legacy rows
+    # to worry about.

{memorytalk-0.9.0 → memorytalk-0.9.2}/memorytalk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: memorytalk
-Version: 0.9.0
+Version: 0.9.2
 Summary: Persistent cross-session memory for AI agents — Talk-Card architecture with forum-dynamics sinking/floating (v3)
 License-Expression: Apache-2.0
 Requires-Python: >=3.10

{memorytalk-0.9.0 → memorytalk-0.9.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "memorytalk"
-version = "0.9.0"
+version = "0.9.2"
 description = "Persistent cross-session memory for AI agents — Talk-Card architecture with forum-dynamics sinking/floating (v3)"
 readme = "README.md"
 requires-python = ">=3.10"