Check the participants list in composition: E_PARTICIPANT_MISSING and E_PARTICIPANT_STALE #231

Parent

#195

What to build

Composition reads the participants list and refuses a render that silently omits a project (spec/v1/40-composition.md#participants, docs/adr/model/0043-participants-list-staleness.md). A participant with no fragment is E_PARTICIPANT_MISSING. One whose newest fragment is older than its maxAge (seven days by default) is E_PARTICIPANT_STALE, unless it is dormant. Either way it is isolated at its last composed fragment, never rendered absent (spec/v1/40-composition.md#a-missed-publish-is-a-deletion).

Today deploy-kit compose takes whatever fragments it is handed. The worked compose workflow records the gap where it pulls participants.

Acceptance criteria

• participants.yml has a schema in the model: maxAge with a written reason when overridden, and dormant with an owner, a reason and a review date. A review date in the past fails.
• composeEstate takes the participants list and the fragments' publish times. A missing or stale participant is isolated at its last composed fragment, with its code in the lock's isolated.
• A missing Platform document is E_PARTICIPANT_MISSING and fails the run.
• deploy-kit compose --participants <file> passes the list through, and the worked compose workflow uses it.
• Each code is exercised by a test (npm run lint:codes), with coverage and Stryker holding at 100.

Blocked by

• Compose the estate: a compose use-case and CLI, pin annotations and fragment versions #197