Manuel/meeting-assistant
Public Access
1
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity Open in Coder

Strengthen workflow automation diagnostics

Browse Source
This commit is contained in:
codex
2026-05-27 12:55:19 +02:00
parent b114071957
commit 2422236ef7
8 changed files with 629 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/add-meeting-automation-rules/specs/meeting-session/spec.md
+8
View File
@@ -8,6 +8,8 @@ The local rules file SHALL be ignored by source control.
Rules SHALL be evaluated against the latest meeting note data read from disk for each event.
Meeting Assistant SHALL expose a diagnostic endpoint that reloads application configuration so workflow automation configuration changes can be picked up without restarting the application.
#### Scenario: Missing rules file is ignored
- **WHEN** Meeting Assistant handles a meeting event and no configured rules file exists
- **THEN** it leaves the meeting note and assistant context unchanged
@@ -17,6 +19,12 @@ Rules SHALL be evaluated against the latest meeting note data read from disk for
- **WHEN** Meeting Assistant creates a meeting note without attendees
- **THEN** it adds the configured attendee to the meeting note
#### Scenario: Workflow configuration is reloaded diagnostically
- **GIVEN** the workflow automation configuration has changed on disk
- **WHEN** the diagnostic workflow reload endpoint is called
- **THEN** Meeting Assistant reloads application configuration without restarting
- **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`.
openspec/changes/add-meeting-automation-rules/tasks.md
+3
View File
@@ -5,8 +5,11 @@
- [x] 1.4 Render step values with Razor syntax.
- [x] 1.5 Apply supported steps to meeting notes and assistant context.
- [x] 1.6 Fire rules from meeting creation, state transitions, and speaker identification.
- [x] 1.7 Add a diagnostic workflow configuration reload endpoint.
## 2. Verification
- [x] 2.1 Cover created, state-transition, and speaker-identified paths.
- [x] 2.2 Cover nested condition logic and templated values.
- [x] 2.3 Run relevant tests and strict OpenSpec validation.
- [x] 2.4 Cover diagnostic workflow configuration reload behavior.
- [x] 2.5 Cover expanded workflow trigger, condition, parameter, templating, ordering, step, and rules-file reload scenarios.