Add transcript line workflow rules

openspec/specs/meeting-session/spec.md

@@ -179,12 +179,14 @@ Meeting Assistant SHALL expose a diagnostic endpoint that reloads application co
 - **AND** future workflow events use the reloaded workflow automation configuration
 
 ### Requirement: Meeting automation rules support lifecycle triggers
-Meeting Assistant SHALL support rule triggers for `created`, `state_transition`, and `speaker_identified`.
+Meeting Assistant SHALL support rule triggers for `created`, `state_transition`, `speaker_identified`, and `transcript_line`.
 
 A `state_transition` trigger MAY filter by `from`, `to`, or both state values.
 
 A `speaker_identified` trigger MAY filter by speaker name.
 
+A `transcript_line` trigger MAY filter by speaker name.
+
 #### Scenario: State transition rule matches from and to
 - **GIVEN** a configured rule that triggers on a state transition from `collecting metadata` to `transcribing`
 - **WHEN** Meeting Assistant transitions that meeting from `collecting metadata` to `transcribing`
@@ -197,6 +199,12 @@ A `speaker_identified` trigger MAY filter by speaker name.
 - **WHEN** Meeting Assistant identifies speaker `Ada`
 - **THEN** it applies the rule steps
 
+#### Scenario: Transcript line rule rewrites masked profanity before persistence
+- **GIVEN** a configured rule that triggers on transcript line writes and sets `transcript.line` by replacing `*****` with `[redacted]`
+- **WHEN** Meeting Assistant writes a transcript line for speaker `Guest-1` containing `*****`
+- **THEN** the written transcript line contains `[redacted]`
+- **AND** the written transcript line does not contain `*****`
+
 ### Requirement: Meeting automation rules support conditions and steps
 Meeting Assistant SHALL support rule conditions using an expression engine.
 
@@ -206,6 +214,8 @@ Step values SHALL support Razor syntax against the current meeting event model.
 
 Step values SHALL treat `@` characters inside valid email address tokens as literal text rather than Razor transitions.
 
+Meeting Assistant SHALL expose the formatted transcript line and transcript speaker to `transcript_line` rule conditions and Razor step templates.
+
 Meeting Assistant SHALL support these initial rule steps:
 
 - `add_attendee`
@@ -214,6 +224,8 @@ Meeting Assistant SHALL support these initial rule steps:
 - `add_context`
 - `add_project`
 
+The `set_property` step SHALL support setting `transcript.line` during `transcript_line` events.
+
 #### Scenario: Nested conditions choose a matching rule
 - **GIVEN** a configured rule with nested `and`, `or`, and `not` conditions over meeting title, attendees, and event data
 - **WHEN** the condition evaluates to true
@@ -241,6 +253,11 @@ Meeting Assistant SHALL support these initial rule steps:
 - **WHEN** the rule runs
 - **THEN** Meeting Assistant can update the meeting title through `set_property`
 
+#### Scenario: Transcript line conditions can use the written line and speaker
+- **GIVEN** a configured `transcript_line` rule with conditions over `transcript.line` and `transcript.speaker`
+- **WHEN** Meeting Assistant writes a transcript line that matches both conditions
+- **THEN** it applies the rule steps before the line is persisted
+
 ### Requirement: Workflow rules and speaker identities can be edited through a tray-launched assistant
 Meeting Assistant SHALL expose an `Edit rules and identities` item from the tray icon menu.