ChucK has no hot-reload path in this rig and runs as a separate process

ChucK is not wired as an engine in the web/glicol+glslviewer presets of this rig — there is no engines/chuck.yaml. Running ChucK means a separate chuck/miniAudicle install outside the rig. ChucK’s own live-coding mechanism (chuck --loop plus chuck +/-/= to add/remove/replace shreds, or miniAudicle’s shred management) is the correct hot-swap path, but it is external to the rig. Consequently every ChucK corpus snippet carries runs_in_rig:null — never assume it runs in-rig.

Examples

To live-code ChucK: chuck --loop in one terminal, then chuck + mysketch.ck to add a shred, chuck = mysketch.ck to replace it.

Assessment

Explain why the rig’s browser hot-reload cannot run a ChucK sketch, and name the two tools you install to live-code ChucK outside the rig.