Public Access
codex
7b2bcd3631
PR and Push Build/Test / build-and-test (push) Successful in 12m0s
Append successful offline recovery with a duplicate-warning marker and retain failed replay sources. Offer newly available microphones through confirmation notifications. Add project discovery metadata and blocking association approval, plus nonblocking workflow requests that start a separate settings-agent conversation. Include regression tests, OpenSpec changes, and verified local Release startup.
24 lines
1.9 KiB
Markdown
24 lines
1.9 KiB
Markdown
## MODIFIED Requirements
|
|
|
|
### Requirement: Summary agent receives bound project instructions
|
|
Meeting Assistant SHALL append a project section for projects bound to the meeting note frontmatter. Each entry SHALL identify the project ID and include its display name and description from PROJECT.md when available. For each bound project with a root AGENTS.md, the entry SHALL also include that file's content. Metadata SHALL appear even when AGENTS.md is absent. Unassociated project instructions SHALL NOT be appended.
|
|
|
|
#### Scenario: Project AGENTS files are appended
|
|
- **GIVEN** the meeting note frontmatter lists projects Alpha and Beta with root AGENTS.md files
|
|
- **WHEN** the summary agent is created
|
|
- **THEN** its project section includes both project IDs and their instructions
|
|
|
|
#### Scenario: Project metadata without instructions is appended
|
|
- **GIVEN** a bound project has PROJECT.md metadata but no AGENTS.md
|
|
- **WHEN** the summary agent is created
|
|
- **THEN** its entry contains ID, display name and description
|
|
|
|
## ADDED Requirements
|
|
|
|
### Requirement: Summarizer maintains project metadata and proposes missing associations
|
|
Both default and custom summary-agent instructions SHALL explain the full metadata catalog, the distinction between catalog visibility and project access, and the approval process. They SHALL instruct the agent to propose plausible missing associations with concise evidence before finalizing the summary and to maintain associated PROJECT.md name and description (maximum 256 characters). They SHALL explain that workflow improvements require a short intention and a detailed request and are executed only by the settings agent after user approval.
|
|
|
|
#### Scenario: Custom base prompt still receives capability guidance
|
|
- **WHEN** a custom summary base prompt is configured
|
|
- **THEN** the resulting instructions still explain metadata maintenance, association approvals and workflow-change requests
|