Expand settings and logs agent tools

2026-06-01 21:07:08 +02:00
parent abac46c691
commit 11c65ce669
12 changed files with 1160 additions and 45 deletions
@@ -30,6 +30,8 @@ The settings/logs agent SHALL receive speaker sample tools to list, read, delete

 The settings/logs agent SHALL receive tools to read the local appsettings configuration file, write a complete valid JSON replacement for that file, read Meeting Assistant configuration documentation, read current or rotated application log files by tail or 1-based line range, search current or rotated application log files, search copied OpenSpec specification files, and read copied OpenSpec specification files by relative path and optional 1-based line range.

+The settings/logs agent SHALL receive in-process diagnostic tools for health, recording status, current meeting metadata lookup, recent speaker identity merging, workflow configuration reload, ASR file transcription, and ASR file diarization so those diagnostics do not require HTTP calls.
+
 Meeting Assistant SHALL copy specification markdown files from `openspec/specs` into build and publish output through a recursive include so future spec folders are included automatically.

 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`.
@@ -87,6 +89,11 @@ Meeting Assistant SHALL provide a diagnostic endpoint that opens the settings/lo
 - **THEN** it receives the requested file content or clamped 1-based line range
 - **AND** paths outside the copied specs tree are refused

+#### Scenario: Settings and logs assistant runs diagnostics without HTTP
+- **WHEN** the settings/logs agent requests health, recording status, current meeting metadata, speaker identity merge, workflow reload, or ASR file diagnostics
+- **THEN** Meeting Assistant runs the same in-process services used by the local diagnostic endpoints
+- **AND** returns the diagnostic result to the agent
+
 #### Scenario: New spec folders are included in output
 - **WHEN** a new markdown spec file is added under `openspec/specs`
 - **THEN** the application build includes it in the output under `openspec/specs`