docs(skill): address review — purge the last no-defaults statements

CodeRabbit caught two passages my phrase-sweep missed (the checklist's
field-types line still banning arrays/multi-select, and the worked
example's summary still claiming no prefilled defaults); a re-read
caught a third in the worked example's intro. All three now state the
shipped dialect.

Author: ardaerzin

.agents/skills/write-template-playbooks/references/prompting-checklist.md

@@ -61,8 +61,9 @@ builder-reliability findings, or design reasoning).
   trigger) so the user can veto. Commit and trigger are approval gates; pre-state what is
   coming.
 
-Field types are `string`, `number`, `integer`, `boolean` only. No arrays, no nested objects,
-no multi-select. Formats: `date`, `date-time`, `email`, `uri`, `multiline`.
+Field types are `string`, `number`, `integer`, `boolean`, and the multi-pick array
+`{type: "array", items: {type: "string", enum: [...]}}`. No nested objects. Formats: `date`,
+`date-time`, `email`, `uri`, `multiline` (date fields ignore defaults).
 
 ## Verification (against our runtime)
 

.agents/skills/write-template-playbooks/references/worked-example.md

@@ -2,9 +2,9 @@
 
 Copy from this. It is the seed playbook, already corrected against the runtime: `test_run`
 explores uncommitted tools through its delta, the trigger test is the Lightning "Test event"
-button (Play "Run" for schedules), and no field is prefilled because `request_input` has no
-default. Notice how each section is short, names exact tools, and ends the instructions on the
-terminal side effect.
+button (Play "Run" for schedules), and proposals ride each field's `default` so the form is
+one-click acceptable. Notice how each section is short, names exact tools, and ends the
+instructions on the terminal side effect.
 
 The fenced block below is the file that ships as `references/agent-templates/changelog-writer.md`.
 
@@ -80,8 +80,9 @@ authorize).
 - **Required vs researchable is explicit.** The repo and publish target are required (the agent
   cannot proceed without them). The release process is researchable, so its enum leads with
   "Use your best judgment."
-- **No prefilled defaults.** The repo guess lives in the field description, not a default field.
-  The recommended enum choice is listed first.
+- **Proposals ride the `default` field.** The repo guess becomes the field `default` when a
+  prior read surfaces one; the recommended enum choice is set as the `default`, and the
+  built-in Other… covers off-list answers.
 - **The priors table proposes a setup** per release process, so the agent does not interrogate
   the user about the trigger and tools.
 - **The instructions template ends on the publish tool** and names each tool in order. It does