Public Access
Fix past meeting summary tool edge cases
PR and Push Build/Test / build-and-test (push) Successful in 10m54s
PR and Push Build/Test / build-and-test (push) Successful in 10m54s
This commit is contained in:
@@ -37,7 +37,7 @@ The `search` tool SHALL refuse requested project scopes that are not assigned to
|
||||
- **THEN** `read_projectfile` clamps the requested range to the available file lines without failing
|
||||
|
||||
#### Scenario: Agent searches project knowledge
|
||||
- **WHEN** the agent calls `search` with ripgrep syntax keywords
|
||||
- **WHEN** the agent calls `search` with .NET regular expression keywords
|
||||
- **THEN** Meeting Assistant runs the search against the requested projects or the meeting-bound projects and returns matches as `filename:line text`
|
||||
|
||||
#### Scenario: Agent searches past project meeting summaries
|
||||
|
||||
@@ -52,12 +52,16 @@ The summary agent SHALL be able to list paginated past meeting summary notes for
|
||||
|
||||
The past meeting summary listing SHALL read summary notes from the configured summaries folder only.
|
||||
|
||||
The past meeting summary listing SHALL skip malformed or non-summary markdown files instead of failing the whole listing.
|
||||
|
||||
When no project filter is supplied to the past meeting summary listing, Meeting Assistant SHALL include past summaries assigned to any project assigned to the current meeting.
|
||||
|
||||
When a project filter is supplied to the past meeting summary listing, Meeting Assistant SHALL include only past summaries assigned to those requested projects and SHALL refuse requested projects not assigned to the current meeting.
|
||||
|
||||
The summary agent SHALL be able to read past project meeting summary files through a read-only tool. Meeting Assistant SHALL refuse reads for summary files outside the configured summaries folder, the current summary file, or summary files that do not belong to one of the current meeting's assigned projects.
|
||||
|
||||
When search results identify past meeting summaries with the `past-meetings/` prefix, the past meeting summary read tool SHALL accept that prefixed path.
|
||||
|
||||
The summary instructions SHALL clearly distinguish `write_summary`, which writes the current meeting's summary, from past meeting summary read tools, which are read-only historical context.
|
||||
|
||||
The summary pipeline SHALL write the summary note as a markdown artifact linked to the meeting note, transcript, and assistant context.
|
||||
@@ -223,6 +227,14 @@ When `delete_identity` is called with an existing transcript speaker identity, M
|
||||
- **WHEN** the summary agent lists past project meetings for `Project Z`
|
||||
- **THEN** Meeting Assistant refuses the request because `Project Z` is not assigned to the current meeting
|
||||
|
||||
#### Scenario: Past project meeting listing skips malformed notes
|
||||
- **GIVEN** the current meeting note is assigned to `Project X`
|
||||
- **AND** the summaries folder contains one valid prior `Project X` summary note
|
||||
- **AND** the summaries folder contains one markdown file with malformed frontmatter
|
||||
- **WHEN** the summary agent lists past project meetings
|
||||
- **THEN** Meeting Assistant returns the valid prior summary
|
||||
- **AND** does not fail because of the malformed file
|
||||
|
||||
#### Scenario: Past project meeting summary is read-only historical context
|
||||
- **GIVEN** the current meeting note is assigned to `Project X`
|
||||
- **AND** a prior summary note in the configured summaries folder is assigned to `Project X`
|
||||
@@ -230,6 +242,13 @@ When `delete_identity` is called with an existing transcript speaker identity, M
|
||||
- **THEN** Meeting Assistant returns the clamped inclusive line range
|
||||
- **AND** exposes no tool to write that prior summary note
|
||||
|
||||
#### Scenario: Past project meeting search paths can be read
|
||||
- **GIVEN** the current meeting note is assigned to `Project X`
|
||||
- **AND** a prior summary note in the configured summaries folder is assigned to `Project X`
|
||||
- **WHEN** the summary agent searches and receives a `past-meetings/` prefixed summary path
|
||||
- **THEN** the summary agent can pass that prefixed path to `read_past_project_meeting_summary`
|
||||
- **AND** Meeting Assistant reads the prior summary note
|
||||
|
||||
### Requirement: Meeting screenshots are captured into assistant context
|
||||
Meeting Assistant SHALL expose a configurable screenshot hotkey.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user