Every chat, one verdict.

1. 21 Oct 2026 · e3c3be7
   The door now sends the share flag with a status he posts, so others can pass it on, and never with a message to a person. The bridge ignores the flag until it is upgraded.
2. 24 Sept 2026 · 8eaf26e
   The lane now keeps deletions, including the words someone took back, and round video notes. A file that has gone missing gets one more try before it is called gone.
3. 8 Sept 2026 · a2221c8
   The send door came home to the Worker that already captures. Every send now writes its own record, and a send that is not recorded fails loudly instead of quietly.
4. 7 Sept 2026 · bcdc8d5
   A short-lived read-only list of file fingerprints was served so an old store could be compared exactly. It served nothing else, and was closed again the same day.
5. 7 Sept 2026 · a97a03a
   A claim in a comment, that large files could not be checked on the free plan, turned out to be a guess. It was measured, withdrawn, and the 8 MB limit stayed.
6. 7 Sept 2026 · 875fa12
   A note in the Worker’s settings said it ran on a paid plan. It runs on the free one, and the note now says what that costs the media lane.
7. 6 Sept 2026 · 40c4af4
   The first build of the WhatsApp capture Worker, beside the older ones and with nothing changed at the bridge. It saves the raw message, writes the record, and returns an error so the bridge tries again when anything did not land.

This history is from the commits that touched the WhatsApp lane’s skill folder in his private plugin repository and the capture Worker’s folder in his private bob repository, read through the GitHub API on 28 Oct 2026: 24 commits, from 6 September to 21 October 2026. Dates are Israel time. Every change in that history is shown except 17, left out to keep other people’s names, clients and money off this page, judged on the full commit message. Some entries are left out (17), because they touched things that are not for this page.

Starts when

The skill loads, when he asks about WhatsApp, and its check runs once, right then. The Worker runs whenever the bridge posts an event, and by itself every fifteen minutes.

Checks

Whether the send route can still find his phone, whether each WhatsApp lane has beaten within its own declared allowance, how many messages have no author yet, and how many pictures, voice notes and files have no reading.

Produces

One line per conversation of the last five days, up to eight, unread media first: “awaiting you”, “unread media”, “you spoke last”, or “ruled” when he has set it aside. On the Worker side: the raw message, one row for it, and the media bytes.

If it breaks

The check never fails the skill. It prints DOWN with the reason rather than nothing, and a lane that has never beaten says so. The Worker returns an error when something it meant to keep did not land, so the bridge sends it again.

Sends

Nothing. A reply needs his yes, then runs through the one sender, which checks the recipient three times. If a send went out but was not recorded, the rule is to recover the record and never to send again.

Tested

The Worker has two small self-checks, for the status receipts and for group names, and the status one was shown to fail on a planted fault. The check script and the skill have no test of their own. They were corrected by use.

Code

A skill in his private plugin and a Worker in his private repository. Neither is published, so the commit hashes above are for him to check.

Read from the lane’s code on 28 October 2026. No keys, addresses, ids or passwords are shown, by rule.