What problem does it solve? In HOT-Step CPP, a parameter set in the UI can silently never reach the C++ sampler, and nothing errors. This Skill maps the full lifecycle of a generation request (UI form → Node job queue → engine LM → synth → SQLite row) and catalogs every point where a parameter can be lost, including the LM echo sideband gotcha and the yyjson int-vs-float trap. ## Core Features & Use Cases - End-to-end pipeline map: Documents the path from Zustand UI store through translateParams, aceClient, and hot-step-server.cpp into the DiT sampler, with verified file and line references. - Param-drop checklist: Eleven known silent-drop locations (LM echo rebuild, falsy guards, UI gating, LM cache staleness, multipart truncation, upstream sync hook loss) with failure signatures and fixes. - Five-layer procedure for adding parameters: Step-by-step instructions for threading a new generation parameter through UI state, Node translation, wire types, engine parsing, and the g_hotstep_params global. - Use Case: You add a new guidance knob to the UI but the engine keeps using the default. This Skill tells you to check the UI gate in getGlobalParams, the translateParams guard, and the int-safe get_num parse pattern before suspecting the engine. ## Quick Start Ask the assistant to trace why a generation parameter set in the UI is not reaching the engine, using the generation-request-flow skill.
