Add taskbar controls and summary oneliner

This commit is contained in:
2026-05-27 23:31:40 +02:00
parent 7777b349a5
commit 71f1e6a0b8
22 changed files with 720 additions and 9 deletions
@@ -0,0 +1,13 @@
## Why
Meeting summaries are useful as full notes, but downstream views and file lists also need a very short human-readable blurb without parsing the full markdown body.
## What Changes
- Require the summary agent to provide a one-line summary when calling `write_summary`.
- Reject one-line summaries containing line breaks.
- Store the one-line summary in summary note frontmatter.
- Update default summary-agent instructions to keep the one-line summary very short and concise.
## Impact
- Changes the `write_summary` tool signature.
- Adds summary frontmatter field `oneliner`.
- Adds focused tests for validation, frontmatter output, and instructions.
@@ -0,0 +1,18 @@
## ADDED Requirements
### Requirement: Summary note includes a one-line blurb
The `write_summary` tool SHALL require a one-line summary parameter in addition to the markdown summary body.
Meeting Assistant SHALL reject `write_summary` calls when the one-line summary contains line breaks.
Meeting Assistant SHALL write the one-line summary into summary note frontmatter as `oneliner`.
The summary-agent instructions SHALL tell the agent to keep the one-line summary very short, blurb-like, and concise, with complete sentences not required.
#### Scenario: Summary one-liner is written to frontmatter
- **WHEN** the summary agent calls `write_summary` with markdown content and one-line summary `Architecture risks and next steps`
- **THEN** Meeting Assistant writes `oneliner: Architecture risks and next steps` to the summary note frontmatter
#### Scenario: Multiline one-liner is rejected
- **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
@@ -0,0 +1,13 @@
## 1. Specification
- [x] Add summary one-liner requirements and scenarios.
## 2. Behavior
- [x] Require `oneliner` in the `write_summary` tool signature.
- [x] Validate `oneliner` does not contain line breaks.
- [x] Write `oneliner` to summary note frontmatter.
- [x] Instruct the summary agent to keep the one-liner very short.
## 3. Verification
- [x] Add focused behavior tests.
- [x] Run relevant tests.
- [x] Validate OpenSpec change.