Behaviour graph: a node canvas replaces the rule list

[sp00ktober]

Phase 2 of the moveset editor: a port's behaviour is a graph of blocks, edited on a node canvas. It replaces [[rule]]. Stacked on #64.

• The manifest:
  • Schema 2 adds [behaviour]: blocks (kind, params, next, play, label, at) and the moves' during links.
  • mhfu_port.behaviour.KINDS is the one schema of a block: the loader, the compiler and the studio all read it.
  • A schema 1 file migrates on load, one chain per old rule.
  • The rule table is compiled at build: one path is one rule, and higher on the canvas is checked first.
  • The Zinogre's migrated graph compiles to its 7 old rules in order, so its moves module is byte-identical.
• The Behaviour dock:
  • Every move is a node, with "while playing" and "then" (after).
  • Blocks come from a right-click palette: events, the base monster's state, conditions, modifiers. Their values are edited on the node.
  • Badges show each path's priority; unfinished chains are dimmed; refused paths get a warning and a finding.
  • Every gesture is one undo step. The old rule form is gone.
• NodeGraphQt 0.6.44:
  • New dependencies:
    • NodeGraphQt itself, through Qt.py, pinned below 2 because 2.x ships stubs that break mypy strict;
    • setuptools on Python 3.12 and later, which supplies the distutils NodeGraphQt imports.
  • The view uses only its public API: signals, the ports' connect_to, and an undo stack that holds nothing.

Tests: 2199 passed in CI's test job on Linux 3.11 and 3.14; 2762 passed with game data on macOS.

🤖 Generated with Claude Code