nextcloud-vue 2.33.0 lets a `choice` setup step render as a grid of cards over
a list the SERVER owns: `display: "cards"` picks the renderer, `optionsSource`
names the key in the app's own /api/setup/status document to read the options
from. decidiq is the first consumer, and its manifest stops carrying a
hand-written copy of that list entirely.

The vendored schema here has to know both keys before that manifest exists.
check_manifest.js deliberately prefers this CANONICAL copy over the app's
pinned node_modules copy, so a stale copy rejects a correct manifest and names
the app rather than itself. That has now happened five times, most recently
with the store plane at 2.29.0 against 2.32.0.

Family N is the acceptance arm, in the shape families K and M established:

  N1  the currency arm — the step decidiq ships, `display: "cards"` plus
      `optionsSource` plus `multiple`, must PASS on gate-22 and gate-53
  N2  a typo'd step key (`displayy`) must still FAIL, or the step's
      additionalProperties was loosened rather than extended
  N3  `display: "carousel"` must still FAIL, or the enum was dropped

N1 alone would pass just as well against a schema "fixed" either of those two
ways, which is why it is not alone.

Co-authored-by: Conduction Release Bot <release-bot@conduction.nl>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>