docs: cite the landing commits where ten objectui issue links answer 404 (objectui#10755)

content/docs/fields/lookup.mdx

@@ -73,7 +73,7 @@ control. `FieldSchema` routes a field's `options` through that schema, so
 authoring `description` on an option in an object document fails the **whole
 field** with a 422 — the key lives on the runtime read model the widget consumes
 and must never reach authored object metadata
-([objectui#7014](https://github.com/objectstack-ai/objectui/issues/7014)). The
+(`0e3b3be09`). The
 `dataSource` a host injects and the `onCreateNew` callback it passes are widget props,
 not metadata.
 

content/docs/fields/select.mdx

@@ -127,7 +127,7 @@ field designer writes it whenever you fill only the value box) is therefore a do
 the platform stores and serves, and every option widget — `select`, `multiselect`,
 `radio`, `checkboxes` — **displays its `value`** for it rather than an empty row, on
 both the editable and the read-only path
-([objectui#9230](https://github.com/objectstack-ai/objectui/issues/9230)). A label that
+(`20b507aff`). A label that
 is only whitespace is treated the same way.
 
 This is a display fallback, not a repair: the stored option keeps its empty `label`.