@@ -23,9 +23,16 @@ unbound report's switch stays the one-key patch it always was. `runtimeFilter` a
 `drilldown` are kept: the joined branch reads both. Switching between two non-joined
 types keeps the binding; switching away from `joined` restores nothing — the author
 re-binds. `blocks` is never touched. The clear holds for the patch and for the save that
-follows it. The metadata-admin editor rebuilds its draft as the served draft spread over
-`layered.effective` (on load, after each save and after publish), and `effective` is the
-published layer, so a report whose PUBLISHED version was bound gets those keys back in the
-draft after the first draft save until it is published, and a report already saved `joined`
-with stale keys is not repaired on load. Both are the host's draft-over-baseline merge,
-objectui#10765.
+follows it. At this change the metadata-admin editor rebuilds its draft as the served draft
+spread over `layered.effective` (on load, after each save and after publish), and
+`effective` is the published layer, so a report whose PUBLISHED version was bound gets those
+keys back in the draft after the first draft save until it is published, and a report already
+saved `joined` with stale keys is not repaired on load. Both are the host's
+draft-over-baseline merge, objectui#10765.
+
+⚠️ **Dated note, 2026-09-27 — that merge has since been removed — objectui#10765.** Later in
+this same release the metadata-admin editor takes a served draft as-is instead of spreading
+it over the published layer, so the clear holds across the refresh after the save and through
+publish. A report already saved `joined` with stale keys is still not repaired on load; the
+author deletes them from the JSON tab. The rest of this entry is kept as the reading of this
+change; the objectui#10765 entry states what the editors now do.
@@ -19,4 +19,7 @@ The spread existed for a partial draft overlay that never reaches these editors:
 row raw, and every draft writer sends a whole document. So each site now takes the served draft
 as-is when there is one and falls back to `effective` (then `code`) only when no draft exists;
 the inherited `type` the spread was protecting is already inside the draft. `config.toDraft`
-still normalises whatever is taken, now on the post-publish refresh as well.
+still normalises whatever is taken, now on the post-publish refresh as well. This removes the
+reach limit the objectui#10746 entry states — a bound published report getting its cleared
+keys back after the first draft save; a report already saved `joined` with stale keys is still
+not repaired on load, and the author deletes them from the JSON tab.
@@ -39,7 +39,10 @@ import { isExternalWider, deriveMasterObject } from './owd-sharing.js';
 import { toast } from 'sonner';
 
 
-/** A single object's loaded OWD baseline (already merged over any pending draft). */
+/**
+ * A single object's loaded OWD values — read from its pending draft as-is when
+ * one exists, else from its layered baseline (objectui#10765).
+ */
 interface OwdRow {
   name: string;
   label: string;
@@ -143,8 +146,9 @@ export function PackageOwdOverviewPanel({
 
       // The list row carries `sharingModel` but not reliably `fields` (needed
       // for the master link), and never the pending-draft value — so read each
-      // object's merged body (layered ∪ its draft), exactly as the per-object
-      // Settings tab does, and derive every column from that one source.
+      // object's body (its pending draft as-is, else its layered baseline),
+      // exactly as the per-object Settings tab does, and derive every column
+      // from that one source.
       const built = await Promise.all(
         names.map(async (name): Promise<OwdRow> => {
           const [layRaw, draftResp] = await Promise.all([
@@ -237,7 +241,7 @@ export function PackageOwdOverviewPanel({
     setSaveError(null);
     try {
       // Each changed row lands as that object's package-scoped DRAFT: read the
-      // fresh merged body, apply just the OWD pair (unset → drop the key), and
+      // fresh body (below), apply just the OWD pair (unset → drop the key), and
       // save. Identical to the per-object Settings write, N times — publish
       // then goes through the same package security-domain gate unchanged.
       for (const s of changed) {
 
@@ -2971,8 +2971,9 @@ export function DataPillar({
         setHasDraft(!!draftBody);
         setHasBaseline(!!(lay.effective ?? lay.code));
         // The projection baseline: the object as the SERVER has it. `objDraft`
-        // below merges the draft on top, which is right for the editor and
-        // wrong for a `select`.
+        // above is the pending draft as-is when one exists, which is right for
+        // the editor and wrong for a `select`: a draft-only field is not a
+        // column the data API can answer yet (see `gridColumns`).
         setPublishedFieldNames(new Set(readFields(baseline.fields).entries.map((e) => e.name)));
       } catch (e) {
         if (!cancelled) setError(formatMetadataError(e));