* feat(plugins): check host API calls against released Orca at validation
orca plugin validate and pnpm validate:plugin now read the literal host
method names a plugin's worker, panel and editor code calls, and report
methods this Orca does not have, proposed methods, wrong-surface calls,
and methods newer than engines.orca (unless guarded by orca.host.has).
Deprecated methods warn with a stable 'deprecated host method <name>'
prefix. Adds the Host API minor to first-Orca-release table.
* fix(plugins): avoid host-call validation false positives
Guarded proposed and wrong-surface calls warn instead of failing, and an orca.api.minor comparison counts as a floor guard. Only host.call/has receivers count, comments are stripped, files are stat-capped and read through their real path inside the plugin, root-relative script sources resolve, and each file is read once.
* fix(plugins): keep has-guarded host calls as errors before orca.host.has existed
* fix(plugins): fail only certain host-call problems and bound the scan
Floor and wrong-surface findings are warnings, since guards and per-surface reachability are not visible to a text scan; unknown and proposed methods without a literal has guard stay errors. Read attempts, references per file and queued files are capped, has?.() counts as a guard, and HTML script and comment scanning is linear.
* fix(plugins): treat any orca.host.has call as feature detection for unknown methods
* build(cli): ship the host-call validation module with the packaged CLI
Orca already drops protected strings when it loads a language pack and keeps
its own English text for trust, permission and destructive dialogs.
validate:plugin and orca plugin validate still rejected the whole pack, so the
community directory refused otherwise-good packs. They now report how many
protected strings are ignored as a warning; every other pack rule stays strict.