[vannt-dev]

Summary

Release 1.12.0 of all five packages (core, react, vue, angular, svelte):

• conditions as data with appearWhen / requiredWhen and JSON Schema mapping (feat(core): conditions as data with appearWhen and requiredWhen #116)
• labels on the built-in controls in every adapter; markup change in docs/MIGRATING.md (fix: label the built-in renderers in every adapter #124)
• DynamicFormDevTools for Svelte (feat(svelte): add DynamicFormDevTools #117), a built-in control for all 14 types in Angular (fix(angular): draw a built-in control for every field type #125)
• every adapter's @dynamic-field-kit/core peer is now ^1.12.0, because the adapters
  import resolveVisible and makeLabelId. Installing an adapter with an older core
  now fails at install time instead of at run time.

The versions and changelogs came from the same steps release.yml runs
(create-changeset --bump minor, changeset version, lockfile sync). They are committed here
because the peer floor can't land on develop while core is still 1.11.0: the
React/Vue/Angular peer-range gates pack the workspace core and fail with ERESOLVE.

How to publish after merge

Run Release on develop with resume ticked. A normal run (resume off) would bump
everything again, to 1.13.0.

1. resume + dry_run: the log should show 1.12.0 for all five, and the list of
   packages needing their own tag should be empty.
2. resume only: publishes the five packages to npm with provenance, tags v1.12.0 and
   creates the GitHub Release from core's 1.12.0 CHANGELOG section.

Then sync master the same way as #91 and #103.

Verification

All on this commit, Node 26 / npm 11.19:

• npm ci, npm run build, lint, format-check, typecheck, core type tests,
  test:scripts, npm audit --omit=dev --audit-level=high: all pass
• package tests: core 393, react 189, vue 208, angular 121, svelte 209; smoke 12 + 12
• verify-framework-deps, cross-framework imports, renderer prop parity, package
  entry points, docs API references, cross-registry integration: all pass
• React/Vue/Angular peer-range scripts: all pass. Before this commit they failed
  with ERESOLVE.
• the react, vue and svelte example apps install and build
• npm pack of all five gives 1.12.0 tarballs, and each adapter declares core ^1.12.0.
  Fresh Vite apps (React 19, Vue 3) were installed from the tarballs only and checked in
  a browser. Every built-in control has a label.dfk-field-label whose for points at
  the control, and the radio group's aria-labelledby resolves. Typing US shows the
  appearWhen field and sets required on the requiredWhen field; FR hides the
  field and drops required again. No page errors.
• installing the react tarball next to core 1.11.0 fails with ERESOLVE, as intended