[ako]

Fixes #1327 (mirror of mendixlabs#1454).

Symptom (as reported)

alter snippet M.S { set (lazyLoading: false) on comboBox1; } stores PrimitiveValue = "no" (and "yes" for true). Studio Pro stores pluggable Boolean properties as "true" / "false".
… a bare true is stored as "yes", and the compiled client reads that as false. mx check and mxbuild both pass, and the property silently does the opposite.

Cause

setPluggableWidgetPropertyMut spelled every Go bool as yes/no, whatever the property's declared ValueType.Type. CREATE's own pluggable path (widget_engine.go) writes %t, so the two write paths disagreed.

Fix

The spelling now comes from the property's declared kind, the same way columnValueField already picks the value field:

• Boolean → "true" / "false"
• an Enumeration that declares yes/no keys keeps taking a boolean as those keys (the reporter's scan found 2.1k such values)
• any other enumeration refuses a boolean and names its keys

TestSetWidgetProperty_PluggableWidget had pinned "no" on a fixture with no kind. It now asserts "false", with a comment.

Evidence

• Control: with the fix stashed, TestSetPluggableBooleanWritesTrueFalse_1454 fails with PrimitiveValue = "yes", want "true".
• Real run (blank 11.13.0 app, reporter's set (showFooter: true, clearable: false) on cbColor): the unfixed and fixed builds differ in exactly the two reported values ("no"→"false", "yes"→"true"). Both report The app contains: 0 errors., which is why only the stored bytes show the defect.
• Regression script: mdl-examples/bug-tests/1454-alter-set-pluggable-boolean-true-false.mdl. Finding recorded.
• make build && make test && make lint, make check-mdl and make check-findings all pass.

Side note, not fixed here: describe prints neither showFooter nor clearable for a combobox on either build, so the bug-test checks the result with bson dump.

---

Generated by Claude Code