[P0] build-time vs runtime validation parity: objectstack build accepts metadata the runtime rejects #1876

Activity

1. os-zhuang

   added a commit that references this issue on Jun 15, 2026

   fix(cli): keep non-self-contained hook handlers out of body-only lowe…

   ...

   8c7e7e4
2. os-zhuang commented on Jun 15, 2026

   

   os-zhuang

   on Jun 15, 2026

   Contributor

   More actions

   Resolved — closing. Both repros in this issue are addressed, and a parity sweep confirmed no remaining schema-level divergence:

   • Repro Add metamodel interfaces for ObjectQL/ObjectUI contract #1 (legacy object/aggregate dashboard widgets pass build, runtime rejects) — already closed by the ADR-0021 single-form cutover. DashboardWidgetSchema requires dataset/values, and objectstack build (ObjectStackDefinitionSchema.safeParse) + the runtime metadata plugin (ObjectStackDefinitionSchema.parse) validate with the same schema. Verified empirically that a legacy widget is rejected at build; there's an existing regression test.
   • Repro ✨ Set up Copilot instructions #2 (body-only hooks ReferenceError) — fixed in fix(cli): keep non-self-contained hook handlers out of body-only lowering (#1876) #1907 (PR): detectFreeIdentifiers refuses body-only lowering for handlers referencing module-scope identifiers, falling back to bundling the real closure.

   Parity sweep: build and runtime both validate the artifact via ObjectStackDefinitionSchema, and the runtime per-item validate() adds no stricter check — so schema-level "build accepts what runtime rejects" no longer occurs. The remaining divergences are semantic/callable-level, and those instances (#1877 conditions, #1870 callables, #1876 repro #2 hook bodies) are now fixed.

   If a new build↔runtime divergence surfaces, please file it as a fresh focused issue rather than reopening this umbrella.
3. os-zhuang

   closed this as completedon Jun 15, 2026