stories::on-config-change
Internal: re-read the stories configuration after an operator change.
- idstring
Configuration id that changed.
- okbooleanrequired
Component stories for any React project — builds CSF story files with the project's own Vite (monorepo-aware), indexes components and their states per git line, compares the working tree with a branch, a commit or a chat turn, renders deterministic screenshots and DOM/React trees through the browser worker, and injects an explorer and compare page into the console.
iii trigger compose::add worker=storiesRun in your project with the iii engine running. Exact versions are immutable and digest-pinned.
Internal: re-read the stories configuration after an operator change.
Configuration id that changed.
Fires on every build state transition (queued, running, done, failed) of any line. Config: { workspace?, metadata? }.
queued | running | done | failed
Fires after a working-tree rebuild changed components, with each change classified as direct, indirect, new or removed. Config: { workspace?, project?, kinds?, metadata? }.
Change kinds to fire for: direct, indirect, new, removed. Omit for all.
Metadata attached to every invocation this binding receives.
Project name. Omit for every project.
Workspace slug. Omit for every workspace.
The line the changes were classified against.
RFC 3339.
Whether the working tree had uncommitted changes when built.
Stable key: `worktree`, `worktree.prev`, or a git object sha.
Which kind of source tree a line photographs.
Human label: the ref name, the turn, or `working tree`.
Only the changed components (never `unchanged`).
Smallest hop at which the file reaches the component.
added | removed | modified
added | removed | kept
RFC 3339.
Whether the working tree had uncommitted changes when built.
Stable key: `worktree`, `worktree.prev`, or a git object sha.
Which kind of source tree a line photographs.
Human label: the ref name, the turn, or `working tree`.
Find workers, kits and executables, or jump to a page.