Archive completed meeting assistant changes

openspec/specs/meeting-summary/spec.md

@@ -4,32 +4,22 @@
 TBD - created by archiving change define-meeting-assistant-v1. Update Purpose after archive.
 ## Requirements
 ### Requirement: Meeting Assistant generates meeting outputs
-The summary note SHALL keep frontmatter links to meeting artifacts and SHALL copy `title`, `start_time`, `end_time`, `attendees`, and `projects` from the meeting note when available. If the meeting note has no title, the summary agent SHALL be able to provide a title when writing the summary.
+The settings/logs agent SHALL instruct meeting-note correction workflows to keep project knowledge consistent when the corrected meeting note has project references.
 
-When the summary agent calls `write_summary` with a non-empty `title` parameter, Meeting Assistant SHALL update the current meeting note title and write that title to the summary note frontmatter.
+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 the summary agent calls `write_summary` without a `title` parameter or with a blank `title` parameter, Meeting Assistant SHALL keep the existing meeting note title and summary title behavior.
+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.
 
-The summary instructions SHALL tell the summary agent to provide a concise `title` parameter to `write_summary` when the meeting note still has a generated default title and the meeting purpose is clear from context.
+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: Summary agent renames default-titled meeting
-- **GIVEN** the current meeting note has a generated default title
-- **AND** the meeting purpose is clear from transcript, user notes, or assistant context
-- **WHEN** the summary agent writes the summary
-- **THEN** the summary instructions tell the agent to provide a concise `title` parameter
-- **AND** Meeting Assistant updates the meeting note title and summary note title to the provided title
-
-#### Scenario: Summary title parameter is omitted
-- **GIVEN** the current meeting note has an existing title
-- **WHEN** the summary agent writes the summary without a title parameter
-- **THEN** Meeting Assistant keeps the existing meeting note title
-- **AND** writes the existing title to the summary note frontmatter
-
-#### Scenario: Summary title parameter is blank
-- **GIVEN** the current meeting note has an existing title
-- **WHEN** the summary agent writes the summary with a blank title parameter
-- **THEN** Meeting Assistant keeps the existing meeting note title
-- **AND** writes the existing title to the summary note frontmatter
+#### 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
 
 ### Requirement: Meeting screenshots are captured into assistant context
 Meeting Assistant SHALL expose a configurable screenshot hotkey.
@@ -50,6 +40,14 @@ When OCR returns valid crop coordinates within the original image bounds, Meetin
 
 When OCR returns no crop coordinates or invalid crop coordinates, Meeting Assistant SHALL keep the original screenshot link and OCR result without writing a cropped image.
 
+After transcription finishes and before summarization starts, Meeting Assistant SHALL scan the meeting note for user-authored Obsidian image embeds and Markdown image embeds.
+
+When configured screenshot OCR is enabled and the meeting note contains image embeds, Meeting Assistant SHALL append each resolvable image to the assistant context note, state that the image came from the meeting note, preserve the original embed text for cross-reference, and run OCR for the linked image.
+
+Meeting-note image OCR SHALL NOT copy the image file, SHALL NOT write crop images, SHALL NOT add attendees from OCR metadata, and SHALL NOT modify the meeting note.
+
+Meeting Assistant SHALL wait for meeting-note image OCR to finish or time out before transitioning the assistant context to summarizing.
+
 When screenshot OCR is not configured, Meeting Assistant SHALL skip OCR and keep the screenshot link.
 
 The default OCR prompt SHALL explain that the image is from a meeting and ask the model to identify who is talking, who is presenting, what is presented, capture slide text in markdown, convert diagrams to Mermaid when possible, indicate whether visible people are clearly the exact meeting participants or only a partial result, return crop coordinates only for confidently isolated presentation/shared-screen content, and otherwise describe the scene.
@@ -73,6 +71,16 @@ The default OCR prompt SHALL explain that the image is from a meeting and ask th
 - **THEN** Meeting Assistant saves a cropped screenshot beside the original image
 - **AND** links the cropped screenshot before the OCR text in assistant context
 
+#### Scenario: Meeting note image embeds are OCRed before summarization
+- **GIVEN** screenshot OCR is configured
+- **AND** the meeting note contains `![[whiteboard.png]]`
+- **AND** the meeting note contains `![Diagram](attachments/diagram.png)`
+- **WHEN** transcription finishes
+- **THEN** Meeting Assistant appends both images to the assistant context as images from the meeting note
+- **AND** includes the original embed text for each image
+- **AND** runs OCR for each image without copying files, writing crop images, adding attendees, or modifying the meeting note
+- **AND** waits for this OCR to finish or time out before transitioning to summarizing
+
 #### Scenario: OCR is skipped when not configured
 - **GIVEN** screenshot OCR is not configured
 - **WHEN** the user captures a screenshot
@@ -131,3 +139,4 @@ The summary-agent instructions SHALL tell the agent to keep the one-line summary
 - **WHEN** the summary agent calls `write_summary` with a one-line summary containing a line break
 - **THEN** Meeting Assistant refuses the write
 - **AND** does not mark the summary as written
+