README: what is now demonstrated on production replaces a stale not-yet line (#67)

OP OpenVibers committed 29 days ago · 4b501d53fb · 1 file, +7 −2

**README: what is now demonstrated on production replaces a stale "Not yet demonstrated" line (2026-10-15).**

The README said something had not been shown on production that has been, and was checked today:
- **Sources:** 32 sources are enabled across seven categories after their terms were read, and News, Reviews, Deals, Trade, Coupons and Host consume their items (counts from production's databases).
- **Watch:** a feed watch on openvibe.work's `/jobs.atom`, made from Work's Get alerts link, was checked by the deployed Watch (HTTP 200, one observation, condition met, notification fired) and then deleted.
- **Reviews:** 19 review sources are enabled and 1,187 signals have arrived through the deployed Events subscription. A real `reviews.summarize_entity` run is still not demonstrated, because entities wait on an editor.
- **Actor:** the approval inbox and Watch triggers are built. Chat and Frame access are still to come.

Docs only.

Changes

ddiff --git a/README.md b/README.md
iindex a90959a..f1d4f8b 100644
---- a/README.md
++++ b/README.md
@@@ -484,8 +484,13 @@ Called elsewhere, as the service principal `watch` (client credentials from Open
    every page and form, pause/resume/delete/check-now against a stub site (with the API's 409s and
    422), cross-site writes refused, and hostile names and values escaped on every page
  
--Not yet demonstrated: a check against a real site from a deployed service (nothing is deployed
--yet), the Run rung (step 6), which answers `watch.carrier_unavailable` and fetches nothing
++Demonstrated on production (2026-10-15): a check against a real site from the deployed service.
++- A feed watch on openvibe.work's `/jobs.atom` was made from Work's Get alerts link and submitted through the
++  prefilled form.
++- One check answered HTTP 200 with one observation; the condition was met and the notification fired.
++- The proof watch was deleted.
++
++Not yet demonstrated: the Run rung (step 6), which answers `watch.carrier_unavailable` and fetches nothing
  today (node sources are covered by `test/node-carrier.test.js` against a stand-in Bot) — and the action kinds beyond notifications. Event sources are covered end to end by
  `test/event-sources.test.js` (matching, visibility, once per event, the budget, the signed route and the subscription
  sync against a stand-in Events), and webhook sources by `test/webhook-sources.test.js` (the secret shown once, both

diff --git a/README.md b/README.md

index a90959a..f1d4f8b 100644

--- a/README.md

+++ b/README.md

@@ -484,8 +484,13 @@ Called elsewhere, as the service principal `watch` (client credentials from Open

every page and form, pause/resume/delete/check-now against a stub site (with the API's 409s and

422), cross-site writes refused, and hostile names and values escaped on every page

-Not yet demonstrated: a check against a real site from a deployed service (nothing is deployed

-yet), the Run rung (step 6), which answers `watch.carrier_unavailable` and fetches nothing

+Demonstrated on production (2026-10-15): a check against a real site from the deployed service.

+- A feed watch on openvibe.work's `/jobs.atom` was made from Work's Get alerts link and submitted through the

+ prefilled form.

+- One check answered HTTP 200 with one observation; the condition was met and the notification fired.

+- The proof watch was deleted.

+Not yet demonstrated: the Run rung (step 6), which answers `watch.carrier_unavailable` and fetches nothing

today (node sources are covered by `test/node-carrier.test.js` against a stand-in Bot) — and the action kinds beyond notifications. Event sources are covered end to end by

`test/event-sources.test.js` (matching, visibility, once per event, the budget, the signed route and the subscription

sync against a stand-in Events), and webhook sources by `test/webhook-sources.test.js` (the secret shown once, both