Update actions/checkout action to v7

MeetingAssistant.Tests/MeetingAssistant.Tests.csproj

@@ -10,7 +10,7 @@
   <ItemGroup>
     <PackageReference Include="coverlet.collector" Version="10.0.1" />
     <PackageReference Include="Microsoft.AspNetCore.Mvc.Testing" Version="10.0.8" />
-    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.6.0" />
+    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.7.0" />
     <PackageReference Include="xunit" Version="2.9.3" />
     <PackageReference Include="xunit.runner.visualstudio" Version="3.1.5" />
   </ItemGroup>

MeetingAssistant.Tests/WorkflowRulesEditorTests.cs

@@ -721,6 +721,10 @@ public sealed class WorkflowRulesEditorTests
         Assert.Contains("read_logs", instructions);
         Assert.Contains("read_spec_file", instructions);
         Assert.Contains("list_recent_summaries", instructions);
+        Assert.Contains("When correcting a meeting note that has project references", instructions);
+        Assert.Contains("read that project's AGENTS.md", instructions);
+        Assert.Contains("new project reference", instructions);
+        Assert.Contains("matching correction", instructions);
     }
 
     [Fact]

MeetingAssistant/MeetingAssistant.csproj

@@ -20,7 +20,7 @@
   </ItemGroup>
 
   <ItemGroup>
-    <PackageReference Include="Microsoft.Agents.AI.OpenAI" Version="1.10.0" />
+    <PackageReference Include="Microsoft.Agents.AI.OpenAI" Version="1.11.0" />
     <PackageReference Include="DiffPlex" Version="1.9.0" />
     <PackageReference Include="Microsoft.CognitiveServices.Speech" Version="$(MicrosoftSpeechVersion)" />
     <PackageReference Include="Microsoft.CognitiveServices.Speech.Extension.MAS" Version="$(MicrosoftSpeechVersion)" ExcludeAssets="build" />
@@ -28,7 +28,7 @@
     <PackageReference Include="NAudio" Version="2.3.0" />
     <PackageReference Include="NCalcSync" Version="5.12.0" />
     <PackageReference Include="RazorLight" Version="2.3.1" />
-    <PackageReference Include="System.Drawing.Common" Version="10.0.8" />
+    <PackageReference Include="System.Drawing.Common" Version="10.0.9" />
     <PackageReference Include="Whisper.net" Version="1.9.1" />
     <PackageReference Include="Whisper.net.Runtime" Version="1.9.1" />
     <PackageReference Include="YamlDotNet" Version="18.0.0" />

MeetingAssistant/Workflow/WorkflowRulesEditorInstructionBuilder.cs

@@ -27,6 +27,7 @@ public sealed class WorkflowRulesEditorInstructionBuilder : IWorkflowRulesEditor
         Use list_recent_summaries, read_summary, read_transcript, read_meeting_note, read_context, and the matching search tools when the user wants help post-processing meeting notes or investigating past meeting artifacts.
         Prefer list_recent_summaries first when the user refers to recent meetings without naming an exact file.
         Use the matching write_summary, write_transcript, write_meeting_note, write_context, and *_frontmatter tools only to repair or post-process meeting artifacts the user asked you to change. Prefer the frontmatter-specific tools when only metadata needs repair.
+        When correcting a meeting note that has project references, also check whether the affected project knowledge needs an update. For each affected project, read that project's AGENTS.md when it exists and follow it before writing project files. If no project AGENTS.md exists, use judgment based on the correction: when adding a new project reference, review the corrected note broadly for project-relevant information to add; when changing specific information for an existing project reference, check whether the project needs the matching correction.
         Use get_health, get_recording_status, diagnose_current_meeting, merge_recent_speaker_identities, reload_workflow_configuration, diagnose_asr_transcribe_file, and diagnose_asr_diarize_file for diagnostics that would otherwise require local HTTP endpoints.
         Use search_identities and read_identity before changing identities unless the user gives an exact identity id.
         Prefer updating identities by id, not by guessed name. If a user asks about names, search first and confirm ambiguity in your final response.

openspec/changes/sync-projects-after-note-corrections/proposal.md

@@ -0,0 +1,14 @@
+## Why
+
+Meeting notes are often corrected after the original summary run. When a corrected note is tied to project knowledge, the settings/logs assistant should carry those corrections through to the affected project files instead of leaving project knowledge stale.
+
+## What Changes
+
+- Add settings/logs assistant instructions for post-correction project synchronization.
+- Require the assistant to follow a referenced project's `AGENTS.md` when present.
+- Require the assistant to use judgment when no project instructions exist, with broader review for newly added project references and targeted review for corrections to existing references.
+
+## Impact
+
+- Affects the built-in settings/logs assistant prompt.
+- No new tool surface is required; the assistant already has meeting artifact and project read/write tools.

openspec/changes/sync-projects-after-note-corrections/specs/meeting-summary/spec.md

@@ -0,0 +1,18 @@
+## MODIFIED Requirements
+### Requirement: Meeting Assistant generates meeting outputs
+The settings/logs agent SHALL instruct meeting-note correction workflows to keep project knowledge consistent when the corrected meeting note has project references.
+
+When a corrected meeting note adds a new project reference, the settings/logs agent SHALL inspect the corrected note broadly enough to find project-relevant information that should be written to that project.
+
+When a corrected meeting note changes specific content for an existing project reference, the settings/logs agent SHALL check whether corresponding project knowledge needs the same correction.
+
+For each affected project, when an `AGENTS.md` file exists directly in the project folder, the settings/logs agent SHALL follow those project instructions before updating the project. When no project `AGENTS.md` exists, the settings/logs agent SHALL use judgment to decide what project file updates are warranted by the note correction.
+
+#### Scenario: Settings/logs agent syncs corrected meeting notes to projects
+- **GIVEN** the settings/logs agent corrects a meeting note with project references
+- **WHEN** a referenced project has an `AGENTS.md`
+- **THEN** the settings/logs instructions tell the agent to follow that project's instructions before updating the project
+- **WHEN** a corrected note adds a new project reference
+- **THEN** the instructions tell the agent to review the corrected note for project-relevant information to add to that project
+- **WHEN** a corrected note changes specific information for an existing project reference
+- **THEN** the instructions tell the agent to check whether project knowledge needs a matching correction

openspec/changes/sync-projects-after-note-corrections/tasks.md

@@ -0,0 +1,4 @@
+- [x] 1. Add OpenSpec scenario for syncing project knowledge after corrected meeting notes.
+- [x] 2. Add a focused instruction-builder test for the new settings/logs guidance.
+- [x] 3. Update the built-in settings/logs assistant instructions.
+- [x] 4. Run focused tests and `openspec validate sync-projects-after-note-corrections --strict`.