[leonatwork]

Zusammenfassung

Autonome Umsetzung von #10: [Agent] Suchen und Ersetzen im Kapitel und im ganzen Projekt

Verifikation

• Coder-/Reviewer-Loop: APPROVE nach 2 Runde(n)

• Tests und Qualitätsprüfungen: siehe Commit und CI-Checks

• Kein automatischer Merge oder Produktionsdeploy

• Modell: azure/gpt-6.1-sol; Decision-1 (active): route gpt-5.3-codex, Risiko medium; QS: npm run build && npm test bestanden

• Art der Änderung (Triage): code; Zweitprüfung: azure/gpt-5.3-codex

• Kosten (Listenpreis): 15,4 Mio Tokens · 7,23 €

Hinweise der Qualitätsprüfung

• Review-Hinweis (minor: core/suche/index.ts:14 copies the pattern from src/features/schreiben/verweise.ts:19. If a new reference type is added later, both places must change. A short note in the comment, or a shared constant in core/text, would prevent them drifting apart. Optional.)

Closes #10

---

Note

Medium Risk
Bulk edits touch persisted manuscript and plan/note data with snapshot gating, but the behavior is heavily tested and scoped to local text fields rather than auth or external services.

Overview
Adds local find/replace for the current chapter and the whole project (Issue #10), with no KI or network use.

Core (core/suche) introduces literal paragraph-level search (optional whole word / case), project field enumeration with an allowlist (manuscript, plan, notes; skips IDs, anchors, and full [[typ:id|…]] spans), and replace that keeps manuscript Markdown markup while inserting literal replacement text in plan/notes.

UI & commands: ⌘F opens in-editor chapter search with highlights and navigation; ⌥⌘F opens a project dialog grouped by manuscript / plan / notes. Native Edit menu entries, DE/EN strings, and Recherche still uses ⌘F for its own filter via a custom event.

Safety & persistence: Each affected chapter gets a mandatory snapshot (SchnappschussAnlass: ersetzen) before write; failed snapshots leave that chapter untouched. Plan/notes support one in-memory undo for the last replace action; manuscript uses editor undo or version history. Replace updates writing statistics stand only, not geschrieben. An import-boundary test keeps search code off KI/backend paths.

^{Reviewed by Cursor Bugbot for commit 1cb8a0c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Partial undo becomes unrestorable

Medium Severity

undo writes fields one by one and only clears the in-memory stack after every write succeeds. If a later speichern throws, earlier fields are already back to vorher while the stack still expects every field to equal nachher, so the next undo raises undoKonflikt and cannot finish the rest of the action.

 

^{Reviewed by Cursor Bugbot for commit cf29b0a. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1cb8a0c. Configure here.}

[cursor]

Replace loses out to dirty editor

High Severity

The new replace handoff via editorErsetzungAbholen runs only after the existing dirty-buffer guard. If the open chapter changes between editorSichern and the store write (snapshot I/O), that guard keeps the local buffer, skips the handoff, and autosave.jetzt() writes the editor back over the replacement already persisted.

Additional Locations (1)

• src/state/slices/suche.ts#L78-L82

 

^{Reviewed by Cursor Bugbot for commit 1cb8a0c. Configure here.}