Riddle

Previous value: -"Narrow block-types further, to these block type name(s) (e.g. \"SingleChoice\", \"WheelSpinner\"), on top of whatever \"riddleType\" already kept. Names are NOT enumerated here - there are dozens across 9 Riddle types, and this schema is read by every agent on every turn regardless of whether it filters. An unknown name, or one that exists but is not part of the Riddle type(s) you filtered to, is rejected and the error names the valid names for your situation. Omit for every block type."New value: +"The block type name(s) you are actually going to build (e.g. \"SingleChoice\", \"WheelSpinner\"), narrowing block-types on top of whatever \"riddleType\" kept - the normal way to read that document, not an optimization for later: pass the two or three the Riddle needs, and come back for another. The names are deliberately not enumerated here (dozens of them, on a schema every agent reads every turn); an unknown one, or a real one outside the Riddle type(s) you filtered to, is rejected with the names that are valid for your situation. Omit for every block type."

Previous value: -"Narrow form-field-types down to these form field type name(s) (e.g. \"Dropdown\", \"Privacy\"). The property sets a kept field type refers to (propertySets/commonProperties) and the \"fields\" usage notes are always returned with it. Names are NOT enumerated here for the same reason \"blockTypes\" does not enumerate its own - an unknown one is rejected with the full list of the 18 valid names. Ignored on every other topic. Omit for every field type."New value: +"Narrow form-field-types and form-field-defaults to these form field type name(s) (e.g. \"Dropdown\", \"Privacy\"); the property sets a kept type refers to (propertySets/commonProperties) and the \"fields\" usage notes always come with it. Not enumerated here for the same reason \"blockTypes\" is not - an unknown one is rejected with the full list. Ignored on every other topic. Omit for every field type."

Previous value: -"Whether the response should carry the full \"availableTopics\" catalogue. Omit it: the first reference_get of a session gets the catalogue, every call after it gets a one-line pointer back to it instead of repeating ~2.5 KB you already have - which on a small document is several times the document itself. Pass true to get it again (a fresh conversation on an existing session, or after losing it), false to never pay for it."New value: +"Whether to carry the full \"availableTopics\" catalogue. Omit it - the first reference_get of a session gets it, later ones get a pointer instead of repeating ~2.5 KB you already have. true gets it again (a fresh conversation on an existing session), false never pays for it."

Previous value: -"Narrow riddle-types/block-types down to these Riddle type(s) - e.g. [\"Quiz\"] on block-types drops every other type's question blocks while keeping the shared conventions (commonBlockProperties, the general Content/Ad/Quote blocks, ...). Ignored, with the whole document returned, on a topic that has no per-type split (form-field-types, result-blocks, concepts/defaults, the palette/question-bank documents). Not applicable to the block-defaults/riddle-defaults families - read the entity's own address instead. Omit for every type."New value: +"Narrow riddle-types/block-types to these Riddle type(s) - on block-types that drops every other type's question blocks while keeping the shared conventions (commonBlockProperties, the general Content/Ad/Quote blocks). REQUIRED on block-types unless \"blockTypes\" is given instead, and only the WIDE scope of it. Ignored on a topic with no per-type split, and not applicable to the block-defaults/riddle-defaults families - read the entity's own address there. Omit for every type."

Previous value: -"The reference documents to read, as their \"riddle://reference/...\" URIs."New value: +"The documents to read, as their \"riddle://reference/...\" URIs (a document's short resource name, e.g. \"block-types\", works too). What each one holds:\n- riddle://reference/index: every document this server has, with its exact size. Read this first when you do not know which of the others you need - it is by far the smallest, and the one place the member names of the {...} families below are listed.\n- riddle://reference/getting-started: what this server is for, the authentication model, the guided prompts, and the addresses of the documents that hold the rules. Start here when unsure which tool to use.\n- riddle://reference/prompts/{prompt} (one per guided prompt, e.g. riddle://reference/prompts/build_LeadGenQuiz): the playbook for a whole goal - what to ask the user first, the tool calls in order, what to verify, the traps. Read one when the user states a GOAL rather than an operation.\n- riddle://reference/response-format: the envelope every Riddle-returning tool answers with, plus the list, bulk and error shapes.\n- riddle://reference/riddle-builder/riddle-types: all 9 Riddle types with their required/optional build fields and result structure.\n- riddle://reference/riddle-builder/block-types: every question and content block type - the reference for the \"blocks\" of a riddle_builder_* call. Returned scoped only, and worth scoping twice (see \"blockTypes\").\n- riddle://reference/riddle-builder/form-field-types and .../result-blocks: the 18 form field types of the FormBuilder block, and the 12 result page block types with their format and styling options.\n- riddle://reference/concepts/{concept} (one per subject, e.g. riddle://reference/concepts/merge-semantics): how an edit merges, the \"preset\" and \"publish\" objects, branching logic, defaults, bulk calls, move restrictions, limits, troubleshooting.\n- riddle://reference/block-defaults/{blockType}, riddle://reference/riddle-defaults/{riddleType}, riddle://reference/form-field-defaults, riddle://reference/publish-defaults: what a read-back leaves out for still being at its default, and what that default is. Read riddle://reference/concepts/defaults once for how to use them.\n- riddle://reference/palette/fields, .../built-in-palettes, .../fonts: every palette value palette_customize accepts and where it shows up, the built-in palettes to start from, the available font families.\n- riddle://reference/question-bank/overview: what a question bank is, its draft/publish model, and how its items relate to a QuestionBank block - read before the first question_bank_create."

Previous value: -[
-  {
-    "enum": [
-      "riddle://reference/index",
-      "riddle://reference/getting-started",
-      "riddle://reference/response-format",
-      "riddle://reference/riddle-builder/riddle-types",
-      "riddle://reference/riddle-builder/block-types",
-      "riddle://reference/riddle-builder/form-field-types",
-      "riddle://reference/riddle-builder/result-blocks",
-      "riddle://reference/palette/fields",
-      "riddle://reference/palette/built-in-palettes",
-      "riddle://reference/palette/fonts",
-      "riddle://reference/publish-defaults",
-      "riddle://reference/form-field-defaults",
-      "riddle://reference/question-bank/overview"
-    ],
-    "type": "string"
-  },
-  {
-    "pattern": "^riddle://reference/(block-defaults|riddle-defaults|concepts)/[^/]+$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "enum": [
+      "riddle://reference/index",
+      "riddle://reference/getting-started",
+      "riddle://reference/response-format",
+      "riddle://reference/riddle-builder/riddle-types",
+      "riddle://reference/riddle-builder/block-types",
+      "riddle://reference/riddle-builder/form-field-types",
+      "riddle://reference/riddle-builder/result-blocks",
+      "riddle://reference/palette/fields",
+      "riddle://reference/palette/built-in-palettes",
+      "riddle://reference/palette/fonts",
+      "riddle://reference/publish-defaults",
+      "riddle://reference/form-field-defaults",
+      "riddle://reference/question-bank/overview",
+      "riddle://reference/question-bank/block-type-columns"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^riddle://reference/(block-defaults|riddle-defaults|concepts|prompts)/[^/]+$",
+    "type": "string"
+  },
+  {
+    "pattern": "^[a-zA-Z0-9][a-zA-Z0-9-]*$",
+    "type": "string"
+  }
+]

Previous value: -8New value: +3

Previous value: -"Every topic this tool can return - sent in full on the FIRST reference_get of a session only, so a client that reached this tool without reading its schema still learns what else is documented and what reading it would cost. Later calls carry a short {omitted, namesAndSizesIn, resend} pointer instead of repeating ~2.5 KB the caller already has; \"includeAvailableTopics\" overrides both directions. In the full form the static documents are listed as uri => {sizeBytes, summary}, same as riddle://reference/index and what resources/list advertises as \"size\". The two generated families (block-defaults, riddle-defaults - one address per entity) are compacted under \"families\": the address template, how many addresses it has and what they cost in total, without the individual names - those, with their exact sizes, are in riddle://reference/index. An address is built by replacing the {variable} of a \"uriTemplate\" with the entity you are working on, e.g. riddle://reference/block-defaults/Flashcard."New value: +"Every topic this tool can return, uri => {sizeBytes, summary} - sent in full on the FIRST reference_get of a session, then replaced by a short {omitted, namesAndSizesIn, resend} pointer (\"includeAvailableTopics\" overrides both directions). The generated families are compacted under \"families\" - the address template, how many addresses and what they cost in total, the individual names being in riddle://reference/index. Build one by replacing a \"uriTemplate\" variable with your entity, e.g. riddle://reference/block-defaults/Flashcard."

Previous value: -"The UUID of the Riddle to edit (as returned by riddle_list / riddle_get)"New value: +"The UUID of the Riddle to edit, as returned by riddle_list or riddle_get (e.g. \"6FA740EW\") - the Riddle itself, never a block id or a project id."

Previous value: -"The changes to apply, as a partial build configuration in the engine's own key names - the same shape riddle_get returns under \"build\" and the riddle_builder_<type> tools take. Only the fields you send are touched; send at least one. A field only exists for the Riddle types that have it, and unknown keys are rejected rather than ignored."New value: +"The changes to apply, as a partial build configuration in the engine's own key names - the same shape riddle_get returns under \"build\" and riddle_builder_create takes. Only the fields you send are touched; send at least one. A field only exists for the Riddle types that have it, and unknown keys are rejected rather than ignored."

Previous value: -"The new order of the Riddle's blocks, as the complete list of their IDs - [3, 1, 2] puts block 3 first. Complete means every ID the Riddle has after this edit, exactly once: a partial list is rejected, because where the blocks you left out belong is exactly what it does not say. It is applied after everything else in the same call, so a block you delete here must NOT be listed and a block you add here MUST be - give a \"$create\" entry an explicit \"id\" to name it, taken from \"nextBlockId\" in the riddle_get response (count up from it for several new blocks) and never derived from the ids in \"build\", which are shared with the Riddle's results and personalities; claiming a taken id is rejected with an error naming the free one. The same marker works inside a block, next to the collection it orders: {\"id\": 3, \"$itemsOrder\": [2, 1]} reorders that block's items, \"$fieldsOrder\" a Form's fields, and it reaches one level deeper through a merged \"fields\" edit - {\"id\": 3, \"fields\": [{\"id\": 5, \"$itemsOrder\": [2, 1]}]} reorders the items of that one Dropdown field. Only a collection whose entries have ids of their own can be ordered at all, and a few that do still reject the marker because an entry's position carries meaning of its own - riddle://reference/concepts/merge-semantics says which collection is which, and the error says so too if you try."New value: +"The new order of the Riddle's blocks, as the complete list of their IDs - [3, 1, 2] puts block 3 first. Complete means every ID the Riddle has AFTER this edit, exactly once; a partial list is rejected. It runs last, so a deleted block must NOT be listed and an added one MUST be - give the \"$create\" entry an explicit \"id\" from riddle_get's \"nextBlockId\". The same marker orders a collection inside a block (\"$itemsOrder\", \"$fieldsOrder\"). Rules: riddle://reference/concepts/merge-semantics."

