Add tray rules and identities editor

openspec/specs/meeting-session/spec.md

@@ -182,3 +182,73 @@ Meeting Assistant SHALL support these initial rule steps:
 - **GIVEN** a configured state-transition rule that matches a title containing a configured marker
 - **WHEN** the rule runs
 - **THEN** Meeting Assistant can update the meeting title through `set_property`
+
+### 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.
+
+The tray icon SHALL be implemented through the Uno notification icon stack.
+
+The tray icon menu SHALL show every configured launch profile when recording can be started and SHALL include each profile's configured toggle hotkey in the corresponding start or switch menu item.
+
+When the user selects `Edit rules and identities`, Meeting Assistant SHALL open a basic MewUI chat window for editing the configured workflow rules file and speaker identities.
+
+The chat window SHALL be titled `Edit rules and identities`, SHALL display user and assistant messages as visually distinct cards, SHALL display basic markdown emphasis, inline code, fenced code blocks, pipe tables rendered as grid views, and line breaks in agent responses, SHALL display a plain `Thinking...` line while the agent is working, SHALL provide a multiline text input at the bottom with placeholder text for asking to make a rule or list identities, SHALL send on Enter, SHALL insert a newline on Shift+Enter, and SHALL provide an explicit Send button.
+
+When a new chat message or thinking state is appended, the chat window SHALL scroll to the bottom of the newly rendered content if the conversation was already near the bottom or did not need scrolling before the append.
+
+The Windows executable and rules-and-identities editor window SHALL use the Meeting Assistant application icon so the editor has a taskbar icon.
+
+The rules editor agent SHALL be configured from the summarizer agent settings by default, while allowing workflow-rules-editor-specific endpoint, key, model, reasoning, reconnection, output, and compaction settings to override those defaults.
+
+The rules and identities editor agent SHALL include the workflow engine documentation in its system prompt and SHALL receive read, write, and search tools scoped to the configured workflow rules file.
+
+The rules and identities editor agent SHALL receive speaker identity tools to search/list, read, create, update, delete, and merge identities in the local speaker identity database.
+
+The rules and identities editor agent SHALL receive speaker sample tools to list, read, delete, and queue playback of samples linked to identities.
+
+The first model request caused by each user-submitted chat turn SHALL send the `X-Initiator: user` header, while follow-up model requests within that same turn, such as tool-call continuations, SHALL send `X-Initiator: agent`.
+
+Meeting Assistant SHALL provide a diagnostic endpoint that opens the workflow rules editor through the same window service used by the tray menu.
+
+#### Scenario: Tray menu opens the editor
+- **WHEN** the user opens the tray icon menu
+- **THEN** the menu includes `Edit rules and identities`
+- **WHEN** the user selects `Edit rules and identities`
+- **THEN** Meeting Assistant opens the workflow rules and identities editor chat window
+
+#### Scenario: Tray menu shows configured profile hotkeys
+- **GIVEN** the `default` launch profile uses `Ctrl+Alt+M`
+- **AND** the `english` launch profile uses `Ctrl+Alt+E`
+- **WHEN** the user opens the tray icon menu while Meeting Assistant is idle
+- **THEN** the menu includes a start item for `default` showing `Ctrl+Alt+M`
+- **AND** the menu includes a start item for `english` showing `Ctrl+Alt+E`
+
+#### Scenario: Rules editor can be opened diagnostically
+- **WHEN** a diagnostic caller requests the workflow rules editor to open
+- **THEN** Meeting Assistant invokes the workflow rules editor window service
+
+#### Scenario: Rules editor is scoped to the configured rules file
+- **GIVEN** a configured workflow rules file
+- **WHEN** the rules editor agent runs
+- **THEN** its read, write, and search tools can access only that configured workflow rules file
+- **AND** its system prompt includes the workflow engine documentation
+
+#### Scenario: Rules editor can manage speaker identities
+- **GIVEN** the speaker identity database contains speaker identities and samples
+- **WHEN** the rules editor agent runs
+- **THEN** it can search, read, create, update, delete, and merge speaker identities
+- **AND** it can list, read, delete, and queue playback of identity samples
+
+#### Scenario: User sends a rules-editing chat turn
+- **GIVEN** the rules editor chat window is open
+- **WHEN** the user types a prompt and presses Enter
+- **THEN** the user message appears in the conversation
+- **AND** a plain `Thinking...` line appears while the agent is running
+- **AND** the first model request for that turn is marked as user-initiated
+- **AND** the final assistant response replaces the thinking line
+
+#### Scenario: Chat auto-scrolls after appended content
+- **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
+