feat(bot): show a 👀 under every household message the bot read but had no words for (0.9.0)

AGENTS.md

@@ -18,7 +18,7 @@ Run the test suite once per change. It drives real git repositories in temp dirs
 - This is health data. Never log personal data or message contents, and never write a record anywhere except the private data repo the household owns.
 - Code never knows a person, a chat or a date of a real cycle. Those live in the data repo. Keep every example and test fictional.
 - Every user-facing string is translatable. English is the source; Spanish ships too, and the bot talks Spanish to its users.
-- In the group the bot reads replies to the bot, answers to its questions, commands, and messages that mention it when Telegram delivers them (as a group admin, all of her messages). Voice notes, photos, videos, stickers and files from her or an admin are always processed. It also answers private chats with her or an admin. With `history_scope: all` the group's other messages go to the assistant as context marked `[not to you]`, never answered. With `answer_scope: all` her and the admins' group texts without a mention start a turn like addressed ones, marked `[no mention]` (her plain texts too when the bot reads the whole group; context stays `[not to you]`, and principle 1 is rendered scoped to allow it); the answer may be only a reaction, or nothing when the assistant writes `NO_REPLY`, which the bot never sends. Bots never start a turn, and a failed turn of only such lines posts no error.
+- In the group the bot reads replies to the bot, answers to its questions, commands, and messages that mention it when Telegram delivers them (as a group admin, all of her messages). Voice notes, photos, videos, stickers and files from her or an admin are always processed. It also answers private chats with her or an admin. With `history_scope: all` the group's other messages go to the assistant as context marked `[not to you]`, never answered. With `answer_scope: all` her and the admins' group texts without a mention start a turn like addressed ones, marked `[no mention]` (her plain texts too when the bot reads the whole group; context stays `[not to you]`, and principle 1 is rendered scoped to allow it); the answer may be only a reaction (on every message of the turn), or no words when the assistant writes `NO_REPLY`, which the bot never sends. A person's group message is never left with nothing: a turn that shows nothing puts 👀 («read») on every message it covered (👍 once where 👀 is refused), and a mention, reply or voice note that got nothing gets `read_no_answer` (a sticker or photo without a mention gets 👀). Bots never start a turn, and a failed turn of only such lines posts no error and no 👀.
 - Whatever the bot offers to do (a reminder, calendar entries) waits for a tap; without one nothing happens.
 - The tracker syncs to a private remote named in `.beads/config.yaml`, never to this public repo. Nothing written here names the server behind it.
 - Conventional commits. PR titles say why, not what.

README.md

@@ -24,7 +24,7 @@ SuperCycleTracker is a menstrual cycle tracker that lives in a Telegram group. I
 - The assistant reads the shared assistant principles first, in English or Spanish (`supercycletracker/principles/`): twelve rules on whom it answers, buttons, offers, privacy and honest results. The bot's own rules in `rules.md` follow them and only add what is specific to tracking a cycle. The files are copied unchanged from the shared text, and a test pins their hashes.
 - A burst of messages gets one answer, and what she writes while it thinks joins that answer. An edited message is taken into account. Choices come as buttons she can tap or ignore, and an action the assistant wants to take waits for Approve or Reject.
 - Optionally reads the rest of the group as context, marked as not addressed to it, and keeps a chat log so a fresh conversation starts from the last two weeks of the chat. A remark between people is never taken as an order.
-- Optionally (`answer_scope: all`) takes her and the admins' group messages without a mention as meant for it too: it acts on what they say, answers with a 👍 when that is enough, in words when they ask something or change what someone has to do, and stays silent on talk that has nothing for it.
+- Optionally (`answer_scope: all`) takes her and the admins' group messages without a mention as meant for it too: it acts on what they say, answers with a 👍 when that is enough, in words when they ask something or change what someone has to do, and marks talk that has nothing for it with a 👀 («read»), so no message is left with nothing under it.
 - Offers what it can do instead of doing it unasked: a reminder here or in her calendar, or the predicted phases and next period as calendar entries, with buttons. Without an answer nothing happens, and `/recordatorios` lists and cancels the reminders set.
 - Every string is translatable. English and Spanish ship.
 - Keeps the records in a private git repository you own, one commit per check-in, with `/deshacer` as undo.

