tabc 0.2.2__tar.gz → 0.2.3__tar.gz

{tabc-0.2.2 → tabc-0.2.3}/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog
 
+## 0.2.3 — 2026-10-17
+
+### Added
+
+- The CLI accepts the exact name of an open tac, compared after case folding,
+  wherever it takes a tac:
+  `tac show`, `add`, `rm`, `rename` (the target, not the new name), `close`,
+  `link` (child and parent), `search --tac`, and `send --tac`. It prints
+  `tac <name> = <uuid>` on stderr and runs with that UUID.
+- A closed tac, a missing name, or names that only resemble the input run
+  nothing. The CLI lists the candidates with UUID and `open` or `closed` date,
+  prints `code TAC_NAME_UNRESOLVED`, and exits 2. A partial name is never
+  chosen.
+- A read-only, signed server endpoint, `GET /tac_lookup?name=`, returns the
+  exact match and up to 20 similar names within the same scope as `/tacs`.
+
+### Unchanged
+
+- `tac create` does not look up its name.
+- A canonical lowercase UUID is used as given, without a lookup. Any other
+  string is looked up as a name first. Only when no tac has that exact name is
+  another spelling of a UUID (upper case, braces, 32 hex digits, `urn:uuid:`)
+  sent as that identifier.
+- Every other server endpoint and the MCP adapter take only the UUID. An older
+  `tabd` without the lookup endpoint receives the typed value unchanged,
+  including another UUID spelling, and answers `TAC_ID_INVALID` as before.
+- The ledger schema, registration, the notifier, and the MCP adapter are
+  unchanged.
+
+### Upgrade notes (from 0.2.2)
+
+- Nodes, signing keys, messages, delivery states, TACs, routes, and Codex
+  queue receipts are kept. No conversion and no re-registration are needed.
+- Stop `tabus.doorbell`, install 0.2.3, restart `tabd`, then start one
+  `tabus.doorbell` from the same installation:
+
+```bash
+python -m pip install --upgrade "tabc==0.2.3"
+# Or, for desktop MCP support:
+python -m pip install --upgrade "tabc[mcp]==0.2.3"
+```
+
+- Name lookup needs the restarted `tabd`. Before the restart it answers 404 for
+  `/tac_lookup`, the CLI sends the typed name, and the server answers
+  `TAC_ID_INVALID`. UUIDs work either way.
+- A running `tabc-mcp` process does not need a restart for this change.
+- After restart, `tabc --version` and `tabd --version` report 0.2.3.
+
 ## 0.2.2 — 2026-10-17
 
 ### Changed

{tabc-0.2.2 → tabc-0.2.3}/GUIDE.md

@@ -269,12 +269,19 @@ tabd returns a stable `code`, a plain `message`, structured `details`, and a
 | `REQUEST_TIMEOUT` | the declared request body did not arrive within 30 seconds |
 | `REQUEST_INCOMPLETE` | the connection ended before the declared body length arrived |
 | `UNREAD_BLOCKED` | read-before-send is blocking this DM or TAC send |
-| `TAC_ID_INVALID` | a TAC operation requires a canonical lowercase UUID |
+| `TAC_ID_INVALID` | a TAC operation requires a canonical lowercase UUID; the server does not resolve names |
 | `TAC_NOT_FOUND` | no TAC matches the supplied identifier |
 | `TAC_NAME_TAKEN` | the folded name or a reserved legacy identifier is already used |
 | `TAC_NAME_INVALID` | the TAC name violates the name rules |
 | `TAC_NOT_CONVERTED` | a partially converted ledger still contains string TAC IDs |
 
+From 0.2.3, the CLI adds one code of its own before the requested TAC operation is sent.
+`TAC_NAME_UNRESOLVED` means the TAC name was not exactly one open tac: it is
+closed, missing, or only similar names exist. Nothing was done. The CLI lists the
+candidates with UUID and state on stderr and exits 2. Use a listed UUID, or check
+the name with `tabc tac ls`. The lookup accepts names of 1 to 200 characters. A
+longer value fails the lookup, runs nothing, and exits 1; use the UUID instead.
+
 `retry=never` means change the request. `retry=after_condition` means satisfy the
 reported condition first. `retry=as_is` means the same request may be tried again,
 but a write that lost its response must first be checked by message ID. A timeout,
