Plain words in rule errors and the submit API docs

[PhilReinking]

The rule errors the editor shows now use the editor's words ("question", "rule", "condition") instead of field names like "source block" or "evaluate". The API docs for submitting a form no longer say "multiple choice".

Part of BITS-287

• Example: "Pick a question for condition 1." instead of "The source block for your Inputs defined for Multiple Choice should be reused for Radio (vice-versa) #1 condition is required."
• Same for Refuse rules that point to a missing question, list the rules that use each question #264's check of a deleted question: "Pick a question from this form for condition 1."
• The docs now say only checkbox and consent questions send a list of answers. Single choice sends one, as the public form does.

Tested: full PHP suite on MariaDB, and in CI after the main merge. The new test lines fail with the old texts.

🤖 Generated with Claude Code

[PhilReinking]

OK at a781985, CI green. Two shoulds inline.

The new test fails with main's messages, and "condition 1" is the first condition, as the editor numbers them. The other messages match the editor: question, comparison, and/or, hide/show/go to. The API docs still build with Scribe.

[PhilReinking]

Should: single choice sends one payload-object, not a list. The public form uses setResponse for single choice and toggleResponse (a list) only for checkbox and consent (ButtonAction.vue:150, ConsentAction.vue:68). The server takes both shapes, so nothing breaks, but the docs say otherwise, and two picks in the example fit only checkboxes.

Suggested change

	For single choice, checkbox and consent questions, the payload is an array of payload-objects.
	DESC, example: [
	'7j' => ['payload' => 'Secret', 'actionId' => '59R'],
	'4x1' => ['payload' => 'mail@example.com', 'actionId' => 'pQ6'],
	// For multiple choice questions, the payload is an array of the selected options
	// For single choice and checkbox questions, the payload is an array of the selected choices
	For checkbox and consent questions, the payload is an array of payload-objects, one for each ticked choice or policy. A single choice question sends one payload-object for the picked choice.
	DESC, example: [
	'7j' => ['payload' => 'Secret', 'actionId' => '59R'],
	'4x1' => ['payload' => 'mail@example.com', 'actionId' => 'pQ6'],
	// For checkbox questions, the payload is an array of the ticked choices

[PhilReinking]

Should: the wording table renames this field from "Enter a value" to "Pick an answer" (choices) and "Answer" (text). The rule editor in #274 labels it "Answer for condition 1" and sends an empty answer to the server, so this message shows next to that field. Test line 123 changes with it (I ran it: 9 of 9 pass).

Suggested change

	'conditions.*.value.required' => 'Enter a value for condition :position.',
	'conditions.*.value.required' => 'Add an answer for condition :position.',

[PhilReinking]

OK at 0aa6a12, CI green.

Both shoulds are fixed as suggested, and nothing else changed since a781985. The docs now say only checkbox and consent questions send a list, which matches the public form, and the condition message asks for an answer.

[PhilReinking]

OK at 8b02c1a, CI green. The merge of main changes only CHANGELOG.md and the test order in FormBlockLogicTest.php by hand; both sides stay whole. The PR's own diff against main is the reviewed one from 0aa6a12 plus 8b02c1a. The new message fits the rule: it fails for a question that was deleted or is in another form, and the test checks the full text.