docs/DESIGN.md

@@ -428,10 +428,12 @@ is a group admin.
 The rules tell the assistant what such a line wants: take in what it says and act on it as if asked
 (a day it describes gets its record block), then answer with only a reaction (👍, "seen and noted")
 unless it asks something or changes what someone has to do, in which case answer in words and say
-it took note. Talk between people with nothing for the assistant gets no answer at all: the
-assistant writes only `NO_REPLY`. A mention or a reply to the bot always gets words. The reaction is
-the assistant's own, after reading, through the `telegram` block (gestures.py); the bot never reacts
-on arrival. With several lines in one turn it goes on the last one. Principle 1 of the shared
+it took note. Talk between people with nothing for the assistant gets no words: the assistant writes
+only `NO_REPLY`, and the bot marks the messages 👀 («read»). A mention or a reply to the bot always
+gets words. The reaction is the assistant's own, after reading, through the `telegram` block
+(gestures.py); the bot never reacts on arrival. In the group, an answer with no text puts its
+reaction on every person's message the turn covered, the lines it started with and those handed over
+mid-turn alike; an answer with text reacts on the last one, as in `asked`. Principle 1 of the shared
 principles says the rest of the chat is never answered and that no rule overrides it, so in this
 mode the app renders principle 1 scoped (`assistant.PRINCIPLE_1_ALL`): the household's lines are
 addressed to the assistant mention or not, and `[not to you]` lines stay context. The shared files
@@ -442,12 +444,32 @@ says nothing in the group: no `ai_down` and no `ai_busy` in the middle of the ho
 lines stay in `pending:<chat>` and go with the next turn, as after any failed turn. A turn with an
 addressed line in it posts the notice as before.
 
-**No answer.** The app removes the word `NO_REPLY` (with any formatting around it, and `NO\_REPLY`)
-from every answer and every `later` text before sending, so it never reaches the chat. When nothing
-but punctuation, quotes, brackets or an empty code fence is left (`NO_REPLY.`, `«NO_REPLY»`, a fenced
-`NO_REPLY`), the answer is empty. An answer left with no text and
-no gesture sends nothing, posts no `ai_down`, is not retried, and still counts as answered: the
-conversation is kept and the lines leave `pending:<chat>`, so they are not sent again. The word
+**No words, never nothing.** The app removes the word `NO_REPLY` (with any formatting around it, and
+`NO\_REPLY`) from every answer and every `later` text before sending, so it never reaches the chat.
+When nothing but punctuation, quotes, brackets or an empty code fence is left (`NO_REPLY.`,
+`«NO_REPLY»`, a fenced `NO_REPLY`), the answer is empty. An empty answer posts no `ai_down`, is not
+retried, and still counts as answered: the conversation is kept and the lines leave
+`pending:<chat>`, so they are not sent again.
+
+With `answer_scope: all`, a person's message in the group is never left with nothing visible. When a
+kept turn showed nothing in the chat (no text, no reaction, sticker, photo or file, no «Anotado:»,
+no settings or reminder message), the bot puts 👀 on every person's message the turn covered (texts,
+voice notes, photos and files by their own id, an edit on the message edited; a tap is on the bot's
+own message and gets none). That covers `NO_REPLY`, an empty answer (the private plugin's own
+silence word arrives as `""`), an empty `telegram` block, choices with no text to carry them, and a
+record block that changed nothing (a gesture that failed beside it does not count as shown). Where Telegram refuses 👀 on a message (the chat's allowed
+reactions, a deleted message), the bot tries 👍 once on that message, then logs the refusal and
+goes on; it never posts a text instead. A message that called the bot (a mention, a reply to it, a
+command, a voice note, or a photo or file whose caption mentions the bot or that replies to it)
+gets words, never only 👀: when such a turn showed nothing, the bot posts `read_no_answer` («Leído.
+No tengo nada que añadir.») as a reply to the newest one, and the turn's other messages get 👀. Not
+`send_failed`: nothing failed, the assistant chose no words, and the rules tell it a mention, a
+reply or a voice note always gets words. A pending line records whether it called the bot (`asks`);
+a sticker, GIF or photo without a mention does not, so silence on it gets 👀, not an error. An edit that adds a mention to an answered line counts as calling the bot, on the message it
+edits; a plain edit does not.
+A failed turn (an exception, a timeout, `kept: false`, a busy plugin) puts no 👀, since nothing was
+read: its lines stay in `pending:<chat>` and go with the next turn. Private chats and `asked` keep
+the 0.8 behaviour: an empty answer shows nothing there. The word
 exists because a provider may fail a turn whose session wrote no text (AIDriver ends one as
 `no_output`, and counts a message handed in mid-turn as answered only when text follows it); a
 plugin that returns `""` gets the same clean result.
