Skip to content

docs: correct captureFreshness.asOfMs semantics (ADR-0020 rev 2) #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Deniffer001 merged 1 commit into from
Nov 3, 2026
Merged

docs: correct captureFreshness.asOfMs semantics (ADR-0020 rev 2) #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions packages/wbot/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,9 @@ All notable changes to the public wbot client are documented in this file.

- Poll incrementally with `messages.updates` and the saved cursor, or use webhooks. Do not loop over
`conversations.list`; `messages.history` is for looking back, not polling.
- `captureFreshness.asOfMs` is now rounded to the minute by the Platform; do not rely on
sub-minute precision.
- `captureFreshness.status` is authoritative; `asOfMs` is a lower bound on the last successful
scan (exact at status changes, otherwise refreshed at most every 10 minutes). Do not derive
freshness from `asOfMs` yourself.

## 0.2.5 - 2026-11-02

Expand Down
6 changes: 4 additions & 2 deletions packages/wbot/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,10 @@ Polling guidance:
them, then follow each conversation's updates cursor.
- `messages.history` is for looking back at older context, not for polling.

`captureFreshness.asOfMs` is rounded to the minute so read results stay cacheable; do not compare
it at sub-minute precision.
`captureFreshness` is maintained by the Platform so read results stay cacheable: `status` is
authoritative, and `asOfMs` is a lower bound on the last successful capture scan. It is exact when
the status changes and otherwise refreshed at most every 10 minutes, so do not compute freshness
yourself from `asOfMs`.

## Send a JPEG image from the CLI

Expand Down
Loading