README/STATUS: OpenCoins have been credited in production since 2026-10-14 (both still said they were off) (#68)

ddiff --git a/README.md b/README.md
iindex a85ef7e..c0c7e32 100644
---- a/README.md
++++ b/README.md
@@@ -2,8 +2,9 @@
  
  > Quests across the whole network.
  
--**Status:** first release. The quest log, the events consumer, the OpenCoins crediting and the pages are written and
--tested; it is deployed, and OpenCoins are off until the feature is turned on.
++**Status:** first release. The quest log, the events consumer, the OpenCoins crediting, the item rewards and the pages
++are written and tested; it is deployed, and OpenCoins have been credited in production since 2026-10-14
++(`QUEST_COINS=on`, within the daily caps).
  **Domain:** `openvibe.quest` · **Port:** 4980 · **Service id:** `quest` · **Env prefix:** `QUEST`
  **License:** AGPL-3.0 (same as every OpenVibe service).
  
ddiff --git a/STATUS.json b/STATUS.json
iindex 522fd8a..58db327 100644
---- a/STATUS.json
++++ b/STATUS.json
@@@ -32,7 +32,6 @@
    ],
    "notYet": [
      "Its own capabilities: the quest manifest in openvibe-contracts lists none yet (no quest.* capability exists)",
--    "OpenCoins are off in production until OpenVibe.Network grants the quest client identity.subject.resolve and network.coins.credit",
      "Community-made quests (streamers, communities, mods): they need moderation, which this release does not have",
      "Repeatable quests and seasonal resets: every quest completes once per person",
      "Account merges (ADR-029): quest_progress, quest_completions and quest_badges rows are not re-keyed when a Network account is merged into another (deletion is answered, ADR-033; a merge's aliases are erased with the account)",
@@@ -51,5 +50,5 @@
      "crawl artifacts"
    ],
    "deployment": "openvibe-ovh: unit openvibe-quest.service on 127.0.0.1:4980 (git checkout /opt/openvibe.quest, env /etc/openvibe/quest.env, database ov_quest), deployed with `sudo ovhost deploy quest`; public at https://openvibe.quest since 2026-10-08.",
--  "updated": "2026-10-18"
++  "updated": "2026-10-20"
  }