glennandClaude Opus 5 6b48fdf126 Refuse to run on config keys the builder cannot build ...

build_demo.py reads every key with cfg.get(), so a config describing objects it does
not implement was skipped in silence — it printed DONE over an empty database. That
is the same "reports success over an environment that isn't" failure the purge section
exists to prevent, one layer up, and it is how a vertical config (take-offs, progress
statements) would have failed.

Unknown top-level keys now list themselves and abort. DEMO_ALLOW_UNKNOWN_KEYS=1
overrides for a deliberate partial run. Keys starting with _ stay free for comments,
so the shipped example config passes clean.

SKILL.md now states outright that build_demo.py is a per-engagement template rather
than an engine, since that is what makes the failure mode surprising.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-07-31 11:10:16 +02:00

..

build_demo.py

Refuse to run on config keys the builder cannot build

2026-07-31 11:10:16 +02:00

odoo_connect.py

odoo-demo-architect: discovery -> live Odoo demo + sales docs, AI-built

2026-06-28 20:13:22 +03:00