docs/tasks/README.md (1)

41-41: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update stale “Latest active task” value.

Line 41 still points to slides font load repaint, but Line 21 adds slides grouped text edit entry as the newest listed active task. Please align this footer line with the current index content.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/tasks/README.md` at line 41, Update the stale footer string "Latest
active task: slides font load repaint" so it matches the current newest task
entry; replace that value with "slides grouped text edit entry" (the updated
latest task referenced earlier in the file) so the footer and the index content
are consistent.

packages/slides/src/view/editor/editor.ts (2)

3404-3409: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Keep permanent guides visible during live adjustment preview.

This overlay repaint drops permanentGuides, so guides disappear on the first adjustment pointermove and only come back after mouseup. The other live-paint paths preserve that chrome.

Suggested patch

     renderOverlay(this.options.overlay, [liveEl], {
       scale: this.scale(),
       slideWidth: SLIDE_WIDTH,
       slideHeight: SLIDE_HEIGHT,
       allElements: synthetic.elements,
+      permanentGuides: this.options.store.read().guides,
+      pendingGuide: this.pendingGuide,
     });

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/slides/src/view/editor/editor.ts` around lines 3404 - 3409,
renderOverlay call during live adjustment is dropping permanentGuides so they
disappear on pointermove; update the renderOverlay invocation to preserve and
pass the permanent guides into the overlay render. Specifically, when calling
renderOverlay(this.options.overlay, [liveEl], {...}), include the
permanentGuides (e.g. this.options.overlay.permanentGuides or
synthetic.permanentGuides) in the options object or merge them into allElements
so renderOverlay receives permanentGuides alongside
scale/slideWidth/slideHeight/allElements; ensure renderOverlay receives the same
permanentGuides the other live-paint paths do so guides remain visible during
pointermove.

---

2221-2224: ⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Sync the drill-in scope before selecting a grouped edit target.

The new recursive lookup lets enterTextEditing() open a nested element from root scope, but this.selection.set([elementId]) leaves Selection.getScope() unchanged. After commit/cancel, the overlay and drag paths in this file still convert frames through toWorldFrame(..., this.selection.getScope(), slide), so that grouped element comes back selected with root-scoped geometry and its handles/drags are misplaced.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/slides/src/view/editor/editor.ts` around lines 2221 - 2224, When
selecting a grouped/nested edit target in enterTextEditing(), also update the
selection's drill-in scope before calling this.selection.set([elementId]) so
Selection.getScope() matches the element’s actual nested scope; compute the
element’s scope (e.g. via the same recursive lookup used to locate the element)
and call the appropriate selection API to set that scope (for example
setScope(...) or the overload that accepts a scope with set([...], scope)) and
only then set this.selection and this.editingElementId so subsequent
toWorldFrame(..., this.selection.getScope(), slide) conversions use the correct
geometry.