Filing gate ③: a ruled task. Stage (iii) of ruling 甲 on #20051 (5856781584, batch #227 item 2, maintainer 「开始总监决裁」).
Blocked-by: #20456
Filed by the triage seat (seat post #6015, session_01AavokzJ5DndAwitDXvKy4U) in place of domain:spec seat 2, which the ruling names as filer and which is vacant (#18549). The maintainer asked the triage seat directly, verbatim: 「#20051 的子卡 你为什么不能立」. ⛔ Not a claim.
What the ruling orders (item 1, stage iii, verbatim)
Sub-card 「ADR-0005 appendix (c) amendment」: governed (docs/adr/**), Tier H, the maintainer's APPROVED review; the appendix says the persisted document is the parsed body once every round-trip key is declared, with a dated note pointing at the spec symbols.
The text it amends
docs/adr/0005-metadata-customization-overlay.md, appendix (c): 「The persisted document is the original request.item, NOT parsed.data. Studio attaches auxiliary fields (isPinned, isDefault, sortOrder, objectName, …) that aren't in the canonical schema; storing parsed.data would silently strip them on every save.」
Why it is blocked
The amendment says the parsed body is persisted once every round-trip key is declared, and its dated note cites the spec symbols that stage (ii) creates. It cannot be written truthfully before those symbols exist on main. Release when the stage (ii) card closes with its PR merged, after reading the symbol names on main.
Acceptance
Part of #20051
Filing gate ③: a ruled task. Stage (iii) of ruling 甲 on #20051 (
5856781584, batch #227 item 2, maintainer 「开始总监决裁」).Blocked-by: #20456
Filed by the triage seat (seat post #6015,
session_01AavokzJ5DndAwitDXvKy4U) in place ofdomain:specseat 2, which the ruling names as filer and which is vacant (#18549). The maintainer asked the triage seat directly, verbatim: 「#20051 的子卡 你为什么不能立」. ⛔ Not a claim.domain:skillsseat, sincedocs/adr/**is a governed surface; it lands at Tier H with the maintainer's APPROVED review.options.KINDwith the strict per-kind schema and persist the PARSED body — the door half of objectui#10380 #20051 (spec(ui): a flattenedviewKind: 'list'view overlay with nocolumnsis refused by the list overlay member, then ACCEPTED by the form overlay member, so its list keys are stripped unjudged and a wrong 200 stores it #20186, spec(ui): a flattened view overlay acceptsowner/hiddenat the save door and nothing reads either, sohidden: truesaves clean and the view stays listed #20230, metadata: a page saved withouttypeis stored and served without it, soPageSchema's declaredtypedefault (record) never reaches a consumer that reads the served body #20101), none of them this stage. No open duplicate.What the ruling orders (item 1, stage iii, verbatim)
The text it amends
docs/adr/0005-metadata-customization-overlay.md, appendix (c): 「The persisted document is the originalrequest.item, NOTparsed.data. Studio attaches auxiliary fields (isPinned,isDefault,sortOrder,objectName, …) that aren't in the canonical schema; storingparsed.datawould silently strip them on every save.」Why it is blocked
The amendment says the parsed body is persisted once every round-trip key is declared, and its dated note cites the spec symbols that stage (ii) creates. It cannot be written truthfully before those symbols exist on
main. Release when the stage (ii) card closes with its PR merged, after reading the symbol names onmain.Acceptance
options.KINDwith the strict per-kind schema and persist the PARSED body — the door half of objectui#10380 #20051 itself.Part of #20051