docs(events,rust): MODULE_API 1.14.0's multiple param; permission rewards built (PLAN_REDESIGNS §12.10)

- website/MODULE_API.md: 1.14.0 in §1.1 and the changelog — `multiple: true`
  with `max` on a string/int action param, the JSON-array value, a bare value
  as a list of one, refused on a duration, a template input and a list
  example; the catalog serves both keys; the editor's multi-select;
  Module-uo unaffected. §2.4's registerEventActions line names it.
- website/EVENTS.md §F: the param that holds several values and its control.
- modules/rust/PLAN_REDESIGNS.md §12.10: built in website#213 and
  Module-Rust#42, with the eight points settled in code, overrulable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

website/EVENTS.md

@@ -1107,6 +1107,16 @@ is a JSON editor with better fonts.
 shows under the field while that row is the chosen value — advice such as *"9 of 41 linked players
 have used this kit up"*. It is never a rule; the save path does not read it.
 
+**A param may hold several values** (MODULE_API 1.14.0; Rust PLAN_REDESIGNS §12.3, D344):
+`multiple: true`, with an optional `max` (1 to 100, 20 when left out), on a `string` or `int` param
+that is not a duration and not a template's input. The step stores a JSON array — a bare value is a
+list of one, duplicates are dropped in order, `required` means at least one — and `perform()` and
+`cost()` receive the array. The editor's control is a **multi-select**: the chosen values as chips
+above a grouped checklist with a filter box, over the source's own rows and in the source's order;
+the typeahead adding a chip per pick for a `searchable` source; a tag box, a value per Enter, with
+no source or one that cannot answer. The first user is Rust's permission rewards, one step giving
+several permissions.
+
 ### Integration Kit
 
 A fifth chapter, obeying the kit's own rule — teach and link out, re-specify nothing. The four things