Add resilient Azure offline transcription backlog

docs/meeting-workflow-engine.md

@@ -68,7 +68,7 @@ The engine runs when `MeetingRecordingCoordinator` emits a meeting workflow even
 - `created`: after the meeting note and assistant context artifact are created.
 - `state_transition`: after the assistant context state moves forward.
 - `speaker_identified`: when live or final speaker identification reports a display name.
-- `transcript_line`: before a formatted transcript line is appended or used in a transcript rewrite.
+- `transcript_line`: after a formatted live transcript line is durably appended, before any changed line is rewritten in place, and before lines are used in full transcript rewrites.
 
 For every event, the engine:
 
@@ -80,9 +80,9 @@ For every event, the engine:
 6. Saves the meeting note once if any meeting-note step changed it.
 7. Updates assistant-context frontmatter links/title from the saved meeting note after note changes.
 
-For `transcript_line` events, the engine returns the possibly updated transcript line to the caller. Live transcript appends, live speaker relabel rewrites, final diarization rewrites, and final speaker-identity rewrites all pass their formatted lines through this event before writing markdown.
+For `transcript_line` events, the engine returns the possibly updated transcript line to the caller. Live transcript appends first write the original formatted line and keep a reference to that exact body line, then run transcript-line rules out of band. Later transcript segments can continue to be appended while the workflow runs. If rules return a changed line, Meeting Assistant rewrites the referenced line in the transcript file. If a transcript-line rule fails during live recording, Meeting Assistant logs the failure and keeps the original line so later transcript segments can continue to be written.
 
-Rules are best-effort automation. The settings/logs write tool rejects invalid YAML, unknown steps, unsupported set-property fields, trigger or condition entries without a supported key, and step value Razor templates that fail against the workflow template model before writing the rules file. Invalid NCalc expressions can still fail at workflow runtime and should be covered by tests before the engine is broadened.
+Rules are best-effort automation for live transcript persistence. The settings/logs write tool rejects invalid YAML, unknown steps, unsupported set-property fields, trigger or condition entries without a supported key, and step value Razor templates that fail against the workflow template model before writing the rules file. Invalid NCalc expressions can still fail at workflow runtime. Workflow execution logs every triggered rule with its rule name and event type, logs completion with whether the note or transcript line changed, and logs rule failures with the rule name and event type.
 
 ## YAML Shape
 
@@ -227,6 +227,10 @@ valid email address token. Literal email addresses such as `Support@contoso.com`
 unchanged; if the same value also contains a Razor expression, the email `@` is escaped
 before rendering so the address still appears normally in the rendered result.
 
+Rendered values are plain text for markdown artifacts, not HTML. UTF-8 characters such as
+`ß`, `ö`, and `ä` are preserved after Razor rendering instead of being persisted as HTML
+entities.
+
 ## Steps
 
 ### `add_attendee`
@@ -251,7 +255,7 @@ steps:
 
 ### `set_property`
 
-Sets a supported property. Supported meeting properties are `title` and `meeting.title`. During `transcript_line` events, `transcript.line` is also supported and replaces the single formatted line that will be written.
+Sets a supported property. Supported meeting properties are `title` and `meeting.title`. During `transcript_line` events, `transcript.line` is also supported. For live transcription, changing `transcript.line` rewrites the referenced formatted line after the workflow task completes.
 
 ```yaml
 steps: