Public Access
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.
26 lines
1.9 KiB
Markdown
26 lines
1.9 KiB
Markdown
## Why
|
|
|
|
The summarizer cannot currently discover missing project associations or propose workflow improvements with explicit user approval. Project folder names alone do not provide enough context for selecting the right project.
|
|
|
|
## What Changes
|
|
|
|
- Maintain `PROJECT.md` frontmatter with `name` and a description of at most 256 characters through the summarizer's existing project-file tools.
|
|
- Include available project metadata alongside bound project instructions and expose the full project metadata catalog through `list_projects`.
|
|
- Add `request_project_association` with a project ID and a reason of at most 100 characters. Wait up to ten minutes for a native Yes/No notification; approval adds the association and returns project instructions.
|
|
- Enforce meeting association for summarizer project-file writes as well as reads. Catalog visibility alone does not grant project access.
|
|
- Add nonblocking `request_workflow_change` with a short intention and detailed scenario/specification. Approval opens a settings-agent conversation and immediately submits the detailed request; the summarizer cannot edit workflows directly.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
- `summary-agent-requests`: User approval for blocking project association and asynchronous workflow-change handoff.
|
|
|
|
### Modified Capabilities
|
|
- `project-knowledge`: Project identity and discovery metadata in `PROJECT.md`.
|
|
- `agent-project-tools`: Full metadata catalog and association-scoped writes.
|
|
- `meeting-summary`: Project metadata in initial instructions and guidance for metadata maintenance and requests.
|
|
|
|
## Impact
|
|
|
|
Summary tools and agent instructions, project lookup and meeting frontmatter, native Windows notifications, the settings-agent window/prompt submission, DI registration, tests, and workflow/configuration documentation. Existing project IDs remain directory names; no bulk vault migration or live service restart is required.
|