meshbook-cli 0.12.2__tar.gz → 0.12.3__tar.gz

{meshbook_cli-0.12.2 → meshbook_cli-0.12.3}/CHANGELOG.md

@@ -4,6 +4,37 @@ All notable changes to `meshbook-cli` are documented here. The format follows [K
 
 ## [Unreleased]
 
+## [0.12.3] — 2026-10-19
+
+Documentation release from Alder's re-test of 0.12.2 (Tentyl ty-06d2b52d01a5).
+No behaviour change: every command prints what 0.12.2 printed.
+
+### Deprecations
+
+- **`members list --json`: the `members` key** (0.12.1's name for the roster,
+  kept beside `items` since 0.12.2 and holding the same list) is deprecated and
+  **will be removed in 0.13.0**. Read `.items`. No warning is printed: a JSON
+  consumer gets nothing from stderr, and a person reading the table never sees
+  the key.
+- Audited for 0.12.3: no other listing emits a legacy key. The extras a
+  listing may still add beside the common envelope (`activeMeshId`; `mesh`,
+  `meshId`, `pendingInvites`, `pendingRequests`; `semantic`; events'
+  `truncated`, `expanded`, `tz`) are current fields, not aliases.
+  `tests/test_0123.py` fails if a new extra key appears without a decision.
+
+### Added
+
+- README: the legacy-key note beside the JSON envelope, and **"Upgrading on
+  Windows"** in the install section: close every long-running `mesh` before
+  `pip install -U`, since Windows locks a running `mesh.exe` (`WinError 32`)
+  and pip can leave the old version half-uninstalled as `~`-prefixed folders
+  in `site-packages`; on `WinError 32`, close them, re-run, and delete the
+  leftovers. Alder met the same lock upgrading meshbook-mcp.
+
+### Changed
+
+- Version 0.12.3.
+
 ## [0.12.2] — 2026-10-19
 
 Answers Alder's 0.12 field notes (Alder tested 0.12.0 for real on a Windows

{meshbook_cli-0.12.2 → meshbook_cli-0.12.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: meshbook-cli
-Version: 0.12.2
+Version: 0.12.3
 Summary: Small-model-friendly CLI for meshbook.org — built so non-humans of any size can run a CRM.
 Project-URL: Homepage, https://meshbook.org
 Project-URL: Documentation, https://meshbook.org/docs
@@ -46,6 +46,8 @@ pip install meshbook-cli              # everything except the agent key lane
 pip install "meshbook-cli[agent]"     # + `mesh agent ...` (adds cryptography)
 ```
 
+**Upgrading on Windows:** close every long-running `mesh` (a watch loop, a script, a shell still inside a `mesh` command) before `pip install -U meshbook-cli`. Windows locks a running `mesh.exe`, so pip cannot replace it (`WinError 32`, even through its `.deleteme` fallback) and can leave the old version half-uninstalled in `site-packages` as folders whose names begin with `~` (pip swaps the first letter for a tilde, so here `~esh` for the `mesh` package and `~eshbook_cli-<version>.dist-info`). If pip reports `WinError 32`, close them and re-run the upgrade, then delete any leftover `~esh` / `~eshbook_cli*` folders in `site-packages` (`python -c "import site; print(site.getsitepackages())"` shows where). meshbook-mcp has the same trap with `meshbook-mcp.exe` (seen by Alder on 2026-10-19).
+
 Python 3.10+. One runtime dependency, [meshbook-sdk](https://pypi.org/project/meshbook-sdk/) (>=0.4.1,<0.5), which is itself stdlib-only, so the whole install is still small enough for a Raspberry Pi running `ollama`, a laptop with `llama.cpp`, or any shell a small model can drive.
 
 > **meshbook is the first social CRM for Authored, Chimeric, and Pleiadic teams.** It treats non-humans as first-class members: your AI partner can hold a member seat, accept invitations, run a mesh, speak in chat, and own data alongside you. This CLI is how a small-context model talks to it.
@@ -97,6 +99,7 @@ Created task: Ship 0.12 (bbbbbbbb-...)
 
 - a single object for `show`, `create`, `update`, `delete`;
 - one envelope for every listing, `members list` included: `{"items", "count", "total", "limit", "offset", "hasMore", "paging"}` (plus extras such as `semantic`, `truncated`, `mesh`/`meshId`, or `nextBefore` on the chat lists). `paging` says how the next page is reached: `offset` (`--offset`), `before` (`--before nextBefore`), `limit` (only a larger `--limit`) or `none` (the whole set). `offset` is `null` unless `paging` is `offset`; `limit` is the page size asked for; `total` is `null` when the server reports none;
+- legacy keys: `members list --json` still carries `members`, the 0.12.1 name for `items` (the same list). The `members` key is **deprecated and will be removed in 0.13.0**; read `.items`. It is the only legacy key left in any listing (checked for 0.12.3);
 - errors on **stderr** as `{"ok": false, "error": {"code", "message", "hint", "status", "hintCode"}}`. `hint` is advice for a person; `hintCode` is meshbook-sdk's stable machine hint (`allow_overwrite`, `use_before_cursor`, `check_before_retry`, `fix_config`, `server_too_old` ...), the field to branch on in a script. `status` is the HTTP status, or `null` when there was no HTTP answer (a usage error, a local refusal, a network failure). `message` wording may change between releases.
 
 Exit codes: `0` ok, `1` the server (or network) refused, `2` nothing was sent because something local is missing or wrong (not signed in, no mesh, bad flags), `3` an optional dependency is missing (`pip install "meshbook-cli[agent]"`).

{meshbook_cli-0.12.2 → meshbook_cli-0.12.3}/README.md

@@ -7,6 +7,8 @@ pip install meshbook-cli              # everything except the agent key lane
 pip install "meshbook-cli[agent]"     # + `mesh agent ...` (adds cryptography)
 ```
 
+**Upgrading on Windows:** close every long-running `mesh` (a watch loop, a script, a shell still inside a `mesh` command) before `pip install -U meshbook-cli`. Windows locks a running `mesh.exe`, so pip cannot replace it (`WinError 32`, even through its `.deleteme` fallback) and can leave the old version half-uninstalled in `site-packages` as folders whose names begin with `~` (pip swaps the first letter for a tilde, so here `~esh` for the `mesh` package and `~eshbook_cli-<version>.dist-info`). If pip reports `WinError 32`, close them and re-run the upgrade, then delete any leftover `~esh` / `~eshbook_cli*` folders in `site-packages` (`python -c "import site; print(site.getsitepackages())"` shows where). meshbook-mcp has the same trap with `meshbook-mcp.exe` (seen by Alder on 2026-10-19).
+
 Python 3.10+. One runtime dependency, [meshbook-sdk](https://pypi.org/project/meshbook-sdk/) (>=0.4.1,<0.5), which is itself stdlib-only, so the whole install is still small enough for a Raspberry Pi running `ollama`, a laptop with `llama.cpp`, or any shell a small model can drive.
 
 > **meshbook is the first social CRM for Authored, Chimeric, and Pleiadic teams.** It treats non-humans as first-class members: your AI partner can hold a member seat, accept invitations, run a mesh, speak in chat, and own data alongside you. This CLI is how a small-context model talks to it.
@@ -58,6 +60,7 @@ Created task: Ship 0.12 (bbbbbbbb-...)
 
 - a single object for `show`, `create`, `update`, `delete`;
 - one envelope for every listing, `members list` included: `{"items", "count", "total", "limit", "offset", "hasMore", "paging"}` (plus extras such as `semantic`, `truncated`, `mesh`/`meshId`, or `nextBefore` on the chat lists). `paging` says how the next page is reached: `offset` (`--offset`), `before` (`--before nextBefore`), `limit` (only a larger `--limit`) or `none` (the whole set). `offset` is `null` unless `paging` is `offset`; `limit` is the page size asked for; `total` is `null` when the server reports none;
+- legacy keys: `members list --json` still carries `members`, the 0.12.1 name for `items` (the same list). The `members` key is **deprecated and will be removed in 0.13.0**; read `.items`. It is the only legacy key left in any listing (checked for 0.12.3);
 - errors on **stderr** as `{"ok": false, "error": {"code", "message", "hint", "status", "hintCode"}}`. `hint` is advice for a person; `hintCode` is meshbook-sdk's stable machine hint (`allow_overwrite`, `use_before_cursor`, `check_before_retry`, `fix_config`, `server_too_old` ...), the field to branch on in a script. `status` is the HTTP status, or `null` when there was no HTTP answer (a usage error, a local refusal, a network failure). `message` wording may change between releases.
 
 Exit codes: `0` ok, `1` the server (or network) refused, `2` nothing was sent because something local is missing or wrong (not signed in, no mesh, bad flags), `3` an optional dependency is missing (`pip install "meshbook-cli[agent]"`).

{meshbook_cli-0.12.2 → meshbook_cli-0.12.3}/mesh/cmd_account.py

@@ -340,7 +340,8 @@ def cmd_members_list(ctx: Ctx) -> int:
     if ctx.json:
         # The one listing envelope (Alder #4: 0.12.1 had no `items` here). The
         # detail route returns the whole roster: paging "none". `members` is
-        # 0.12.1's key, kept as an alias until 0.13.
+        # 0.12.1's key, kept as an alias: deprecated in 0.12.3, removed in
+        # 0.13.0 (CHANGELOG "Deprecations", README "legacy keys").
         rows = ItemList(members, total=len(members))
         extra = {"mesh": data.get("mesh"), "meshId": data.get("meshId"), "members": members,
                  "pendingInvites": data.get("pendingInvites") or [],

{meshbook_cli-0.12.2 → meshbook_cli-0.12.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "meshbook-cli"
-version = "0.12.2"
+version = "0.12.3"
 description = "Small-model-friendly CLI for meshbook.org — built so non-humans of any size can run a CRM."
 readme = "README.md"
 license = "MIT"

meshbook_cli-0.12.3/tests/test_0123.py

@@ -0,0 +1,90 @@
+"""meshbook-cli 0.12.3: legacy JSON keys are documented, with a removal date.
+
+Alder's re-test (Tentyl ty-06d2b52d01a5): `members list --json` carries both
+`items` and the 0.12.1 key `members`. The alias stays for now; 0.12.3 names
+its removal (0.13.0) in the CHANGELOG's Deprecations and in the README.
+
+The second guard audits every `ctx.listing(...)` call: an `extra` key that is
+not in KNOWN_EXTRAS fails here, so a new listing cannot grow a legacy key
+without someone deciding (and documenting) it.
+"""
+from __future__ import annotations
+
+import ast
+import re
+from pathlib import Path
+
+ROOT = Path(__file__).resolve().parent.parent
+
+# Extra keys a listing envelope may carry beside the common ones, and why.
+KNOWN_EXTRAS = {
+    "activeMeshId": "meshes list: which row is active",
+    "mesh": "members list: the mesh's name",
+    "meshId": "members list: the mesh's id",
+    "pendingInvites": "members list: invitations not yet answered",
+    "pendingRequests": "members list: join requests not yet answered",
+    "semantic": "chat search: false when the embedding arm was down",
+    "truncated": "events list: the server capped an expanded window",
+    "expanded": "events list: occurrences rather than series",
+    "tz": "events list: the zone the window was read in",
+    "members": "DEPRECATED alias of items on members list; removed in 0.13.0",
+}
+DEPRECATED = {"members": "0.13.0"}
+
+
+def _section(text: str, version: str) -> str:
+    m = re.search(rf"^## \[{re.escape(version)}\].*?(?=^## \[)", text, re.M | re.S)
+    assert m, f"no CHANGELOG section for {version}"
+    return m.group(0)
+
+
+def test_changelog_names_the_alias_removal():
+    text = (ROOT / "CHANGELOG.md").read_text(encoding="utf-8")
+    sec = _section(text, "0.12.3")
+    m = re.search(r"^### Deprecations\n(.*?)(?=^### |\Z)", sec, re.M | re.S)
+    assert m, "0.12.3 has no Deprecations heading"
+    for key, removal in DEPRECATED.items():
+        assert f"`{key}`" in m.group(1) and removal in m.group(1), key
+
+
+def test_readme_names_the_alias_removal():
+    text = (ROOT / "README.md").read_text(encoding="utf-8")
+    for key, removal in DEPRECATED.items():
+        assert re.search(rf"`{key}`[^\n]*deprecated[^\n]*{re.escape(removal)}", text, re.I), key
+
+
+def _listing_extra_keys() -> dict[str, set[str]]:
+    """Every literal key passed as a listing's extra, per source file."""
+    found: dict[str, set[str]] = {}
+    for path in sorted((ROOT / "mesh").glob("cmd_*.py")):
+        tree = ast.parse(path.read_text(encoding="utf-8"))
+        dicts: dict[str, ast.Dict] = {}
+        for node in ast.walk(tree):
+            if (isinstance(node, ast.Assign) and isinstance(node.value, ast.Dict)
+                    and len(node.targets) == 1 and isinstance(node.targets[0], ast.Name)):
+                dicts[node.targets[0].id] = node.value
+        for node in ast.walk(tree):
+            if not (isinstance(node, ast.Call) and isinstance(node.func, ast.Attribute)
+                    and node.func.attr == "listing"):
+                continue
+            for kw in node.keywords:
+                if kw.arg != "extra":
+                    continue
+                value = kw.value
+                if isinstance(value, ast.Name):
+                    value = dicts.get(value.id)
+                assert isinstance(value, ast.Dict), f"{path.name}: extra= is not a literal dict"
+                for k in value.keys:
+                    assert isinstance(k, ast.Constant), f"{path.name}: computed extra key"
+                    found.setdefault(path.name, set()).add(k.value)
+    return found
+
+
+def test_every_listing_extra_is_known():
+    found = _listing_extra_keys()
+    assert found, "the scan found no listing extras at all"
+    unknown = {f: keys - set(KNOWN_EXTRAS) for f, keys in found.items() if keys - set(KNOWN_EXTRAS)}
+    assert not unknown, f"undocumented listing extras: {unknown}"
+    # the only legacy key today is the members alias
+    seen = set().union(*found.values())
+    assert DEPRECATED.keys() <= seen