The suite's answer fields, for their labels and help.
Prefix for element ids, unique on the page.
The case's input, when there is one yet (null on "Add a case").
The form field to submit the answer under, as JSON.
The current answer, or null for a new one.
What an app's own answer editor gets, for answers plain fields can't edit well (a list of facts with a category each, a verdict with reasons). The editor is a client component that renders its own controls and keeps the whole answer, as JSON, in a form field named
name(a hidden input). Register it in your wiring module'sanswerEditors, keyed by suite; the copied answer key, "Add a case", and blind rating use it in place of the suite's answer fields, and the actions check what it submits against the suite'slabelValue.