ReactiveUI-Godot

Runbook for bringing the library up to a newly released Godot version — dump + diff ClassDB between the old and new binaries, classify every added/removed Control class/property/signal, apply the AUTOMATION.md checklist (bundled LSP dump, curated schema, docs versionManifest, CI + verified-on stamps), and verify the full matrix. Use when the user says a new Godot version is out or asks to support/verify one.

The house development methodology for ReactiveUI projects (Godot + Unity + analyzer) — research→develop→test→bughunt→fix→commit→repeat, production-grade only, plus the changelog and version-bump rules every change must follow.

Run the local field-test loop for the Godot native editor (reactive_ui + reactive_ui_editor + bundled analyzer) — the AI prepares, fixes, verifies, and applies; the user tests in a real Godot editor; repeat until the bug is dead.

Create a new .guitkx component for ReactiveUI-Godot — file placement, component/props/hooks/events syntax, children, styling, and what the compiler generates.

The ReactiveUI-Godot release runbook — version bumps, the two-lane changelog system (hand-written library lane vs script-generated tooling lane), Discord notes, verification gates, and the merge→fast-forward→Publish flow. Use when preparing, staging, or publishing a release of any artifact in this repo.