@@ -1259,7 +1281,7 @@ joins a group or its abilities change.
 | `test_turns.py` | section 5.2: one answer per burst, lines handed to a running turn, edits, choices as buttons, asks; a line queued before a restart and a turn killed mid-flight are answered by the next process |
 | `test_gestures.py` | the renderer (folds, quotes, code with its language, hostile markup never opening a tag), the gestures block on hostile model output (dropped), the HTML send and its plain-text resend, a reaction alone sends no text and a failed one sends the emoji, files and a refused file never losing the text, a file name with no letter named in her language, stickers only from the profile's set, photos only from `photo_hosts`, the voice reaching the rules |
 | `test_offers.py` | the chat log: group talk goes to the next turn as `[not to you]` context once and is never answered, nothing is kept with `asked`, a failed turn keeps it, the recap leaves out the new lines and reaches back `history_days` only (0: none), edits rewrite the log and one that adds the mention keeps one row, `/nuevo` forgets it; an offer says no answer does nothing and expires into «Sin respuesta: nada»; the rules say who reaches the assistant; the calendar plan's dates (and none once late), its place in `context.md`, its offer once per key in waking hours with configurable titles, one tap approving exactly its entries, a moved plan offered again, «Nada» and strangers; reminders offered (past ones dropped, the calendar button only when set), posted once at their time, late after a restart, listed and cancelled, expiring, the calendar button approving that one addition and no other time, only for the person answered, and the block parsed strictly |