Previous value: -"The blocks to change, add or remove - only the ones you touch, everything else stays as it is. To EDIT, pass the block's \"id\" (riddle_get reports it) plus only the properties that change - {\"id\": 3, \"title\": \"New question title\"}. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new block needs, the same shape the riddle_builder_<type> tool of this Riddle's type takes - {\"$create\": true, \"type\": \"SingleChoice\", \"title\": \"New question\", \"items\": [...]}. To REMOVE, pass \"id\" plus \"$delete\": true. A block cannot change its \"type\" in an edit (delete it and add a new one instead), and an unknown \"id\" is rejected with the list of IDs that do exist. The collections INSIDE a block work the same way wherever their entries have ids - {\"id\": 3, \"items\": [{\"id\": 2, \"title\": \"Bonn\"}]} renames one answer and leaves the others alone - and are replaced wholesale where they do not. Which collection is which, what an entry id is scoped to, why an entry without an \"id\" or \"$create\" is rejected, which deletes are refused for still being referenced (custom logic, a hotspot's \"goToImage:\"), and which rules are checked against the merge result rather than against what you sent: riddle://reference/concepts/merge-semantics, with the marker rules themselves in riddle://reference/concepts/editing."New value: +"The blocks to change, add or remove - only the ones you touch, everything else stays as it is. EDIT: the block's \"id\" (riddle_get reports it) plus only the properties that change - {\"id\": 3, \"title\": \"New question title\"}. ADD: \"$create\": true instead of an \"id\", plus everything a new block needs in the shape riddle_builder_create takes - {\"$create\": true, \"type\": \"SingleChoice\", \"title\": \"New question\", \"items\": [...]}. REMOVE: \"id\" plus \"$delete\": true. A block cannot change its \"type\"; an unknown \"id\" is rejected naming the ids that exist. A collection inside a block merges by \"id\" the same way - {\"id\": 3, \"items\": [{\"id\": 2, \"title\": \"Bonn\"}]} renames one answer and leaves the others alone. Which collections merge, which are replaced wholesale, and which deletes are refused for still being referenced: riddle://reference/concepts/merge-semantics (markers: riddle://reference/concepts/editing)."

Previous value: -"Prioritized (first match wins), time-windowed list of routing rules evaluated before the fallback \"riddleId\" (max 100 conditions). Each condition targets either another Riddle or a tag - exactly one of \"riddleId\" (UUID of an existing, non-Placeholder, published Riddle) or \"tag\" (name or numeric id of an EXISTING tag in this Riddle's own scope - a typo'd name is rejected, never auto-created; sending a numeric id reads back as the tag NAME, which is ambiguous if two tags in this scope share a name) is required, never both. No other key is accepted on a condition: unknown keys and \"$create\"/\"$delete\" markers are rejected - \"conditions\" always replaces the whole list, there is no per-entry merge (see \"resend\" below). A \"tag\" condition additionally requires \"tagMode\": \"lastPublished\" (the most recently published Riddle carrying that tag) or \"random\" (a random one, optionally re-picked every \"randomRefreshIntervalSeconds\", a positive integer of seconds, only accepted together with tagMode \"random\"; defaults to 86400 when omitted and that default is written into the read-back, so echo it back on a resend for a byte-identical round-trip). Each condition may also carry a time window, either a date range (\"from\", required; \"to\", optional - open-ended) or a daily time-of-day range (\"dailyFrom\" and \"dailyTo\", both required together) - never both kinds on the same condition, and a condition with neither always matches whenever it is reached. Dates accept \"YYYY-MM-DD\" (midnight UTC) or full ISO 8601 (a trailing \"Z\" allowed) and are canonicalized to \"YYYY-MM-DDTHH:MM:SS+00:00\"; daily times accept \"HH:MM\" or \"HH:MM:SS\" and always come back as \"HH:MM:SS\"; a non-string date/time value (a unix int, a bool) is rejected. A date \"to\" before \"from\" is rejected; an out-of-range daily component (\"25:00:00\", \"12:60\") is rejected too, NOT wrapped - \"dailyTo\" before \"dailyFrom\" is the one legitimate exception, meaning an overnight window (e.g. 22:00-02:00). Normalization: the list is NOT stored or returned in the order you send it. It is sorted into three tiers - date-windowed conditions first, then daily-windowed, then windowless (so a daily window can never outrank a date window) - ascending within a tier by \"from\"/\"dailyFrom\" (windowless entries keep your send order); date and daily windows are never compared against each other, and duplicates are kept, not deduplicated. When two windows of the SAME kind overlap, the earlier condition's \"to\"/\"dailyTo\" is silently rewritten to the later condition's start (the later condition wins the contested interval - this is lossy and unannounced); a \"to\"-less condition that is not last in its tier gets a \"to\" synthesized as the next condition's start, so only the last condition of a tier may stay open-ended. Applying this to an already-normalized list changes nothing (idempotent). Resend safety: because \"conditions\" replaces the whole list, a condition (or the fallback) whose target Riddle was deleted/unpublished, or whose tag was removed, is DROPPED from riddle_get with a warning (reason \"PROPERTY_NOT_SERIALIZABLE\" for a condition, path \"conditions[<target>] (<why>)\"; reason \"RIDDLE_DATA_NOT_EXPRESSIBLE\" for the fallback, path \"riddleId\") while still being RETAINED in storage - it reappears once the target becomes valid again. Sending that damaged read-back straight back to riddle_builder_update therefore PERMANENTLY deletes the hidden dangling condition(s); the fallback is not affected the same way, because an omitted \"riddleId\" means \"don't touch it\" rather than \"clear it\" (see that field)."New value: +"Placeholder only. Prioritized (first match wins), time-windowed routing rules evaluated before the fallback \"riddleId\"; at most 100. Each targets exactly one of \"riddleId\" (UUID of an existing, non-Placeholder, published Riddle) or \"tag\" (name or numeric id of an EXISTING tag in this Riddle's scope - a typo'd name is rejected, never auto-created), never both; a \"tag\" also requires \"tagMode\": \"lastPublished\" or \"random\" (with optional \"randomRefreshIntervalSeconds\", \"random\" only). ONE kind of time window per condition - a date range (\"from\" required, \"to\" optional) or a daily one (\"dailyFrom\" plus \"dailyTo\") - with neither it always matches. No other key is accepted. This REPLACES the whole list, and the stored list is re-sorted into tiers with overlapping windows trimmed, so a read-back is not what you sent. Normalization, and why resending a read-back can delete a condition: riddle://reference/riddle-builder/riddle-types with riddleType [\"Placeholder\"]."

Previous value: -"Quiz/Predictor/Minigame only. New leaderboard connection, same shape as in the riddle_builder_<type> tools. Omit to leave the Riddle's leaderboard connections exactly as they are - unlike \"riddleConnections\", this is not resolved into a scalar leaf that could be silently reset: the underlying block only runs, and only ever appends a connection, when you actually send this field, so there is nothing to merge per key."New value: +"Quiz/Predictor/Minigame only. New leaderboard connection: \"connections\" (leaderboard UUIDs), \"identifier\", \"nickname\", as in riddle_builder_create. Omit to leave the Riddle's connections exactly as they are - sending this only ever appends a connection, so there is nothing to merge per key."

Previous value: -"New branching logic tree, same shape as in the riddle_builder_<type> tools. Replaces the current logic; omit to keep it. Deleting a block (see \"blocks\") that is still referenced by the Riddle's existing CUSTOM logic is rejected unless the same request resolves it: either send a full replacement tree here that no longer references the deleted block(s), or send \"logic\": {\"$reset\": true} to discard the custom logic and fall back to the default linear flow - mutually exclusive, \"$reset\": true alongside any other key in \"logic\" is rejected. The error names exactly which deleted block(s) are still referenced and by which logic node(s). This guard never fires when the logic is already the default linear one: deleting a block always works there, the linear order is simply regenerated."New value: +"New branching logic tree, same shape as in riddle_builder_create. Replaces the current logic; omit to keep it. Deleting a block the stored CUSTOM logic still references is rejected unless the same call sends a replacement tree without it, or \"logic\": {\"$reset\": true} to fall back to the default linear flow (\"$reset\" with any other key is rejected). Node shapes: riddle://reference/concepts/logic."

Previous value: -"Personality Test only. The personalities to change, add or remove - only the ones you touch, everything else stays as it is, merged entry-by-entry by \"id\" exactly like the Riddle's own \"blocks\" (see EDIT_BLOCKS). To EDIT, pass the personality's \"id\" (riddle_get reports it) plus only the properties that change. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new personality needs (the same shape riddle_builder_personality takes). To REMOVE, pass \"id\" plus \"$delete\": true. An entry with no \"id\" and no \"$create\" is rejected the same way a block is - it has no \"id\"; add \"$create\": true to add it as a new one instead. The order of the personalities is NOT editable: there is no \"$personalitiesOrder\" (sending one is rejected) and, because this collection is merged by id, the order the entries are sent in has no meaning either - a \"$create\" is appended at the end and everything else keeps the place it has. Reorder them in the Creator if the order matters. The minimum of 2 personalities is checked against the result AFTER the merge, so a \"$delete\" that would leave fewer than 2 is rejected. The scores already stored on every answer item follow their personality BY IDENTITY, not by position: a personality that stays keeps its score, a deleted personality takes its scores with it, and a newly created personality starts at 0 on every existing answer item until you say otherwise - resend the affected blocks' \"items\" with their full \"scores\" arrays in the same call to set them yourself (that is applied after this and simply wins)."New value: +"Personality Test only. The personalities to change, add or remove, merged by \"id\" exactly like \"blocks\" - \"id\" plus the changed properties, \"$create\": true plus a full new personality, or \"id\" plus \"$delete\": true. There is no \"$personalitiesOrder\": the order is not editable, and the order you send carries no meaning. The minimum of 2 is checked against the merge result. Answer \"scores\" follow a personality by identity, not position - a new one starts at 0 on every existing answer item, so resend the affected blocks' \"items\" with their full \"scores\" arrays in the same call."

Previous value: -"Design and riddle-level behaviour settings to change, same shape as in the riddle_builder_<type> tools. Only the keys you send are applied. A Leaderboard's own display settings are part of this too, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them."New value: +"Design and riddle-level behaviour settings to change, same shape as in riddle_builder_create; only the keys you send are applied. A Leaderboard's podium colours (\"color1st\"/\"color2nd\"/\"color3rd\") and \"isEmailVerificationEnabled\" live here too."

Previous value: -"Publish-configuration settings to change, same shape as in the riddle_builder_<type> tools. Only the keys you send are applied. Distinct from this tool's top-level \"publish\" boolean, which publishes the Riddle right away."New value: +"Publish-configuration settings to change, same shape as in riddle_builder_create; only the keys you send are applied. Distinct from this tool's top-level \"publish\" boolean, which publishes right away."

Previous value: -"New single result page (Poll / Form / Predictor / Personality / Minigame / Story), same shape as in the riddle_builder_<type> tools. Replaces the current result page as a whole - a result page cannot be edited property-by-property or merged by id the way \"blocks\" can; send it complete, exactly as you would when creating the Riddle. Omit to keep the current one untouched."New value: +"New single result page (Poll / Form / Predictor / Personality / Minigame / Story), same shape as in riddle_builder_create. Replaces the current one as a whole - a result page is neither editable property-by-property nor mergeable by \"id\", so send it complete. Omit to keep it untouched."

