# Batch S Worker A: 5-29 overlay sync boundary audit

## Project root

`/mnt/Data1T/mnote-worktrees/0525-s-worker-a-5-29-overlay-sync-readonly`

## Goal

Do a read-only audit for the next safe 5-29 editor runtime extraction slice around:

- `rust/spikes/leptos-tiptap-spike/src/lib.rs::try_sync_editor_overlay_state`
- `on_selection_change` / selection bridge paths near it if needed
- `rust/spikes/leptos-tiptap-spike/src/editor_runtime/overlays.rs`

Answer what can still be extracted safely without changing runtime behavior.

## Required questions

1. Is `try_sync_editor_overlay_state` now small enough to move wholesale into `editor_runtime/overlays.rs`, or should it stay in `lib.rs`?
2. If not wholesale, what is the next smallest pure/helper extraction?
3. Which exact files/functions would a future implementation worker be allowed to edit?
4. What smoke/tests must Codex run after that future patch?

## Allowed files

Read-only task. Do not modify any repository file.

## Hard forbidden leaf-worker rules

You are a leaf worker, not a coordinator.

- Do not create `.codex/reasonix-tasks/*.md`.
- Do not start `reasonix-coding-runner`, `reasonix acp`, Claude Code, Codex, Hermes, or any sub-agent.
- Do not create, delete, or operate any worktree other than your project root.
- Do not commit, reset, checkout, delete, clean, or revert files.
- If you think the task needs splitting, report that in handoff only.

## Suggested checks

```bash
git status --short
git diff --stat
```

## Required final artifacts

Create these files under your output directory if the runner supports it, or include equivalent content in final output:

- `process-handoff.md`
- `process-handoff.json`
- `result.json`

Include:

- Findings with file/function references.
- Recommended next implementation slice.
- Explicit "do not move" boundary.
- `git status --short`.
- `git diff --stat`.