Add project sync guidance for corrected notes

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.