@@ -295,7 +302,7 @@ The same visible text can therefore use different byte counts in NFC and NFD.
 | dm | a message addressed to named recipients (`send --to`) |
 | tac | a named topic. Members receive everything posted to it |
 | tac name | a unique display and search name. It can change |
-| tac id | a canonical UUID minted by the server. It addresses the tac and does not change when the name changes |
+| tac id | a canonical UUID minted by the server. It addresses the tac and does not change when the name changes. From 0.2.3 the CLI also resolves an exact open tac name to it |
 | program | a send-only node. It claims no terminal and is refused as a recipient |
 
 ---

{tabc-0.2.2 → tabc-0.2.3}/MCP.md

@@ -114,7 +114,8 @@ titles without that wait, including messages claimed by an earlier call. Use
 
 Use the CLI to create TACs and manage membership. Use the `tac_id` returned by
 `tabc_tacs`, not its display name. A TAC name can be renamed; its canonical UUID
-does not change. TAC history inspection does not change delivery state. Before
+does not change. The CLI resolves an exact open tac name from 0.2.3; the MCP
+adapter does not. TAC history inspection does not change delivery state. Before
 sending, open and acknowledge the relevant pending deliveries using the inbox
 tools. tabd enforces the same read-before-send rules as it does for the CLI.
 

