Fix YAML escaping for meeting note frontmatter

2026-07-15 14:55:37 +02:00
parent 89d81fa4c6
commit 0e0feedad2
3 changed files with 158 additions and 3 deletions
@@ -44,6 +44,8 @@ The meeting note frontmatter SHALL link to the transcript, assistant context, an

 Generated artifact notes SHALL link only to the other notes from the same run and SHALL omit the frontmatter property that would reference themselves.

+Meeting Assistant SHALL escape generated meeting-note frontmatter string values after metadata enrichment and workflow rules have been applied, immediately before writing the final markdown file.
+
 #### Scenario: Meeting note links to generated artifacts
 - **WHEN** Meeting Assistant creates a meeting note
 - **THEN** the note frontmatter links to the configured transcript, assistant context, and summary note locations
@@ -59,6 +61,12 @@ Generated artifact notes SHALL link only to the other notes from the same run an
 - **THEN** the artifact frontmatter links to the other run notes
 - **AND** the artifact frontmatter omits the property for the artifact's own note type

+#### Scenario: Generated frontmatter remains parseable after attendee transforms
+- **GIVEN** meeting metadata or workflow rules produce an attendee name that contains a single quote
+- **WHEN** Meeting Assistant writes the final meeting note
+- **THEN** the attendee value is escaped in frontmatter
+- **AND** the meeting note frontmatter remains parseable when read back
+
 ### Requirement: Meeting notes preserve user-authored content
 Meeting Assistant SHALL preserve user-authored meeting notes and include them as input when generating summaries, decisions, and next steps.

@@ -354,4 +362,3 @@ Meeting Assistant SHALL provide a diagnostic endpoint that opens the workflow ru
 - **GIVEN** the rules editor chat window content fits without scrolling or is already near the bottom
 - **WHEN** a new user or assistant message is appended
 - **THEN** the conversation scrolls to the bottom of the newly rendered message content
-