nx_cook_coach.nx

nx_cook_coach.nx -- COOKING as a discipline of the EXISTING curriculum coach. No new engine. nx_coach_curriculum_lib already does the whole loop: serve a framework's required elements, take a SELF-REPORT of which ones you actually did, name what was missing, hand back that element's drill. Its own header says it: "coaching is coaching -- same loop, self-report instead of a sensor." Knife technique is structurally identical to its NVC framework: the required elements are the target chord, what you did is the played notes, missing is the gap. So cooking is ROWS, not code. This file is a data seeder and a self-gate. THE SKILL IDS ARE THE JOIN. dice-onion / chop-veg / sear / braise are the same ids nx_meal_effort uses in its skill tree, so the coach and the opportunity-cost engine talk about the same skill: assessed level drives how long a step takes, which drives whether cooking the dish is the right call at all. Different ids here would have quietly produced two unrelated systems that both looked right. WHY SELF-REPORT AND NOT VIDEO. nx_pose_coach can already compare a pose track to a reference and name the worst joint. What does NOT exist is video -> keypoints: nx_video_pose_coder declares itself PARTIAL_WIRED with VIDEO_DECODE / NEURAL_NET_INFERENCE / POSE_KEYPOINT_DETECTION missing, and nx_pose_estimate caps itself at coarse single-joint classification on our own renders. So the honest coaching surface today is the checklist, and the camera path stays closed until the tracks are real. argv[1] = store prefix (default: the live coach-curriculum plane). Pass a /tmp prefix to gate cleanly. license_tier: ORIGINAL No hw writes (Rule 26).