Previous value: -"New result pages (Quiz), same shape as in riddle_builder_quiz. Replaces ALL current result pages with what you send, in the order you send it: result pages are deliberately neither editable per entry nor reorderable, so read them with riddle_get first and resend every page you want to keep, including its \"id\", which is honored to keep the page stable across the resend. Omit the field to keep all result pages untouched. Why, and which markers are rejected on a page: riddle://reference/concepts/result-pages."New value: +"New result pages (Quiz), same shape as in riddle_builder_create. Replaces ALL current pages with what you send, in the order you send it - pages are neither editable per entry nor reorderable, so read them with riddle_get first and resend every page you want to keep, including its \"id\", which is honored to keep the page stable. Omit to keep them all untouched. riddle://reference/concepts/result-pages."

Previous value: -"Leaderboard only. The complete list of connected Riddle UUIDs - it REPLACES the stored set wholesale rather than appending (the property has no \"append\" flag and buildRiddleConnections() rebuilds the array from scratch), so to add or drop a single connection, call riddle_get first and resend every UUID you want to keep. Max 10; each target Riddle must already be published and must have Name and Email form fields."New value: +"Leaderboard only. The complete list of connected Riddle UUIDs - it REPLACES the stored set rather than appending, so read the Riddle with riddle_get first and resend every UUID you want to keep. Max 10; each target must already be published and have Name and Email form fields."

Previous value: -"The fallback target: the UUID of the Riddle to show when no condition matches (or there are none). Must be an existing, non-Placeholder, published Riddle, and cannot be this Placeholder itself. Having no fallback at all is meaningful on its own - a Placeholder with no fallback and no matching condition resolves to nothing, which is a decision the Embed side makes, not this repo. On an EDIT, omitting this field means \"don't touch it\"; send \"riddleId\": null to actually clear the fallback back to none - which is rejected when it would leave the Placeholder with no fallback AND no conditions at all (it could then never display any Riddle), so clear it only while at least one condition remains, or send a replacement \"conditions\" list in the same call. The same rule rejects \"conditions\": [] on a Placeholder that has no fallback. If the target is later deleted/unpublished, the fallback is dropped from riddle_get with a warning (reason \"RIDDLE_DATA_NOT_EXPRESSIBLE\", path \"riddleId\") but stays in storage and reappears once the target is valid again."New value: +"Placeholder only. The fallback target: the UUID of the Riddle to show when no condition matches. Must be an existing, non-Placeholder, published Riddle, and not this Placeholder itself. Having none is meaningful - the Placeholder then resolves to nothing. On an EDIT, omitting it leaves it as it is; \"riddleId\": null clears it, and is rejected if that would leave the Placeholder with no fallback and no conditions at all - as is \"conditions\": [] while this is empty. riddle://reference/riddle-builder/riddle-types with riddleType [\"Placeholder\"]."

Previous value: -"Predictor only. New scoring rules, same shape as in riddle_builder_predictor - only the keys you send are changed, the rest of the stored rules are kept. Applied the same way \"preset\"/\"publish\" are: a merge into the existing nested config, not a wholesale replacement, so e.g. sending only {\"correct\": 50} leaves tendency/difference/wrong exactly as they were."New value: +"Predictor only. New scoring rules, same shape as in riddle_builder_create - only the keys you send are changed, so {\"correct\": 50} leaves \"tendency\"/\"difference\"/\"wrong\" as they were. Omit to keep them."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Sections of the returned envelope to leave out; omit the parameter for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned, and whatever you leave out is echoed back under \"omittedFields\", so a missing key never means the Riddle has none of it. Details: riddle://reference/concepts/warnings."

Previous value: -[
-  "build",
-  "warnings",
-  "nextBlockId",
-  "published",
-  "context",
-  "build.omittedDefaults"
-]New value: +[
+  "build",
+  "warnings",
+  "nextBlockId",
+  "published",
+  "context"
+]

Previous value: -"Whether to publish the Riddle after the edit; default is false, which leaves the changes in the draft. It rides along with an edit, it is not one: this tool with publish: true and an empty \"build\" is rejected with \"Nothing to edit: send at least one of ...\". To publish what is already in the draft, call riddle_publish."New value: +"Whether to publish the Riddle after the edit; default false, which leaves the changes in the draft. It rides along with an edit, it is not one: publish: true with an empty \"build\" is rejected. To publish what is already in the draft, call riddle_publish."

Previous value: -"The build configs to dry-run, one entry each: {type, build} for a would-be creation or\n{UUID, build} for a would-be edit - exactly one of \"type\"/\"UUID\" per entry, creates and\nedits mixable in one call, 1 to 20 entries. \"type\" is one of Quiz / Poll / Personality /\nForm / Predictor / Leaderboard / Minigame / Story / Placeholder. \"build\" is exactly the\nbuild configuration the matching riddle_builder_<type> tool (creation) or\nriddle_builder_update (edit) takes, so a config can be moved between them unchanged. An\nedit entry is subject to the same origin gate as riddle_builder_update: rejected if the\nRiddle is not apiManageable (check context.origin.apiManageable on riddle_get first)."New value: +"The build configs to dry-run, 1 to 20 entries, creates and edits mixable: {type, build}\nfor a would-be creation or {UUID, build} for an edit, exactly one of \"type\"/\"UUID\" per\nentry. \"type\" is one of Quiz / Poll / Personality / Form / Predictor / Leaderboard /\nMinigame / Story / Placeholder, and \"build\" is exactly what riddle_builder_create or\nriddle_builder_update takes, so a config moves between them unchanged. An edit entry hits\nthe same origin gate as riddle_builder_update - rejected unless the Riddle is\napiManageable (context.origin.apiManageable on riddle_get)."

Removed value: -{
-  "default": null,
-  "description": "Leaves the per-block \"omittedDefaults\" maps out of every echoed-back build config, for a much smaller answer: omit: [\"build.omittedDefaults\"]. The same defaults are stated in riddle://reference/riddle-defaults/<riddle type> and riddle://reference/block-defaults/<block type>, so nothing is lost - what you must not do either way is resend those values. Omit the parameter to keep them. The other values of riddle_get's \"omit\" do not apply here: this envelope has no sections to drop.",
-  "items": {
-    "enum": [
-      "build.omittedDefaults"
-    ],
-    "type": "string"
-  },
-  "type": "array",
-  "uniqueItems": true
-}

Added value: +{
+  "default": null,
+  "description": "The project to dry-run the CREATING entries in - riddle_builder_create's own parameter, and it must be the project you intend to create in: the scratch Riddle is built inside it, and anything project-scoped the build REFERENCES (a Form behind FormSelect, a tag, a project ad slot) is only resolvable from there. Without it such a build is evaluated in the personal project and rejected with \"You are not authorized to access Form <UUID>\" - a scope problem wearing a permissions error, and a false negative for a build a real create would accept. NULL means the personal project, omitted the currently selected one. Ignored by editing entries ({UUID, build}), always evaluated in their own Riddle's project.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

Added value: +[
+  {
+    "properties": {
+      "UUID": {
+        "not": {
+          "type": "null"
+        }
+      },
+      "UUIDs": {
+        "const": null
+      }
+    },
+    "required": [
+      "UUID"
+    ]
+  },
+  {
+    "properties": {
+      "UUID": {
+        "const": null
+      },
+      "UUIDs": {
+        "not": {
+          "type": "null"
+        }
+      }
+    },
+    "required": [
+      "UUIDs"
+    ]
+  }
+]

Removed value: -{
-  "items": {
-    "pattern": "^[A-Za-z0-9]{4,32}$",
-    "type": "string"
-  },
-  "maxItems": 100,
-  "minItems": 1,
-  "type": "array",
-  "uniqueItems": true
-}

Added value: +{
+  "pattern": "^\\s*[A-Za-z0-9]{4,32}\\s*$",
+  "type": "string"
+}

Added value: +100

Added value: +1

Added value: +{
+  "default": false,
+  "description": "true reports whether each Riddle could be deleted and deletes nothing. Works for one UUID and for UUIDs.",
+  "type": "boolean"
+}

Added value: +[
+  {
+    "properties": {
+      "UUID": {
+        "not": {
+          "type": "null"
+        }
+      },
+      "UUIDs": {
+        "const": null
+      }
+    },
+    "required": [
+      "UUID"
+    ]
+  },
+  {
+    "properties": {
+      "UUID": {
+        "const": null
+      },
+      "UUIDs": {
+        "not": {
+          "type": "null"
+        }
+      }
+    },
+    "required": [
+      "UUIDs"
+    ]
+  }
+]

Removed value: -{
-  "items": {
-    "pattern": "^[A-Za-z0-9]{4,32}$",
-    "type": "string"
-  },
-  "maxItems": 20,
-  "minItems": 1,
-  "type": "array",
-  "uniqueItems": true
-}

Previous value: -"Several Riddles to read at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"]\n(max 20 - lower than the other bulk tools, since every entry here is a full\nbuild-configuration envelope, not compact state). Pass either this or UUID; rejected\ntogether with includeRiddleData: true, which would overflow the inline response size.\nThe response is the {bulk, operation: \"read\", summary, results} envelope the other bulk\ntools answer with, but with the full riddle_get envelope per entry. Size is therefore\nthe thing to manage: entries are read in the order you listed them, and once the\nresponse would exceed the inline size budget, the remaining ones are reported as\n{uuid, success: true, truncated: true, ...compact state} instead of their full envelope\n- never silently dropped - with a top-level \"truncated\" block naming those UUIDs. Put\nthe Riddles you most need in full first, and use \"omit\" to fit more of them in: an\nunfiltered bulk read of several non-trivial Riddles will truncate.\nomit: [\"build.omittedDefaults\"] is by far the most effective (~85-90% off every entry);\nleaving out whole sections saves much less, a build configuration being almost the\nentire envelope."New value: +"Several Riddles to read at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"]\n(max 20 - lower than the other bulk tools, since every entry is a full envelope rather\nthan compact state). Either this or UUID; rejected together with includeRiddleData.\nEntries are read in the order given and, once the response would exceed the inline size\nbudget, the remaining ones come back as compact state with \"truncated\": true instead -\nso put the Riddles you need in full first. See riddle://reference/concepts/bulk."

Added value: +{
+  "pattern": "^\\s*[A-Za-z0-9]{4,32}\\s*$",
+  "type": "string"
+}

Added value: +20

Added value: +1

Previous value: -"Additionally returns the full stored Riddle payload (content, settings, preset\nmerge/diff, ...) under \"riddle\". A large payload (tens of KB) - only for\ninspecting raw stored data, leave it false for normal use. Not allowed\ntogether with UUIDs."New value: +"Additionally returns the full stored Riddle payload (content, settings, preset\nmerge/diff, ...) under \"riddle\" - tens of KB, only for inspecting raw stored\ndata. Not allowed together with UUIDs."

