Repository navigation
release: 1.3.3 — the card anchor falls back to last_message_id; system notices start no kit cycle; manual 2.3.4 fixtures - #25
Merged
Conversation
…e contract (manual 2.3.4)
…ontract v1 section 4) A message.new whose message has type "system" (a member joined or left, a rename, a group deleted) no longer wakes the ReceiveLoop: no tray read, no gate call, no run. The socket still acks it (delivered). A real message in the same burst still wakes. Each notice emits a "notice" event and counts in status().counters["notices"].
…erdict docs for the server's migration 104 The card property returned None for a card with no preview (since 104, every card whose only unread messages are system notices), unlike gate.anchor_of and the TypeScript gate.anchorOf. It now gives the same anchor. Tests: a notices-only card and a preview whose sender is not last_sender parse; a verdict whose anchor is not a message of the conversation surfaces as NotFoundError (MESSAGE_NOT_FOUND), one attempt, sync and async, for reply, dismiss and defer.
…ray docs, manual 2.3.4 fixtures (Unreleased)
…; the founder set the number)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Patch release 1.3.3, the number you confirmed on 2026-11-12. It catches the Python SDK up with the server's migration 104, which is live, and matches TS 1.3.2.
Fixed:
InboxCard.anchor_message_idfalls back tolast_message_id(types/inbox.py:132).Nonewhenever the card had no preview. Since 104, that's every card with only notices. A verdict anchored with it then went out with no anchor and read through "now", including messages the gate never saw.last_message_id, elseNone. That's the same answer asgate.anchor_ofand TSgate.anchorOf.message.newwhose message hastype: "system"(a member joined or left, a rename, a group deleted) is still acked on receipt. It starts no cycle, gate call or run (contract v1 §4).noticeevent andcounters["notices"](integration/receive_loop.py:902).Docs and types:
MESSAGE_NOT_FOUND. It already raisedNotFoundError; tests now pin that, sync and async, for reply, dismiss and defer.Conformance:
texts.sample.jsonandmanifest.sha256are copied byte-identical from the contract (manual 2.3.4), and they match agentchat.me.Tested locally: ruff and mypy are clean (41 files), and pytest passes 792 with 2 skipped on 3.9, 3.10, 3.11, 3.12 and 3.13. The new notice and anchor tests fail without the fix.
After merge: tag
v1.3.3; you approve the PyPI publish. Then OpenClaw (on TS 1.3.2) and Hermes (floor 1.3.3).