Now: At 390 px the Lunge and Disengage views render a 425 px document; the stage and playback-speed group extend beyond the right edge. The home page also expands to 332 px at a 320 px viewport.

Change to: Allow the shared grid and flex children to shrink (min-width: 0), constrain the transport segmented group to max-width: 100%, and wrap its buttons within the available panel width. Keep the scene, scrubber and every playback speed visible without horizontal scrolling.

Why: The review requires no horizontal scrolling at 320, 390 or 1440 px, and Learn must support touch playback.

Now: The referee uses claimed hit events even after geometric contact validation rejects them. A 2.00 m left-handed demonstrator performing BL14 is awarded the touch while only the right green lamp registers.

Change to: Derive scoring hit events from the registered contacts after geometry and lockout filtering, and pass those events to the referee and priority explanation. A rejected contact must not score.

Why: Sections 0.5, 2 and 5.5 require every awarded touch to pass animated-geometry verification and the referee to agree with the scoring box.

Now: The resolver declares a successful parry from the deception table and deflects the attacker without placing the two blades in contact. In the default Sixte demo the nearest blade axes are about 0.462 m apart at the recorded contact.

Change to: Apply the existing contact-frame IK to both blade rigs at the parry event so their segments meet at a shared contact point, and verify that contact before emitting a successful parry. Reuse that contact in the blade-contact overlay and referee timeline.

Why: Sections 0.1 and 2 require accurate 3D demonstrations; Section 2 explicitly requires tips and blades to meet physically at the exact tick for parries, beats and binds.

Now: Tempo Mode resolves a complete simultaneous slice on each keypress, removes the pad during playback, and ignores every further key until stage returns to pick. It also substitutes an NPC when Human is selected.

Change to: Keep the existing Tempo action controls live during the exchange and timestamp each accepted action at the current simulation tick, including overlapping footwork and blade actions; schedule the NPC response from its actual reaction delay. Respect the selected opponent.

Why: Section 4.4 requires real-time Tempo Mode in which actions start the moment they are pressed with real reaction timing, using the same footwork-plus-blade action set.

Now: Build It shows four already-written sentence answers. One click completes the round, and the demonstration is just demoFor(good.id), so the preparation and the described opponent are not part of a constructed sequence.

Change to: Let the visitor select and order the existing preparation and finishing action cards, validate that assembled sequence for the stated situation, and play that sequence against the described partner.

Why: Section 4.5 requires the visitor to construct an ordered sequence for the stated situation; selecting a complete sentence does not implement that interaction.

Now: Counter Explorer combines two IDs at the attack’s default line and distance, without arranging the situation in which the listed counter works. The default “reliable” quarte counter to FW04 loses because the lunge is aimed outside; the “reliable” septime answer to AT06 similarly closes the wrong line.

Change to: Use a scenario for each counter link: aim FW04 into high-in for quarte and AT06 into low-in for septime, choose the appropriate measure/timing, and include prerequisite parry slices for riposte counters. Keep the listed reliability tied to the situation actually shown.

Why: Sections 0.3 and 4.3 require attack-versus-counter demos that show each counter’s purpose; Section 5.4 requires parries to close the attack’s final line.

Now: The full-lunge pose leaves the rear knee bent about 39.5° and the front shin tilted about 7.5° instead of the required straight rear leg and vertical front shin. Advance-lunge reuses the same faulty pose.

Change to: Correct the shared LUNGE_LOWER pelvis height, pelvis displacement and foot placement against the existing rig dimensions, solving for a nearly extended rear leg and front knee directly over the ankle while keeping the rear foot flat and lean at or below 15°.

Why: Section 3.3 explicitly requires “The rear leg drives to full extension” and a heel-first landing “with the shin vertical and the knee over the instep”; these are core coaching demonstrations.

Now: The circular-parry branch checks only whether an attack evades a circle; it never checks the final line. Counter-septime and counter-octave therefore stop a straight high-outside thrust and award a riposte from the wrong line.

Change to: For a straight attack, require the circular parry’s ending position to close the attack’s final line before returning parried; preserve the separate circular-deception rules for disengages and doublés.

Why: Section 5.4 explicitly says a straight thrust is caught by a circular parry ending in its final line. Low-line parries cannot be unconditional answers to high-line thrusts.

Now: The end-line check tests only the rear heel, then captions the result as both feet crossing. A fencer loses a touch while the front foot is still 35 cm inside the piste.

Change to: Check the front and rear foot extents against the same end boundary and award the penalty only after both feet have crossed that end line. Keep the existing rule-11 caption for the corrected condition.

Why: Section 5.6 rule 11 explicitly requires crossing the end line with both feet for a penalty touch.