docs+example: package READMEs, vue/angular demo parity, source panels

[vannt-dev]

What

Three gaps found after #31 merged, plus two follow-ups requested while reviewing the deployed demos.

Package READMEs documented none of the v1.4 surface. Grepping each for useDynamicForm, createDynamicFormStore, createWizardState, goNext, DynamicFormDevTools, zodValidator, onBlurField or defaultRenderersMap:

	before	after
core (344 lines)	0	12
react (256 lines)	2 (bare names in a list)	12
vue (242 lines)	0	9
angular (235 lines)	0	9

Anyone reading a package page on npm saw a library two releases out of date. All four also linked a "Demo app" repo that is not where the demos live.

The Vue and Angular demos referenced zero v1.4 features. React had three pages covering everything; the other two had one file each and not a single hit for any new API. Both now have Enterprise and Wizard tabs — useDynamicForm / createDynamicFormStore, extended renderers, blur wiring, DevTools, and the wizard engine.

No way back to the landing page. Once you were in /react you were stuck. All three apps now carry an absolute "← Tất cả demo" link — absolute because the landing page only exists on the deployed site, one level above each app's base path.

Code beside each demo. Every demo now shows its own source in a toggleable panel with a copy button, and it is guaranteed to be the running code rather than a snippet that can drift:

• React: each route splits into a Server Component that reads demo.tsx with fs and a client demo. Static export means the read happens at build time and the text is baked into the HTML. (?raw was tried first — Turbopack compiles it inside a private folder but fails on a real route.)
• Vue: Vite's native ?raw.
• Angular: no equivalent in its builder, so scripts/embed-demo-sources.js generates a module from the real files, wired to prestart/prebuild.

docs/superpowers/ untracked. .gitignore already excluded .superpowers/ as scratch planning docs; the same content under docs/ was tracked and showed up next to the real documentation. Files stay on disk.

Why

The features shipped in #31 were invisible to anyone who did not read the root README — which is most people arriving from npm or the demo site.

How to test

npm run lint && npm run format-check && npm run typecheck
for p in core react vue angular; do npm run test --workspace=@dynamic-field-kit/$p -- --coverage; done
cd example/vue-app && npm install && npm run build      # then the Enterprise / Wizard tabs
cd example/angular-app && npm install && npm run build

---

• Tests unchanged and passing — core 117, react 116, vue 115, angular 74
• Every identifier written into a README was checked against the built dist
• All three example apps build
• No changeset: docs and examples only, no package source changed

One thing worth knowing: '</> Xem code' had to become '‹/› Xem code'. Angular's template parser reads the </ inside an interpolated string as a closing tag and refuses to compile.