Previous value: -"Leaves parts of the response out - the one way to make this call smaller. Valid values:\n\"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole envelope sections) and\n\"build.omittedDefaults\" (the per-block \"omittedDefaults\" maps inside every build\nconfiguration in the response, including \"published.build\" - not a section, but by far\nthe largest part of one). Omit the parameter, or pass [], for everything;\n\"uuid\"/\"type\"/\"modifiedAt\" are always present and cannot be left out.\nWhich value to reach for: \"build.omittedDefaults\" shrinks a read-back by ~85-90% and\nloses no information, since riddle://reference/block-defaults/<block type> and\nriddle://reference/riddle-defaults/<riddle type> state the very same defaults - the right\ndefault for any call that does not specifically need to know which properties sit at\ntheir default. Whole sections\nare worth naming when you truly do not need them: \"published\" is a second full build\nconfiguration whenever the draft has unpublished changes (about half the response),\nwhile \"warnings\"/\"nextBlockId\"/\"context\" together are only a few percent of it - though\nleaving out \"published\" also skips re-serializing the live version entirely, and\n\"context\" skips that section's extra lookups (features/origin, cover image, preset\ndiff), so the saving is in work as well as bytes.\nWhatever you leave out is echoed back in \"omittedFields\", so a key missing from the\nresponse never has to be read as \"this Riddle has none of that\", only as \"I asked for it\nto be left out\"; a call that omitted nothing carries no such key. With UUIDs, the same\nomissions apply to every entry."New value: +"Leaves whole sections out: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\"\n(identity fields always stay). The one omission that materially shrinks a response is\n\"published\" on a Riddle with unpublished changes - a second full build configuration.\nWhatever you leave out is echoed in \"omittedFields\", so a missing key never reads as\n\"this Riddle has none of that\". Details: riddle://reference/concepts/warnings."

Previous value: -[
-  "build",
-  "warnings",
-  "nextBlockId",
-  "published",
-  "context",
-  "build.omittedDefaults"
-]New value: +[
+  "build",
+  "warnings",
+  "nextBlockId",
+  "published",
+  "context"
+]

Added value: +{
+  "default": null,
+  "description": "Whether every block should additionally carry its \"omittedDefaults\" map: the properties it left at that block type's default, with the value each is at. Off by default - measured, those maps are 85-90% of a read-back, and riddle://reference/block-defaults/<block type> states the same defaults without a Riddle in hand. Ask for them only to learn what THIS Riddle left at its default, and read them, never resend them.",
+  "type": "boolean"
+}

Previous value: -"Exclude specific Riddle types (array of strings, same valid values as type). Omit to exclude nothing."New value: +"Exclude specific Riddle types (array of strings, same valid values as type). Omit to exclude nothing. Scope \"project\" only - the account list has no exclusion filter."

Previous value: -"Filter by how the Riddle was created: \"api\" (built via the Riddle Builder API or\ngenerated by the Riddle AI, so riddle_delete/riddle_builder_update/palette_customize\nwork on it) or \"manual\" (created by hand in the Creator, where those three are\nrejected). Omit to include both. Filter value only: the \"origin\" field returned per\nRiddle is an object {builder, aiGenerated, apiManageable}, not one of these strings."New value: +"Filter by how the Riddle was created: \"api\" (Riddle Builder API or Riddle AI, so\nriddle_delete/riddle_builder_update/palette_customize work on it) or \"manual\" (built by\nhand in the Creator, where those three are rejected). Omit for both. A filter value\nonly - the \"origin\" returned per Riddle is {builder, aiGenerated, apiManageable}."

Previous value: -"Page number, 1-indexed, 12 Riddles per page (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as project_list/questionBank_list."New value: +"Page number, 1-indexed, 12 Riddles per page (default: 1). Zero or negative is rejected with a VALIDATION_ERROR rather than clamped."

Previous value: -"Filter by project ID; omit or null for the authenticated user's personal project"New value: +"Filter by project ID; omit or null for the authenticated user's personal project. Scope \"project\" only."

Added value: +{
+  "default": null,
+  "description": "What to list: \"project\" (default) for the Riddles of a single project, \"account\" for every Riddle of the account at once.",
+  "enum": [
+    "project",
+    "account"
+  ],
+  "type": "string"
+}

Added value: +[
+  {
+    "properties": {
+      "UUID": {
+        "not": {
+          "type": "null"
+        }
+      },
+      "UUIDs": {
+        "const": null
+      }
+    },
+    "required": [
+      "UUID"
+    ]
+  },
+  {
+    "properties": {
+      "UUID": {
+        "const": null
+      },
+      "UUIDs": {
+        "not": {
+          "type": "null"
+        }
+      }
+    },
+    "required": [
+      "UUIDs"
+    ]
+  }
+]

Previous value: -"The UUID of the single Riddle you want to move. Pass either this or UUIDs."New value: +"The UUID of the single Riddle you want to move or check. Pass either this or UUIDs."

Removed value: -{
-  "items": {
-    "pattern": "^[A-Za-z0-9]{4,32}$",
-    "type": "string"
-  },
-  "maxItems": 100,
-  "minItems": 1,
-  "type": "array",
-  "uniqueItems": true
-}

Previous value: -"Several Riddles to move at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."New value: +"Several Riddles to move or check at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID. For a move, this must be the complete set of Riddles that have to move together."

Added value: +{
+  "pattern": "^\\s*[A-Za-z0-9]{4,32}\\s*$",
+  "type": "string"
+}

Added value: +100

Added value: +1

Added value: +{
+  "default": false,
+  "description": "true runs the movability check against the given projectId and changes nothing. Pointless without projectId, which already only checks.",
+  "type": "boolean"
+}

Added value: +[
+  {
+    "description": "A project (team) ID from project_list.",
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "const": "personal",
+    "description": "Move the Riddles into the personal project.",
+    "type": "string"
+  }
+]

Previous value: -"The project (team) ID to move the Riddles into, as returned by project_list. Omit or pass null to move them to your personal project instead."New value: +"Where to move the Riddles: the project (team) ID to move them into, as returned by project_list, or the string \"personal\" for your personal project. There is no default destination - omit this and nothing is moved, the call reports the read-only movability check instead."

Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "null",
+  "integer",
+  "string"
+]

Added value: +[
+  {
+    "properties": {
+      "UUID": {
+        "not": {
+          "type": "null"
+        }
+      },
+      "UUIDs": {
+        "const": null
+      }
+    },
+    "required": [
+      "UUID"
+    ]
+  },
+  {
+    "properties": {
+      "UUID": {
+        "const": null
+      },
+      "UUIDs": {
+        "not": {
+          "type": "null"
+        }
+      }
+    },
+    "required": [
+      "UUIDs"
+    ]
+  }
+]

Previous value: -"The UUID of the single Riddle you want to publish. Pass either this or UUIDs."New value: +"The UUID of the single Riddle you want to publish or unpublish. Pass either this or UUIDs."

Removed value: -{
-  "items": {
-    "pattern": "^[A-Za-z0-9]{4,32}$",
-    "type": "string"
-  },
-  "maxItems": 100,
-  "minItems": 1,
-  "type": "array",
-  "uniqueItems": true
-}

Previous value: -"Several Riddles to publish at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."New value: +"Several Riddles to publish or unpublish at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."

Added value: +{
+  "pattern": "^\\s*[A-Za-z0-9]{4,32}\\s*$",
+  "type": "string"
+}

Added value: +100

Added value: +1

Previous value: -[
-  "build",
-  "warnings",
-  "nextBlockId",
-  "published",
-  "context",
-  "build.omittedDefaults"
-]New value: +[
+  "build",
+  "warnings",
+  "nextBlockId",
+  "published",
+  "context"
+]

Added value: +{
+  "default": true,
+  "description": "true (the default) publishes the Riddles, false takes them off the web again.",
+  "type": "boolean"
+}

Previous value: -"The project (team) ID the tag belongs to, as returned by project_list. Omit for the project the API key is scoped to, or your personal tags on a user API key - the same scoping riddle_tag_list uses."New value: +"The project (team) ID the tag belongs to, as returned by project_list. Omit for the project the API key is scoped to, or your personal tags on a user API key."

Previous value: -"The ID of the tag to delete, as returned by riddle_tag_list."New value: +"The ID of the tag to delete, as returned by riddle_tag_list. The only way to name it: a tag is deleted by id, not by name."

Previous value: -"The project (team) ID whose tags you want, as returned by project_list. Omit for the tags of the project the API key is scoped to, or your personal tags on a user API key."New value: +"The project (team) ID, as returned by project_list. Omit for the project the API key is scoped to, or your personal tags on a user API key."

Previous value: -"Start date (inclusive), format: YYYY-MM-DD. Omit both dateFrom and dateTo to get alltime stats."New value: +"Start date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-01\". Required for \"timeseries\". On \"totals\" and a Riddle/project \"breakdown\", omit both dates for alltime and pass only one for an open-ended range; the account-wide summary and the project breakdown instead default to one CALENDAR month before today - the same default the Creator's dashboards use, so 29 to 32 days depending on the month, not exactly 30. Send it explicitly when the exact span matters."

Previous value: -"End date (inclusive), format: YYYY-MM-DD. Omit both dateFrom and dateTo to get alltime stats."New value: +"End date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-31\". Same rules as dateFrom; where a default applies it is today."

Added value: +null

Previous value: -"ID of the entity: a project ID (integer as string) for \"project\", a user ID (integer as string) for \"user\", a Riddle UUID for \"riddle\". Get them from project_list, whoami and riddle_list respectively."New value: +"ID of the entity: a project ID (integer as string) for \"project\", a user ID (integer as string) for \"user\", a Riddle UUID for \"riddle\". Get them from project_list, whoami (\"user\", not the string \"user\") and riddle_list respectively. Required for every view except the account-wide summary (view \"breakdown\" with namespace \"user\"), which measures the API key's own account and rejects it."

Previous value: -"string"New value: +[
+  "null",
+  "string"
+]

Previous value: -"Entity type to fetch stats for: \"project\", \"user\" or \"riddle\"."New value: +"Entity type to fetch stats for."

