fix: unwrap label-as-key option objects in ask_user

Author: will-lamerton

source/utils/type-helpers.spec.ts

@@ -144,6 +144,13 @@ test('toOptionString extracts content-shaped options', t => {
 	);
 });
 
+test('toOptionString uses the lone key when value is empty (label-as-key shape)', t => {
+	t.is(
+		toOptionString({'Playfair Display - elegant, high-contrast, editorial': ''}),
+		'Playfair Display - elegant, high-contrast, editorial',
+	);
+});
+
 test('toOptionString falls back to JSON for unlabeled objects', t => {
 	t.is(toOptionString({foo: 1}), JSON.stringify({foo: 1}));
 });

source/utils/type-helpers.ts

@@ -238,6 +238,22 @@ export function toOptionString(option: unknown): string {
 				return candidate;
 			}
 		}
+		// Some models emit each option as a single-entry map where the KEY is
+		// the display text and the value is empty, e.g.
+		// `{"Playfair Display - elegant, high-contrast, editorial": ""}`. None
+		// of the known keys match, so fall back to the lone key as the label.
+		// Guarded on an empty value so genuinely-keyed objects like `{foo: 1}`
+		// still serialize to JSON.
+		const entries = Object.entries(option);
+		if (entries.length === 1) {
+			const [key, value] = entries[0];
+			if (
+				key.trim() !== '' &&
+				(value === '' || value === null || value === undefined)
+			) {
+				return key;
+			}
+		}
 	}
 	return ensureString(option);
 }