Verify the skill against Odoo 20.0 and note what changed

Odoo 20.0 (FINAL) is on GitHub. Every v19 field the skill relies on
(group_ids, privilege_id, is_storable, credit-limit fields, stock_fleet
dispatch fields) is unchanged; the JSON-2 connector already speaks the
v20 API. Real deltas: the RPC db service is gone, custom-module security
is a single ir.access.csv, binary fields have a new RPC shape.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: callista-odoo-demo
-description: Build a complete, client-tailored Odoo demo end to end — assembles the discovery brief from any source (transcript, notes, email, Knowcap, or a live interview), researches native-vs-custom per hero feature, stands up a LIVE Odoo database over the Odoo 19 JSON-2 API (modules + realistic data + working heroes), tests it, and generates the sales docs and the post-demo follow-through set (objection sheet, scoped quote, timeline, SOW). Use when prepping an Odoo sales demo, POC, or proof-of-value, or when writing the follow-up after one. Triggers: "build an Odoo demo", "demo DB for <client>", "Odoo proof of concept", "stand up a demo before the meeting", "write the follow-up after the demo".
+description: Build a complete, client-tailored Odoo demo end to end — assembles the discovery brief from any source (transcript, notes, email, Knowcap, or a live interview), researches native-vs-custom per hero feature, stands up a LIVE Odoo database over the Odoo 19/20 JSON-2 API (modules + realistic data + working heroes), tests it, and generates the sales docs and the post-demo follow-through set (objection sheet, scoped quote, timeline, SOW). Use when prepping an Odoo sales demo, POC, or proof-of-value, or when writing the follow-up after one. Triggers: "build an Odoo demo", "demo DB for <client>", "Odoo proof of concept", "stand up a demo before the meeting", "write the follow-up after the demo".
 ---
 
 # Callista Odoo Demo
@@ -130,7 +130,7 @@ An extending skill may insert its own tier ahead of native — see [Extension po
 ### Connect
 
 Use `scripts/odoo_connect.py`. It speaks **JSON-2** (`POST /json/2/<model>/<method>`, API key
-as a bearer token) — Odoo 19's external API. `/xmlrpc`, `/xmlrpc/2` and `/jsonrpc` are all
+as a bearer token) — the Odoo 19/20 external API. `/xmlrpc`, `/xmlrpc/2` and `/jsonrpc` are all
 deprecated and disappear in Odoo 22; do not write execute_kw calls.
 
 Print `version()["version"]` to confirm the major version (field names differ across versions
@@ -244,7 +244,8 @@ Rules:
   Portable to any Odoo, no deploy.
 - **Custom module only if needed:** generate a minimal module, push to the instance's git
   (Odoo.sh) or hand it to the user to deploy, then install + test. Keep modules tiny and
-  version-correct.
+  version-correct: on v20 security is one `security/ir.access.csv` (no `ir.model.access.csv`,
+  no `ir.rule`); on v19 it is still `ir.model.access.csv`. Check `version()` first.
 - Example hero (credit hard-block + manager override): override `sale.order.action_confirm`
   to raise `UserError` when `partner.credit + amount_total > credit_limit` unless the user
   is in an approver group; add an "Override" button gated to that group.
@@ -406,7 +407,7 @@ Rules for the boundary:
 - Never hand over an environment holding test records. Purge them and read back the counts;
   do not settle for "cancelled and archived" and do not write leftovers off as a note.
 - Never send anything client-facing without the user reading it first.
-- Read `reference/odoo19-field-gotchas.md` before touching Odoo 19 — several core fields
+- Read `reference/odoo19-field-gotchas.md` before touching Odoo 19/20 — several core fields
   were renamed.
 - `discovery_brief.md`, `demo_config.json` and the follow-through docs hold client data and
   API keys — keep them in the project directory, never in a scratchpad you'd forget.