2 Commits

Include renames

Author	SHA1	Message	Date
Neil	ec0d3cedd1	Plugin panels talk to their worker; panel storage, settings and agent events (#37013) ... * feat(plugins): panels talk to their own worker, read storage, settings and events - plugin.request (host API 1.2): a panel or editor asks its plugin's worker, which answers with orca.panels.handle(name); the worker pushes with orca.panels.post. Same plugin only, JSON checked, 1 MiB answers, 256 KiB/200-per-10s posts, a deadline and the panel's lifetime. - Panels and editors get storage.*, settings.* and secrets.* behind the same capabilities, and storage/settings onDidChange on every surface; events.subscribe delivers workspace and agent events to panels that hold the read capability. - contributes.settings: typed settings (a JSON Schema subset) with defaults and value checks. - Frames get orca.plugin/storage/settings/secrets; components panels import plugin, storage, settings, secrets from 'orca', and atom(key, init, { persist: 'storage' }) shares a value with the worker. Workers get orca.panels/storage/settings/secrets sugar. - One typed contract: declare module 'orca' { interface PluginRequests / PluginPanelEvents }. - Desktop push channel per open panel session (plugins:openPanelPush). * feat(plugins): Orca Settings shows and edits a plugin's contributes.settings The plugin page lists declared settings with Orca's own controls (switch, picker, text and number fields, Reset to default). Edits are checked against the declaration in main, written to the plugin's settings, and reach open panels and the running worker through onDidChange. * docs(plugins): hello-tsx talks to its worker; authoring guide covers panels, workers and data The example now uses one of each: plugin.request answered by orca.panels.handle, a worker post heard with plugin.on, a persist: 'storage' atom the worker watches, two contributes.settings and agent.status.changed in the panel, all typed by one src/protocol.ts. The build-less TSX e2e drives the whole loop. * fix(plugins): typed bridge overloads, panel call budget, settings IPC and catalog keys - PluginBridgeApi/PanelsApi use overloads: declared names are typed (and complete), any other name carries JSON; no never-unions for the type-aware lint. - The per-plugin panel call budget is 120 per 10 s, since a panel loading storage atoms, settings and its first requests makes a burst; the hostile fixture floods past it. - Settings IPC builds its host per call; the settings section's strings are in en.json. * test(plugins): the example's declared settings show under the plugin with the person's value * refactor(plugins): keep hello-tsx the minimal starter; the bridge demo is hello-worker-panel hello-tsx goes back to a sandboxed-ui panel with no worker or capabilities. The worker, protocol, storage atom, settings and events move to examples/plugins/hello-worker-panel, with their own e2e (plugin-worker-panel) and PR route. * feat(plugins): test kit covers the panel bridge and plugin data mockHost keeps the plugin's storage, settings and secrets in memory (seeded with storage, settings, secrets; read with host.data()) and fakes the worker with requests, so plugin.request, storage/settings/secrets and persist: 'storage' atoms work under mount(), writes reach onDidChange, and panel.post(event, payload) is what plugin.on hears. Typed by PluginRequests and PluginPanelEvents. * test(plugins): focusInGuest waits for the guest and retries focusing as one step Under load the custom-editor guest could still be attaching, so executeJavaScript threw 'dom-ready' before the focus poll began. Wait for waitForGuestReady, then retry focusing the webview and the element together, tolerating a guest that is still attaching or remounts. * docs(plugins): the authoring skill covers panels, workers and data; persistence leaves the renderer - skill-guides/orca-plugin-authoring.md gains Panels, workers and data (plugin.request/on, orca.panels.handle/post, persist: 'storage', contributes.settings, panel events, test kit), and its generated references read orca-services.d.ts for shell, files, on and the bridge types. - After the dev-loop rebase, persisted-atom wiring (queue plus storage sync) moves to createDeclarativePersistence so the renderer stays under max-lines. * feat(plugins): panels show agents: agents.list, terminal ids on agent events, workspace.changed - agents.list (agent:read, every surface): the focused workspace's agents with terminalId, title, agent kind, state and stateStartedAt, from the hook server's store. - agent.status.changed carries terminalId and title: paneKey mapped through the runtime's terminal list (tabId:leafId) or the status's terminal handle; looked up only while a plugin listens, in arrival order. - workspace.readContext terminals carry title; workspace.changed (workspace:read) fires after workspace session writes when the focused workspace or its terminals change. - Event subscriptions are kept per panel session, so one made before the push channel opens still counts. - shell.openExternal never prompts on a hidden or minimized window: it settles { opened: false, reason: 'consent-unavailable' } and says so in the plugin log, which also notes 'waiting for the person to confirm' while a prompt is up; the rate budget is spent only when Orca acts. e2e launches never open a real browser or mail client. - A worker may export activate as default or by name; docs, typings and the authoring skill document the entry, the agent events and a live agent status recipe. * fix(plugins): the plugin page names the workspace.changed subscription * fix(plugins): workers activate only by default export, and say so when it is named Orca calls the worker module's default export. A module with a named `activate` and no default now fails to start with an error naming the fix (`export default function activate(orca)`), instead of being called by a fallback; docs, typings and the skill say default export. hello-worker-panel gains a picker setting (suggestionOrder) the worker reads.	2026-11-01 04:40:17 -08:00
Neil	4ee788a725	Build-less TS/TSX plugins, typings and authoring tools (#36918) ... * 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.	2026-11-01 01:28:35 -08:00