{tabc-0.2.2/tabc.egg-info → tabc-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.2
+Version: 0.2.3
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -105,6 +105,25 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
+## Updating from 0.2.2
+
+The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
+TACs, routes, and Codex queue receipts are kept, and nodes do not register
+again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
+`tabus.doorbell` from the same installation:
+
+```bash
+python -m pip install --upgrade "tabc==0.2.3"
+# Or, when the local desktop MCP adapter is required:
+python -m pip install --upgrade "tabc[mcp]==0.2.3"
+```
+
+The CLI now accepts the exact name of an open tac and lists candidates instead
+of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
+is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
+unchanged. See the
+[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
+
 ## Updating from 0.2.1
 
 The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
@@ -161,7 +180,7 @@ python -m pip install --upgrade "tabc[mcp]==0.2.0"
 Existing string TAC IDs are not converted during installation. Follow the
 repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
 to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
+Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
 
 ## Commands
 
@@ -175,6 +194,9 @@ Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 Register each recipient before sending. tac creators must also join their topic.
 Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
 sending, reading, renaming and closing; use the unique name for display and search.
+From 0.2.3, the CLI also accepts the exact name of an open tac and prints the UUID
+it used. A closed, missing or only similar name runs nothing and lists candidates
+with `TAC_NAME_UNRESOLVED`. The MCP adapter still takes only the UUID.
 Run `tabc --help` for available commands. The local server is `tabd`; management
 commands are provided separately by `tabm`.
 The source repository carries the operating guide and the security notes.

{tabc-0.2.2 → tabc-0.2.3}/PYPI.md

@@ -63,6 +63,25 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
+## Updating from 0.2.2
+
+The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
+TACs, routes, and Codex queue receipts are kept, and nodes do not register
+again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
+`tabus.doorbell` from the same installation:
+
+```bash
+python -m pip install --upgrade "tabc==0.2.3"
+# Or, when the local desktop MCP adapter is required:
+python -m pip install --upgrade "tabc[mcp]==0.2.3"
+```
+
+The CLI now accepts the exact name of an open tac and lists candidates instead
+of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
+is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
+unchanged. See the
+[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
+
 ## Updating from 0.2.1
 
 The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
@@ -119,7 +138,7 @@ python -m pip install --upgrade "tabc[mcp]==0.2.0"
 Existing string TAC IDs are not converted during installation. Follow the
 repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
 to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
+Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
 
 ## Commands
 
@@ -133,6 +152,9 @@ Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 Register each recipient before sending. tac creators must also join their topic.
 Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
 sending, reading, renaming and closing; use the unique name for display and search.
+From 0.2.3, the CLI also accepts the exact name of an open tac and prints the UUID
+it used. A closed, missing or only similar name runs nothing and lists candidates
+with `TAC_NAME_UNRESOLVED`. The MCP adapter still takes only the UUID.
 Run `tabc --help` for available commands. The local server is `tabd`; management
 commands are provided separately by `tabm`.
 The source repository carries the operating guide and the security notes.

{tabc-0.2.2 → tabc-0.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tabc"
-version = "0.2.2"
+version = "0.2.3"
 description = "A shared inbox for AI agents and programs on one machine"
 readme = "PYPI.md"
 requires-python = ">=3.9"

{tabc-0.2.2 → tabc-0.2.3/tabc.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: tabc
-Version: 0.2.2
+Version: 0.2.3
 Summary: A shared inbox for AI agents and programs on one machine
 License: MIT License
         
@@ -105,6 +105,25 @@ from the `pull --mode full` detail block, or a unique prefix of it.
 Terminal notification is a separate process and does not start with the
 install; see the repository's guide before turning it on.
 
+## Updating from 0.2.2
+
+The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
+TACs, routes, and Codex queue receipts are kept, and nodes do not register
+again. Stop `tabus.doorbell`, install, restart `tabd`, then start one
+`tabus.doorbell` from the same installation:
+
+```bash
+python -m pip install --upgrade "tabc==0.2.3"
+# Or, when the local desktop MCP adapter is required:
+python -m pip install --upgrade "tabc[mcp]==0.2.3"
+```
+
+The CLI now accepts the exact name of an open tac and lists candidates instead
+of guessing. Name lookup needs the restarted `tabd`; before that, a typed name
+is refused with `TAC_ID_INVALID` and UUIDs still work. The MCP adapter is
+unchanged. See the
+[changelog](https://github.com/jultabc/tabc/blob/main/CHANGELOG.md).
+
 ## Updating from 0.2.1
 
 The ledger schema is unchanged. Nodes, signing keys, messages, delivery states,
@@ -161,7 +180,7 @@ python -m pip install --upgrade "tabc[mcp]==0.2.0"
 Existing string TAC IDs are not converted during installation. Follow the
 repository README's 0.2.0 ledger conversion procedure when converting TAC IDs
 to UUIDs. Without conversion, restart `tabd` first, then `tabus.doorbell`.
-Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
+Then follow "Updating from 0.2.0", "Updating from 0.2.1" and "Updating from 0.2.2".
 
 ## Commands
 
@@ -175,6 +194,9 @@ Then follow "Updating from 0.2.0" and "Updating from 0.2.1".
 Register each recipient before sending. tac creators must also join their topic.
 Since 0.2.0, the server mints a UUID for each new tac. Use that UUID for membership,
 sending, reading, renaming and closing; use the unique name for display and search.
+From 0.2.3, the CLI also accepts the exact name of an open tac and prints the UUID
+it used. A closed, missing or only similar name runs nothing and lists candidates
+with `TAC_NAME_UNRESOLVED`. The MCP adapter still takes only the UUID.
 Run `tabc --help` for available commands. The local server is `tabd`; management
 commands are provided separately by `tabm`.
 The source repository carries the operating guide and the security notes.

{tabc-0.2.2 → tabc-0.2.3}/tabc.egg-info/SOURCES.txt

@@ -30,6 +30,7 @@ tabus/route_capture.py
 tabus/send_refusal.py
 tabus/sent.py
 tabus/tac_identity.py
+tabus/tac_lookup.py
 tabus/tac_migration.py
 tabus/tac_refusal.py
 tabus/tac_search.py

{tabc-0.2.2 → tabc-0.2.3}/tabus/bus.py

@@ -74,7 +74,7 @@ DB_PATH = os.environ.get(
 #    drifted once already — 0.1.0.post1 shipped while this said 0.1.0. Bump
 #    both together; tests/test_version_agreement.py fails the build otherwise.
 #    Do not copy the number into documentation.
-__version__ = "0.2.2"
+__version__ = "0.2.3"
 PROTOCOL_VERSION = "tabus.v1"
 
 # TTLs. Past these, a derived status counts as old.

{tabc-0.2.2 → tabc-0.2.3}/tabus/cli.py

@@ -94,6 +94,7 @@ MAPPING = {
     "tac_link": "/tac_link",
     "tac_rename": "/tac_rename",
     "tac_check": "/tac_check",
+    "tac_lookup": "/tac_lookup",
     # name uses only the register endpoint; setting the session title is local
 }
 
@@ -440,6 +441,8 @@ def fn_send(a):
     if a.body_file:
         body = open(a.body_file, encoding="utf-8").read()
     group = getattr(a, "tac", None)
+    if group:
+        group = _designate_tac(group, a.sender)
     bcast = getattr(a, "broadcast", False)
     requested = _recipients(a.to)
     # 🔴 Recipients come from --to, --tac, or --broadcast. With none of the three
@@ -806,6 +809,64 @@ def fn_restore(a):
         sys.exit(1)
 
 
+def _tac_state(row):
+    closed = row.get("closed_at")
+    return f"closed {closed[:10]}" if closed else "open"
+
+
+def _designate_tac(given, node):
+    """A tac argument → the identifier to send. A name is looked up here, in the client.
+
+    🔴 The server still takes only the identifier. A name is turned into one before the
+    request, and the identifier used is printed on stderr, so a later rename cannot
+    make the record ambiguous. Only an exact name of an open tac is used. A closed tac,
+    or no exact match, prints the candidates with identifier and open/closed and
+    exits 2 without doing anything. A partial name is never chosen for the caller.
+    """
+    from .tac_identity import is_uuid_id
+
+    if not isinstance(given, str) or not given.strip() or is_uuid_id(given):
+        return given
+    try:
+        # Another UUID spelling (uppercase, braces, 32 hex digits) of an identifier.
+        spelled = str(uuid.UUID(given.strip()))
+    except ValueError:
+        spelled = None
+    from urllib.parse import urlencode
+
+    # 🔴 The name is asked first, even for a string uuid.UUID can read: a tac may be
+    #    named "0123456789abcdef0123456789abcdef", and that name must not turn into
+    #    some other tac's identifier (jack 4c84df2c). Only with no tac of that exact
+    #    name is the string read as an identifier spelling.
+    code, r = call("GET", MAPPING["tac_lookup"] + "?" + urlencode({"name": given}), node=node)
+    if code == 404:
+        # 🔴 A server before this lookup existed: send the string as typed, and the
+        #    server answers TAC_ID_INVALID as it always did.
+        return given
+    if code != 200 or r.get("error"):
+        print(f"failed: tac lookup: {r.get('error') or r}", file=sys.stderr)
+        sys.exit(1)
+    exact, similar = r.get("exact"), r.get("similar") or []
+    if exact is None and spelled is not None:
+        return spelled
+    if exact and not exact.get("closed_at"):
+        print(f"tac {exact['name']} = {exact['tac_id']}", file=sys.stderr)
+        return exact["tac_id"]
+    rows = ([exact] if exact else []) + similar
+    if exact:
+        print(f"tac {exact['name']} is closed; nothing was done. Use its identifier to read it:",
+              file=sys.stderr)
+    elif rows:
+        print(f"no tac is named {given!r}; nothing was done. Similar names:", file=sys.stderr)
+    else:
+        print(f"no tac is named {given!r}; nothing was done (list them with: tabc tac ls)",
+              file=sys.stderr)
+    for row in rows:
+        print(f"  {row['name']:<24} {row['tac_id']}  {_tac_state(row)}", file=sys.stderr)
+    print("  code TAC_NAME_UNRESOLVED", file=sys.stderr)
+    sys.exit(2)
+
+
 def fn_tac(a):
     """tac — a named topic for group delivery.
 
@@ -818,6 +879,12 @@ def fn_tac(a):
     from another, which covers direction, forks, and merges.
     """
     action = a.action
+    # 🔴 Every subcommand that takes an existing tac accepts a name here and sends the
+    #    identifier. create takes a new name and is not looked up.
+    if action in ("show", "add", "rm", "rename", "close", "link") or (action == "search" and a.tac):
+        a.tac = _designate_tac(a.tac, a.node)
+        if action == "link":
+            a.member = _designate_tac(a.member, a.node)
     if action == "search":
         from urllib.parse import urlencode
 
@@ -1135,7 +1202,7 @@ COMMANDS = {
                 ("--tac",),
                 dict(
                     default=None,
-                    help="send to a tac, fanning out to every member (instead of --to)",
+                    help="send to a tac, by identifier or exact name, fanning out to every member (instead of --to)",
                 ),
             ),
             (
@@ -1235,8 +1302,9 @@ COMMANDS = {
                     "close <tac> --summary | link <child> <parent>",
                 ),
             ),
-            (("tac",), dict(nargs="?", help="the tac, by its identifier (not needed for ls); "
-                                            "find it with ls or search; for link this is the child")),
+            (("tac",), dict(nargs="?", help="the tac, by its identifier or its exact name (not needed for ls); "
+                                            "a name is looked up and the identifier used is printed; "
+                                            "for create this is the new name; for link this is the child")),
             (("member",), dict(nargs="?", help="node for add and rm; for link this is the parent; "
                                                "for rename this is the new name")),
             (("--description",), dict(default=None, help="what the tac is for, for create")),

{tabc-0.2.2 → tabc-0.2.3}/tabus/daemon.py

@@ -498,6 +498,27 @@ class BusHandler(BaseHTTPRequestHandler):
                 con.close()
             return self._json(200, {"hits": hits})
 
+        if path == "/tac_lookup":
+            # 🔴 Read-only: which tac carries this name now. Same scope as /tacs. The
+            #    client sends the identifier this returns; every other endpoint still
+            #    takes only the identifier.
+            if not self._authorized():
+                return self._json(401, {"error": "token"})
+            from urllib.parse import parse_qs
+            from .tac_lookup import lookup
+
+            params = parse_qs(query, keep_blank_values=True)
+            if any(len(values) != 1 for values in params.values()):
+                return self._json(400, {"error": "duplicate query parameters"})
+            con = self._connect()
+            try:
+                exact, similar = lookup(con, params.get("name", [None])[0])
+            except (ValueError, TypeError) as exc:
+                return self._json(400, {"error": str(exc)})
+            finally:
+                con.close()
+            return self._json(200, {"exact": exact, "similar": similar})
+
         if path == "/tac_messages":
             # 🔴 tac contents, read-only, and member-only: a tac is a conversation you
             #    read by joining it, so only its members see the body. A non-member is

tabc-0.2.3/tabus/tac_lookup.py

@@ -0,0 +1,42 @@
+"""Find a tac by name, read-only. The client turns a typed name into an identifier here.
+
+🔴 Designation stays by identifier. This endpoint does not make a name a designation:
+every other endpoint still refuses a name with TAC_ID_INVALID. It answers one question,
+"which tac carries this name now", so the client can print the identifier it is about
+to use and then send that identifier. A rename moves the name; the identifier the
+client printed is what the request used.
+
+Names are unique on the folded key (ux_tacs_name_key), closed tacs included, so an
+exact match is at most one row. `similar` lists the rows whose folded name contains
+the folded query, for a caller who typed part of a name. Neither changes state.
+"""
+
+from .tac_identity import name_key
+
+SIMILAR_LIMIT = 20
+
+
+def _row(r):
+    return {"tac_id": r["tac_id"], "name": r["name"], "label": r["label"],
+            "closed_at": r["closed_at"]}
+
+
+def lookup(con, name, limit=SIMILAR_LIMIT):
+    """(exact row or None, similar rows). Raises ValueError on a bad query."""
+    if not isinstance(name, str) or not name.strip() or len(name) > 200:
+        raise ValueError("name must contain 1..200 characters")
+    columns = {row[1] for row in con.execute("PRAGMA table_info(tacs)")}
+    # 🔴 A ledger before the identity migration has no name column. There is nothing
+    #    to look up there: the identifier is the string a caller types.
+    if not {"name", "name_key"} <= columns:
+        return None, []
+    key = name_key(name.strip())
+    rows = con.execute(
+        "SELECT tac_id, name, label, closed_at, name_key FROM tacs ORDER BY name"
+    ).fetchall()
+    exact = next((r for r in rows if r["name_key"] == key), None)
+    # 🔴 Compared on name_key in Python, as tac_store.search_name does: sqlite lower()
+    #    folds ASCII only.
+    similar = [r for r in rows if r["name_key"] and key in r["name_key"]
+               and (exact is None or r["tac_id"] != exact["tac_id"])][:limit]
+    return (_row(exact) if exact else None), [_row(r) for r in similar]