Added value: +{
+  "default": null,
+  "description": "Page number of the account-wide summary, 1-indexed (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as riddle_list/project_list. That view only.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

Added value: +{
+  "default": null,
+  "description": "Narrow the account-wide summary to these project IDs (array of integers, from project_list). Omit to cover the whole account, including the personal project. Passing a project the user cannot view stats of is an error, not a silently skipped project. That view only.",
+  "type": [
+    "array",
+    "null"
+  ]
+}

Added value: +{
+  "default": null,
+  "description": "Metric the account-wide summary's Riddles are ranked by before the page is cut: \"views\" (default), \"starts\", \"submissions\" or \"timeActive\". Sorting always spans the whole account (or the projects given), so page 1 is genuinely the top of the account. That view only.",
+  "enum": [
+    "views",
+    "starts",
+    "submissions",
+    "timeActive"
+  ],
+  "type": "string"
+}

Added value: +{
+  "description": "How deeply to measure: \"totals\" (one aggregate for the period), \"timeseries\" (that aggregate per consecutive interval, requires dateFrom and dateTo) or \"breakdown\" (the per-block detail, or the per-Riddle summary for namespace \"user\").",
+  "enum": [
+    "totals",
+    "timeseries",
+    "breakdown"
+  ],
+  "type": "string"
+}

Previous value: -[
-  "namespace",
-  "entityId"
-]New value: +[
+  "view",
+  "namespace"
+]

Added value: +{
+  "default": null,
+  "description": "Leaves parts of the response out - the way to keep this call small. \"paletteValues\" lists every palette as {uuid, name} instead of with its ~30 values (then read the one you want with paletteUUID); \"builtInPalettes\", \"customizedValues\" and \"hints\" drop those keys entirely. Omit the parameter for the full response. Whatever you leave out is echoed back under \"omittedFields\", so a missing key never means the Riddle has none of it.",
+  "items": {
+    "enum": [
+      "paletteValues",
+      "builtInPalettes",
+      "customizedValues",
+      "hints"
+    ],
+    "type": "string"
+  },
+  "type": "array",
+  "uniqueItems": true
+}

Added value: +{
+  "default": null,
+  "description": "Whether the response should carry the full \"availableTopics\" catalogue. Omit it: the first reference_get of a session gets the catalogue, every call after it gets a one-line pointer back to it instead of repeating ~2.5 KB you already have - which on a small document is several times the document itself. Pass true to get it again (a fresh conversation on an existing session, or after losing it), false to never pay for it.",
+  "type": "boolean"
+}

Previous value: -"Every topic this tool can return. The static documents are listed as uri => {sizeBytes, summary}, same as riddle://reference/index and what resources/list advertises as \"size\". The two generated families (block-defaults, riddle-defaults - one address per entity) are compacted under \"families\": the address template, how many addresses it has and what they cost in total, without the individual names - those, with their exact sizes, are in riddle://reference/index. An address is built by replacing the {variable} of a \"uriTemplate\" with the entity you are working on, e.g. riddle://reference/block-defaults/Flashcard. Repeated in the response so a client that reached this tool without reading its schema still learns what else is documented - and what reading it would cost, so the next call can be planned instead of guessed."New value: +"Every topic this tool can return - sent in full on the FIRST reference_get of a session only, so a client that reached this tool without reading its schema still learns what else is documented and what reading it would cost. Later calls carry a short {omitted, namesAndSizesIn, resend} pointer instead of repeating ~2.5 KB the caller already has; \"includeAvailableTopics\" overrides both directions. In the full form the static documents are listed as uri => {sizeBytes, summary}, same as riddle://reference/index and what resources/list advertises as \"size\". The two generated families (block-defaults, riddle-defaults - one address per entity) are compacted under \"families\": the address template, how many addresses it has and what they cost in total, without the individual names - those, with their exact sizes, are in riddle://reference/index. An address is built by replacing the {variable} of a \"uriTemplate\" with the entity you are working on, e.g. riddle://reference/block-defaults/Flashcard."

Previous value: -"Page number, 12 Riddles per page (default: 1)"New value: +"Page number, 1-indexed, 12 Riddles per page (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as project_list/questionBank_list."

Previous value: -"Array of minigame blocks. Supported types: SlotMachine (title, plus optional startBalance, winningProbability, custom reel symbols and win message), WheelSpinner (title and an \"items\" array of at least 2 objects with title, type (Win/Loss/FreeSpin), percent (all of them must sum to 100) and award (required on a Win item)), Sudoku (difficulty, score, plus an optional success message). Only Sudoku has a score - neither SlotMachine nor WheelSpinner (nor its items) supports scoring, so a Minigame consisting of nothing but a WheelSpinner cannot be connected to a Leaderboard. The remaining per-type properties are in riddle://reference/riddle-builder/block-types. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."New value: +"Array of minigame blocks. Supported types: SlotMachine (title, plus optional startBalance, winningProbability (\"Low\" / \"Medium\" / \"High\" - an enum, NOT a percentage), custom reel symbols and win message), WheelSpinner (title and an \"items\" array of at least 2 objects with title, type (Win/Loss/FreeSpin), percent (all of them must sum to 100) and award (required on a Win item)), Sudoku (difficulty as an integer 0-100, the percentage of cells blanked out rather than \"easy\"/\"medium\"/\"hard\", plus score and an optional success message). Only Sudoku has a score - neither SlotMachine nor WheelSpinner (nor its items) supports scoring, so a Minigame consisting of nothing but a WheelSpinner cannot be connected to a Leaderboard. The remaining per-type properties are in riddle://reference/riddle-builder/block-types. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."

Previous value: -"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice / Matrix / Order / Upvote / NetPromoterScore / RateIt / Swiper / Reaction / TextEntry / TierList / ThisOrThat / QuestionBank) and items (array of answer objects, each {\"title\": \"Answer text\"} plus that type's optional per-item properties). Optional: media (URL or object), isRequired, otherOption (SingleChoice/MultipleChoice only - adds an \"Other\" answer with a free-text entry). Three types differ structurally: TextEntry is a free-text answer with no items and no scoring at all, TierList needs \"tiers\" and treats its \"items\" as the optional pool the respondent drags into them, and QuestionBank draws its questions from an existing question bank instead of items authored here (\"questionBankId\" plus a non-empty \"questionBankBlocks\" - see riddle://reference/question-bank/overview first). Every type has further structural and display properties on top of that (ThisOrThat pairs its contenders positionally out of ONE flat \"items\" list, never a list of pairs; the RateIt scale, selection limits, wrapping, sorting after vote, mobile view, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges."New value: +"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice / Matrix / Order / Upvote / NetPromoterScore / RateIt / Swiper / Reaction / TextEntry / TierList / ThisOrThat / QuestionBank) and items (array of answer objects, each {\"title\": \"Answer text\"} plus that type's optional per-item properties). Optional: media (URL or object), isRequired, otherOption (SingleChoice/MultipleChoice only - adds an \"Other\" answer with a free-text entry). Four types differ structurally: NetPromoterScore is a fixed 0-10 scale with no items at all and REQUIRES positiveTitle plus negativeTitle (the labels of its high (10) and low (0) end); TextEntry is a free-text answer with no items and no scoring at all, TierList needs \"tiers\" and treats its \"items\" as the optional pool the respondent drags into them, and QuestionBank draws its questions from an existing question bank instead of items authored here (\"questionBankId\" plus a non-empty \"questionBankBlocks\" - see riddle://reference/question-bank/overview first). Every type has further structural and display properties on top of that (ThisOrThat pairs its contenders positionally out of ONE flat \"items\" list, never a list of pairs; the RateIt scale, selection limits, wrapping, sorting after vote, mobile view, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges."

Previous value: -"Page number, 12 Riddles per page (default: 1)"New value: +"Page number, 1-indexed, 12 Riddles per page (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as project_list/questionBank_list."

Added value: +{
+  "default": null,
+  "description": "Same \"omit\" parameter as riddle_get's, applied to the returned envelope (see riddle_get for the full description). Reach for omit: [\"build.omittedDefaults\"] here as well - the created Riddle is a copy of the template, so its per-block default maps are the biggest part of this response and state nothing riddle://reference/block-defaults/<block type> does not.",
+  "items": {
+    "enum": [
+      "build",
+      "warnings",
+      "nextBlockId",
+      "published",
+      "context",
+      "build.omittedDefaults"
+    ],
+    "type": "string"
+  },
+  "type": "array",
+  "uniqueItems": true
+}

Previous value: -"Start date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-01\". Optional."New value: +"Start date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-01\". Optional, defaults to 30 days ago."

Previous value: -"End date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-31\". Optional."New value: +"End date (inclusive), format: YYYY-MM-DD, e.g. \"2026-01-31\". Optional, defaults to today."

Added value: +{
+  "default": null,
+  "description": "Page number, 1-indexed (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as riddle_list/project_list.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

Added value: +{
+  "default": null,
+  "description": "Narrow the summary to these project IDs (array of integers, from project_list). Omit to cover the whole account, including the personal project. Passing a project the user cannot view stats of is an error, not a silently skipped project.",
+  "type": [
+    "array",
+    "null"
+  ]
+}

Added value: +{
+  "default": null,
+  "description": "Metric the Riddles are ranked by before the page is cut: \"views\" (default), \"starts\", \"submissions\" or \"timeActive\". Sorting always spans the whole account (or the projects given), so page 1 is genuinely the top of the account.",
+  "enum": [
+    "views",
+    "starts",
+    "submissions",
+    "timeActive"
+  ],
+  "type": "string"
+}

Previous value: -"The question content, as {columnName: [values]}. Which column names are expected depends on the bank's riddleType AND the blockType, so read them off questionBank_blockTypeColumns rather than guessing: an unknown column name is rejected. E.g. a \"Quiz\" bank's \"SingleChoice\" takes {\"QUESTION\": [\"Capital of France?\"], \"CORRECT_CHOICE\": [\"Paris\"], \"INCORRECT_CHOICE\": [\"London\", \"Berlin\"]}, a \"Poll\" bank's \"SingleChoice\" {\"QUESTION\": [...], \"CHOICE\": [...]} instead, a Poll answer never being right or wrong."New value: +"The question content, as {columnName: [values]}. Which column names are expected depends on the bank's riddleType AND the blockType, so read them off questionBank_blockTypeColumns rather than guessing: an unknown column name is rejected, naming the column it did not recognise and listing the valid ones. E.g. a \"Quiz\" bank's \"SingleChoice\" takes {\"QUESTION\": [\"Capital of France?\"], \"CORRECT_CHOICE\": [\"Paris\"], \"INCORRECT_CHOICE\": [\"London\", \"Berlin\"]}, a \"Poll\" bank's \"SingleChoice\" {\"QUESTION\": [...], \"CHOICE\": [...]} instead, a Poll answer never being right or wrong."

Previous value: -"The question content, as {columnName: [values]} - the same shape questionBank_addItem takes, with the columns questionBank_blockTypeColumns lists for this riddleType and blockType (an unknown column name is rejected). Replaces the item's content entirely, it is not a partial merge. The values questionBank_getItems returns can go straight back in, {\"id\": .., \"value\": ..} objects included: keeping their ids is what makes this an edit of the existing values rather than a fresh set."New value: +"The question content, as {columnName: [values]} - the same shape questionBank_addItem takes, with the columns questionBank_blockTypeColumns lists for this riddleType and blockType (an unknown column name is rejected, naming the column it did not recognise and listing the valid ones). Replaces the item's content entirely, it is not a partial merge. The values questionBank_getItems returns can go straight back in, {\"id\": .., \"value\": ..} objects included: keeping their ids is what makes this an edit of the existing values rather than a fresh set."

Previous value: -"Narrow block-types/block-defaults further, to these block type name(s) (e.g. \"SingleChoice\", \"WheelSpinner\"), on top of whatever \"riddleType\" already kept. Names are NOT enumerated here - there are dozens across 9 Riddle types, and this schema is read by every agent on every turn regardless of whether it filters. An unknown name, or one that exists but is not part of the Riddle type(s) you filtered to, is rejected and the error names the valid names for your situation. Omit for every block type."New value: +"Narrow block-types further, to these block type name(s) (e.g. \"SingleChoice\", \"WheelSpinner\"), on top of whatever \"riddleType\" already kept. Names are NOT enumerated here - there are dozens across 9 Riddle types, and this schema is read by every agent on every turn regardless of whether it filters. An unknown name, or one that exists but is not part of the Riddle type(s) you filtered to, is rejected and the error names the valid names for your situation. Omit for every block type."

Removed value: -{
-  "default": null,
-  "description": "Leaves parts of a document out instead of narrowing it. The only value with anything to leave out here is \"commonDefaults\", on block-defaults: its shared-defaults map is not itself scoped to a Riddle type or block type, so \"riddleType\"/\"blockTypes\" alone cannot always shrink it (an unfiltered call, or one whose kept blocks still reference most of it, keeps the whole map either way) - \"omit\": [\"commonDefaults\"] drops it outright. Nothing about a kept Riddle type or block type is lost by dropping it: their \"sharedDefaults\" lists still name what they need, \"filtered.omitted\" reports the drop the same way every other omission is reported, and the document itself says to call reference_get again (without this omit, or with a narrower riddleType/blockTypes) to get those names' actual values back. Ignored on every other topic. Omit for the complete document.",
-  "items": {
-    "enum": [
-      "commonDefaults"
-    ],
-    "type": "string"
-  },
-  "type": "array",
-  "uniqueItems": true
-}

Previous value: -"Narrow riddle-types/block-types/block-defaults down to these Riddle type(s) - e.g. [\"Quiz\"] on block-types drops every other type's question blocks while keeping the shared conventions (commonBlockProperties, the general Content/Ad/Quote blocks, ...). Ignored, with the whole document returned, on a topic that has no per-type split (form-field-types, result-blocks, the palette/question-bank documents). Omit for every type."New value: +"Narrow riddle-types/block-types down to these Riddle type(s) - e.g. [\"Quiz\"] on block-types drops every other type's question blocks while keeping the shared conventions (commonBlockProperties, the general Content/Ad/Quote blocks, ...). Ignored, with the whole document returned, on a topic that has no per-type split (form-field-types, result-blocks, concepts/defaults, the palette/question-bank documents). Not applicable to the block-defaults/riddle-defaults families - read the entity's own address instead. Omit for every type."

Added value: +[
+  {
+    "enum": [
+      "riddle://reference/index",
+      "riddle://reference/getting-started",
+      "riddle://reference/response-format",
+      "riddle://reference/riddle-builder/riddle-types",
+      "riddle://reference/riddle-builder/block-types",
+      "riddle://reference/riddle-builder/form-field-types",
+      "riddle://reference/riddle-builder/result-blocks",
+      "riddle://reference/palette/fields",
+      "riddle://reference/palette/built-in-palettes",
+      "riddle://reference/palette/fonts",
+      "riddle://reference/publish-defaults",
+      "riddle://reference/form-field-defaults",
+      "riddle://reference/question-bank/overview"
+    ],
+    "type": "string"
+  },
+  {
+    "pattern": "^riddle://reference/(block-defaults|riddle-defaults|concepts)/[^/]+$",
+    "type": "string"
+  }
+]

Removed value: -[
-  "riddle://reference/getting-started",
-  "riddle://reference/response-format",
-  "riddle://reference/riddle-builder/riddle-types",
-  "riddle://reference/riddle-builder/block-types",
-  "riddle://reference/riddle-builder/block-defaults",
-  "riddle://reference/riddle-builder/form-field-types",
-  "riddle://reference/riddle-builder/result-blocks",
-  "riddle://reference/palette/fields",
-  "riddle://reference/palette/built-in-palettes",
-  "riddle://reference/palette/fonts",
-  "riddle://reference/question-bank/overview"
-]

Removed value: -"string"

Previous value: -4New value: +8

Previous value: -"Every topic this tool can return, as uri => summary. Repeated in the response so a client that reached this tool without reading its schema still learns what else is documented."New value: +"Every topic this tool can return. The static documents are listed as uri => {sizeBytes, summary}, same as riddle://reference/index and what resources/list advertises as \"size\". The two generated families (block-defaults, riddle-defaults - one address per entity) are compacted under \"families\": the address template, how many addresses it has and what they cost in total, without the individual names - those, with their exact sizes, are in riddle://reference/index. An address is built by replacing the {variable} of a \"uriTemplate\" with the entity you are working on, e.g. riddle://reference/block-defaults/Flashcard. Repeated in the response so a client that reached this tool without reading its schema still learns what else is documented - and what reading it would cost, so the next call can be planned instead of guessed."

Previous value: -"Always present, even when no scoping was requested. {riddleType, blockTypes, fieldTypes, omit: the values you sent (or [] if you sent none); applied: whether this document was actually narrowed down or had something omitted; omitted: {\"<bucket>\": <count dropped>, ...}; note: a plain-language explanation, including why nothing was narrowed on a document with no per-type split, and - on block-defaults with \"omit\": [\"commonDefaults\"] - that the drop was requested rather than narrowed away."New value: +"Always present, even when no scoping was requested. {riddleType, blockTypes, fieldTypes: the values you sent (or [] if you sent none); applied: whether this document was actually narrowed down; omitted: {\"<bucket>\": <count dropped>, ...}; note: a plain-language explanation, including why nothing was narrowed on a document with no per-type split."

Previous value: -"Array of form blocks. Each block must have: title (string), type (FormBuilder), fields (array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}). 18 field types exist, including \"Privacy\" (GDPR consent text + the two consent checkboxes) and \"Captcha\" (spam protection; a \"google\"/\"cloudflare\" captchaType requires both key and secret, omitting either fails the build) - see riddle://reference/riddle-builder/form-field-types."New value: +"Array of form blocks. Each block must have: title (string), type (FormBuilder), fields (array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}). 18 field types exist, from plain inputs to the GDPR \"Privacy\" consent and \"Captcha\" spam protection - they and their properties are in riddle://reference/riddle-builder/form-field-types."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of minigame blocks. Supported types: SlotMachine (title, plus optional startBalance, winningProbability: Low/Medium/High, customSymbols replacing reel symbols with images, and the win message), WheelSpinner (title and an items array of at least 2 objects with title (string), type (Win/Loss/FreeSpin), percent (int, all of them must sum to 100) and award (string, required on Win items, optional on Loss/FreeSpin)), Sudoku (difficulty, score, plus an optional success message - supplying successMessage already switches the message on, isSuccessMessageEnabled: false switches it back off while keeping the text). The remaining per-type properties (custom symbol keys, win message fields, emojis, copy-to-clipboard, success message media) are in riddle://reference/riddle-builder/block-types. Only Sudoku has a score - neither SlotMachine nor WheelSpinner (nor its items) supports scoring, as both only produce a win/loss outcome; a Minigame consisting of nothing but a WheelSpinner therefore cannot be connected to a Leaderboard. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."New value: +"Array of minigame blocks. Supported types: SlotMachine (title, plus optional startBalance, winningProbability, custom reel symbols and win message), WheelSpinner (title and an \"items\" array of at least 2 objects with title, type (Win/Loss/FreeSpin), percent (all of them must sum to 100) and award (required on a Win item)), Sudoku (difficulty, score, plus an optional success message). Only Sudoku has a score - neither SlotMachine nor WheelSpinner (nor its items) supports scoring, so a Minigame consisting of nothing but a WheelSpinner cannot be connected to a Leaderboard. The remaining per-type properties are in riddle://reference/riddle-builder/block-types. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice), items (array of answer objects, each {\"title\": \"Answer text\", \"scores\": [2, 0]}) - every entry with a \"scores\" key holding an integer array, whose length must match the number of personalities and whose position corresponds to the personality index. Optional: media (URL or object) plus the usual choice-block display properties (wrapping, flexible height, item descriptions, and on MultipleChoice the selection limits) - see riddle://reference/riddle-builder/block-types."New value: +"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice), items (array of answer objects, each {\"title\": \"Answer text\", \"scores\": [2, 0]}) - every entry carries a \"scores\" integer array whose length must match the number of personalities and whose position corresponds to the personality index. Optional: media (URL or object) plus the usual choice-block display properties - see riddle://reference/riddle-builder/block-types."

Previous value: -"Array of personality objects (min 2). Each must have title (string). Optional: description (string), media (URL string or object), minScore / maxScore (0-100, the score window in which this personality wins), ctaButtonText, ctaButtonURL (supplying either shows the CTA button, clearing both hides it), isIncludeCTAButtonEnabled (explicit override for that: send false alongside a ctaButtonText to keep the button configured but hidden), areOtherResultsEnabled (the same override for the runner-up results), areOtherResultsMediaEnabled, otherResults (supplying them shows the runner-up results; each takes title, description, media, minScore, maxScore, ctaButtonText, ctaButtonURL)."New value: +"Array of personality objects (min 2). Each must have title (string). Optional: description, media (URL string or object), minScore / maxScore (0-100, the score window in which this personality wins), the CTA button (ctaButtonText / ctaButtonURL - supplying either shows it - plus the isIncludeCTAButtonEnabled override that keeps it configured but hidden) and the runner-up results (\"otherResults\" plus the areOtherResultsEnabled / areOtherResultsMediaEnabled overrides). The exact shape of each of those is in riddle://reference/riddle-builder/riddle-types under types.Personality."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice / Matrix / Order / Upvote / NetPromoterScore / RateIt / Swiper / Reaction / TextEntry / TierList / ThisOrThat / QuestionBank) and items (array of answer objects, each {\"title\": \"Answer text\"} plus that type's optional per-item properties; TextEntry has none, TierList needs \"tiers\" instead, QuestionBank \"questionBankId\" (int)). Optional: media (URL or object), otherOption ({isEnabled: bool, label: string}, SingleChoice/MultipleChoice only - adds an \"Other\" answer option with a free-text entry the respondent fills in; both keys are independent and optional, label defaults to \"Other\" and must not be empty), isRequired (all types). Three types differ structurally: TextEntry is a free-text answer with no items and no scoring at all; TierList needs \"tiers\" (at least 2 objects with title plus optional colorBg/colorText), its \"items\" being the optional pool the respondent drags into them; ThisOrThat takes at least 2 contenders as ONE flat \"items\" list, never a list of pairs - the pairs are formed positionally, so the item order decides who competes against whom, and each contender needs a title, an image or both. QuestionBank draws its questions from an existing question bank instead of items authored here: it needs questionBankId plus a non-empty \"questionBankBlocks\" (one entry per block type to draw into), and a block with none draws nothing and is rejected - see riddle://reference/question-bank/overview and the questionBank_* tools first. Every type has further display/behaviour properties on top of that (wrapping, flexible height, item descriptions, selection limits, remaining votes, sorting after vote, the RateIt scale (stars vs numbers and its bounds), rank format, mobile view, swiper text position and button type, text-entry validation, tier item media, this-or-that progress bar and separator, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges."New value: +"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice / Matrix / Order / Upvote / NetPromoterScore / RateIt / Swiper / Reaction / TextEntry / TierList / ThisOrThat / QuestionBank) and items (array of answer objects, each {\"title\": \"Answer text\"} plus that type's optional per-item properties). Optional: media (URL or object), isRequired, otherOption (SingleChoice/MultipleChoice only - adds an \"Other\" answer with a free-text entry). Three types differ structurally: TextEntry is a free-text answer with no items and no scoring at all, TierList needs \"tiers\" and treats its \"items\" as the optional pool the respondent drags into them, and QuestionBank draws its questions from an existing question bank instead of items authored here (\"questionBankId\" plus a non-empty \"questionBankBlocks\" - see riddle://reference/question-bank/overview first). Every type has further structural and display properties on top of that (ThisOrThat pairs its contenders positionally out of ONE flat \"items\" list, never a list of pairs; the RateIt scale, selection limits, wrapping, sorting after vote, mobile view, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of predictor blocks. Each block must have: title (string), type (PickTheWinner / GuessTheScore), items (array of objects with title and optional backgroundImage, logo, backgroundColor, textColor). Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."New value: +"Array of predictor blocks. Each block must have: title (string), type (PickTheWinner / GuessTheScore), items (array of objects with title and optional backgroundImage, logo, backgroundColor, textColor). When EDITING an existing Predictor (riddle_builder_update) a block also takes correctResult: the real-world outcome as the two scores in the order of its items - [3, 1] for a GuessTheScore block, or which side won for a PickTheWinner one ([1, 0] / [0, 1] / [1, 1] for a draw); [0, 0] clears it. It is rejected when the block is being created (including a \"$create\" marked block), since an outcome only exists once the Riddle does. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of question blocks. Each block must have: title (string), type (SingleChoice / MultipleChoice / TextEntry / Order / Flashcard / TypeRush / GuessIt / QuestionBank), and that type's content: items (array of answer objects, each {\"title\": \"Answer text\", \"isCorrect\": true|false} plus any of description/media/score/explanation for that one answer - the last two on SingleChoice/MultipleChoice only) on the choice types, answers (array of {\"title\": \"...\"} objects) on TextEntry, acceptableAnswers (array of {\"title\": \"...\"} objects) on GuessIt, questionBankId (int) on QuestionBank. Optional on every type: media (URL or object), explanation (object with title - supplying it is what switches the explanation on; send isExplanationEnabled: false to switch it back off while keeping the content). Every type has further display/behaviour properties on top of that (shuffling, layout, item descriptions, selection limits, hints, lives, guesses, rank format, case/space handling, column titles, blur mode, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges. Two GuessIt-specific traps: it is the one Quiz type without a \"score\" - it is always scored by how many guesses were needed, so sending \"score\" on it is a validation error, not silently ignored - and its \"media\" is the picture to be guessed rather than a decorative image (also not a validation error, just a different meaning than on every other type); on TypeRush set either a total block \"score\" or a per-item score, never both. QuestionBank draws its questions from an existing question bank instead of items authored here: it needs questionBankId plus a non-empty \"questionBankBlocks\" (one entry per block type to draw into) - a block with no questionBankBlocks draws nothing and is rejected. See riddle://reference/question-bank/overview and the questionBank_* tools before using it. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."New value: +"Array of question blocks. Each block must have: title (string; a QuestionBank block does not need one), type (SingleChoice / MultipleChoice / TextEntry / Order / Flashcard / TypeRush / GuessIt / QuestionBank), and that type's content: items (array of answer objects, each {\"title\": \"Answer text\", \"isCorrect\": true|false} plus any of description/media/score/explanation for that one answer - the last two on SingleChoice/MultipleChoice only) on the choice types, answers (array of {\"title\": \"...\"} objects) on TextEntry, acceptableAnswers (array of {\"title\": \"...\"} objects) on GuessIt, questionBankId (int) plus a non-empty \"questionBankBlocks\" on QuestionBank. Optional on the authored types: media (URL or object) and explanation (an object with a title is what switches it on; isExplanationEnabled: false switches it back off while keeping the content) - TypeRush has no explanation, and a QuestionBank block, which authors nothing itself, takes neither. Every type has further display/behaviour properties and its own traps on top of that (GuessIt accepts no \"score\" at all, TypeRush either a block score or per-item scores but never both, ...) - look them up per type in riddle://reference/riddle-builder/block-types instead of guessing names or value ranges, and read riddle://reference/question-bank/overview before your first QuestionBank block. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Array of content blocks. Each block must have: type (Content / Ad / Quote / InteractiveGraphic / FormBuilder / FormField / FormSelect). Content takes title plus optional description and media; Quote takes title, quoteText and quoteAuthor plus optional description, media, quoteMedia, quoteBackgroundColor, quoteTextColor; Ad takes either projectSlot ({slotId, variables}) or iframe ({url, height}) plus optional media, isNextButtonVisible, showNextButtonDelay, isShowNextButtonAfterDelayEnabled; InteractiveGraphic takes an \"images\" array (min 1) of {media, label, hotspots} - \"media\" and at least one \"hotspots\" entry are required on every image you create (an image without media is an empty canvas its hotspots float on, one without hotspots is a picture nobody can interact with), \"label\" only names the image inside the editor; each hotspot placed at x/y percentages with an \"action\" that decides its remaining properties (\"showInfo\" pop-up, \"openUrl\", \"goToNextBlock\", \"noAction\", \"goToImage:<image id or label>\" to another image of the same block, which you can point at by its \"label\" so a connection needs no prior riddle_get). Hotspot coordinates cannot be judged from JSON: build it, publish it, look at the rendered Riddle in a browser and correct the hotspots that are off - see the \"authoringNote\" in riddle://reference/riddle-builder/block-types. A Story has no question blocks of any kind - use riddle_builder_poll or riddle_builder_quiz if you need answers. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."New value: +"Array of content blocks. Each block must have: type (Content / Ad / Quote / InteractiveGraphic / FormBuilder / FormField / FormSelect) plus that type's own content - Content a title, Quote a title with quoteText and quoteAuthor, Ad either a projectSlot ({slotId, variables}) or an iframe ({url, height}), InteractiveGraphic an \"images\" array (min 1) whose every image needs \"media\" and at least one \"hotspots\" entry. A hotspot is placed at x/y percentages, and those cannot be judged from JSON: build it, publish it, look at the rendered Riddle in a browser and correct the hotspots that are off. A Story has no question blocks of any kind - use riddle_builder_poll or riddle_builder_quiz if you need answers. The properties of each type, the hotspot actions (including \"goToImage:<image id or label>\") and the authoring note are in riddle://reference/riddle-builder/block-types. Lead-collecting blocks go in the same array: FormBuilder (\"fields\": array of field objects, each {\"title\": \"Your email\", \"type\": \"Email\"}, the 18 types are in riddle://reference/riddle-builder/form-field-types), FormField (one standalone field) or FormSelect (\"form\": UUID of an existing Form Riddle). Name and Email fields are what make this Riddle Leaderboard-connectable."

Previous value: -"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact names: presetStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Riddle-level design and behaviour settings (design, open/close scheduling, timers, progress, live score, result visibility, vote integrity, page chrome, ~20 UX flags); only the keys you send are applied and a key only exists for the types that have it. On a Leaderboard this is also where its own display settings live, the podium colours (color1st/color2nd/color3rd) and isEmailVerificationEnabled among them. Exact name: riddle://reference/concepts/preset."

Previous value: -"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: publishStructure in riddle://reference/riddle-builder/riddle-types."New value: +"Publish CONFIGURATION stored on the Riddle - an object, and not to be confused with this tool's separate top-level \"publish\" boolean, which publishes the Riddle right away. Covers showcase/QR code, lead verification (double opt-in, email OTP, SMS OTP - mutually exclusive), email automation, dataLayer, tracking, integrations, embedSettings. Keys: riddle://reference/concepts/publish."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"The new order of the Riddle's blocks, as the complete list of their IDs - [3, 1, 2] puts block 3 first. Complete means every ID the Riddle has after this edit, exactly once: a partial list is rejected, because where the blocks you left out belong is exactly what it does not say. It is applied after everything else in the same call, so a block you delete here must NOT be listed and a block you add here MUST be - give a \"$create\" entry an explicit \"id\" to name it, taken from \"nextBlockId\" in the riddle_get response (count up from it for several new blocks). Do not derive that id from the ids in \"build\": they are shared with the Riddle's results and personalities and are never reused, so the next one is usually already taken; claiming a taken id is rejected with an error naming the free one. The same marker works inside a block, next to the collection it orders: {\"id\": 3, \"$itemsOrder\": [2, 1]} reorders that block's items, \"$fieldsOrder\" a Form's fields, and so on. It reaches one level deeper through a merged \"fields\" edit: {\"id\": 3, \"fields\": [{\"id\": 5, \"$itemsOrder\": [2, 1]}]} reorders the items of that one Dropdown field. The one limit is that the collection's entries need ids of their own. Collections without ids - reply-to/CC/BCC addresses, selected Riddles/types/tags, a TypeRush item's answers, a reaction scale, a Matrix question's scale, custom symbols, riddle connections, tracking networks, share networks, ad variables, per-block timer times, a personality answer's scores, a Predictor block's items (their id IS their position, 0/1 - resend \"items\" in the order you want instead), a Swiper block's items (their position IS the swipe answer, first card \"dislike\", second \"like\" - swap the two by resending both cards by id) - are simply sent in the order you want them in, and the error says so if you try."New value: +"The new order of the Riddle's blocks, as the complete list of their IDs - [3, 1, 2] puts block 3 first. Complete means every ID the Riddle has after this edit, exactly once: a partial list is rejected, because where the blocks you left out belong is exactly what it does not say. It is applied after everything else in the same call, so a block you delete here must NOT be listed and a block you add here MUST be - give a \"$create\" entry an explicit \"id\" to name it, taken from \"nextBlockId\" in the riddle_get response (count up from it for several new blocks) and never derived from the ids in \"build\", which are shared with the Riddle's results and personalities; claiming a taken id is rejected with an error naming the free one. The same marker works inside a block, next to the collection it orders: {\"id\": 3, \"$itemsOrder\": [2, 1]} reorders that block's items, \"$fieldsOrder\" a Form's fields, and it reaches one level deeper through a merged \"fields\" edit - {\"id\": 3, \"fields\": [{\"id\": 5, \"$itemsOrder\": [2, 1]}]} reorders the items of that one Dropdown field. Only a collection whose entries have ids of their own can be ordered at all, and a few that do still reject the marker because an entry's position carries meaning of its own - riddle://reference/concepts/merge-semantics says which collection is which, and the error says so too if you try."

Previous value: -"The blocks to change, add or remove - only the ones you touch, everything else stays as it is. To EDIT, pass the block's \"id\" (riddle_get reports it) plus only the properties that change - {\"id\": 3, \"title\": \"New question title\"}; the block's other properties, and every block you do not list, are untouched. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new block needs (the same shape the riddle_builder_<type> tool of this Riddle's type takes) - {\"$create\": true, \"type\": \"SingleChoice\", \"title\": \"New question\", \"items\": [...]}. To REMOVE, pass \"id\" plus \"$delete\": true - {\"id\": 3, \"$delete\": true}. Removing a block still referenced by custom logic is rejected unless \"logic\" (see that field) resolves it in the same request. A block cannot change its \"type\" in an edit (delete it and add a new one instead), and an unknown \"id\" is rejected with the list of IDs that do exist. The collections INSIDE a block whose entries have a stable id merge the very same way - a question's \"items\" (of every type: Quiz/Personality answers, Poll answers, Matrix rows, Swiper cards, TierList tiers and items, ThisOrThat contenders, WheelSpinner items), an InteractiveGraphic's \"images\" and the \"hotspots\" inside each of them (deleting an image a hotspot still points at with \"goToImage:\" is rejected the same way a logic-referenced block is - repoint or delete those hotspots in the same request), a FormBuilder's \"fields\" and a Dropdown field's \"items\": {\"id\": 3, \"items\": [{\"id\": 2, \"title\": \"Bonn\"}]} renames one answer and leaves the others alone, {\"$create\": true, ...} adds an entry, {\"id\": 2, \"$delete\": true} removes one - those entry ids are scoped to their own collection and never come from \"nextBlockId\", so they repeat across blocks and only mean anything together with the id of the block holding them. An entry with no \"id\" is rejected rather than added under a new one, so a resend that dropped its ids cannot silently re-create the collection and break references into it (blockId_fieldId identifiers, logic, personality scores) - add \"$create\": true when you do mean a new entry. Every entry of every collection is an object, which is what lets it carry its \"id\" or its marker and so address a stored entry. Minimum/maximum entry counts are checked against the result of the merge, not against what you sent, and so is any rule spanning the whole collection (a question needs a correct answer; a WheelSpinner's item percents must sum to 100, so send the percent of every item you shift weight between). Collections that have NOT opted into this (a question bank's target blocks, a Matrix question's \"scale\") are still replaced wholesale - send every entry you want to keep. A Matrix \"scale\" is keyed by the value each rating stands for and has no ids at all, so a merge-style entry ({\"id\": 2, ...}, \"$create\", \"$delete\") is rejected instead of taken as the new scale: resend the complete scale, e.g. {\"id\": 3, \"scale\": {\"0\": {\"title\": \"Bad\"}, \"1\": {\"title\": \"Okay\"}, \"2\": {\"title\": \"Good\"}}}."New value: +"The blocks to change, add or remove - only the ones you touch, everything else stays as it is. To EDIT, pass the block's \"id\" (riddle_get reports it) plus only the properties that change - {\"id\": 3, \"title\": \"New question title\"}. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new block needs, the same shape the riddle_builder_<type> tool of this Riddle's type takes - {\"$create\": true, \"type\": \"SingleChoice\", \"title\": \"New question\", \"items\": [...]}. To REMOVE, pass \"id\" plus \"$delete\": true. A block cannot change its \"type\" in an edit (delete it and add a new one instead), and an unknown \"id\" is rejected with the list of IDs that do exist. The collections INSIDE a block work the same way wherever their entries have ids - {\"id\": 3, \"items\": [{\"id\": 2, \"title\": \"Bonn\"}]} renames one answer and leaves the others alone - and are replaced wholesale where they do not. Which collection is which, what an entry id is scoped to, why an entry without an \"id\" or \"$create\" is rejected, which deletes are refused for still being referenced (custom logic, a hotspot's \"goToImage:\"), and which rules are checked against the merge result rather than against what you sent: riddle://reference/concepts/merge-semantics, with the marker rules themselves in riddle://reference/concepts/editing."

Previous value: -"Personality Test only. The personalities to change, add or remove - only the ones you touch, everything else stays as it is, merged entry-by-entry by \"id\" exactly like the Riddle's own \"blocks\" (see EDIT_BLOCKS). To EDIT, pass the personality's \"id\" (riddle_get reports it) plus only the properties that change. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new personality needs (the same shape riddle_builder_personality takes). To REMOVE, pass \"id\" plus \"$delete\": true. An entry with no \"id\" and no \"$create\" is rejected the same way a block is - it has no \"id\"; add \"$create\": true to add it as a new one instead. Reorder with \"$personalitiesOrder\": the complete list of personality ids in the new order, the same way \"$blocksOrder\"/\"$itemsOrder\" work (see EDIT_BLOCKS_ORDER). The minimum of 2 personalities is checked against the result AFTER the merge, so a \"$delete\" that would leave fewer than 2 is rejected. The scores already stored on every answer item follow their personality BY IDENTITY, not by position: a personality that stays keeps its score wherever it ends up in the order, a deleted personality takes its scores with it, and a newly created personality starts at 0 on every existing answer item until you say otherwise - resend the affected blocks' \"items\" with their full \"scores\" arrays in the same call to set them yourself (that is applied after this and simply wins)."New value: +"Personality Test only. The personalities to change, add or remove - only the ones you touch, everything else stays as it is, merged entry-by-entry by \"id\" exactly like the Riddle's own \"blocks\" (see EDIT_BLOCKS). To EDIT, pass the personality's \"id\" (riddle_get reports it) plus only the properties that change. To ADD, pass \"$create\": true instead of an \"id\" plus everything a new personality needs (the same shape riddle_builder_personality takes). To REMOVE, pass \"id\" plus \"$delete\": true. An entry with no \"id\" and no \"$create\" is rejected the same way a block is - it has no \"id\"; add \"$create\": true to add it as a new one instead. The order of the personalities is NOT editable: there is no \"$personalitiesOrder\" (sending one is rejected) and, because this collection is merged by id, the order the entries are sent in has no meaning either - a \"$create\" is appended at the end and everything else keeps the place it has. Reorder them in the Creator if the order matters. The minimum of 2 personalities is checked against the result AFTER the merge, so a \"$delete\" that would leave fewer than 2 is rejected. The scores already stored on every answer item follow their personality BY IDENTITY, not by position: a personality that stays keeps its score, a deleted personality takes its scores with it, and a newly created personality starts at 0 on every existing answer item until you say otherwise - resend the affected blocks' \"items\" with their full \"scores\" arrays in the same call to set them yourself (that is applied after this and simply wins)."

Previous value: -"New result pages (Quiz), same shape as in riddle_builder_quiz. Replaces ALL current result pages with what you send, in the order you send it. Result pages are deliberately not editable and not reorderable: there is no \"$resultsOrder\" marker, no \"$create\"/\"$delete\" on an entry, and a page's \"id\" does not address it for a partial update - a score window, its blocks and the answers it reveals only make sense as one consistent set. Read them with riddle_get first and resend every page you want to keep, including its \"id\", which is honored to keep the page stable across the resend. Omit the field to keep all result pages untouched."New value: +"New result pages (Quiz), same shape as in riddle_builder_quiz. Replaces ALL current result pages with what you send, in the order you send it: result pages are deliberately neither editable per entry nor reorderable, so read them with riddle_get first and resend every page you want to keep, including its \"id\", which is honored to keep the page stable across the resend. Omit the field to keep all result pages untouched. Why, and which markers are rejected on a page: riddle://reference/concepts/result-pages."

Previous value: -"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/riddle-builder/block-defaults states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."New value: +"Leaves parts of the returned envelope out. Values: \"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole sections) and \"build.omittedDefaults\" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. \"uuid\"/\"type\"/\"modifiedAt\" are always returned. Reach for omit: [\"build.omittedDefaults\"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under \"omittedFields\", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's."

Previous value: -"Leaves the per-block \"omittedDefaults\" maps out of every echoed-back build config, for a much smaller answer: omit: [\"build.omittedDefaults\"]. The same defaults are stated per Riddle type and block type in riddle://reference/riddle-builder/block-defaults, so nothing is lost - what you must not do either way is resend those values. Omit the parameter to keep them. The other values of riddle_get's \"omit\" do not apply here: this envelope has no sections to drop."New value: +"Leaves the per-block \"omittedDefaults\" maps out of every echoed-back build config, for a much smaller answer: omit: [\"build.omittedDefaults\"]. The same defaults are stated in riddle://reference/riddle-defaults/<riddle type> and riddle://reference/block-defaults/<block type>, so nothing is lost - what you must not do either way is resend those values. Omit the parameter to keep them. The other values of riddle_get's \"omit\" do not apply here: this envelope has no sections to drop."

Previous value: -"Leaves parts of the response out - the one way to make this call smaller. Valid values:\n\"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole envelope sections) and\n\"build.omittedDefaults\" (the per-block \"omittedDefaults\" maps inside every build\nconfiguration in the response, including \"published.build\" - not a section, but by far\nthe largest part of one). Omit the parameter, or pass [], for everything;\n\"uuid\"/\"type\"/\"modifiedAt\" are always present and cannot be left out.\nWhich value to reach for: \"build.omittedDefaults\" shrinks a read-back by ~85-90% and\nloses no information, since riddle://reference/riddle-builder/block-defaults states the\nvery same defaults per Riddle type and block type - the right default for any call that\ndoes not specifically need to know which properties sit at their default. Whole sections\nare worth naming when you truly do not need them: \"published\" is a second full build\nconfiguration whenever the draft has unpublished changes (about half the response),\nwhile \"warnings\"/\"nextBlockId\"/\"context\" together are only a few percent of it - though\nleaving out \"published\" also skips re-serializing the live version entirely, and\n\"context\" skips that section's extra lookups (features/origin, cover image, preset\ndiff), so the saving is in work as well as bytes.\nWhatever you leave out is echoed back in \"omittedFields\", so a key missing from the\nresponse never has to be read as \"this Riddle has none of that\", only as \"I asked for it\nto be left out\"; a call that omitted nothing carries no such key. With UUIDs, the same\nomissions apply to every entry."New value: +"Leaves parts of the response out - the one way to make this call smaller. Valid values:\n\"build\", \"warnings\", \"nextBlockId\", \"published\", \"context\" (whole envelope sections) and\n\"build.omittedDefaults\" (the per-block \"omittedDefaults\" maps inside every build\nconfiguration in the response, including \"published.build\" - not a section, but by far\nthe largest part of one). Omit the parameter, or pass [], for everything;\n\"uuid\"/\"type\"/\"modifiedAt\" are always present and cannot be left out.\nWhich value to reach for: \"build.omittedDefaults\" shrinks a read-back by ~85-90% and\nloses no information, since riddle://reference/block-defaults/<block type> and\nriddle://reference/riddle-defaults/<riddle type> state the very same defaults - the right\ndefault for any call that does not specifically need to know which properties sit at\ntheir default. Whole sections\nare worth naming when you truly do not need them: \"published\" is a second full build\nconfiguration whenever the draft has unpublished changes (about half the response),\nwhile \"warnings\"/\"nextBlockId\"/\"context\" together are only a few percent of it - though\nleaving out \"published\" also skips re-serializing the live version entirely, and\n\"context\" skips that section's extra lookups (features/origin, cover image, preset\ndiff), so the saving is in work as well as bytes.\nWhatever you leave out is echoed back in \"omittedFields\", so a key missing from the\nresponse never has to be read as \"this Riddle has none of that\", only as \"I asked for it\nto be left out\"; a call that omitted nothing carries no such key. With UUIDs, the same\nomissions apply to every entry."

Previous value: -"Leaves parts of the response out. The only value with anything to leave out here is \"build.omittedDefaults\": every block then loses its \"omittedDefaults\" map (the properties left out for still being at their default, with the value each one is at), for a much smaller response. Nothing is lost by it: the same defaults are stated per Riddle type and block type in riddle://reference/riddle-builder/block-defaults - and a value read there must not be resent as the property either way. Same parameter as riddle_get's; its section values do not apply here, this envelope has no such sections."New value: +"Leaves parts of the response out. The only value with anything to leave out here is \"build.omittedDefaults\": every block then loses its \"omittedDefaults\" map (the properties left out for still being at their default, with the value each one is at), for a much smaller response. Nothing is lost by it: the same defaults are stated in riddle://reference/riddle-defaults/<riddle type> and riddle://reference/block-defaults/<block type> - and a value read there must not be resent as the property either way. Same parameter as riddle_get's; its section values do not apply here, this envelope has no such sections."