* fix(plugins): give no catalog release entry for a commit install would reject
The release entry printed by validate:plugin and orca plugin release-entry hashed the
committed HEAD tree without running install's file checks, so a commit with only
orca-plugin.json (declared theme files left uncommitted) got an entry whose install fails.
Run install's validatePluginInstallTree on the materialized tree, shared with install staging.
* refactor(plugins): return early per release-entry rejection; drop the temp tree path from the note
* fix(plugins): check the release entry the way install reads it
Read the committed manifest with install's 1 MiB bound, and round-trip the entry through
the catalog release schema and pluginCatalogReleaseError, so a field a catalog drops (e.g.
a contribution title over 160 chars) gives a note instead of an entry install refuses.
* fix(plugins): name the field and drop temp paths in release-entry notes
* feat(plugins): build-less TS/TSX plugins, typings and authoring tools
- Plugin frames transpile .ts/.tsx/.mts/.jsx on load (sucrase on a shared worker thread with a
2 s budget, cached in main), resolve relative imports to exact files, and refuse bare
package imports by name. Components and html panel/editor entries may be .ts/.tsx.
- orca plugin types writes typings for the components orca module, window.orca, worker
activate(orca), host.call and events into .orca/types, from one host-typings generator.
- orca plugin create --template components; templates omit publisher and target 1.4.246.
- orca plugin release-entry, dev inspect and restart; validate:plugin checks named files.
- Guest console errors reach orca plugin logs; dev workers restart on edits; the dev watcher
ignores .git, .orca and node_modules; Git and folder installs cannot replace catalog installs.
- examples/plugins/hello-tsx, docs, and the plugin-buildless-tsx e2e spec.
* ci: run the Windows parity probes with one tsgo checker
tsconfig.node peaks near 22 GB with tsgo's default four checkers (each holds its own types)
and about 16 GB with one; the 16 GB Windows runner paged the native probe past its 900 s
timeout once this branch's package.json change triggered the job. One checker gives the
same diagnostics (verified locally with --parity-only); the timing benchmark is unchanged.