`#5175` disabled the three Host rows (`time-context`, `schedule`, `ui-schedule`) as a temporary stopgap and refreshed the Web fixtures for that composition. Those rows and fixtures stay as master has them; this branch keeps its preset ownership of the reminder stack, which takes effect when the stopgap is lifted. Resolutions: - `packages/bundle/web-app/cordis.patch.yml` keeps master's `disabled: true` on all three rows. - The three presets declare the clock under `preset-time-context`: a row id belongs to exactly one plane, and the Host row retains `time-context`. - `apps/web/tests/schedule-after.e2e.ts`, `apps/web/tests/fixtures/ time-context-every-step.patch.yml`, `web-default-isolation.expected.e2e.ts`, and the `minimal-preset` session fixture keep master's stopgap-era state.
description, kind
| description | kind |
|---|---|
| Runtime API inspection, process-local runners, and historical Cordis cards. | package-group |
packages/extensions
English | 中文
Summary
The extensions group provides read-only runtime API discovery for agents, process-local runners for programmatic and browser consumers, and historical generated-plugin cards. Creator mode installs persistent plugins through Plugin Manager. Choose a child package for inspection, Host execution, Client execution, or browser controls.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
tool-cordis |
Two read-only tools for runtime API discovery | registers on ctx.tools |
cordis-host-runner |
Host half: definition registry, sandboxed host-half lifecycle, and the inspect registry that answers browser queries | provides ctx.dynamicCordisRunner and ctx.cordisInspect |
cordis-client-runner |
Browser half: evaluates a browser-half source into a live plugin and answers run requests | client face; provides browser ctx.dynamicCordisRunner |
ui-cordis |
Browser panel and historical lifecycle tool cards | client face; registers slots |
Related documentation
- Extensions subsystem — the generated
ctx.cordisInspectandctx.dynamicCordisRunnerservice API. - Generated tool catalog — the two read-only tool schemas.
- Generated configuration catalog — the runner's accepted config fields.
- Self-referential Cordis toolset Agent Note — design home for sandbox semantics, lifecycle, and composition.
- Client shells and dynamic packages Agent Note — package placement and build faces for the client halves.
Dev Note
Working context for maintainers — click to expand
The two browser-half packages live in this group rather than under packages/client/ because they are halves of this subsystem's dual-half packages; the client face compiles them through the client program, while the host program references only the host runner.