[timothy-mccormack]

What this is

PT-4008: in the paragraph-structure view, the active-text box now outlines just the verse the caret is in, instead of its whole paragraph.

What changes for users

• The outline follows the verse. It starts where the verse's text starts and ends where it ends, with straight sides in between, so a verse that starts mid-line makes a Z. This is the "new C" shape from UX review.
• A verse is outlined across every line it spans: a \q1 with its \q2 lines, or a \p break mid-verse. It stops at headings, tables and chapters.
• An empty verse's outline is full text height, so it doesn't grow when you start typing.
• Headings, text before a chapter's first verse, and tables keep the whole-paragraph box, as before.
• The outline is hidden while the editor is blurred, and is measured again after every update and on resize.

How it works

1. $getActiveVerseSections (ActiveTextPlugin.tsx) finds the caret's verse, one section per paragraph it runs through. A verse nested in a char span still bounds its section. $getActiveVerseSection, which drives the empty-verse ellipsis, is unchanged.
2. measureVerseSections reads the sections' line boxes with Range.getClientRects() and drops the hanging space at line wraps.
3. computeVerseOutlineSegments (verseOutlineGeometry.ts, pure) turns the line boxes into the boxes of one outline.
4. outlinePathData (verseOutlinePath.ts, pure) traces those boxes into an SVG path, rounding corners by a chosen style. The path is drawn in a .psc-verse-outline overlay placed just after the editor's root element.

Change from the ticket's plan: the ticket proposed three boxes positioned from the verse markers' own boxes. A verse marker is shorter than its line and doesn't show where a section ends mid-line, so that approach breaks with fonts, indents and mid-line endings. Measuring the text's actual line boxes handles every shape with one code path.

Open UX questions

The drawing settings are constants at the top of ActiveTextPlugin.tsx, so each answer is a one-line change:

• Corners: Sebastian chose between rounding every outward corner and rounding every corner. Outward corners for now (OUTLINE_CORNERS).
• Shape: Ian is choosing between straight sides ("new C", used now) and hugging every line (OUTLINE_HUGS_LINES).
• Gutter marker and selection behaviour: Sebastian's answer to Q3 (the \p glyph depending on selection state, plus triple-click, Ctrl+A and Ctrl+Shift+Up/Down behaviours) needs selection and keyboard work beyond this PR. I'd suggest a separate ticket.

For reviewers

• Anchor vs. focus: CLAUDE.md says to read the selection's focus for "the node the caret is in". This code reads the anchor, to match the toolbar's verse reference and paragraph style; reading focus here alone would make the outline and the toolbar disagree during a range selection.
• Known limit: in tall scripts (Myanmar, Nastaliq) glyph boxes exceed the line box, so the top and bottom of the outline can cross into neighbouring lines.
• Unrelated flake: a known-failure test in Editor.test.tsx (PT-4925) sometimes throws an unhandled Lexical error, which fails the run. It happens without this branch too (3 of 5 runs).

Testing

• nx run-many -t test,lint,typecheck -p platform-editor: 5415 passed. The only lint warning (verse-block.utils.ts, no-loop-func) is already on main.
• Each fix and behaviour has a test, and reintroducing each bug makes a test fail.
• Checked in the editor demo in Chromium:
  • a prose Z;
  • a poetry verse across \q1/\q2;
  • the heading fallback;
  • an empty verse before and after typing (the same 22px height);
  • rewrapping when the editor narrows;
  • hiding on blur.
• The committed packages/platform/dist/ is rebuilt, and verify-committed-dist passes.

🤖 Generated with Claude Code

---

This change is