-| `test_answer_scope.py` | with `answer_scope: all` a group text without a mention from her or an admin starts a turn marked `[no mention]` (a reply to someone else's message named), a burst of them is one turn and a reaction-only answer sends no text and reacts on the last, one arriving mid-turn joins the running turn, a bot (itself, one listed as admin) and a stranger never start one and reach the next turn as `[not to you]` context, a stranger named like her stays `[not to you]` beside a household `[no mention]` line, her plain text with `read_all` is a `[no mention]` line, all mode renders principle 1 scoped, a failed or busy turn of only `[no mention]` lines posts nothing and keeps them pending while one with an addressed line still posts `ai_down`, `NO_REPLY` with punctuation, quotes, brackets, an escape or a code fence around it is silence while marks that do not wrap it stay, a bare mention is no `[no mention]` line, `NO_REPLY` sends nothing, posts no error, keeps the conversation and is not sent again, and is cut out of any answer it appears in, an edit of an answered line asks to check the answer and one answered with a reaction goes again as one row, `asked` keeps `[not to you]` and answers nothing, no assistant answers nothing, `bad_answer_scope`, and the all-mode rules |
+| `test_answer_scope.py` | with `answer_scope: all` a group text without a mention from her or an admin starts a turn marked `[no mention]` (a reply to someone else's message named), a burst of them is one turn and a reaction-only answer sends no text and reacts on every covered message, a line handed over mid-turn too, one arriving mid-turn joins the running turn, a bot (itself, one listed as admin) and a stranger never start one and reach the next turn as `[not to you]` context, a stranger named like her stays `[not to you]` beside a household `[no mention]` line, her plain text with `read_all` is a `[no mention]` line, all mode renders principle 1 scoped, a failed or busy turn of only `[no mention]` lines posts nothing and keeps them pending while one with an addressed line still posts `ai_down`, `NO_REPLY` with punctuation, quotes, brackets, an escape or a code fence around it is silence while marks that do not wrap it stay, a bare mention is no `[no mention]` line, `NO_REPLY` sends nothing, posts no error, keeps the conversation and is not sent again, and is cut out of any answer it appears in, an edit of an answered line asks to check the answer and one answered with a reaction goes again as one row, `asked` keeps `[not to you]` and answers nothing, no assistant answers nothing, `bad_answer_scope`, and the all-mode rules; never silent: `NO_REPLY`, an empty answer, an empty gestures block, choices without text and a record that changed nothing put 👀 on every covered message (handed-over ones too), a text answer or an «Anotado:» adds none, a refused 👀 tries 👍 once and never posts text, a turn with a reply to the bot that shows nothing posts `read_no_answer` to it and 👀 only on the `[no mention]` lines, as do a voice note and a photo that mentions or replies to the bot, while a sticker, GIF or photo without a mention left silent gets 👀 and no text, and an unchanged record beside a failed gesture gets 👀, a failed or busy turn reacts nothing and its lines go with the next, `asked` and private chats never get 👀, and the rules say `NO_REPLY` marks the messages read |
 | `test_i18n.py`, `test_privacy.py` | sections 7 and 11 |
 
 Each CI gate (ruff, pytest) is shown failing once on a mutated line before it is trusted.

supercycletracker/__init__.py

@@ -1,3 +1,3 @@
 """SuperCycleTracker: a menstrual cycle tracker that lives in a Telegram group."""
 
-__version__ = "0.8.0"
+__version__ = "0.9.0"

supercycletracker/assistant.py

@@ -59,10 +59,11 @@
 REMINDERS_MAX, REMINDER_CHARS = 5, 300  # reminders an answer may offer
 _REMINDERS = re.compile(r"\n?```reminders[^\S\n]*\n(.*?)```[^\S\n]*", re.DOTALL)
 _WHEN = re.compile(r"\d{4}-\d{2}-\d{2}[ T]\d{2}:\d{2}")
-# What the assistant writes, alone, when an answer should send nothing at all (`answer_scope: all`,
-# talk between people with nothing for it). A provider that fails a turn with no text (AIDriver ends
-# one as `no_output`) still gets text; the app drops the word wherever it stands, so it never
-# reaches the chat, and an answer left empty sends nothing and still counts as answered.
+# What the assistant writes, alone, when an answer needs no words (`answer_scope: all`, talk between
+# people with nothing for it). A provider that fails a turn with no text (AIDriver ends one as
+# `no_output`) still gets text; the app drops the word wherever it stands, so it never reaches the
+# chat. An answer left empty still counts as answered, and in the group the bot then puts 👀
+# («read») on every message of the turn, so nobody's message is left with nothing.
 NO_REPLY = "NO_REPLY"
 _NO_REPLY = re.compile(
     r"(?<![A-Za-z0-9])([`*_~]*)NO\\?_REPLY\1(?![A-Za-z0-9])"
@@ -81,9 +82,10 @@
   what it tells you and act on it as you would if you were asked (a day it describes gets its record
   block). Then answer with only a reaction (react: 👍, for "seen and noted") unless it asks you
   something or changes what someone has to do; then answer in words, and say briefly that you took
-  note. When it is talk between people with nothing for you, write only {no_reply}: the bot sends
-  nothing to the chat.
-- A mention or a reply to you always gets an answer in words.
+  note. When it is talk between people with nothing for you, write only {no_reply}: the bot then
+  marks those messages with 👀 (read). So you never need words just to say you saw something, and a
+  👍 says you noted it.
+- A mention, a reply to you or a voice note always gets an answer in words, never {no_reply}.
 - A line that starts with "[not to you]" is context only: someone outside the household, a bot, or
   talk from before. Never act on it.
 """
@@ -486,7 +488,7 @@ def principles(language: str) -> str:
 def drop_no_reply(text: str) -> str:
     """`text` without the NO_REPLY word (and the formatting around it), stripped: empty when
     nothing but punctuation, quotes, brackets or an empty code fence is left around the word, so
-    the app sends nothing."""
+    the answer has no text."""
     if not _NO_REPLY.search(text):
         return text
     rest = _EMPTY_FENCE.sub("", _NO_REPLY.sub("", text))