Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/design/docs-remote-cursor.md`:
- Around line 165-173: Update the spec to reflect that label text color is
dynamic rather than fixed white: replace the hardcoded "White (`#FFFFFF`)" entry
with a note that text color is determined at runtime using the same logic as the
implementation (see getLabelTextColor in packages/docs/src/view/peer-cursor.ts),
e.g., "Text color: dynamic — computed via getLabelTextColor (black or white)";
keep other layout entries unchanged.
- Around line 102-108: The fenced code block that begins with "Yorkie
others-changed event" is missing a language tag causing markdownlint MD040; add
a language identifier (use "text") to the opening fence so it becomes ```text
and keep the closing fence unchanged to satisfy the linter and preserve the
event-flow snippet formatting.

In `@packages/docs/src/view/editor.ts`:
- Around line 40-43: The peer-cursor API is missing lineAffinity, causing
wrap-boundary offsets to resolve incorrectly; update the onCursorMove callback
signature and the getPeerCursorPixels presence payload to include lineAffinity
(e.g., { blockId, offset, lineAffinity }) and thread that field through the
selection/text-editor helpers, ensuring callers pass lineAffinity into
resolvePositionPixel when computing pixel positions; update all related helpers
and any call sites (including functions that build peer cursor presences and the
resolvePositionPixel invocations) to accept and propagate lineAffinity so
visual-line hit-testing uses the correct affinity.

In `@packages/frontend/src/app/docs/docs-view.tsx`:
- Around line 214-243: The hover state isn't cleared when the pointer exits the
editor; update the logic around handleMouseMove/hoveredPeerClientID so pointer
exit clears the hover: add a pointerleave/pointerout (or mouseleave) event
handler on the same container that sets hoveredPeerClientID.current = null and
calls ed.setPeerCursors(buildPeerCursors()) using editorRef.current (same
approach as in handleMouseMove), and apply the same fix to the other hover block
referenced (lines ~249-263) so leaving the editor always hides the peer label.
- Around line 199-210: The trailing-send timer currently always re-arms for the
full CURSOR_UPDATE_THROTTLE which can delay the final broadcast; inside the
editor.onCursorMove handler (use symbols editor.onCursorMove,
cursorTrailingTimer, lastCursorUpdate, CURSOR_UPDATE_THROTTLE,
store.updateCursorPos) compute the remaining window = CURSOR_UPDATE_THROTTLE -
(Date.now() - lastCursorUpdate.current), clamp to >=0, and use that remaining
time for window.setTimeout so the suppressed move flushes exactly at
lastCursorUpdate + CURSOR_UPDATE_THROTTLE instead of adding a full extra
throttle interval.

In `@packages/frontend/src/app/docs/yorkie-doc-store.ts`:
- Around line 444-447: The current updateCursorPos method (updateCursorPos) and
the presence serializer drop Cursor.lineAffinity by only storing {blockId,
offset}; update the code to preserve and broadcast lineAffinity: change the
presence/activeCursorPos shape to include lineAffinity (e.g., {blockId, offset,
lineAffinity}), set p.set({ activeCursorPos: pos ?? undefined }) with that full
object, and update the DocsPresence type/serializer and any code that
reads/writes cursor presence to accept and forward lineAffinity so wrap-boundary
offsets resolve to the correct visual line for collaborators.

In `@packages/frontend/src/types/users.ts`:
- Around line 16-21: DocsPresence currently extends User but the actual presence
seeded in docs-detail.tsx only includes username, email, photo, and
activeCursorPos, making YorkieDocStore.getPresences() unsafe; either narrow the
DocsPresence type to exactly the runtime shape (e.g., remove/optionalize id and
authProvider) or ensure the presence initialization in docs-detail.tsx seeds the
missing User fields (id, authProvider, etc.) so the runtime payload matches the
DocsPresence type; update the type declaration in
packages/frontend/src/types/users.ts (DocsPresence) or the presence creation
logic in docs-detail.tsx and adjust any usages in YorkieDocStore.getPresences()
accordingly.

---

Nitpick comments:
In `@packages/docs/src/view/editor.ts`:
- Around line 230-242: The stacking is non-deterministic because stackIndex is
assigned in the incoming peerPixels order; before computing stackCounts and
building resolvedPeers, sort peerPixels by their pixel position and then by
clientKey and clientID (as tie-breakers) so peers at the same position always
get the same stackIndex; keep the existing stackCounts/resolvedPeers mapping
logic and only change the input order used to compute stackIndex.

In `@packages/docs/test/view/peer-cursor.test.ts`:
- Around line 80-142: Add a test that exercises wrap-boundary affinity by
creating a block with two visual lines (e.g., first line text length N, second
line starts immediately) and calling resolvePositionPixel with the same position
offset at the boundary but with different lineAffinity values; specifically,
pass a position object that includes blockId, offset (boundary offset), and
lineAffinity ('backward' and 'forward'), call resolvePositionPixel twice (once
per affinity) and assert the returned pixel coords differ in y (or line context)
to prove the affinity chooses the preceding vs following visual line; locate
resolvePositionPixel usages in this test suite (peer-cursor.test.ts) and follow
the existing mockRun/mockLine/mockBlock/makePaginatedLayout/makeCtx pattern to
build the layout and expectations.