chore: atualização geral

code/docs/WORKFLOWS.md

@@ -168,6 +168,29 @@ Mark mode adds markers instead of deleting — safer for first pass.
 
 ---
 
+## Dynamic Subtitles: Generate, Then Always Validate
+
+**Scenario:** Word-by-word progressive-composition subtitles (the diagrammed look — small supporting words, one key word large in a display italic) need to go on a cut before delivery.
+
+```
+"Generate dynamic subtitles for /path/to/project.fcpxml"
+```
+
+**Tool chain:** `generate_dynamic_subtitles` → `validate_subtitle_layout`
+
+Run `generate_dynamic_subtitles` on the *final* cut, after cuts/zooms are already applied — a connected title anchors to its parent clip's source-media coordinates, so re-cutting the timeline afterward can silently detach captions from the words they were built for.
+
+**Never treat generation as done without the second call.** The layout only guarantees non-overlap *by construction* for what it itself lays out — it cannot see a hand-edited title, stray content left over in a reused base file, or a word long/uppercase enough to have needed shrinking. `validate_subtitle_layout` re-measures every `<title>` independently and reports a severity (`none`/`warning`/`probable`/`severe`) plus per-issue suggested corrections:
+
+```
+"Validate the subtitle layout in /path/to/project_dynamic_subtitles.fcpxmld"
+```
+
+- `none`/`warning` (only `outside_safe_area`, no `outside_frame` or `collision`) — safe to deliver; the emphasis word sitting close to the 5% margin is expected on the diagrammed look.
+- `probable`/`severe` — investigate before touching code. Read the issue's exact FCPXML fraction times (not the rounded float) before deciding whether it's a real overlap; two titles that are only touching at a shared boundary can still round to "equal-looking but not bit-identical" floats and misreport. See `Engine/docs/03_SERVER_TOOLS.md`'s "Legendas dinâmicas" section and `Engine/docs/05_EXPERIENCIAS.md` (2026-08-19 entries) for the concrete bugs already found and fixed this way, and the checklist for the next one.
+
+---
+
 ## Composing Tools in AI Agent Workflows
 
 Each tool in this MCP server follows the same pattern: read FCPXML → process → write modified FCPXML. This makes them composable — the output of one tool is valid input for the next.