demobite 1.7.0 → 1.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "demobite",
-  "version": "1.7.0",
+  "version": "1.7.1",
   "description": "The DemoBites agentic recorder — you prompt, it films a real browser, and DemoBites turns the take into an editable demo bite.",
   "bin": {
     "demobite": "launcher/index.mjs"

package/scripts/record.mjs

@@ -427,6 +427,13 @@ const pushWide = (tStart, tEnd, label, extra) =>
 // spans the whole landing — the line "you land on the report" plays over it.
 let wideAfter = null; // { tStart, label, extra }
 const wantsWide = (step) => step.frame === "wide";
+// Every click keeps its close shot this long past the click (founder
+// 2026-09-29). The export FINISHES a pull-out at the shot's end, so a close
+// shot ending 0.3 s after the click started pulling out ~0.7 s BEFORE it: the
+// last click of bite 1110 (the pause switch) played at 1.12x. 1.1 s puts the
+// whole pull-out after the click lands. A click framed wide (option 2) hands
+// over to its wide landing at the same moment.
+const LANDING_PULL_OUT = 1.1;
 const wantsClose = (step) => step.frame === "close";
 // The page as a signature, so a submit that swaps the page IN PLACE (a search
 // that re-renders a list, a client-side route change) counts as a landing
@@ -967,9 +974,14 @@ try {
           await page.evaluate(([a, b]) => window.__recSetCursor?.(a, b), [cx, cy]);
         }
         // Shot one: the control — beginning near ARRIVAL (see the camera
-        // choreography law above), never spanning the approach glide.
-        if (stepWide) wideAfter = { tStart: Math.max(shotStart, arrivalT - 0.3), label: step.label, extra: { n: rec.n } };
-        else pushShot(userShotBox(step, box), Math.max(shotStart, arrivalT - 0.3), t() + 0.3, step.label, { n: rec.n, glide: { t_start: Math.round(shotStart * 100) / 100, t_end: Math.round(arrivalT * 100) / 100 } });
+        // choreography law above), never spanning the approach glide. A click
+        // framed `wide` (its line is about where it leads) is STILL filmed
+        // close on the click; the landing after it is the wide shot. Before
+        // 2026-09-29 the whole step went wide from arrival, so the viewer saw
+        // a tiny cursor click a tiny item (bite 1117: all three clicks).
+        const closeEnd = Math.max(t() + 0.3, rec.click_at + LANDING_PULL_OUT);
+        pushShot(userShotBox(step, box), Math.max(shotStart, arrivalT - 0.3), closeEnd, step.label, { n: rec.n, glide: { t_start: Math.round(shotStart * 100) / 100, t_end: Math.round(arrivalT * 100) / 100 } });
+        if (stepWide) wideAfter = { tStart: closeEnd, label: `${step.label ?? "click"}, landing`, extra: { n: rec.n, revealed: true } };
         // LAW (press physics, founder 2026-08-09): a press has a down and an
         // up — but the up only exists if the clicked surface is still there.
         // A menu item or modal button that DESTROYS itself on click gets a

package/skill/SKILL.md

@@ -172,6 +172,7 @@ Framing is our job, never the customer's (founder, 2026-09-27). Decide it from t
 - A field, a button, a menu item, a toggle, a badge, a row = `"close"`.
 - Landing on a page, a report, a chart, a table, a dashboard, a list of results = `"wide"`. So is every line that says "here is", "you see", "you land on", "the whole".
 - A `type` step with `enter` is close for the typing. What Enter reveals is wide by itself; the recorder sees the new page. Do not add a beat for it.
+- A `click` whose line is about where it leads ("pick it, and you are on the right screen") = `"wide"`. The recorder still films the click itself close, then goes wide on the landing from the moment of the click (founder, 2026-09-29). The viewer always sees what was clicked, then where it led.
 - A bare `settle` right after a navigation is wide by itself.
 - Two consecutive wides on the same page are one shot. Write both; the server joins them.
 - Never more than 4 seconds of close on a static screen. When the line runs longer, the beat is wide.