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.
19 lines
1.3 KiB
Markdown
19 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Projects have compact discovery metadata
|
|
Each project SHALL use a root `PROJECT.md` with YAML frontmatter `name` and `description` for agent-maintained discovery metadata. `name` SHALL be the display name; the project ID SHALL remain its direct subfolder name. The summarizer SHALL be instructed to create and maintain this metadata for associated projects from grounded project knowledge, preserving other frontmatter and body content. The description SHALL contain at most 256 characters.
|
|
|
|
Catalog lookup SHALL tolerate missing or malformed metadata by falling back to the ID as display name and an empty description. Metadata lookup SHALL NOT grant access to project files or instructions.
|
|
|
|
#### Scenario: Project has metadata
|
|
- **WHEN** a project has valid name and description frontmatter
|
|
- **THEN** catalog lookup exposes its ID, display name, and description
|
|
|
|
#### Scenario: Legacy project has no metadata
|
|
- **WHEN** a project has no PROJECT.md or no usable frontmatter
|
|
- **THEN** it remains discoverable with its ID as display name and an empty description
|
|
|
|
#### Scenario: Agent writes invalid metadata
|
|
- **WHEN** the summarizer attempts a PROJECT.md update without valid name/description or with a description longer than 256 characters
|
|
- **THEN** the write is refused without changing the existing file
|