The product name and hostname below are Jake's decision; recommended name is WAVE Composer at compose.wave.online, per WAVE-COMPOSER-PRODUCT-SPEC.md.
What
Add a products.json manifest entry id:"composer" alongside the existing 53 products served at api.wave.online/.well-known/wave-products.json, carrying the standard seven fields: id, name, url, accent, status, blurb, cta[]. Set status:"preview" since Composer has no live surface yet.
Why
WAVE-COMPOSER-PRODUCT-SPEC.md section 9 says Composer must be built out fully, like every other product: API, CLI, MCP, and 402 all route through WAVE's one engine, so the human-facing surface is that same engine wearing a screen. Every live product (captions is the exemplar) starts with a manifest entry before it earns a generated projection, scopes, meters, or a spoke repo. Without this entry Composer is invisible to every downstream consumer of the catalog, including wave-www's generator.
Done means
- products.json has one new object with id:"composer" and all seven fields populated.
- api.wave.online/.well-known/wave-products.json serves 54 entries including composer.
- status is "preview".
Dependencies
wave-console #453 to #460 are the E1 object-management half (flows table and routes, createdBy/sourceFlowId/createdAt columns, a proposal record for diff/approve/reject, connections list/revoke, re-run, one undo per object) and hard-gate the Composer write path per the spec's phase table. This manifest entry is not gated by them; it only advertises the product.
Receipts
wave-pen PR #441.
The product name and hostname below are Jake's decision; recommended name is WAVE Composer at compose.wave.online, per WAVE-COMPOSER-PRODUCT-SPEC.md.
What
Add a products.json manifest entry id:"composer" alongside the existing 53 products served at api.wave.online/.well-known/wave-products.json, carrying the standard seven fields: id, name, url, accent, status, blurb, cta[]. Set status:"preview" since Composer has no live surface yet.
Why
WAVE-COMPOSER-PRODUCT-SPEC.md section 9 says Composer must be built out fully, like every other product: API, CLI, MCP, and 402 all route through WAVE's one engine, so the human-facing surface is that same engine wearing a screen. Every live product (captions is the exemplar) starts with a manifest entry before it earns a generated projection, scopes, meters, or a spoke repo. Without this entry Composer is invisible to every downstream consumer of the catalog, including wave-www's generator.
Done means
Dependencies
wave-console #453 to #460 are the E1 object-management half (flows table and routes, createdBy/sourceFlowId/createdAt columns, a proposal record for diff/approve/reject, connections list/revoke, re-run, one undo per object) and hard-gate the Composer write path per the spec's phase table. This manifest entry is not gated by them; it only advertises the product.
Receipts
wave-pen PR #441.