Example apps declare no engines.protocol range — ADR-0087's compatibility check is skipped on the templates users copy #4097

Newly visible after #4084 unblocked boot-phase logging. Booting examples/app-todo prints:

WARN [AppPlugin] [protocol] package 'com.example.todo' declares no engines.protocol range;
loading under protocol 17.0.0 without a compatibility check (ADR-0087).

The same warning appears for the minimal fixture I wrote for #4084's e2e test, i.e. it is what any newly authored package gets.

Why it matters

The examples are templates — people copy objectstack.config.ts out of them to start a project. An omission here propagates into every derived app, and each one silently opts out of the ADR-0087 compatibility check that exists to catch a package built against an older protocol major. The check is exactly the thing a v17 upgrade needs, and it is off by default in the apps we ship as the reference.

Suggested fix

Declare an explicit engines.protocol range in examples/app-todo, examples/app-crm, and examples/app-showcase (and whatever os init scaffolds), so the shipped templates model the right thing. Worth deciding at the same time whether a package with no range should stay a warning or become a lint failure at os compile — the warning has been unobservable on both CLI entrypoints until now, so "nobody complained" carries no information.