The demo data covers whichever states someone noticed were missing #32

New Issue

2026-09-21T07:18:10Z

cgalo5758 commented

2026-09-21 07:18:10 +00:00

What a person cannot do today

See every state an operator page can render without contriving it. The demo data has grown one state at a time, each added after a screenshot showed the state could not be demonstrated: the invoice states and the canceling subscription came that way, and the empty actor column on the activity feed is the same gap.

What they should be able to do

Derive the demo world's coverage from the states the console can render, so that every badge and every status a surface knows how to draw exists somewhere in the data, and a new state is either seeded or deliberately listed as unseeded.

Why it matters

A state nobody seeds is a state nobody reviews, and the screenshot sheets and the accessibility checks only ever see the states the data happens to contain.

Where

internal/demoseed, and the badge and status vocabularies the operator surfaces render.

Done when

The seed's coverage is checked against those vocabularies rather than maintained by hand, and the two known gaps are closed: no seeded product confers the wiki-site allowance, so no demo member can hold one and the member site card always shows its no-entitlement branch; and three seeded products carry no entitlement set at all, a state the console's own create form cannot produce. A demo that exercises delivery needs at least one product carrying the site allowance on a ladder, one price mapped at the payment provider, and one grant issued by a person.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today See every state an operator page can render without contriving it. The demo data has grown one state at a time, each added after a screenshot showed the state could not be demonstrated: the invoice states and the canceling subscription came that way, and the empty actor column on the activity feed is the same gap. ## What they should be able to do Derive the demo world's coverage from the states the console can render, so that every badge and every status a surface knows how to draw exists somewhere in the data, and a new state is either seeded or deliberately listed as unseeded. ## Why it matters A state nobody seeds is a state nobody reviews, and the screenshot sheets and the accessibility checks only ever see the states the data happens to contain. ## Where [`internal/demoseed`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/demoseed), and the badge and status vocabularies the operator surfaces render. ## Done when The seed's coverage is checked against those vocabularies rather than maintained by hand, and the two known gaps are closed: no seeded product confers the wiki-site allowance, so no demo member can hold one and the member site card always shows its no-entitlement branch; and three seeded products carry no entitlement set at all, a state the console's own create form cannot produce. A demo that exercises delivery needs at least one product carrying the site allowance on a ladder, one price mapped at the payment provider, and one grant issued by a person. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

enhancement

area/testing labels 2026-09-21 07:18:10 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#32